Sep 25 11:33:58 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] start
Sep 25 11:33:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 25 11:33:58 node-4 rsyslogd: rsyslogd's groupid changed to 104
Sep 25 11:33:58 node-4 rsyslogd: rsyslogd's userid changed to 101
Sep 25 11:33:58 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 25 11:33:58 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 25 11:33:58 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 25 11:33:58 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 25 11:33:58 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=c432d52a-b697-4095-a059-645eef5c5588 nomdmonddf nomdmonisw
Sep 25 11:33:58 node-4 kernel: [    0.000000] KERNEL supported cpus:
Sep 25 11:33:58 node-4 kernel: [    0.000000]   Intel GenuineIntel
Sep 25 11:33:58 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Sep 25 11:33:58 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Sep 25 11:33:58 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 25 11:33:58 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 25 11:33:58 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 25 11:33:58 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 25 11:33:58 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 25 11:33:58 node-4 kernel: [    0.000000] No AGP bridge found
Sep 25 11:33:58 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 25 11:33:58 node-4 kernel: [    0.000000] MTRR default type: write-back
Sep 25 11:33:58 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 25 11:33:58 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Sep 25 11:33:58 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 25 11:33:58 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 25 11:33:58 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 25 11:33:58 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 25 11:33:58 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 25 11:33:58 node-4 kernel: [    0.000000]   2 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000]   3 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000]   4 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000]   5 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000]   6 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000]   7 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000]   8 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000]   9 disabled
Sep 25 11:33:58 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 25 11:33:58 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 25 11:33:58 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 25 11:33:58 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 25 11:33:58 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 25 11:33:58 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 25 11:33:58 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 25 11:33:58 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 25 11:33:58 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 25 11:33:58 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 25 11:33:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 25 11:33:58 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 25 11:33:58 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 25 11:33:58 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 25 11:33:58 node-4 kernel: [    0.000000] Zone ranges:
Sep 25 11:33:58 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] Movable zone start for each node
Sep 25 11:33:58 node-4 kernel: [    0.000000] Early memory node ranges
Sep 25 11:33:58 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep 25 11:33:58 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 25 11:33:58 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 25 11:33:58 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 25 11:33:58 node-4 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep 25 11:33:58 node-4 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep 25 11:33:58 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 25 11:33:58 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 25 11:33:58 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 25 11:33:58 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 25 11:33:58 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 25 11:33:58 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 25 11:33:58 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 25 11:33:58 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 25 11:33:58 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 25 11:33:58 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 25 11:33:58 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 25 11:33:58 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 25 11:33:58 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 25 11:33:58 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 25 11:33:58 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 25 11:33:58 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 25 11:33:58 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 25 11:33:58 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 25 11:33:58 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 25 11:33:58 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep 25 11:33:58 node-4 kernel: [    0.000000] Policy zone: Normal
Sep 25 11:33:58 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=c432d52a-b697-4095-a059-645eef5c5588 nomdmonddf nomdmonisw
Sep 25 11:33:58 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 25 11:33:58 node-4 kernel: [    0.000000] Checking aperture...
Sep 25 11:33:58 node-4 kernel: [    0.000000] No AGP bridge found
Sep 25 11:33:58 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 25 11:33:58 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 25 11:33:58 node-4 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep 25 11:33:58 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 25 11:33:58 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 25 11:33:58 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 25 11:33:58 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 25 11:33:58 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 25 11:33:58 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 25 11:33:58 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 25 11:33:58 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 25 11:33:58 node-4 kernel: [    0.000000] console [tty0] enabled
Sep 25 11:33:58 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 25 11:33:58 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 25 11:33:58 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 25 11:33:58 node-4 kernel: [    0.000000] hpet clockevent registered
Sep 25 11:33:58 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 25 11:33:58 node-4 kernel: [    0.004000] tsc: Detected 3491.872 MHz processor
Sep 25 11:33:58 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.74 BogoMIPS (lpj=13967488)
Sep 25 11:33:58 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 25 11:33:58 node-4 kernel: [    0.000043] Security Framework initialized
Sep 25 11:33:58 node-4 kernel: [    0.000062] AppArmor: AppArmor initialized
Sep 25 11:33:58 node-4 kernel: [    0.000063] Yama: becoming mindful.
Sep 25 11:33:58 node-4 kernel: [    0.001452] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.006313] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.008241] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.008270] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.008562] Initializing cgroup subsys memory
Sep 25 11:33:58 node-4 kernel: [    0.008570] Initializing cgroup subsys devices
Sep 25 11:33:58 node-4 kernel: [    0.008572] Initializing cgroup subsys freezer
Sep 25 11:33:58 node-4 kernel: [    0.008574] Initializing cgroup subsys blkio
Sep 25 11:33:58 node-4 kernel: [    0.008576] Initializing cgroup subsys perf_event
Sep 25 11:33:58 node-4 kernel: [    0.008578] Initializing cgroup subsys hugetlb
Sep 25 11:33:58 node-4 kernel: [    0.008598] CPU: Physical Processor ID: 0
Sep 25 11:33:58 node-4 kernel: [    0.008599] CPU: Processor Core ID: 0
Sep 25 11:33:58 node-4 kernel: [    0.008603] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 25 11:33:58 node-4 kernel: [    0.008603] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 25 11:33:58 node-4 kernel: [    0.009297] mce: CPU supports 22 MCE banks
Sep 25 11:33:58 node-4 kernel: [    0.009324] CPU0: Thermal monitoring enabled (TM1)
Sep 25 11:33:58 node-4 kernel: [    0.009345] process: using mwait in idle threads
Sep 25 11:33:58 node-4 kernel: [    0.009348] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 25 11:33:58 node-4 kernel: [    0.009348] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 25 11:33:58 node-4 kernel: [    0.009348] tlb_flushall_shift: 6
Sep 25 11:33:58 node-4 kernel: [    0.009437] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 25 11:33:58 node-4 kernel: [    0.010162] ACPI: Core revision 20131115
Sep 25 11:33:58 node-4 kernel: [    0.022839] ACPI: All ACPI Tables successfully acquired
Sep 25 11:33:58 node-4 kernel: [    0.023002] ftrace: allocating 28617 entries in 112 pages
Sep 25 11:33:58 node-4 kernel: [    0.031977] dmar: Host address width 46
Sep 25 11:33:58 node-4 kernel: [    0.031979] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 25 11:33:58 node-4 kernel: [    0.031985] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 25 11:33:58 node-4 kernel: [    0.031987] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 25 11:33:58 node-4 kernel: [    0.031991] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 25 11:33:58 node-4 kernel: [    0.031993] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 25 11:33:58 node-4 kernel: [    0.031994] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 25 11:33:58 node-4 kernel: [    0.031995] dmar: ATSR flags: 0x0
Sep 25 11:33:58 node-4 kernel: [    0.031996] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 25 11:33:58 node-4 kernel: [    0.031997] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 25 11:33:58 node-4 kernel: [    0.032113] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 25 11:33:58 node-4 kernel: [    0.032114] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 25 11:33:58 node-4 kernel: [    0.032115] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 25 11:33:58 node-4 kernel: [    0.032116] HPET id 0 under DRHD base 0xc7ffc000
Sep 25 11:33:58 node-4 kernel: [    0.032117] Your BIOS is broken and requested that x2apic be disabled.
Sep 25 11:33:58 node-4 kernel: [    0.032117] This will slightly decrease performance.
Sep 25 11:33:58 node-4 kernel: [    0.032117] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 25 11:33:58 node-4 kernel: [    0.032548] Enabled IRQ remapping in xapic mode
Sep 25 11:33:58 node-4 kernel: [    0.032549] x2apic not enabled, IRQ remapping is in xapic mode
Sep 25 11:33:58 node-4 kernel: [    0.032553] Switched APIC routing to physical flat.
Sep 25 11:33:58 node-4 kernel: [    0.033130] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 25 11:33:58 node-4 kernel: [    0.072780] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 25 11:33:58 node-4 kernel: [    0.072785] TSC deadline timer enabled
Sep 25 11:33:58 node-4 kernel: [    0.072792] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 25 11:33:58 node-4 kernel: [    0.072798] ... version:                3
Sep 25 11:33:58 node-4 kernel: [    0.072799] ... bit width:              48
Sep 25 11:33:58 node-4 kernel: [    0.072800] ... generic registers:      4
Sep 25 11:33:58 node-4 kernel: [    0.072801] ... value mask:             0000ffffffffffff
Sep 25 11:33:58 node-4 kernel: [    0.072802] ... max period:             0000ffffffffffff
Sep 25 11:33:58 node-4 kernel: [    0.072803] ... fixed-purpose events:   3
Sep 25 11:33:58 node-4 kernel: [    0.072804] ... event mask:             000000070000000f
Sep 25 11:33:58 node-4 kernel: [    0.074207] x86: Booting SMP configuration:
Sep 25 11:33:58 node-4 kernel: [    0.088322] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 25 11:33:58 node-4 kernel: [    0.074209] .... node  #0, CPUs:        #1  #2  #3
Sep 25 11:33:58 node-4 kernel: [    0.116233] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 25 11:33:58 node-4 kernel: [    0.270189] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 25 11:33:58 node-4 kernel: [    0.325802] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 25 11:33:58 node-4 kernel: [    0.382657] x86: Booted up 2 nodes, 16 CPUs
Sep 25 11:33:58 node-4 kernel: [    0.382660] smpboot: Total of 16 processors activated (111752.14 BogoMIPS)
Sep 25 11:33:58 node-4 kernel: [    0.406343] devtmpfs: initialized
Sep 25 11:33:58 node-4 kernel: [    0.409486] EVM: security.selinux
Sep 25 11:33:58 node-4 kernel: [    0.409488] EVM: security.SMACK64
Sep 25 11:33:58 node-4 kernel: [    0.409489] EVM: security.ima
Sep 25 11:33:58 node-4 kernel: [    0.409490] EVM: security.capability
Sep 25 11:33:58 node-4 kernel: [    0.409541] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.410221] pinctrl core: initialized pinctrl subsystem
Sep 25 11:33:58 node-4 kernel: [    0.410281] regulator-dummy: no parameters
Sep 25 11:33:58 node-4 kernel: [    0.410312] RTC time: 11:33:22, date: 09/25/16
Sep 25 11:33:58 node-4 kernel: [    0.410345] NET: Registered protocol family 16
Sep 25 11:33:58 node-4 kernel: [    0.410428] cpuidle: using governor ladder
Sep 25 11:33:58 node-4 kernel: [    0.410430] cpuidle: using governor menu
Sep 25 11:33:58 node-4 kernel: [    0.410464] ACPI: bus type PCI registered
Sep 25 11:33:58 node-4 kernel: [    0.410466] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 25 11:33:58 node-4 kernel: [    0.410511] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 25 11:33:58 node-4 kernel: [    0.410514] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 25 11:33:58 node-4 kernel: [    0.424241] PCI: Using configuration type 1 for base access
Sep 25 11:33:58 node-4 kernel: [    0.425251] bio: create slab <bio-0> at 0
Sep 25 11:33:58 node-4 kernel: [    0.425536] ACPI: Added _OSI(Module Device)
Sep 25 11:33:58 node-4 kernel: [    0.425538] ACPI: Added _OSI(Processor Device)
Sep 25 11:33:58 node-4 kernel: [    0.425539] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 25 11:33:58 node-4 kernel: [    0.425540] ACPI: Added _OSI(Processor Aggregator Device)
Sep 25 11:33:58 node-4 kernel: [    0.438205] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 25 11:33:58 node-4 kernel: [    0.449730] ACPI: Interpreter enabled
Sep 25 11:33:58 node-4 kernel: [    0.449735] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 25 11:33:58 node-4 kernel: [    0.449739] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 25 11:33:58 node-4 kernel: [    0.449742] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 25 11:33:58 node-4 kernel: [    0.449748] ACPI: (supports S0 S4 S5)
Sep 25 11:33:58 node-4 kernel: [    0.449750] ACPI: Using IOAPIC for interrupt routing
Sep 25 11:33:58 node-4 kernel: [    0.449793] HEST: Table parsing has been initialized.
Sep 25 11:33:58 node-4 kernel: [    0.449796] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 25 11:33:58 node-4 kernel: [    0.450349] ACPI: No dock devices found.
Sep 25 11:33:58 node-4 kernel: [    0.462013] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 25 11:33:58 node-4 kernel: [    0.462017] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 25 11:33:58 node-4 kernel: [    0.462020] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 25 11:33:58 node-4 kernel: [    0.462047] PCI host bridge to bus 0000:ff
Sep 25 11:33:58 node-4 kernel: [    0.462049] pci_bus 0000:ff: root bus resource [bus ff]
Sep 25 11:33:58 node-4 kernel: [    0.462057] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462096] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.462127] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462162] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462192] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.462222] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.462254] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462283] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462313] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462341] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462367] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462394] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462422] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462447] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462474] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462500] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462528] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462555] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462582] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.462610] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462636] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.462661] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462687] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462717] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.462751] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462782] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462812] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462843] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462875] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462909] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462941] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.462972] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463004] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463037] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463071] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463104] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463138] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463169] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463197] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463231] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463265] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463304] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463340] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463375] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463406] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463438] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463470] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463501] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463535] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463566] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463598] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463629] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463659] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463689] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463719] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463751] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463783] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463842] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 25 11:33:58 node-4 kernel: [    0.463844] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 25 11:33:58 node-4 kernel: [    0.463847] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 25 11:33:58 node-4 kernel: [    0.463865] PCI host bridge to bus 0000:7f
Sep 25 11:33:58 node-4 kernel: [    0.463867] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 25 11:33:58 node-4 kernel: [    0.463872] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463900] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.463929] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463959] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.463981] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.464006] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.464034] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464059] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464084] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464108] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464132] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464156] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464182] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464206] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464231] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464261] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464282] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464305] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464328] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.464353] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464376] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.464400] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464424] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464452] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 25 11:33:58 node-4 kernel: [    0.464484] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464511] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464539] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464566] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464592] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464618] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464644] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464671] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464697] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464725] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464753] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464780] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464807] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464831] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464856] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464884] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464910] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464938] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464968] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.464995] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465022] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465047] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465075] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465105] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465133] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465161] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465192] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465219] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465242] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465269] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465295] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465325] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.465350] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.466592] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 25 11:33:58 node-4 kernel: [    0.466595] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 25 11:33:58 node-4 kernel: [    0.467719] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 25 11:33:58 node-4 kernel: [    0.468232] PCI host bridge to bus 0000:00
Sep 25 11:33:58 node-4 kernel: [    0.468234] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 25 11:33:58 node-4 kernel: [    0.468236] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 25 11:33:58 node-4 kernel: [    0.468237] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 25 11:33:58 node-4 kernel: [    0.468239] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 25 11:33:58 node-4 kernel: [    0.468240] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 25 11:33:58 node-4 kernel: [    0.468241] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 25 11:33:58 node-4 kernel: [    0.468243] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 25 11:33:58 node-4 kernel: [    0.468248] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 25 11:33:58 node-4 kernel: [    0.468331] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.468362] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.468403] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 25 11:33:58 node-4 kernel: [    0.468423] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.468452] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.468492] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 25 11:33:58 node-4 kernel: [    0.468511] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.468540] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.468583] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 25 11:33:58 node-4 kernel: [    0.468599] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.468669] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.468745] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.468821] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 25 11:33:58 node-4 kernel: [    0.468826] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 25 11:33:58 node-4 kernel: [    0.468910] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 25 11:33:58 node-4 kernel: [    0.469057] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 25 11:33:58 node-4 kernel: [    0.469075] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 25 11:33:58 node-4 kernel: [    0.469152] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.469207] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 25 11:33:58 node-4 kernel: [    0.469228] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.469283] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.469327] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 25 11:33:58 node-4 kernel: [    0.469354] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.469410] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.469453] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 25 11:33:58 node-4 kernel: [    0.469477] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 25 11:33:58 node-4 kernel: [    0.469494] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 25 11:33:58 node-4 kernel: [    0.469572] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.469621] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 25 11:33:58 node-4 kernel: [    0.469647] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 25 11:33:58 node-4 kernel: [    0.469893] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 25 11:33:58 node-4 kernel: [    0.469899] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 25 11:33:58 node-4 kernel: [    0.469905] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.469911] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.469918] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 25 11:33:58 node-4 kernel: [    0.469949] pci 0000:01:00.0: supports D1 D2
Sep 25 11:33:58 node-4 kernel: [    0.476033] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 25 11:33:58 node-4 kernel: [    0.476039] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 25 11:33:58 node-4 kernel: [    0.476044] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 25 11:33:58 node-4 kernel: [    0.476175] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.476209] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 25 11:33:58 node-4 kernel: [    0.484030] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 25 11:33:58 node-4 kernel: [    0.484036] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.484040] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 25 11:33:58 node-4 kernel: [    0.484134] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.484201] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.484282] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.484326] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 25 11:33:58 node-4 kernel: [    0.484329] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.484331] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 25 11:33:58 node-4 kernel: [    0.484383] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.484506] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.484559] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 25 11:33:58 node-4 kernel: [    0.484561] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.484564] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.484612] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.484733] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.484773] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.484891] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.484929] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.485070] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.485107] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 25 11:33:58 node-4 kernel: [    0.485229] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 25 11:33:58 node-4 kernel: [    0.485271] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 25 11:33:58 node-4 kernel: [    0.485274] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.485276] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.485334] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 25 11:33:58 node-4 kernel: [    0.485397] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.485449] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.485490] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 25 11:33:58 node-4 kernel: [    0.485572] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 25 11:33:58 node-4 kernel: [    0.485677] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 25 11:33:58 node-4 kernel: [    0.485680] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.485682] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.485738] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 25 11:33:58 node-4 kernel: [    0.485791] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.485840] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.486074] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 25 11:33:58 node-4 kernel: [    0.486078] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 25 11:33:58 node-4 kernel: [    0.486140] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 25 11:33:58 node-4 kernel: [    0.486197] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.486245] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.486458] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 25 11:33:58 node-4 kernel: [    0.486461] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 25 11:33:58 node-4 kernel: [    0.486520] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 25 11:33:58 node-4 kernel: [    0.486580] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.486632] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 25 11:33:58 node-4 kernel: [    0.486852] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 25 11:33:58 node-4 kernel: [    0.486856] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 25 11:33:58 node-4 kernel: [    0.487029] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 25 11:33:58 node-4 kernel: [    0.487067] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 25 11:33:58 node-4 kernel: [    0.487141] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 25 11:33:58 node-4 kernel: [    0.487160] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 25 11:33:58 node-4 kernel: [    0.487173] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 25 11:33:58 node-4 kernel: [    0.487187] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 25 11:33:58 node-4 kernel: [    0.487237] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 25 11:33:58 node-4 kernel: [    0.492035] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 25 11:33:58 node-4 kernel: [    0.492044] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 25 11:33:58 node-4 kernel: [    0.492097] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 25 11:33:58 node-4 kernel: [    0.492767] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 25 11:33:58 node-4 kernel: [    0.492770] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 25 11:33:58 node-4 kernel: [    0.492893] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 25 11:33:58 node-4 kernel: [    0.492998] PCI host bridge to bus 0000:80
Sep 25 11:33:58 node-4 kernel: [    0.493000] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 25 11:33:58 node-4 kernel: [    0.493002] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 25 11:33:58 node-4 kernel: [    0.493003] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 25 11:33:58 node-4 kernel: [    0.493011] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.493074] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.493142] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 25 11:33:58 node-4 kernel: [    0.493204] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 25 11:33:58 node-4 kernel: [    0.493209] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 25 11:33:58 node-4 kernel: [    0.493282] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 25 11:33:58 node-4 kernel: [    0.493582] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 25 11:33:58 node-4 kernel: [    0.493614] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 25 11:33:58 node-4 kernel: [    0.493644] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 25 11:33:58 node-4 kernel: [    0.493673] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 25 11:33:58 node-4 kernel: [    0.493702] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 25 11:33:58 node-4 kernel: [    0.493732] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 25 11:33:58 node-4 kernel: [    0.493762] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 25 11:33:58 node-4 kernel: [    0.493792] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 25 11:33:58 node-4 kernel: [    0.493876] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 25 11:33:58 node-4 kernel: [    0.493880] ACPI: \_SB_.UNC1: notify handler is installed
Sep 25 11:33:58 node-4 kernel: [    0.493882] ACPI: \_SB_.UNC0: notify handler is installed
Sep 25 11:33:58 node-4 kernel: [    0.493897] ACPI: \_SB_.PCI0: notify handler is installed
Sep 25 11:33:58 node-4 kernel: [    0.493949] ACPI: \_SB_.PCI1: notify handler is installed
Sep 25 11:33:58 node-4 kernel: [    0.494028] Found 4 acpi root devices
Sep 25 11:33:58 node-4 kernel: [    0.494143] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 25 11:33:58 node-4 kernel: [    0.494145] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 25 11:33:58 node-4 kernel: [    0.494146] vgaarb: loaded
Sep 25 11:33:58 node-4 kernel: [    0.494147] vgaarb: bridge control possible 0000:0c:00.0
Sep 25 11:33:58 node-4 kernel: [    0.494260] SCSI subsystem initialized
Sep 25 11:33:58 node-4 kernel: [    0.494323] libata version 3.00 loaded.
Sep 25 11:33:58 node-4 kernel: [    0.494338] ACPI: bus type USB registered
Sep 25 11:33:58 node-4 kernel: [    0.494349] usbcore: registered new interface driver usbfs
Sep 25 11:33:58 node-4 kernel: [    0.494354] usbcore: registered new interface driver hub
Sep 25 11:33:58 node-4 kernel: [    0.494374] usbcore: registered new device driver usb
Sep 25 11:33:58 node-4 kernel: [    0.494531] PCI: Using ACPI for IRQ routing
Sep 25 11:33:58 node-4 kernel: [    0.498137] PCI: pci_cache_line_size set to 64 bytes
Sep 25 11:33:58 node-4 kernel: [    0.498338] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 25 11:33:58 node-4 kernel: [    0.498339] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep 25 11:33:58 node-4 kernel: [    0.498340] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 25 11:33:58 node-4 kernel: [    0.498407] NetLabel: Initializing
Sep 25 11:33:58 node-4 kernel: [    0.498408] NetLabel:  domain hash size = 128
Sep 25 11:33:58 node-4 kernel: [    0.498409] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 25 11:33:58 node-4 kernel: [    0.498418] NetLabel:  unlabeled traffic allowed by default
Sep 25 11:33:58 node-4 kernel: [    0.498476] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 25 11:33:58 node-4 kernel: [    0.498480] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 25 11:33:58 node-4 kernel: [    0.500538] Switched to clocksource hpet
Sep 25 11:33:58 node-4 kernel: [    0.504273] AppArmor: AppArmor Filesystem Enabled
Sep 25 11:33:58 node-4 kernel: [    0.504287] pnp: PnP ACPI init
Sep 25 11:33:58 node-4 kernel: [    0.504295] ACPI: bus type PNP registered
Sep 25 11:33:58 node-4 kernel: [    0.504404] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504412] pnp 00:01: [dma 4]
Sep 25 11:33:58 node-4 kernel: [    0.504424] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504450] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504469] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504497] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504536] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504588] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504590] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 25 11:33:58 node-4 kernel: [    0.504592] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504593] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504595] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504599] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504601] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 25 11:33:58 node-4 kernel: [    0.504603] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504604] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504606] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504607] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504609] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504610] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 25 11:33:58 node-4 kernel: [    0.504612] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504696] pnp 00:07: [dma 0 disabled]
Sep 25 11:33:58 node-4 kernel: [    0.504724] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504798] pnp 00:08: [dma 0 disabled]
Sep 25 11:33:58 node-4 kernel: [    0.504830] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 25 11:33:58 node-4 kernel: [    0.504880] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 25 11:33:58 node-4 kernel: [    0.505229] pnp: PnP ACPI: found 10 devices
Sep 25 11:33:58 node-4 kernel: [    0.505231] ACPI: bus type PNP unregistered
Sep 25 11:33:58 node-4 kernel: [    0.511496] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 25 11:33:58 node-4 kernel: [    0.511499] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 25 11:33:58 node-4 kernel: [    0.511502] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 25 11:33:58 node-4 kernel: [    0.511506] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 25 11:33:58 node-4 kernel: [    0.511508] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511522] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511551] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 25 11:33:58 node-4 kernel: [    0.511566] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511595] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 25 11:33:58 node-4 kernel: [    0.511609] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 25 11:33:58 node-4 kernel: [    0.511638] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 25 11:33:58 node-4 kernel: [    0.511652] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 25 11:33:58 node-4 kernel: [    0.511681] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 25 11:33:58 node-4 kernel: [    0.511683] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511698] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511726] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 25 11:33:58 node-4 kernel: [    0.511728] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511745] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511774] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 25 11:33:58 node-4 kernel: [    0.511776] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511779] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511783] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 25 11:33:58 node-4 kernel: [    0.511784] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511787] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511790] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 25 11:33:58 node-4 kernel: [    0.511795] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 25 11:33:58 node-4 kernel: [    0.511803] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 25 11:33:58 node-4 kernel: [    0.511807] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 25 11:33:58 node-4 kernel: [    0.511813] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 25 11:33:58 node-4 kernel: [    0.511814] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 25 11:33:58 node-4 kernel: [    0.511815] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 25 11:33:58 node-4 kernel: [    0.511816] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 25 11:33:58 node-4 kernel: [    0.511816] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 25 11:33:58 node-4 kernel: [    0.511817] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 25 11:33:58 node-4 kernel: [    0.511818] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 25 11:33:58 node-4 kernel: [    0.511819] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 25 11:33:58 node-4 kernel: [    0.511820] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511821] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511822] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511823] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511823] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511824] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511825] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511826] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511827] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 25 11:33:58 node-4 kernel: [    0.511828] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511829] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 25 11:33:58 node-4 kernel: [    0.511830] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 25 11:33:58 node-4 kernel: [    0.511831] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 25 11:33:58 node-4 kernel: [    0.511832] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 25 11:33:58 node-4 kernel: [    0.511834] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 25 11:33:58 node-4 kernel: [    0.511835] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 25 11:33:58 node-4 kernel: [    0.511874] NET: Registered protocol family 2
Sep 25 11:33:58 node-4 kernel: [    0.512130] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.512455] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.512610] TCP: Hash tables configured (established 262144 bind 65536)
Sep 25 11:33:58 node-4 kernel: [    0.512652] TCP: reno registered
Sep 25 11:33:58 node-4 kernel: [    0.512681] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.512777] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.512922] NET: Registered protocol family 1
Sep 25 11:33:58 node-4 kernel: [    0.548572] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 25 11:33:58 node-4 kernel: [    0.548579] PCI: CLS 64 bytes, default 64
Sep 25 11:33:58 node-4 kernel: [    0.548620] Trying to unpack rootfs image as initramfs...
Sep 25 11:33:58 node-4 kernel: [    0.769077] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep 25 11:33:58 node-4 kernel: [    0.769113] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 25 11:33:58 node-4 kernel: [    0.769116] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep 25 11:33:58 node-4 kernel: [    0.769550] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769557] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769562] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769567] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769592] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769603] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769612] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769620] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769628] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769638] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769644] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769650] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769657] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769664] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769672] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769679] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 25 11:33:58 node-4 kernel: [    0.769719] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 25 11:33:58 node-4 kernel: [    0.769723] Scanning for low memory corruption every 60 seconds
Sep 25 11:33:58 node-4 kernel: [    0.770018] Initialise system trusted keyring
Sep 25 11:33:58 node-4 kernel: [    0.770066] audit: initializing netlink socket (disabled)
Sep 25 11:33:58 node-4 kernel: [    0.770076] type=2000 audit(1474803201.724:1): initialized
Sep 25 11:33:58 node-4 kernel: [    0.787882] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 25 11:33:58 node-4 kernel: [    0.789424] zbud: loaded
Sep 25 11:33:58 node-4 kernel: [    0.789536] VFS: Disk quotas dquot_6.5.2
Sep 25 11:33:58 node-4 kernel: [    0.789577] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 25 11:33:58 node-4 kernel: [    0.789956] fuse init (API version 7.22)
Sep 25 11:33:58 node-4 kernel: [    0.790013] msgmni has been set to 32768
Sep 25 11:33:58 node-4 kernel: [    0.790058] Key type big_key registered
Sep 25 11:33:58 node-4 kernel: [    0.790575] Key type asymmetric registered
Sep 25 11:33:58 node-4 kernel: [    0.790576] Asymmetric key parser 'x509' registered
Sep 25 11:33:58 node-4 kernel: [    0.790598] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 25 11:33:58 node-4 kernel: [    0.790668] io scheduler noop registered
Sep 25 11:33:58 node-4 kernel: [    0.790669] io scheduler deadline registered (default)
Sep 25 11:33:58 node-4 kernel: [    0.790687] io scheduler cfq registered
Sep 25 11:33:58 node-4 kernel: [    0.791001] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    0.791091] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    0.791177] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    0.791263] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    0.791356] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    0.791423] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    0.791680] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 25 11:33:58 node-4 kernel: [    0.791698] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 25 11:33:58 node-4 kernel: [    0.791710] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 25 11:33:58 node-4 kernel: [    0.791720] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791722] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791724] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 25 11:33:58 node-4 kernel: [    0.791728] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791729] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791730] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791732] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791733] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791735] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791736] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791737] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791739] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791740] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791741] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791743] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791745] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 25 11:33:58 node-4 kernel: [    0.791749] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791751] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 25 11:33:58 node-4 kernel: [    0.791759] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791762] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 25 11:33:58 node-4 kernel: [    0.791771] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791773] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 25 11:33:58 node-4 kernel: [    0.791776] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 25 11:33:58 node-4 kernel: [    0.791788] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 25 11:33:58 node-4 kernel: [    0.791879] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 25 11:33:58 node-4 kernel: [    0.791883] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 25 11:33:58 node-4 kernel: [    0.791891] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 25 11:33:58 node-4 kernel: [    0.791927] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 25 11:33:58 node-4 kernel: [    0.791928] vesafb: scrolling: redraw
Sep 25 11:33:58 node-4 kernel: [    0.791930] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 25 11:33:58 node-4 kernel: [    0.812689] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 25 11:33:58 node-4 kernel: [    0.821213] Console: switching to colour frame buffer device 80x30
Sep 25 11:33:58 node-4 kernel: [    0.829891] fb0: VESA VGA frame buffer device
Sep 25 11:33:58 node-4 kernel: [    0.830089] intel_idle: MWAIT substates: 0x2120
Sep 25 11:33:58 node-4 kernel: [    0.830090] intel_idle: v0.4 model 0x3F
Sep 25 11:33:58 node-4 kernel: [    0.830091] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 25 11:33:58 node-4 kernel: [    0.830322] ipmi message handler version 39.2
Sep 25 11:33:58 node-4 kernel: [    0.830583] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 25 11:33:58 node-4 kernel: [    0.831014] ACPI: AC Adapter [P111] (on-line)
Sep 25 11:33:58 node-4 kernel: [    0.836241] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 25 11:33:58 node-4 kernel: [    0.847265] ACPI: Power Button [PWRB]
Sep 25 11:33:58 node-4 kernel: [    0.853043] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 25 11:33:58 node-4 kernel: [    0.864705] ACPI: Power Button [PWRF]
Sep 25 11:33:58 node-4 kernel: [    0.890162] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 25 11:33:58 node-4 kernel: [    0.901849] pstore: Registered erst as persistent store backend
Sep 25 11:33:58 node-4 kernel: [    0.908057] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 25 11:33:58 node-4 kernel: [    0.920038] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 25 11:33:58 node-4 kernel: [    0.946816] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 25 11:33:58 node-4 kernel: [    0.980138] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 25 11:33:58 node-4 kernel: [    0.994240] Linux agpgart interface v0.103
Sep 25 11:33:58 node-4 kernel: [    1.001877] brd: module loaded
Sep 25 11:33:58 node-4 kernel: [    1.008949] loop: module loaded
Sep 25 11:33:58 node-4 kernel: [    1.015725] libphy: Fixed MDIO Bus: probed
Sep 25 11:33:58 node-4 kernel: [    1.022248] tun: Universal TUN/TAP device driver, 1.6
Sep 25 11:33:58 node-4 kernel: [    1.028765] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 25 11:33:58 node-4 kernel: [    1.035334] PPP generic driver version 2.4.2
Sep 25 11:33:58 node-4 kernel: [    1.041761] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 25 11:33:58 node-4 kernel: [    1.048247] ehci-pci: EHCI PCI platform driver
Sep 25 11:33:58 node-4 kernel: [    1.054864] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 25 11:33:58 node-4 kernel: [    1.061342] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 25 11:33:58 node-4 kernel: [    1.074071] ehci-pci 0000:00:1a.0: debug port 2
Sep 25 11:33:58 node-4 kernel: [    1.084352] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 25 11:33:58 node-4 kernel: [    1.084369] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 25 11:33:58 node-4 kernel: [    1.100034] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 25 11:33:58 node-4 kernel: [    1.106121] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 25 11:33:58 node-4 kernel: [    1.112295] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 25 11:33:58 node-4 kernel: [    1.124229] usb usb1: Product: EHCI Host Controller
Sep 25 11:33:58 node-4 kernel: [    1.130265] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 25 11:33:58 node-4 kernel: [    1.136331] usb usb1: SerialNumber: 0000:00:1a.0
Sep 25 11:33:58 node-4 kernel: [    1.142276] hub 1-0:1.0: USB hub found
Sep 25 11:33:58 node-4 kernel: [    1.148056] hub 1-0:1.0: 2 ports detected
Sep 25 11:33:58 node-4 kernel: [    1.153841] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 25 11:33:58 node-4 kernel: [    1.159444] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 25 11:33:58 node-4 kernel: [    1.170359] ehci-pci 0000:00:1d.0: debug port 2
Sep 25 11:33:58 node-4 kernel: [    1.179668] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 25 11:33:58 node-4 kernel: [    1.179671] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 25 11:33:58 node-4 kernel: [    1.195953] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 25 11:33:58 node-4 kernel: [    1.201164] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 25 11:33:58 node-4 kernel: [    1.206477] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 25 11:33:58 node-4 kernel: [    1.217114] usb usb2: Product: EHCI Host Controller
Sep 25 11:33:58 node-4 kernel: [    1.222646] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 25 11:33:58 node-4 kernel: [    1.228204] usb usb2: SerialNumber: 0000:00:1d.0
Sep 25 11:33:58 node-4 kernel: [    1.233726] hub 2-0:1.0: USB hub found
Sep 25 11:33:58 node-4 kernel: [    1.239088] hub 2-0:1.0: 2 ports detected
Sep 25 11:33:58 node-4 kernel: [    1.244380] ehci-platform: EHCI generic platform driver
Sep 25 11:33:58 node-4 kernel: [    1.249614] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 25 11:33:58 node-4 kernel: [    1.254924] ohci-pci: OHCI PCI platform driver
Sep 25 11:33:58 node-4 kernel: [    1.260219] ohci-platform: OHCI generic platform driver
Sep 25 11:33:58 node-4 kernel: [    1.265418] uhci_hcd: USB Universal Host Controller Interface driver
Sep 25 11:33:58 node-4 kernel: [    1.270759] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 25 11:33:58 node-4 kernel: [    1.463731] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 25 11:33:58 node-4 kernel: [    1.627956] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 25 11:33:58 node-4 kernel: [    1.633477] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 25 11:33:58 node-4 kernel: [    1.639220] hub 1-1:1.0: USB hub found
Sep 25 11:33:58 node-4 kernel: [    1.644693] hub 1-1:1.0: 6 ports detected
Sep 25 11:33:58 node-4 kernel: [    1.759473] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 25 11:33:58 node-4 kernel: [    1.767480] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 25 11:33:58 node-4 kernel: [    2.027618] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 25 11:33:58 node-4 kernel: [    2.033152] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 25 11:33:58 node-4 kernel: [    2.039010] hub 2-1:1.0: USB hub found
Sep 25 11:33:58 node-4 kernel: [    2.044730] hub 2-1:1.0: 8 ports detected
Sep 25 11:33:58 node-4 kernel: [    2.311987] i8042: No controller found
Sep 25 11:33:58 node-4 kernel: [    2.317388] mousedev: PS/2 mouse device common for all mice
Sep 25 11:33:58 node-4 kernel: [    2.322876] rtc_cmos 00:02: RTC can wake from S4
Sep 25 11:33:58 node-4 kernel: [    2.323109] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 25 11:33:58 node-4 kernel: [    2.334103] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 25 11:33:58 node-4 kernel: [    2.339749] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 25 11:33:58 node-4 kernel: [    2.350901] device-mapper: uevent: version 1.0.3
Sep 25 11:33:58 node-4 kernel: [    2.356537] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 25 11:33:58 node-4 kernel: [    2.367824] ledtrig-cpu: registered to indicate activity on CPUs
Sep 25 11:33:58 node-4 kernel: [    2.373777] TCP: cubic registered
Sep 25 11:33:58 node-4 kernel: [    2.379697] NET: Registered protocol family 10
Sep 25 11:33:58 node-4 kernel: [    2.385696] NET: Registered protocol family 17
Sep 25 11:33:58 node-4 kernel: [    2.391390] Key type dns_resolver registered
Sep 25 11:33:58 node-4 kernel: [    2.397362] Loading compiled-in X.509 certificates
Sep 25 11:33:58 node-4 kernel: [    2.403572] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 25 11:33:58 node-4 kernel: [    2.415005] registered taskstats version 1
Sep 25 11:33:58 node-4 kernel: [    2.423004] Key type trusted registered
Sep 25 11:33:58 node-4 kernel: [    2.430652] Key type encrypted registered
Sep 25 11:33:58 node-4 kernel: [    2.436120] AppArmor: AppArmor sha1 policy hashing enabled
Sep 25 11:33:58 node-4 kernel: [    2.441619] IMA: No TPM chip found, activating TPM-bypass!
Sep 25 11:33:58 node-4 kernel: [    2.447786] regulator-dummy: disabling
Sep 25 11:33:58 node-4 kernel: [    2.453376]   Magic number: 0:94:581
Sep 25 11:33:58 node-4 kernel: [    2.458818] pci_bus 0000:02: hash matches
Sep 25 11:33:58 node-4 kernel: [    2.463947] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 25 11:33:58 node-4 kernel: [    2.463948] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 25 11:33:58 node-4 kernel: [    2.463949] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 25 11:33:58 node-4 kernel: [    2.463950] usb 2-1.4: Manufacturer: Avocent
Sep 25 11:33:58 node-4 kernel: [    2.463950] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 25 11:33:58 node-4 kernel: [    2.497160] pci 0000:ff:12.0: hash matches
Sep 25 11:33:58 node-4 kernel: [    2.502588] acpi device:12c: hash matches
Sep 25 11:33:58 node-4 kernel: [    2.508159] rtc_cmos 00:02: setting system clock to 2016-09-25 11:33:24 UTC (1474803204)
Sep 25 11:33:58 node-4 kernel: [    2.520335] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 25 11:33:58 node-4 kernel: [    2.525845] EDD information not available.
Sep 25 11:33:58 node-4 kernel: [    2.531290] PM: Hibernation image not present or could not be loaded.
Sep 25 11:33:58 node-4 kernel: [    2.532147] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 25 11:33:58 node-4 kernel: [    2.542932] Write protecting the kernel read-only data: 12288k
Sep 25 11:33:58 node-4 kernel: [    2.548915] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 25 11:33:58 node-4 kernel: [    2.561331] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 25 11:33:58 node-4 kernel: [    2.593017] device-mapper: multipath: version 1.6.0 loaded
Sep 25 11:33:58 node-4 kernel: [    2.600862] systemd-udevd[217]: starting version 204
Sep 25 11:33:58 node-4 kernel: [    2.622120] md: linear personality registered for level -1
Sep 25 11:33:58 node-4 kernel: [    2.636744] md: multipath personality registered for level -4
Sep 25 11:33:58 node-4 kernel: [    2.644751] md: raid0 personality registered for level 0
Sep 25 11:33:58 node-4 kernel: [    2.653272] md: raid1 personality registered for level 1
Sep 25 11:33:58 node-4 kernel: [    2.661990] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 25 11:33:58 node-4 kernel: [    2.668336] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 25 11:33:58 node-4 kernel: [    2.668538] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 25 11:33:58 node-4 kernel: [    2.680926] hidraw: raw HID events driver (C) Jiri Kosina
Sep 25 11:33:58 node-4 kernel: [    2.681424] megasas: FW now in Ready state
Sep 25 11:33:58 node-4 kernel: [    2.681531] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep 25 11:33:58 node-4 kernel: [    2.681533] 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 25 11:33:58 node-4 kernel: [    2.681535] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 25 11:33:58 node-4 kernel: [    2.681571] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681602] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681609] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681679] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681708] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681722] enic 0000:06:00.0: irq 101 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681742] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681758] enic 0000:06:00.0: irq 103 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681788] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681826] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681837] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681852] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681892] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.681943] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682054] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682075] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682112] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682145] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682187] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682222] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682257] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.682461] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 25 11:33:58 node-4 kernel: [    2.694045] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep 25 11:33:58 node-4 kernel: [    2.694047] 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 25 11:33:58 node-4 kernel: [    2.694048] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 25 11:33:58 node-4 kernel: [    2.694118] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.694177] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.694212] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.694251] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.694291] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.694323] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.694464] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.706870] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep 25 11:33:58 node-4 kernel: [    2.706886] 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 25 11:33:58 node-4 kernel: [    2.706887] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 25 11:33:58 node-4 kernel: [    2.707011] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.707047] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.707117] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.707173] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.707320] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.715159] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep 25 11:33:58 node-4 kernel: [    2.715160] 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 25 11:33:58 node-4 kernel: [    2.715161] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 25 11:33:58 node-4 kernel: [    2.715273] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.715322] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.715404] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.715451] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.715571] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 25 11:33:58 node-4 kernel: [    2.726792] raid6: sse2x1    3625 MB/s
Sep 25 11:33:58 node-4 kernel: [    2.794872] raid6: sse2x2     772 MB/s
Sep 25 11:33:58 node-4 kernel: [    2.862868] raid6: sse2x4    1651 MB/s
Sep 25 11:33:58 node-4 kernel: [    2.930495] raid6: avx2x1    4263 MB/s
Sep 25 11:33:58 node-4 kernel: [    3.002437] raid6: avx2x2   18913 MB/s
Sep 25 11:33:58 node-4 kernel: [    3.074374] raid6: avx2x4   21332 MB/s
Sep 25 11:33:58 node-4 kernel: [    3.080430] raid6: using algorithm avx2x4 (21332 MB/s)
Sep 25 11:33:58 node-4 kernel: [    3.086434] raid6: using avx2x2 recovery algorithm
Sep 25 11:33:58 node-4 kernel: [    3.092315] Switched to clocksource tsc
Sep 25 11:33:58 node-4 kernel: [    3.092318] megasas:IOC Init cmd success
Sep 25 11:33:58 node-4 kernel: [    3.104692] xor: automatically using best checksumming function:
Sep 25 11:33:58 node-4 kernel: [    3.107285] usbcore: registered new interface driver usbhid
Sep 25 11:33:58 node-4 kernel: [    3.107286] usbhid: USB HID core driver
Sep 25 11:33:58 node-4 kernel: [    3.121797] 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 25 11:33:58 node-4 kernel: [    3.122669] megasas: INIT adapter done
Sep 25 11:33:58 node-4 kernel: [    3.138438] 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 25 11:33:58 node-4 kernel: [    3.149543] 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 25 11:33:58 node-4 kernel: [    3.158466]    avx       : 35717.000 MB/sec
Sep 25 11:33:58 node-4 kernel: [    3.166218] 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 25 11:33:58 node-4 kernel: [    3.177684] 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 25 11:33:58 node-4 kernel: [    3.189169] async_tx: api initialized (async)
Sep 25 11:33:58 node-4 kernel: [    3.189486] 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 25 11:33:58 node-4 kernel: [    3.194301] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 25 11:33:58 node-4 kernel: [    3.194758] scsi0 : LSI SAS based MegaRAID driver
Sep 25 11:33:58 node-4 kernel: [    3.201783] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 25 11:33:58 node-4 kernel: [    3.213159] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 25 11:33:58 node-4 kernel: [    3.217359] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 25 11:33:58 node-4 kernel: [    3.217673] sd 0:2:0:0: [sda] Write Protect is off
Sep 25 11:33:58 node-4 kernel: [    3.217674] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 25 11:33:58 node-4 kernel: [    3.217745] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 25 11:33:58 node-4 kernel: [    3.217931] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 25 11:33:58 node-4 kernel: [    3.244243]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 25 11:33:58 node-4 kernel: [    3.246646] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 25 11:33:58 node-4 kernel: [    3.302987] md: raid6 personality registered for level 6
Sep 25 11:33:58 node-4 kernel: [    3.310167] md: raid5 personality registered for level 5
Sep 25 11:33:58 node-4 kernel: [    3.317097] md: raid4 personality registered for level 4
Sep 25 11:33:58 node-4 kernel: [    3.326810] md: raid10 personality registered for level 10
Sep 25 11:33:58 node-4 kernel: [    3.379671] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Sep 25 11:33:58 node-4 kernel: [    3.486266] random: lvm urandom read with 31 bits of entropy available
Sep 25 11:33:58 node-4 kernel: [    3.772114] bio: create slab <bio-1> at 1
Sep 25 11:33:58 node-4 kernel: [    4.520077] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 25 11:33:58 node-4 kernel: [    5.233307] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 25 11:33:58 node-4 kernel: [    5.256741] random: nonblocking pool is initialized
Sep 25 11:33:58 node-4 kernel: [    5.266252] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 25 11:33:58 node-4 kernel: [    5.374285] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 25 11:33:58 node-4 kernel: [    5.410248] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 25 11:33:58 node-4 kernel: [    5.497298] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 25 11:33:58 node-4 kernel: [    5.630598] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 25 11:33:58 node-4 kernel: [    5.663479] XFS (dm-0): Mounting Filesystem
Sep 25 11:33:58 node-4 kernel: [    5.873197] XFS (dm-0): Ending clean mount
Sep 25 11:33:58 node-4 kernel: [    5.976397] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 25 11:33:58 node-4 kernel: [    6.010540] XFS (dm-1): Mounting Filesystem
Sep 25 11:33:58 node-4 kernel: [    6.098819] XFS (dm-1): Ending clean mount
Sep 25 11:33:58 node-4 kernel: [    8.038064] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 25 11:33:58 node-4 kernel: [    8.051670] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 25 11:33:58 node-4 kernel: [    8.201467] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 25 11:33:58 node-4 kernel: [    8.201474] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 25 11:33:58 node-4 kernel: [    8.201479] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 25 11:33:58 node-4 kernel: [    8.201484] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 25 11:33:58 node-4 kernel: [    8.237443] systemd-udevd[774]: starting version 204
Sep 25 11:33:58 node-4 kernel: [    8.399443] power_meter ACPI000D:00: Found ACPI power meter.
Sep 25 11:33:58 node-4 kernel: [    8.399463] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 25 11:33:58 node-4 kernel: [    8.426968] IPMI System Interface driver.
Sep 25 11:33:58 node-4 kernel: [    8.427012] ipmi_si: probing via ACPI
Sep 25 11:33:58 node-4 kernel: [    8.427031] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 25 11:33:58 node-4 kernel: [    8.427032] ipmi_si: Adding ACPI-specified kcs state machine
Sep 25 11:33:58 node-4 kernel: [    8.427040] ipmi_si: probing via SMBIOS
Sep 25 11:33:58 node-4 kernel: [    8.427041] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 25 11:33:58 node-4 kernel: [    8.427042] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 25 11:33:58 node-4 kernel: [    8.427044] ipmi_si: probing via SPMI
Sep 25 11:33:58 node-4 kernel: [    8.427045] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 25 11:33:58 node-4 kernel: [    8.427045] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 25 11:33:58 node-4 kernel: [    8.427046] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 25 11:33:58 node-4 kernel: [    8.438478] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 25 11:33:58 node-4 kernel: [    8.438483] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 25 11:33:58 node-4 kernel: [    8.438486] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 25 11:33:58 node-4 kernel: [    8.438487] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 25 11:33:58 node-4 kernel: [    8.438549] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 25 11:33:58 node-4 kernel: [    8.441502] wmi: Mapper loaded
Sep 25 11:33:58 node-4 kernel: [    8.459345] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 25 11:33:58 node-4 kernel: [    8.498511] systemd-udevd[802]: renamed network interface eth1 to enp7s0
Sep 25 11:33:58 node-4 kernel: [    8.514101] systemd-udevd[791]: renamed network interface eth0 to enp6s0
Sep 25 11:33:58 node-4 kernel: [    8.561834] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Sep 25 11:33:58 node-4 kernel: [    8.577040] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 25 11:33:58 node-4 kernel: [    8.577045] ipmi_si 00:09: IPMI kcs interface initialized
Sep 25 11:33:58 node-4 kernel: [    8.586731] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Sep 25 11:33:58 node-4 kernel: [    8.876292] type=1400 audit(1474803210.870:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.876537] type=1400 audit(1474803210.870:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1048 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.876748] type=1400 audit(1474803210.870:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1048 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.877094] type=1400 audit(1474803210.870:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1000 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.877240] type=1400 audit(1474803210.870:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1000 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.877362] type=1400 audit(1474803210.870:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1000 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.879244] type=1400 audit(1474803210.874:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1008 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.879385] type=1400 audit(1474803210.874:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1008 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.879504] type=1400 audit(1474803210.874:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1008 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    8.884127] type=1400 audit(1474803210.878:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1026 comm="apparmor_parser"
Sep 25 11:33:58 node-4 kernel: [    9.527817] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 25 11:33:58 node-4 kernel: [    9.528604] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 25 11:33:58 node-4 kernel: [    9.729172] enic 0000:06:00.0 enp6s0: Link UP
Sep 25 11:33:58 node-4 kernel: [    9.729620] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 25 11:33:58 node-4 kernel: [    9.729631] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 25 11:33:58 node-4 kernel: [   18.975462] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 25 11:33:59 node-4 failsafe: Failsafe of 120 seconds reached.
Sep 25 11:33:59 node-4 kernel: [   37.777363] init: failsafe main process (8413) killed by TERM signal
Sep 25 11:34:00 node-4 dbus[8459]: [system] AppArmor D-Bus mediation is enabled
Sep 25 11:34:00 node-4 kernel: [   38.048138] audit_printk_skb: 30 callbacks suppressed
Sep 25 11:34:00 node-4 kernel: [   38.048140] type=1400 audit(1474803240.138:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8540 comm="apparmor_parser"
Sep 25 11:34:00 node-4 kernel: [   38.067069] type=1400 audit(1474803240.158:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8539 comm="apparmor_parser"
Sep 25 11:34:00 node-4 kernel: [   38.067075] type=1400 audit(1474803240.158:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8539 comm="apparmor_parser"
Sep 25 11:34:00 node-4 kernel: [   38.067078] type=1400 audit(1474803240.158:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Sep 25 11:34:00 node-4 kernel: [   38.067301] type=1400 audit(1474803240.158:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8539 comm="apparmor_parser"
Sep 25 11:34:00 node-4 kernel: [   38.067303] type=1400 audit(1474803240.158:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Sep 25 11:34:00 node-4 kernel: [   38.067418] type=1400 audit(1474803240.158:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Sep 25 11:34:00 node-4 kernel: [   38.117251] type=1400 audit(1474803240.210:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8542 comm="apparmor_parser"
Sep 25 11:34:00 node-4 anacron[8606]: Anacron 2.3 started on 2016-09-25
Sep 25 11:34:00 node-4 anacron[8606]: Will run job `cron.daily' in 5 min.
Sep 25 11:34:00 node-4 anacron[8606]: Will run job `cron.weekly' in 10 min.
Sep 25 11:34:00 node-4 anacron[8606]: Will run job `cron.monthly' in 15 min.
Sep 25 11:34:00 node-4 anacron[8606]: Jobs will be executed sequentially
Sep 25 11:34:00 node-4 cron[8572]: (CRON) INFO (pidfile fd = 3)
Sep 25 11:34:00 node-4 cron[8629]: (CRON) STARTUP (fork ok)
Sep 25 11:34:00 node-4 multipathd: path checkers start up
Sep 25 11:34:00 node-4 cron[8629]: (CRON) INFO (Running @reboot jobs)
Sep 25 11:34:00 node-4 postfix/master[8751]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 25 11:34:04 node-4 puppet-agent[8936]: Reopening log files
Sep 25 11:34:05 node-4 puppet-agent[8936]: Could not request certificate: Connection refused - connect(2)
Sep 25 11:34:18 node-4 puppet-user[9015]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 25 11:34:18 node-4 puppet-user[9015]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 25 11:34:18 node-4 puppet-user[9015]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 25 11:34:18 node-4 puppet-user[9015]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 25 11:34:18 node-4 puppet-user[9015]: Finished catalog run in 0.41 seconds
Sep 25 11:34:20 node-4 multipathd: uevent trigger error
Sep 25 11:34:20 node-4 puppet-user[9430]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 25 11:34:20 node-4 puppet-user[9430]: Compiled catalog for node-4.domain.tld in environment production in 0.10 seconds
Sep 25 11:34:20 node-4 puppet-user[9430]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 25 11:34:20 node-4 puppet-user[9430]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 25 11:34:20 node-4 puppet-user[9430]: (/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 25 11:34:20 node-4 puppet-user[9430]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 25 11:34:20 node-4 puppet-user[9430]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 25 11:34:20 node-4 puppet-user[9430]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 25 11:34:20 node-4 puppet-user[9430]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 25 11:34:20 node-4 puppet-user[9430]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 25 11:34:20 node-4 puppet-user[9430]: Finished catalog run in 0.07 seconds
Sep 25 11:34:21 node-4 puppet-user[9895]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 25 11:34:21 node-4 puppet-user[9895]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Sep 25 11:34:21 node-4 puppet-user[9895]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 25 11:34:21 node-4 puppet-user[9895]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 25 11:34:21 node-4 puppet-user[9895]: Finished catalog run in 0.03 seconds
Sep 25 11:34:23 node-4 puppet-user[10490]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 25 11:34:23 node-4 puppet-user[10490]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 25 11:34:23 node-4 puppet-user[10490]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 25 11:34:23 node-4 puppet-user[10490]: Finished catalog run in 0.03 seconds
Sep 25 11:34:24 node-4 puppet-user[10941]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 25 11:34:25 node-4 puppet-user[10941]: Compiled catalog for node-4.domain.tld in environment production in 0.16 seconds
Sep 25 11:34:25 node-4 puppet-user[10941]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 25 11:34:25 node-4 puppet-user[10941]: (/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 25 11:34:25 node-4 puppet-user[10941]: Finished catalog run in 0.45 seconds
Sep 25 11:34:26 node-4 puppet-user[11419]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 25 11:34:26 node-4 puppet-user[11419]: Compiled catalog for node-4.domain.tld in environment production in 0.22 seconds
Sep 25 11:34:27 node-4 puppet-user[11419]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 25 11:34:27 node-4 puppet-user[11419]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 25 11:34:27 node-4 puppet-user[11419]: (/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 25 11:34:27 node-4 puppet-user[11419]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 25 11:34:27 node-4 puppet-user[11419]: Finished catalog run in 0.27 seconds
Sep 25 11:34:28 node-4 puppet-user[11896]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 25 11:34:28 node-4 puppet-user[11896]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Sep 25 11:34:28 node-4 puppet-user[11896]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 25 11:34:28 node-4 kernel: [   66.868512] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 25 11:34:28 node-4 kernel: [   66.868562] 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 25 11:34:28 node-4 puppet-user[11896]: (/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 25 11:34:29 node-4 puppet-user[11896]: Finished catalog run in 0.05 seconds
Sep 25 11:34:30 node-4 puppet-user[12367]: (Scope(Class[main])) MODULAR: sync_time
Sep 25 11:34:30 node-4 puppet-user[12367]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 25 11:34:31 node-4 ntpdate[12782]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 25 11:34:37 node-4 ntpdate[12782]: adjust time server 10.20.0.2 offset -0.033683 sec
Sep 25 11:34:37 node-4 puppet-user[12367]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 25 11:34:37 node-4 puppet-user[12367]: Finished catalog run in 6.17 seconds
Sep 25 11:34:42 node-4 puppet-user[13149]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 25 11:34:42 node-4 puppet-user[13149]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Sep 25 11:34:43 node-4 puppet-user[13149]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 25 11:34:43 node-4 puppet-user[13149]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Sep 25 11:34:43 node-4 puppet-user[13149]: Finished catalog run in 0.06 seconds
Sep 25 11:34:44 node-4 puppet-user[13611]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 25 11:34:45 node-4 puppet-user[13611]: Compiled catalog for node-4.domain.tld in environment production in 0.48 seconds
Sep 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/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 25 11:34:45 node-4 puppet-user[13611]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 25 11:34:45 node-4 puppet-user[13611]: Finished catalog run in 0.77 seconds
Sep 25 11:34:46 node-4 kernel: [   84.003834] init: plymouth-upstart-bridge main process ended, respawning
Sep 25 11:34:46 node-4 puppet-agent[8936]: Could not run: SIGTERM
Sep 25 11:34:46 node-4 kernel: [   84.295537] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 25 11:34:46 node-4 ec2: 
Sep 25 11:34:46 node-4 ec2: #############################################################
Sep 25 11:34:46 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 25 11:34:46 node-4 ec2: 1024 15:0b:08:ad:7c:d3:82:71:f1:c1:74:d1:43:cc:b5:7e  root@node-4.domain.tld (DSA)
Sep 25 11:34:46 node-4 ec2: 256 49:5b:1e:59:95:5d:90:71:a4:20:6e:95:00:88:85:cf  root@node-4.domain.tld (ECDSA)
Sep 25 11:34:46 node-4 ec2: 256 11:16:b0:0a:ae:e9:82:f3:cb:d4:4c:94:32:28:58:93  root@node-4.domain.tld (ED25519)
Sep 25 11:34:46 node-4 ec2: 2048 dd:e5:d9:12:97:01:dc:f0:01:f5:f3:a1:3f:2e:be:96  root@node-4.domain.tld (RSA)
Sep 25 11:34:46 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 25 11:34:46 node-4 ec2: #############################################################
Sep 25 11:34:47 node-4 puppet-user[14293]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 25 11:34:47 node-4 puppet-user[14293]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Sep 25 11:34:50 node-4 puppet-user[14293]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 25 11:35:01 node-4 CRON[15817]: (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 25 11:35:03 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 25 11:35:03 node-4 nailgun-agent: I, [2016-09-25T11:35:03.661668 #15820]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 25 11:35:16 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 25 11:35:16 node-4 nailgun-agent: I, [2016-09-25T11:35:16.847225 #15820]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Sep 25 11:35:17 node-4 puppet-user[14293]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 25 11:35:17 node-4 puppet-user[14293]: Finished catalog run in 29.49 seconds
Sep 25 11:35:19 node-4 puppet-user[17033]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 25 11:35:19 node-4 puppet-user[17033]: Compiled catalog for node-4.domain.tld in environment production in 0.56 seconds
Sep 25 11:35:19 node-4 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 25 11:35:19 node-4 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 25 11:35:19 node-4 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 25 11:35:19 node-4 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 25 11:35:20 node-4 puppet-user[17033]: Finished catalog run in 0.08 seconds
Sep 25 11:35:21 node-4 puppet-user[17491]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 25 11:35:22 node-4 puppet-user[17491]: Compiled catalog for node-4.domain.tld in environment production in 0.99 seconds
Sep 25 11:35:23 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 25 11:35:23 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 25 11:35:23 node-4 crontab[17945]: (root) LIST (root)
Sep 25 11:35:23 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 25 11:35:23 node-4 crontab[17946]: (root) REPLACE (root)
Sep 25 11:35:24 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 25 11:35:25 node-4 puppet-user[17491]: (/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 25 11:35:26 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 25 11:35:26 node-4 puppet-user[17491]: (/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 25 11:35:26 node-4 puppet-user[17491]: (/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 25 11:35:26 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 25 11:35:26 node-4 puppet-user[17491]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 25 11:35:26 node-4 puppet-user[17491]: (/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 25 11:35:26 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 25 11:35:26 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 25 11:35:28 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:28 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:28 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:28 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:28 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:43 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:43 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:43 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:43 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:43 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:35:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:36:40 node-4 ntpdate[29666]: no servers can be used, exiting
<27>Sep 25 11:36:40 node-4 ntpdate[29767]: no servers can be used, exiting
<27>Sep 25 11:36:40 node-4 ntpdate[29940]: no servers can be used, exiting
<27>Sep 25 11:37:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:15 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:15 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:15 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:15 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:15 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:15 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:27 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:27 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:27 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:27 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:27 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:27 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:35 node-4 multipathd: uevent trigger error
<43>Sep 25 11:37:46 node-4 apache2_error [Sun Sep 25 11:37:45.177277 2016] [mpm_event:notice] [pid 7265:tid 139966897252224] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 25 11:37:46 node-4 apache2_error [Sun Sep 25 11:37:45.177427 2016] [core:notice] [pid 7265:tid 139966897252224] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 25 11:37:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:37:53 node-4 multipathd: uevent trigger error
<43>Sep 25 11:37:56 node-4 apache2_error [Sun Sep 25 11:37:48.146849 2016] [mpm_event:notice] [pid 7265:tid 139966897252224] AH00491: caught SIGTERM, shutting down
<43>Sep 25 11:37:56 node-4 apache2_error [Sun Sep 25 11:37:49.241880 2016] [mpm_worker:notice] [pid 7625:tid 140284761384832] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 25 11:37:56 node-4 apache2_error [Sun Sep 25 11:37:49.241948 2016] [core:notice] [pid 7625:tid 140284761384832] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 25 11:38:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:38:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:38:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:38:30 node-4 multipathd: uevent trigger error
<27>Sep 25 11:38:30 node-4 multipathd: uevent trigger error
<43>Sep 25 11:38:36 node-4 apache2_error [Sun Sep 25 11:38:26.947132 2016] [mpm_worker:notice] [pid 7625:tid 140284761384832] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 25 11:38:36 node-4 apache2_error [Sun Sep 25 11:38:26.950426 2016] [mpm_worker:warn] [pid 7625:tid 140284761384832] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 25 11:38:36 node-4 apache2_error [Sun Sep 25 11:38:26.950755 2016] [mpm_worker:notice] [pid 7625:tid 140284761384832] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 25 11:38:36 node-4 apache2_error [Sun Sep 25 11:38:26.950761 2016] [core:notice] [pid 7625:tid 140284761384832] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 25 11:39:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:04 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Sep 25 11:39:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:13 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:13 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:13 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:13 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:13 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:13 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:20 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:20 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:21 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:21 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:21 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:21 node-4 multipathd: uevent trigger error
<129>Sep 25 11:39:24 node-4 haproxy[20812]: 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 25 11:39:26 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:26 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:26 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:26 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:26 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:29 node-4 multipathd: uevent trigger error
<129>Sep 25 11:39:32 node-4 haproxy[23003]: 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 25 11:39:33 node-4 haproxy[23012]: 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 25 11:39:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:35 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:35 node-4 multipathd: uevent trigger error
<129>Sep 25 11:39:37 node-4 haproxy[24165]: 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 25 11:39:38 node-4 haproxy[24169]: 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 25 11:39:39 node-4 haproxy[24169]: 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 25 11:39:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:40 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:40 node-4 multipathd: uevent trigger error
<129>Sep 25 11:39:42 node-4 haproxy[25330]: 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 25 11:39:43 node-4 haproxy[25334]: 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 25 11:39:43 node-4 haproxy[25334]: 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 25 11:39:44 node-4 haproxy[25334]: 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 25 11:39:44 node-4 haproxy[25334]: 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 25 11:39:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:45 node-4 multipathd: uevent trigger error
<129>Sep 25 11:39:48 node-4 haproxy[26506]: 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 25 11:39:48 node-4 haproxy[26506]: 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 25 11:39:49 node-4 haproxy[26510]: 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 25 11:39:49 node-4 haproxy[26510]: 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 25 11:39:49 node-4 haproxy[26510]: 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 25 11:39:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:51 node-4 multipathd: uevent trigger error
<129>Sep 25 11:39:52 node-4 haproxy[26510]: Server odl-jetty/node-1 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 25 11:39:52 node-4 haproxy[26510]: proxy odl-jetty has no server available!
<129>Sep 25 11:39:53 node-4 haproxy[27676]: 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 25 11:39:53 node-4 haproxy[27676]: 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 25 11:39:54 node-4 haproxy[27683]: 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 25 11:39:54 node-4 haproxy[27683]: 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 25 11:39:54 node-4 haproxy[27683]: 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 25 11:39:54 node-4 haproxy[27683]: 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 25 11:39:56 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:56 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:56 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:56 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:56 node-4 multipathd: uevent trigger error
<27>Sep 25 11:39:56 node-4 multipathd: uevent trigger error
<129>Sep 25 11:39:56 node-4 haproxy[27683]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:39:56 node-4 haproxy[27683]: 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 25 11:39:56 node-4 haproxy[27683]: proxy aodh has no server available!
<129>Sep 25 11:39:57 node-4 haproxy[27683]: Server odl-jetty/node-1 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 25 11:39:57 node-4 haproxy[27683]: proxy odl-jetty has no server available!
<129>Sep 25 11:39:58 node-4 haproxy[28824]: 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 25 11:39:58 node-4 haproxy[28824]: 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 25 11:39:59 node-4 haproxy[28828]: 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 25 11:39:59 node-4 haproxy[28828]: 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 25 11:39:59 node-4 haproxy[28828]: 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 25 11:40:00 node-4 haproxy[28828]: 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 25 11:40:00 node-4 haproxy[28828]: 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 25 11:40:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:01 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:01 node-4 haproxy[28828]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:01 node-4 haproxy[28828]: 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 25 11:40:01 node-4 haproxy[28828]: proxy aodh has no server available!
<129>Sep 25 11:40:02 node-4 haproxy[28828]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:02 node-4 haproxy[28828]: 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 25 11:40:02 node-4 haproxy[28828]: proxy ceilometer has no server available!
<129>Sep 25 11:40:02 node-4 haproxy[28828]: Server odl-jetty/node-1 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 25 11:40:02 node-4 haproxy[28828]: proxy odl-jetty has no server available!
<129>Sep 25 11:40:04 node-4 haproxy[29987]: 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 25 11:40:04 node-4 haproxy[29987]: 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 25 11:40:04 node-4 haproxy[29987]: 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 25 11:40:04 node-4 haproxy[29987]: 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 25 11:40:05 node-4 haproxy[29987]: 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 25 11:40:05 node-4 haproxy[29987]: 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 25 11:40:05 node-4 haproxy[29987]: 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 25 11:40:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:07 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:07 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:07 node-4 haproxy[29987]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:07 node-4 haproxy[29987]: 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 25 11:40:07 node-4 haproxy[29987]: proxy aodh has no server available!
<129>Sep 25 11:40:07 node-4 haproxy[29987]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:07 node-4 haproxy[29987]: 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 25 11:40:07 node-4 haproxy[29987]: proxy ceilometer has no server available!
<129>Sep 25 11:40:07 node-4 haproxy[29987]: Server odl-jetty/node-1 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 25 11:40:07 node-4 haproxy[29987]: proxy odl-jetty has no server available!
<129>Sep 25 11:40:09 node-4 haproxy[31155]: 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 25 11:40:09 node-4 haproxy[31155]: 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 25 11:40:10 node-4 haproxy[31159]: 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 25 11:40:10 node-4 haproxy[31159]: 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 25 11:40:10 node-4 haproxy[31159]: 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 25 11:40:10 node-4 haproxy[31159]: 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 25 11:40:11 node-4 haproxy[31159]: 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 25 11:40:11 node-4 haproxy[31159]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:11 node-4 haproxy[31159]: 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 25 11:40:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:12 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:12 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:12 node-4 haproxy[31159]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:12 node-4 haproxy[31159]: 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 25 11:40:12 node-4 haproxy[31159]: proxy aodh has no server available!
<129>Sep 25 11:40:12 node-4 haproxy[31159]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:13 node-4 haproxy[31159]: Server ceilometer/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 25 11:40:13 node-4 haproxy[31159]: proxy ceilometer has no server available!
<129>Sep 25 11:40:13 node-4 haproxy[31159]: Server odl-jetty/node-1 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 25 11:40:13 node-4 haproxy[31159]: proxy odl-jetty has no server available!
<129>Sep 25 11:40:15 node-4 haproxy[32344]: 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 25 11:40:15 node-4 haproxy[32344]: 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 25 11:40:15 node-4 haproxy[32344]: 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 25 11:40:15 node-4 haproxy[32344]: 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 25 11:40:16 node-4 haproxy[32348]: 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 25 11:40:16 node-4 haproxy[32348]: 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 25 11:40:16 node-4 haproxy[32348]: 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 25 11:40:16 node-4 haproxy[32348]: 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 25 11:40:16 node-4 haproxy[32348]: 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 25 11:40:16 node-4 haproxy[32348]: 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 25 11:40:17 node-4 haproxy[32348]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:17 node-4 haproxy[32348]: 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.
<129>Sep 25 11:40:18 node-4 haproxy[32348]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:18 node-4 haproxy[32348]: 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 25 11:40:18 node-4 haproxy[32348]: proxy glance-registry has no server available!
<27>Sep 25 11:40:18 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:18 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:18 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:18 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:18 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:18 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:18 node-4 haproxy[32348]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:18 node-4 haproxy[32348]: 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 25 11:40:18 node-4 haproxy[32348]: proxy aodh has no server available!
<129>Sep 25 11:40:18 node-4 haproxy[32348]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:18 node-4 haproxy[32348]: 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 25 11:40:18 node-4 haproxy[32348]: proxy ceilometer has no server available!
<129>Sep 25 11:40:19 node-4 haproxy[32348]: Server odl-jetty/node-1 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 25 11:40:19 node-4 haproxy[32348]: proxy odl-jetty has no server available!
<129>Sep 25 11:40:21 node-4 haproxy[1245]: 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 25 11:40:21 node-4 haproxy[1245]: 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 25 11:40:21 node-4 haproxy[1245]: 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 25 11:40:21 node-4 haproxy[1245]: 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 25 11:40:21 node-4 haproxy[1245]: 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 25 11:40:21 node-4 haproxy[1245]: 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 25 11:40:21 node-4 haproxy[1245]: 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 25 11:40:22 node-4 haproxy[1245]: 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 25 11:40:22 node-4 haproxy[1245]: 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 25 11:40:22 node-4 haproxy[1245]: 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 25 11:40:22 node-4 haproxy[1245]: 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 25 11:40:22 node-4 haproxy[1245]: 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 25 11:40:22 node-4 haproxy[1245]: 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 25 11:40:22 node-4 haproxy[1245]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:22 node-4 haproxy[1245]: 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 25 11:40:23 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:23 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:23 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:23 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:23 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:23 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:23 node-4 haproxy[1245]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:24 node-4 haproxy[1245]: 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 25 11:40:24 node-4 haproxy[1245]: proxy glance-registry has no server available!
<129>Sep 25 11:40:24 node-4 haproxy[1245]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:24 node-4 haproxy[1245]: 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 25 11:40:24 node-4 haproxy[1245]: proxy aodh has no server available!
<129>Sep 25 11:40:24 node-4 haproxy[1245]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:24 node-4 haproxy[1245]: 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 25 11:40:24 node-4 haproxy[1245]: proxy ceilometer has no server available!
<129>Sep 25 11:40:24 node-4 haproxy[1245]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:24 node-4 haproxy[1245]: 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 25 11:40:24 node-4 haproxy[1245]: proxy nova-novncproxy has no server available!
<129>Sep 25 11:40:24 node-4 haproxy[1245]: Server odl-jetty/node-1 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 25 11:40:24 node-4 haproxy[1245]: proxy odl-jetty has no server available!
<129>Sep 25 11:40:26 node-4 haproxy[2382]: 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 25 11:40:26 node-4 haproxy[2382]: 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 25 11:40:26 node-4 haproxy[2382]: 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 25 11:40:26 node-4 haproxy[2382]: 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 25 11:40:26 node-4 haproxy[2382]: 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 25 11:40:26 node-4 haproxy[2382]: 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 25 11:40:26 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: 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 25 11:40:27 node-4 haproxy[2382]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:28 node-4 haproxy[2382]: 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 25 11:40:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:29 node-4 haproxy[2382]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:29 node-4 haproxy[2382]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:29 node-4 haproxy[2382]: proxy glance-registry has no server available!
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:29 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:29 node-4 haproxy[2382]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:29 node-4 haproxy[2382]: 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 25 11:40:29 node-4 haproxy[2382]: proxy aodh has no server available!
<129>Sep 25 11:40:29 node-4 haproxy[2382]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:29 node-4 haproxy[2382]: 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 25 11:40:29 node-4 haproxy[2382]: proxy ceilometer has no server available!
<129>Sep 25 11:40:29 node-4 haproxy[2382]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:29 node-4 haproxy[2382]: 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 25 11:40:29 node-4 haproxy[2382]: proxy nova-novncproxy has no server available!
<129>Sep 25 11:40:29 node-4 haproxy[2382]: Server odl-jetty/node-1 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 25 11:40:29 node-4 haproxy[2382]: proxy odl-jetty has no server available!
<129>Sep 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:32 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: 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 25 11:40:33 node-4 haproxy[3757]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:33 node-4 haproxy[3757]: 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.
<129>Sep 25 11:40:34 node-4 haproxy[3757]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 25 11:40:34 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:34 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:34 node-4 haproxy[3757]: 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 25 11:40:34 node-4 haproxy[3757]: proxy glance-registry has no server available!
<27>Sep 25 11:40:34 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:34 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:34 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:35 node-4 haproxy[3757]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:35 node-4 haproxy[3757]: 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 25 11:40:35 node-4 haproxy[3757]: proxy aodh has no server available!
<129>Sep 25 11:40:35 node-4 haproxy[3757]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:35 node-4 haproxy[3757]: 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 25 11:40:35 node-4 haproxy[3757]: proxy ceilometer has no server available!
<129>Sep 25 11:40:35 node-4 haproxy[3757]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:35 node-4 haproxy[3757]: 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 25 11:40:35 node-4 haproxy[3757]: proxy nova-novncproxy has no server available!
<129>Sep 25 11:40:35 node-4 haproxy[3757]: Server odl-jetty/node-1 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 25 11:40:35 node-4 haproxy[3757]: proxy odl-jetty has no server available!
<27>Sep 25 11:40:38 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:38 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:38 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:38 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:38 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:38 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:41 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:41 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:41 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:41 node-4 multipathd: uevent trigger error
<129>Sep 25 11:40:41 node-4 haproxy[3757]: Server odl-neutron-endpoint/node-1 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 25 11:40:41 node-4 haproxy[3757]: proxy odl-neutron-endpoint has no server available!
<129>Sep 25 11:40:41 node-4 haproxy[3757]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:41 node-4 haproxy[3757]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:41 node-4 haproxy[3757]: proxy keystone-1 has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:42 node-4 haproxy[3757]: proxy keystone-2 has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: 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 25 11:40:42 node-4 haproxy[3757]: proxy nova-api has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:42 node-4 haproxy[3757]: proxy nova-metadata-api has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Backup Server cinder-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 25 11:40:42 node-4 haproxy[3757]: proxy cinder-api has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: 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 25 11:40:42 node-4 haproxy[3757]: proxy glance-api has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: 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 25 11:40:42 node-4 haproxy[3757]: proxy glance-glare has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:42 node-4 haproxy[3757]: proxy neutron has no server available!
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:42 node-4 haproxy[3757]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:42 node-4 haproxy[3757]: proxy mysqld has no server available!
<129>Sep 25 11:40:43 node-4 haproxy[3757]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:43 node-4 haproxy[3757]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:43 node-4 haproxy[3757]: proxy object-storage has no server available!
<129>Sep 25 11:40:43 node-4 haproxy[3757]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:43 node-4 haproxy[3757]: 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 25 11:40:43 node-4 haproxy[3757]: proxy heat-api has no server available!
<129>Sep 25 11:40:43 node-4 haproxy[3757]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:43 node-4 haproxy[3757]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:43 node-4 haproxy[3757]: proxy heat-api-cfn has no server available!
<129>Sep 25 11:40:43 node-4 haproxy[3757]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 25 11:40:43 node-4 haproxy[3757]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 25 11:40:43 node-4 haproxy[3757]: proxy heat-api-cloudwatch has no server available!
<27>Sep 25 11:40:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:40:45 node-4 multipathd: uevent trigger error
<27>Sep 25 11:41:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:41:08 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 25 11:41:17 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 25 11:41:17 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 25 11:41:17 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 25 11:41:32 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 25 11:42:26 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 25 11:42:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:42:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:42:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:42:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:42:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:42:51 node-4 multipathd: uevent trigger error
<27>Sep 25 11:42:59 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 25 11:43:27 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 25 11:43:29 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 25 11:45:10 node-4 multipathd: uevent trigger error
<27>Sep 25 11:45:10 node-4 multipathd: uevent trigger error
<27>Sep 25 11:45:10 node-4 multipathd: uevent trigger error
<27>Sep 25 11:45:10 node-4 multipathd: uevent trigger error
<27>Sep 25 11:45:10 node-4 multipathd: uevent trigger error
<11>Sep 25 11:47:46 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 11:48:14 node-4 multipathd: uevent trigger error
<27>Sep 25 11:48:14 node-4 multipathd: uevent trigger error
<27>Sep 25 11:48:14 node-4 multipathd: uevent trigger error
<27>Sep 25 11:48:14 node-4 multipathd: uevent trigger error
<27>Sep 25 11:48:14 node-4 multipathd: uevent trigger error
<27>Sep 25 11:48:14 node-4 multipathd: uevent trigger error
<43>Sep 25 11:49:17 node-4 apache2_error [Sun Sep 25 11:49:16.387820 2016] [mpm_worker:notice] [pid 7625:tid 140284761384832] AH00295: caught SIGTERM, shutting down
<43>Sep 25 11:49:17 node-4 apache2_error [Sun Sep 25 11:49:17.130392 2016] [mpm_worker:notice] [pid 6914:tid 140664020117376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 25 11:49:17 node-4 apache2_error [Sun Sep 25 11:49:17.130421 2016] [core:notice] [pid 6914:tid 140664020117376] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 25 11:49:26 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 25 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 25 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 25 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 25 11:49:54 node-4 multipathd: uevent trigger error
<43>Sep 25 11:49:57 node-4 apache2_error [Sun Sep 25 11:49:48.931739 2016] [mpm_worker:notice] [pid 6914:tid 140664020117376] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 25 11:49:57 node-4 apache2_error [Sun Sep 25 11:49:48.942313 2016] [mpm_worker:warn] [pid 6914:tid 140664020117376] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 25 11:49:57 node-4 apache2_error [Sun Sep 25 11:49:48.949612 2016] [mpm_worker:notice] [pid 6914:tid 140664020117376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 25 11:49:57 node-4 apache2_error [Sun Sep 25 11:49:48.949639 2016] [core:notice] [pid 6914:tid 140664020117376] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 25 11:50:46 node-4 multipathd: uevent trigger error
<27>Sep 25 11:50:46 node-4 multipathd: uevent trigger error
<27>Sep 25 11:50:46 node-4 multipathd: uevent trigger error
<27>Sep 25 11:50:46 node-4 multipathd: uevent trigger error
<27>Sep 25 11:51:57 node-4 multipathd: uevent trigger error
<27>Sep 25 11:51:57 node-4 multipathd: uevent trigger error
<27>Sep 25 11:51:57 node-4 multipathd: uevent trigger error
<27>Sep 25 11:51:57 node-4 multipathd: uevent trigger error
<27>Sep 25 11:51:57 node-4 multipathd: uevent trigger error
<11>Sep 25 11:52:37 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<11>Sep 25 11:53:34 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<11>Sep 25 11:55:10 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 11:56:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:56:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:56:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:56:01 node-4 multipathd: uevent trigger error
<27>Sep 25 11:56:01 node-4 multipathd: uevent trigger error
<11>Sep 25 11:56:30 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 11:58:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:58:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:58:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:58:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:58:04 node-4 multipathd: uevent trigger error
<27>Sep 25 11:58:04 node-4 multipathd: uevent trigger error
<11>Sep 25 11:58:13 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 11:59:06 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:06 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:06 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:06 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:06 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:06 node-4 multipathd: uevent trigger error
<11>Sep 25 11:59:10 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 11:59:39 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:39 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:39 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:39 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:39 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:39 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:48 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:48 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:48 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:48 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:48 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:53 node-4 multipathd: uevent trigger error
<27>Sep 25 11:59:53 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:09 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:09 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:09 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:09 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:09 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:09 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:00:14 node-4 multipathd: uevent trigger error
<11>Sep 25 12:01:07 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<43>Sep 25 12:01:07 node-4 apache2_error [Sun Sep 25 12:00:59.529952 2016] [mpm_worker:notice] [pid 6914:tid 140664020117376] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 25 12:01:07 node-4 apache2_error [Sun Sep 25 12:00:59.915875 2016] [mpm_worker:warn] [pid 6914:tid 140664020117376] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 25 12:01:07 node-4 apache2_error [Sun Sep 25 12:00:59.920408 2016] [mpm_worker:notice] [pid 6914:tid 140664020117376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 25 12:01:07 node-4 apache2_error [Sun Sep 25 12:00:59.920428 2016] [core:notice] [pid 6914:tid 140664020117376] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 25 12:01:37 node-4 apache2_error [Sun Sep 25 12:01:36.623056 2016] [mpm_worker:notice] [pid 6914:tid 140664020117376] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 25 12:01:37 node-4 apache2_error [Sun Sep 25 12:01:37.008863 2016] [mpm_worker:warn] [pid 6914:tid 140664020117376] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 25 12:01:37 node-4 apache2_error [Sun Sep 25 12:01:37.019340 2016] [mpm_worker:notice] [pid 6914:tid 140664020117376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 25 12:01:37 node-4 apache2_error [Sun Sep 25 12:01:37.019380 2016] [core:notice] [pid 6914:tid 140664020117376] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 25 12:01:40 node-4 multipathd: uevent trigger error
<27>Sep 25 12:01:40 node-4 multipathd: uevent trigger error
<27>Sep 25 12:01:40 node-4 multipathd: uevent trigger error
<27>Sep 25 12:01:40 node-4 multipathd: uevent trigger error
<27>Sep 25 12:01:40 node-4 multipathd: uevent trigger error
<11>Sep 25 12:01:42 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 12:01:53 node-4 multipathd: uevent trigger error
<27>Sep 25 12:01:54 node-4 multipathd: uevent trigger error
<27>Sep 25 12:01:54 node-4 multipathd: uevent trigger error
<27>Sep 25 12:02:01 node-4 multipathd: uevent trigger error
<27>Sep 25 12:02:01 node-4 multipathd: uevent trigger error
<27>Sep 25 12:02:01 node-4 multipathd: uevent trigger error
<27>Sep 25 12:02:01 node-4 multipathd: uevent trigger error
<27>Sep 25 12:02:01 node-4 multipathd: uevent trigger error
<27>Sep 25 12:02:01 node-4 multipathd: uevent trigger error
<27>Sep 25 12:02:01 node-4 multipathd: sda: spurious uevent, path already in pathvec
<11>Sep 25 12:02:31 node-4 epmd: epmd: node name already occupied rabbitmq-cli-97
<27>Sep 25 12:03:00 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:00 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:00 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:00 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:00 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:05 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:05 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:05 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:05 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:05 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:17 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:17 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:17 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:17 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:17 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:17 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:03:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:28 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:28 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:28 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:28 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:28 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:41 node-4 multipathd: uevent trigger error
<27>Sep 25 12:04:41 node-4 multipathd: uevent trigger error
<11>Sep 25 12:04:49 node-4 liberasurecode[60595]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:49 node-4 liberasurecode[60595]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:49 node-4 liberasurecode[60595]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:49 node-4 liberasurecode[60595]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:49 node-4 liberasurecode[60619]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:49 node-4 liberasurecode[60619]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:49 node-4 liberasurecode[60619]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:49 node-4 liberasurecode[60619]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:51 node-4 liberasurecode[61010]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:51 node-4 liberasurecode[61010]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:51 node-4 liberasurecode[61010]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:51 node-4 liberasurecode[61010]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61561]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61561]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61561]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61561]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61640]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61640]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61640]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61640]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61758]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61758]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61758]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61758]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61818]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61818]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61830]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61830]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61845]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61845]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61845]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:56 node-4 liberasurecode[61845]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:57 node-4 liberasurecode[61859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:57 node-4 liberasurecode[61859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:57 node-4 liberasurecode[61859]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:04:57 node-4 liberasurecode[61859]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 25 12:05:01 node-4 liberasurecode[62552]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:05:01 node-4 liberasurecode[62552]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:05:01 node-4 liberasurecode[62552]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:05:01 node-4 liberasurecode[62552]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 25 12:05:03 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:03 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:03 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:03 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:05:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:06:16 node-4 multipathd: uevent trigger error
<27>Sep 25 12:06:16 node-4 multipathd: uevent trigger error
<27>Sep 25 12:06:16 node-4 multipathd: uevent trigger error
<27>Sep 25 12:06:16 node-4 multipathd: uevent trigger error
<27>Sep 25 12:06:16 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:14 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:19 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:19 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:19 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:19 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:19 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:32 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:32 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:32 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:32 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:32 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:37 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:37 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:37 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:37 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:37 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:37 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:50 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:50 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:50 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:50 node-4 multipathd: uevent trigger error
<27>Sep 25 12:08:51 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:04 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:04 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:04 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:04 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:04 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:08 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:13 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:13 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:13 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:13 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:13 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:18 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:18 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:18 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:18 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:18 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:18 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:22 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:22 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:22 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:22 node-4 multipathd: uevent trigger error
<27>Sep 25 12:09:22 node-4 multipathd: uevent trigger error
<11>Sep 25 12:10:02 node-4 liberasurecode[115184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:10:02 node-4 liberasurecode[115184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:10:02 node-4 liberasurecode[115184]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 25 12:10:02 node-4 liberasurecode[115184]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
