Jul 29 23:42:17 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] start
Jul 29 23:42:17 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 29 23:42:17 node-3 rsyslogd: rsyslogd's groupid changed to 104
Jul 29 23:42:17 node-3 rsyslogd: rsyslogd's userid changed to 101
Jul 29 23:42:17 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 29 23:42:17 node-3 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 29 23:42:17 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 29 23:42:17 node-3 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 29 23:42:17 node-3 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=13289587-75fe-49ce-a1f6-f91e261f5227 nomdmonddf nomdmonisw
Jul 29 23:42:17 node-3 kernel: [    0.000000] KERNEL supported cpus:
Jul 29 23:42:17 node-3 kernel: [    0.000000]   Intel GenuineIntel
Jul 29 23:42:17 node-3 kernel: [    0.000000]   AMD AuthenticAMD
Jul 29 23:42:17 node-3 kernel: [    0.000000]   Centaur CentaurHauls
Jul 29 23:42:17 node-3 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 29 23:42:17 node-3 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 29 23:42:17 node-3 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 29 23:42:17 node-3 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 29 23:42:17 node-3 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 29 23:42:17 node-3 kernel: [    0.000000] No AGP bridge found
Jul 29 23:42:17 node-3 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 29 23:42:17 node-3 kernel: [    0.000000] MTRR default type: write-back
Jul 29 23:42:17 node-3 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 29 23:42:17 node-3 kernel: [    0.000000]   00000-9FFFF write-back
Jul 29 23:42:17 node-3 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 29 23:42:17 node-3 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 29 23:42:17 node-3 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 29 23:42:17 node-3 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 29 23:42:17 node-3 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 29 23:42:17 node-3 kernel: [    0.000000]   2 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000]   3 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000]   4 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000]   5 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000]   6 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000]   7 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000]   8 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000]   9 disabled
Jul 29 23:42:17 node-3 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 29 23:42:17 node-3 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 29 23:42:17 node-3 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 29 23:42:17 node-3 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 29 23:42:17 node-3 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 29 23:42:17 node-3 kernel: [    0.000000] Using GB pages for direct mapping
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 29 23:42:17 node-3 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 29 23:42:17 node-3 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 29 23:42:17 node-3 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 29 23:42:17 node-3 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 29 23:42:17 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 29 23:42:17 node-3 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 29 23:42:17 node-3 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 29 23:42:17 node-3 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 29 23:42:17 node-3 kernel: [    0.000000] Zone ranges:
Jul 29 23:42:17 node-3 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] Movable zone start for each node
Jul 29 23:42:17 node-3 kernel: [    0.000000] Early memory node ranges
Jul 29 23:42:17 node-3 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 29 23:42:17 node-3 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 29 23:42:17 node-3 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 29 23:42:17 node-3 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 29 23:42:17 node-3 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 29 23:42:17 node-3 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 29 23:42:17 node-3 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 29 23:42:17 node-3 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 29 23:42:17 node-3 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 29 23:42:17 node-3 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 29 23:42:17 node-3 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 29 23:42:17 node-3 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 29 23:42:17 node-3 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 29 23:42:17 node-3 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 29 23:42:17 node-3 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 29 23:42:17 node-3 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 29 23:42:17 node-3 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 29 23:42:17 node-3 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 29 23:42:17 node-3 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 29 23:42:17 node-3 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 29 23:42:17 node-3 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 29 23:42:17 node-3 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 29 23:42:17 node-3 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 29 23:42:17 node-3 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 29 23:42:17 node-3 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 29 23:42:17 node-3 kernel: [    0.000000] Policy zone: Normal
Jul 29 23:42:17 node-3 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=13289587-75fe-49ce-a1f6-f91e261f5227 nomdmonddf nomdmonisw
Jul 29 23:42:17 node-3 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 29 23:42:17 node-3 kernel: [    0.000000] Checking aperture...
Jul 29 23:42:17 node-3 kernel: [    0.000000] No AGP bridge found
Jul 29 23:42:17 node-3 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 29 23:42:17 node-3 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 29 23:42:17 node-3 kernel: [    0.000000] Memory: 32653452K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 29 23:42:17 node-3 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 29 23:42:17 node-3 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 29 23:42:17 node-3 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 29 23:42:17 node-3 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 29 23:42:17 node-3 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 29 23:42:17 node-3 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 29 23:42:17 node-3 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 29 23:42:17 node-3 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 29 23:42:17 node-3 kernel: [    0.000000] console [tty0] enabled
Jul 29 23:42:17 node-3 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 29 23:42:17 node-3 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 29 23:42:17 node-3 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 29 23:42:17 node-3 kernel: [    0.000000] hpet clockevent registered
Jul 29 23:42:17 node-3 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 29 23:42:17 node-3 kernel: [    0.004000] tsc: Detected 3492.256 MHz processor
Jul 29 23:42:17 node-3 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.51 BogoMIPS (lpj=13969024)
Jul 29 23:42:17 node-3 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 29 23:42:17 node-3 kernel: [    0.000048] Security Framework initialized
Jul 29 23:42:17 node-3 kernel: [    0.000066] AppArmor: AppArmor initialized
Jul 29 23:42:17 node-3 kernel: [    0.000067] Yama: becoming mindful.
Jul 29 23:42:17 node-3 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.006400] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.008329] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.008357] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.008645] Initializing cgroup subsys memory
Jul 29 23:42:17 node-3 kernel: [    0.008653] Initializing cgroup subsys devices
Jul 29 23:42:17 node-3 kernel: [    0.008655] Initializing cgroup subsys freezer
Jul 29 23:42:17 node-3 kernel: [    0.008657] Initializing cgroup subsys blkio
Jul 29 23:42:17 node-3 kernel: [    0.008658] Initializing cgroup subsys perf_event
Jul 29 23:42:17 node-3 kernel: [    0.008661] Initializing cgroup subsys hugetlb
Jul 29 23:42:17 node-3 kernel: [    0.008680] CPU: Physical Processor ID: 0
Jul 29 23:42:17 node-3 kernel: [    0.008681] CPU: Processor Core ID: 0
Jul 29 23:42:17 node-3 kernel: [    0.008685] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 29 23:42:17 node-3 kernel: [    0.008685] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 29 23:42:17 node-3 kernel: [    0.009379] mce: CPU supports 22 MCE banks
Jul 29 23:42:17 node-3 kernel: [    0.009406] CPU0: Thermal monitoring enabled (TM1)
Jul 29 23:42:17 node-3 kernel: [    0.009427] process: using mwait in idle threads
Jul 29 23:42:17 node-3 kernel: [    0.009430] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 29 23:42:17 node-3 kernel: [    0.009430] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 29 23:42:17 node-3 kernel: [    0.009430] tlb_flushall_shift: 6
Jul 29 23:42:17 node-3 kernel: [    0.009519] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 29 23:42:17 node-3 kernel: [    0.010243] ACPI: Core revision 20131115
Jul 29 23:42:17 node-3 kernel: [    0.022911] ACPI: All ACPI Tables successfully acquired
Jul 29 23:42:17 node-3 kernel: [    0.023074] ftrace: allocating 28617 entries in 112 pages
Jul 29 23:42:17 node-3 kernel: [    0.031902] dmar: Host address width 46
Jul 29 23:42:17 node-3 kernel: [    0.031904] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 29 23:42:17 node-3 kernel: [    0.031910] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 23:42:17 node-3 kernel: [    0.031912] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 29 23:42:17 node-3 kernel: [    0.031916] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 23:42:17 node-3 kernel: [    0.031917] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 29 23:42:17 node-3 kernel: [    0.031919] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 29 23:42:17 node-3 kernel: [    0.031920] dmar: ATSR flags: 0x0
Jul 29 23:42:17 node-3 kernel: [    0.031921] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 29 23:42:17 node-3 kernel: [    0.031922] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 29 23:42:17 node-3 kernel: [    0.032038] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 29 23:42:17 node-3 kernel: [    0.032039] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 23:42:17 node-3 kernel: [    0.032040] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 23:42:17 node-3 kernel: [    0.032041] HPET id 0 under DRHD base 0xc7ffc000
Jul 29 23:42:17 node-3 kernel: [    0.032042] Your BIOS is broken and requested that x2apic be disabled.
Jul 29 23:42:17 node-3 kernel: [    0.032042] This will slightly decrease performance.
Jul 29 23:42:17 node-3 kernel: [    0.032042] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 29 23:42:17 node-3 kernel: [    0.032474] Enabled IRQ remapping in xapic mode
Jul 29 23:42:17 node-3 kernel: [    0.032475] x2apic not enabled, IRQ remapping is in xapic mode
Jul 29 23:42:17 node-3 kernel: [    0.032479] Switched APIC routing to physical flat.
Jul 29 23:42:17 node-3 kernel: [    0.033104] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 29 23:42:17 node-3 kernel: [    0.072758] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 29 23:42:17 node-3 kernel: [    0.072764] TSC deadline timer enabled
Jul 29 23:42:17 node-3 kernel: [    0.072771] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 29 23:42:17 node-3 kernel: [    0.072777] ... version:                3
Jul 29 23:42:17 node-3 kernel: [    0.072778] ... bit width:              48
Jul 29 23:42:17 node-3 kernel: [    0.072779] ... generic registers:      4
Jul 29 23:42:17 node-3 kernel: [    0.072780] ... value mask:             0000ffffffffffff
Jul 29 23:42:17 node-3 kernel: [    0.072781] ... max period:             0000ffffffffffff
Jul 29 23:42:17 node-3 kernel: [    0.072782] ... fixed-purpose events:   3
Jul 29 23:42:17 node-3 kernel: [    0.072783] ... event mask:             000000070000000f
Jul 29 23:42:17 node-3 kernel: [    0.074223] x86: Booting SMP configuration:
Jul 29 23:42:17 node-3 kernel: [    0.088327] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 29 23:42:17 node-3 kernel: [    0.074225] .... node  #0, CPUs:        #1  #2  #3
Jul 29 23:42:17 node-3 kernel: [    0.116237] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 29 23:42:17 node-3 kernel: [    0.270208] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 29 23:42:17 node-3 kernel: [    0.325824] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 29 23:42:17 node-3 kernel: [    0.382681] x86: Booted up 2 nodes, 16 CPUs
Jul 29 23:42:17 node-3 kernel: [    0.382685] smpboot: Total of 16 processors activated (111764.62 BogoMIPS)
Jul 29 23:42:17 node-3 kernel: [    0.407002] devtmpfs: initialized
Jul 29 23:42:17 node-3 kernel: [    0.410110] EVM: security.selinux
Jul 29 23:42:17 node-3 kernel: [    0.410112] EVM: security.SMACK64
Jul 29 23:42:17 node-3 kernel: [    0.410113] EVM: security.ima
Jul 29 23:42:17 node-3 kernel: [    0.410113] EVM: security.capability
Jul 29 23:42:17 node-3 kernel: [    0.410162] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.410850] pinctrl core: initialized pinctrl subsystem
Jul 29 23:42:17 node-3 kernel: [    0.410912] regulator-dummy: no parameters
Jul 29 23:42:17 node-3 kernel: [    0.410944] RTC time: 23:41:41, date: 07/29/16
Jul 29 23:42:17 node-3 kernel: [    0.410979] NET: Registered protocol family 16
Jul 29 23:42:17 node-3 kernel: [    0.411062] cpuidle: using governor ladder
Jul 29 23:42:17 node-3 kernel: [    0.411063] cpuidle: using governor menu
Jul 29 23:42:17 node-3 kernel: [    0.411097] ACPI: bus type PCI registered
Jul 29 23:42:17 node-3 kernel: [    0.411099] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 29 23:42:17 node-3 kernel: [    0.411146] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 29 23:42:17 node-3 kernel: [    0.411148] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 29 23:42:17 node-3 kernel: [    0.424879] PCI: Using configuration type 1 for base access
Jul 29 23:42:17 node-3 kernel: [    0.425880] bio: create slab <bio-0> at 0
Jul 29 23:42:17 node-3 kernel: [    0.426165] ACPI: Added _OSI(Module Device)
Jul 29 23:42:17 node-3 kernel: [    0.426167] ACPI: Added _OSI(Processor Device)
Jul 29 23:42:17 node-3 kernel: [    0.426168] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 29 23:42:17 node-3 kernel: [    0.426169] ACPI: Added _OSI(Processor Aggregator Device)
Jul 29 23:42:17 node-3 kernel: [    0.438861] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 29 23:42:17 node-3 kernel: [    0.449430] ACPI: Interpreter enabled
Jul 29 23:42:17 node-3 kernel: [    0.449436] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 29 23:42:17 node-3 kernel: [    0.449440] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 29 23:42:17 node-3 kernel: [    0.449442] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 29 23:42:17 node-3 kernel: [    0.449449] ACPI: (supports S0 S4 S5)
Jul 29 23:42:17 node-3 kernel: [    0.449450] ACPI: Using IOAPIC for interrupt routing
Jul 29 23:42:17 node-3 kernel: [    0.449492] HEST: Table parsing has been initialized.
Jul 29 23:42:17 node-3 kernel: [    0.449495] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 29 23:42:17 node-3 kernel: [    0.450046] ACPI: No dock devices found.
Jul 29 23:42:17 node-3 kernel: [    0.461617] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 29 23:42:17 node-3 kernel: [    0.461622] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-3 kernel: [    0.461626] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 23:42:17 node-3 kernel: [    0.461652] PCI host bridge to bus 0000:ff
Jul 29 23:42:17 node-3 kernel: [    0.461654] pci_bus 0000:ff: root bus resource [bus ff]
Jul 29 23:42:17 node-3 kernel: [    0.461662] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461700] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.461730] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461765] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461794] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.461822] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.461852] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461881] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461910] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461937] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461964] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.461990] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462017] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462045] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462071] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462097] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462125] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462152] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462178] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.462206] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462232] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.462257] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462283] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462313] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.462347] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462378] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462407] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462438] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462468] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462499] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462529] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462559] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462589] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462621] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462653] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462685] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462718] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462748] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462775] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462808] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462840] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 23:42:17 node-3 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 29 23:42:17 node-3 kernel: [    0.462876] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462911] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462943] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.462973] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463004] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463033] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463065] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463095] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463125] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463156] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463185] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463213] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463242] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463271] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463301] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463332] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463389] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 29 23:42:17 node-3 kernel: [    0.463391] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-3 kernel: [    0.463394] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 23:42:17 node-3 kernel: [    0.463411] PCI host bridge to bus 0000:7f
Jul 29 23:42:17 node-3 kernel: [    0.463413] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 29 23:42:17 node-3 kernel: [    0.463418] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463445] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.463471] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463500] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463522] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.463546] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.463571] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463597] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463620] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463648] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463672] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463697] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463724] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463749] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463772] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463798] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463820] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463843] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463865] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.463889] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463911] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.463933] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463956] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.463982] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 23:42:17 node-3 kernel: [    0.464016] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464042] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464068] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464095] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464120] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464148] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464176] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464204] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464229] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464257] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464285] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464312] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464340] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464366] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464392] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464421] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464446] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464472] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464500] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464528] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464553] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464578] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464603] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464630] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464659] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464685] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464715] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464738] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464761] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464786] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464811] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464840] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.464866] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.466108] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 29 23:42:17 node-3 kernel: [    0.466111] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-3 kernel: [    0.467238] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 23:42:17 node-3 kernel: [    0.467755] PCI host bridge to bus 0000:00
Jul 29 23:42:17 node-3 kernel: [    0.467757] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 29 23:42:17 node-3 kernel: [    0.467759] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 29 23:42:17 node-3 kernel: [    0.467760] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 29 23:42:17 node-3 kernel: [    0.467762] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 29 23:42:17 node-3 kernel: [    0.467763] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 29 23:42:17 node-3 kernel: [    0.467764] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 29 23:42:17 node-3 kernel: [    0.467766] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 29 23:42:17 node-3 kernel: [    0.467772] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 29 23:42:17 node-3 kernel: [    0.467854] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.467885] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.467926] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-3 kernel: [    0.467945] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.467975] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.468015] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-3 kernel: [    0.468033] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.468062] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.468102] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-3 kernel: [    0.468119] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.468189] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.468265] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.468340] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 23:42:17 node-3 kernel: [    0.468345] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 29 23:42:17 node-3 kernel: [    0.468430] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 29 23:42:17 node-3 kernel: [    0.468577] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 29 23:42:17 node-3 kernel: [    0.468594] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 29 23:42:17 node-3 kernel: [    0.468673] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.468726] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-3 kernel: [    0.468747] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.468802] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.468845] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-3 kernel: [    0.468872] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.468927] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.468970] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 29 23:42:17 node-3 kernel: [    0.468993] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 29 23:42:17 node-3 kernel: [    0.469010] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 29 23:42:17 node-3 kernel: [    0.469088] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.469138] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-3 kernel: [    0.469164] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 29 23:42:17 node-3 kernel: [    0.469410] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 29 23:42:17 node-3 kernel: [    0.469416] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 29 23:42:17 node-3 kernel: [    0.469422] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.469427] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.469435] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 29 23:42:17 node-3 kernel: [    0.469465] pci 0000:01:00.0: supports D1 D2
Jul 29 23:42:17 node-3 kernel: [    0.479663] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 23:42:17 node-3 kernel: [    0.479666] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 23:42:17 node-3 kernel: [    0.479667] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 23:42:17 node-3 kernel: [    0.479774] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.479807] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 29 23:42:17 node-3 kernel: [    0.491647] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 23:42:17 node-3 kernel: [    0.491653] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.491657] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-3 kernel: [    0.491741] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.491813] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.491908] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.491989] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 23:42:17 node-3 kernel: [    0.491996] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.492001] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-3 kernel: [    0.492080] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.492234] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.492288] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 23:42:17 node-3 kernel: [    0.492290] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.492292] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.492341] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.492460] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.492502] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.492621] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.492657] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.492776] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.492813] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-3 kernel: [    0.492934] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-3 kernel: [    0.492977] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 23:42:17 node-3 kernel: [    0.492980] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.492982] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.493041] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-3 kernel: [    0.493104] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.493156] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.493222] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 29 23:42:17 node-3 kernel: [    0.493303] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 29 23:42:17 node-3 kernel: [    0.493410] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 23:42:17 node-3 kernel: [    0.493413] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.493415] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.493471] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-3 kernel: [    0.493528] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.493577] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.493789] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 23:42:17 node-3 kernel: [    0.493793] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 23:42:17 node-3 kernel: [    0.493855] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-3 kernel: [    0.493907] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.493956] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.494167] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 23:42:17 node-3 kernel: [    0.494171] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 23:42:17 node-3 kernel: [    0.494245] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-3 kernel: [    0.494309] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.494361] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 29 23:42:17 node-3 kernel: [    0.494582] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 23:42:17 node-3 kernel: [    0.494585] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 23:42:17 node-3 kernel: [    0.494759] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 23:42:17 node-3 kernel: [    0.494796] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 23:42:17 node-3 kernel: [    0.494873] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 29 23:42:17 node-3 kernel: [    0.494891] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 29 23:42:17 node-3 kernel: [    0.494905] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 29 23:42:17 node-3 kernel: [    0.494918] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 29 23:42:17 node-3 kernel: [    0.494968] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 29 23:42:17 node-3 kernel: [    0.499654] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 23:42:17 node-3 kernel: [    0.499663] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 23:42:17 node-3 kernel: [    0.499716] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 29 23:42:17 node-3 kernel: [    0.500246] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 29 23:42:17 node-3 kernel: [    0.500249] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-3 kernel: [    0.500369] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 23:42:17 node-3 kernel: [    0.500475] PCI host bridge to bus 0000:80
Jul 29 23:42:17 node-3 kernel: [    0.500478] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 29 23:42:17 node-3 kernel: [    0.500479] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 29 23:42:17 node-3 kernel: [    0.500481] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 29 23:42:17 node-3 kernel: [    0.500489] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.500551] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.500619] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 23:42:17 node-3 kernel: [    0.500680] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 23:42:17 node-3 kernel: [    0.500685] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 29 23:42:17 node-3 kernel: [    0.500757] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 29 23:42:17 node-3 kernel: [    0.501054] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 29 23:42:17 node-3 kernel: [    0.501085] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 29 23:42:17 node-3 kernel: [    0.501115] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 29 23:42:17 node-3 kernel: [    0.501144] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 29 23:42:17 node-3 kernel: [    0.501173] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-3 kernel: [    0.501203] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-3 kernel: [    0.501232] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-3 kernel: [    0.501261] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-3 kernel: [    0.501348] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 29 23:42:17 node-3 kernel: [    0.501352] ACPI: \_SB_.UNC1: notify handler is installed
Jul 29 23:42:17 node-3 kernel: [    0.501353] ACPI: \_SB_.UNC0: notify handler is installed
Jul 29 23:42:17 node-3 kernel: [    0.501368] ACPI: \_SB_.PCI0: notify handler is installed
Jul 29 23:42:17 node-3 kernel: [    0.501421] ACPI: \_SB_.PCI1: notify handler is installed
Jul 29 23:42:17 node-3 kernel: [    0.501501] Found 4 acpi root devices
Jul 29 23:42:17 node-3 kernel: [    0.501607] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 29 23:42:17 node-3 kernel: [    0.501609] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 29 23:42:17 node-3 kernel: [    0.501611] vgaarb: loaded
Jul 29 23:42:17 node-3 kernel: [    0.501612] vgaarb: bridge control possible 0000:0c:00.0
Jul 29 23:42:17 node-3 kernel: [    0.501727] SCSI subsystem initialized
Jul 29 23:42:17 node-3 kernel: [    0.501791] libata version 3.00 loaded.
Jul 29 23:42:17 node-3 kernel: [    0.501806] ACPI: bus type USB registered
Jul 29 23:42:17 node-3 kernel: [    0.501816] usbcore: registered new interface driver usbfs
Jul 29 23:42:17 node-3 kernel: [    0.501822] usbcore: registered new interface driver hub
Jul 29 23:42:17 node-3 kernel: [    0.501845] usbcore: registered new device driver usb
Jul 29 23:42:17 node-3 kernel: [    0.502009] PCI: Using ACPI for IRQ routing
Jul 29 23:42:17 node-3 kernel: [    0.505595] PCI: pci_cache_line_size set to 64 bytes
Jul 29 23:42:17 node-3 kernel: [    0.505798] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 29 23:42:17 node-3 kernel: [    0.505799] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 29 23:42:17 node-3 kernel: [    0.505799] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 29 23:42:17 node-3 kernel: [    0.505864] NetLabel: Initializing
Jul 29 23:42:17 node-3 kernel: [    0.505865] NetLabel:  domain hash size = 128
Jul 29 23:42:17 node-3 kernel: [    0.505866] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 29 23:42:17 node-3 kernel: [    0.505876] NetLabel:  unlabeled traffic allowed by default
Jul 29 23:42:17 node-3 kernel: [    0.505931] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 29 23:42:17 node-3 kernel: [    0.505935] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 29 23:42:17 node-3 kernel: [    0.507991] Switched to clocksource hpet
Jul 29 23:42:17 node-3 kernel: [    0.511948] AppArmor: AppArmor Filesystem Enabled
Jul 29 23:42:17 node-3 kernel: [    0.511962] pnp: PnP ACPI init
Jul 29 23:42:17 node-3 kernel: [    0.511969] ACPI: bus type PNP registered
Jul 29 23:42:17 node-3 kernel: [    0.512083] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512091] pnp 00:01: [dma 4]
Jul 29 23:42:17 node-3 kernel: [    0.512103] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512130] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512149] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512167] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512200] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512254] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512256] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 29 23:42:17 node-3 kernel: [    0.512258] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512259] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512261] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512265] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512267] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 29 23:42:17 node-3 kernel: [    0.512269] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512271] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512272] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512274] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512275] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512277] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 29 23:42:17 node-3 kernel: [    0.512279] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512362] pnp 00:07: [dma 0 disabled]
Jul 29 23:42:17 node-3 kernel: [    0.512390] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512464] pnp 00:08: [dma 0 disabled]
Jul 29 23:42:17 node-3 kernel: [    0.512497] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512548] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 29 23:42:17 node-3 kernel: [    0.512893] pnp: PnP ACPI: found 10 devices
Jul 29 23:42:17 node-3 kernel: [    0.512895] ACPI: bus type PNP unregistered
Jul 29 23:42:17 node-3 kernel: [    0.519198] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 23:42:17 node-3 kernel: [    0.519201] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 23:42:17 node-3 kernel: [    0.519204] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 23:42:17 node-3 kernel: [    0.519208] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 23:42:17 node-3 kernel: [    0.519210] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519225] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519254] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 23:42:17 node-3 kernel: [    0.519269] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519298] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 23:42:17 node-3 kernel: [    0.519312] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 23:42:17 node-3 kernel: [    0.519341] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 23:42:17 node-3 kernel: [    0.519355] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 23:42:17 node-3 kernel: [    0.519384] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 23:42:17 node-3 kernel: [    0.519386] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519400] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519429] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 23:42:17 node-3 kernel: [    0.519431] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519445] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519477] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 23:42:17 node-3 kernel: [    0.519479] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519482] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519486] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 23:42:17 node-3 kernel: [    0.519487] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519490] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519494] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 23:42:17 node-3 kernel: [    0.519498] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 23:42:17 node-3 kernel: [    0.519506] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 23:42:17 node-3 kernel: [    0.519510] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 23:42:17 node-3 kernel: [    0.519516] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 29 23:42:17 node-3 kernel: [    0.519517] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 29 23:42:17 node-3 kernel: [    0.519518] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 29 23:42:17 node-3 kernel: [    0.519519] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 29 23:42:17 node-3 kernel: [    0.519520] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 29 23:42:17 node-3 kernel: [    0.519520] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 29 23:42:17 node-3 kernel: [    0.519521] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 29 23:42:17 node-3 kernel: [    0.519522] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 29 23:42:17 node-3 kernel: [    0.519523] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519524] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519525] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519526] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519527] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519527] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519528] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519529] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519530] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-3 kernel: [    0.519531] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519532] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 29 23:42:17 node-3 kernel: [    0.519533] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 29 23:42:17 node-3 kernel: [    0.519534] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 29 23:42:17 node-3 kernel: [    0.519535] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 29 23:42:17 node-3 kernel: [    0.519537] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 29 23:42:17 node-3 kernel: [    0.519538] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 29 23:42:17 node-3 kernel: [    0.519576] NET: Registered protocol family 2
Jul 29 23:42:17 node-3 kernel: [    0.519839] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.520178] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.520323] TCP: Hash tables configured (established 262144 bind 65536)
Jul 29 23:42:17 node-3 kernel: [    0.520360] TCP: reno registered
Jul 29 23:42:17 node-3 kernel: [    0.520390] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.520486] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.520634] NET: Registered protocol family 1
Jul 29 23:42:17 node-3 kernel: [    0.560088] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 29 23:42:17 node-3 kernel: [    0.560102] PCI: CLS 64 bytes, default 64
Jul 29 23:42:17 node-3 kernel: [    0.560178] Trying to unpack rootfs image as initramfs...
Jul 29 23:42:17 node-3 kernel: [    0.779556] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 29 23:42:17 node-3 kernel: [    0.779606] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 29 23:42:17 node-3 kernel: [    0.779608] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 29 23:42:17 node-3 kernel: [    0.780047] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780053] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780058] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780064] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780075] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780093] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780108] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780124] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780135] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780145] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780151] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780157] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780166] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780179] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780192] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780205] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-3 kernel: [    0.780312] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 29 23:42:17 node-3 kernel: [    0.780318] Scanning for low memory corruption every 60 seconds
Jul 29 23:42:17 node-3 kernel: [    0.780717] Initialise system trusted keyring
Jul 29 23:42:17 node-3 kernel: [    0.780769] audit: initializing netlink socket (disabled)
Jul 29 23:42:17 node-3 kernel: [    0.780784] type=2000 audit(1469835701.732:1): initialized
Jul 29 23:42:17 node-3 kernel: [    0.798739] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 29 23:42:17 node-3 kernel: [    0.800260] zbud: loaded
Jul 29 23:42:17 node-3 kernel: [    0.800388] VFS: Disk quotas dquot_6.5.2
Jul 29 23:42:17 node-3 kernel: [    0.800421] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 29 23:42:17 node-3 kernel: [    0.800800] fuse init (API version 7.22)
Jul 29 23:42:17 node-3 kernel: [    0.800862] msgmni has been set to 32768
Jul 29 23:42:17 node-3 kernel: [    0.800909] Key type big_key registered
Jul 29 23:42:17 node-3 kernel: [    0.801420] Key type asymmetric registered
Jul 29 23:42:17 node-3 kernel: [    0.801422] Asymmetric key parser 'x509' registered
Jul 29 23:42:17 node-3 kernel: [    0.801447] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 29 23:42:17 node-3 kernel: [    0.801526] io scheduler noop registered
Jul 29 23:42:17 node-3 kernel: [    0.801528] io scheduler deadline registered (default)
Jul 29 23:42:17 node-3 kernel: [    0.801546] io scheduler cfq registered
Jul 29 23:42:17 node-3 kernel: [    0.801965] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    0.802089] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    0.802207] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    0.802317] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    0.802432] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    0.802529] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    0.802908] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 29 23:42:17 node-3 kernel: [    0.802934] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 29 23:42:17 node-3 kernel: [    0.802950] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 29 23:42:17 node-3 kernel: [    0.802959] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802961] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802964] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-3 kernel: [    0.802969] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802970] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802971] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802973] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802975] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802976] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802978] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802979] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802981] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802982] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802983] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802985] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802987] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-3 kernel: [    0.802992] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.802994] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-3 kernel: [    0.803009] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.803012] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-3 kernel: [    0.803022] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.803024] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-3 kernel: [    0.803027] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-3 kernel: [    0.803084] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 29 23:42:17 node-3 kernel: [    0.803091] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 29 23:42:17 node-3 kernel: [    0.803095] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 29 23:42:17 node-3 kernel: [    0.803104] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 29 23:42:17 node-3 kernel: [    0.803144] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 29 23:42:17 node-3 kernel: [    0.803146] vesafb: scrolling: redraw
Jul 29 23:42:17 node-3 kernel: [    0.803147] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 29 23:42:17 node-3 kernel: [    0.823689] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 29 23:42:17 node-3 kernel: [    0.832302] Console: switching to colour frame buffer device 80x30
Jul 29 23:42:17 node-3 kernel: [    0.841036] fb0: VESA VGA frame buffer device
Jul 29 23:42:17 node-3 kernel: [    0.841233] intel_idle: MWAIT substates: 0x2120
Jul 29 23:42:17 node-3 kernel: [    0.841234] intel_idle: v0.4 model 0x3F
Jul 29 23:42:17 node-3 kernel: [    0.841235] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 29 23:42:17 node-3 kernel: [    0.841459] ipmi message handler version 39.2
Jul 29 23:42:17 node-3 kernel: [    0.841735] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 29 23:42:17 node-3 kernel: [    0.842172] ACPI: AC Adapter [P111] (on-line)
Jul 29 23:42:17 node-3 kernel: [    0.847433] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 29 23:42:17 node-3 kernel: [    0.858473] ACPI: Power Button [PWRB]
Jul 29 23:42:17 node-3 kernel: [    0.864272] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 29 23:42:17 node-3 kernel: [    0.876060] ACPI: Power Button [PWRF]
Jul 29 23:42:17 node-3 kernel: [    0.889494] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 29 23:42:17 node-3 kernel: [    0.901167] pstore: Registered erst as persistent store backend
Jul 29 23:42:17 node-3 kernel: [    0.907352] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 29 23:42:17 node-3 kernel: [    0.919275] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 29 23:42:17 node-3 kernel: [    0.946011] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 29 23:42:17 node-3 kernel: [    0.979258] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 29 23:42:17 node-3 kernel: [    0.993260] Linux agpgart interface v0.103
Jul 29 23:42:17 node-3 kernel: [    1.000924] brd: module loaded
Jul 29 23:42:17 node-3 kernel: [    1.007955] loop: module loaded
Jul 29 23:42:17 node-3 kernel: [    1.014653] libphy: Fixed MDIO Bus: probed
Jul 29 23:42:17 node-3 kernel: [    1.021111] tun: Universal TUN/TAP device driver, 1.6
Jul 29 23:42:17 node-3 kernel: [    1.027574] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 29 23:42:17 node-3 kernel: [    1.034107] PPP generic driver version 2.4.2
Jul 29 23:42:17 node-3 kernel: [    1.040584] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 29 23:42:17 node-3 kernel: [    1.047144] ehci-pci: EHCI PCI platform driver
Jul 29 23:42:17 node-3 kernel: [    1.053660] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 29 23:42:17 node-3 kernel: [    1.060061] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 29 23:42:17 node-3 kernel: [    1.072583] ehci-pci 0000:00:1a.0: debug port 2
Jul 29 23:42:17 node-3 kernel: [    1.082782] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 29 23:42:17 node-3 kernel: [    1.082800] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 29 23:42:17 node-3 kernel: [    1.099495] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 29 23:42:17 node-3 kernel: [    1.105559] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 23:42:17 node-3 kernel: [    1.111727] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 23:42:17 node-3 kernel: [    1.123634] usb usb1: Product: EHCI Host Controller
Jul 29 23:42:17 node-3 kernel: [    1.129666] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 23:42:17 node-3 kernel: [    1.135707] usb usb1: SerialNumber: 0000:00:1a.0
Jul 29 23:42:17 node-3 kernel: [    1.141667] hub 1-0:1.0: USB hub found
Jul 29 23:42:17 node-3 kernel: [    1.147432] hub 1-0:1.0: 2 ports detected
Jul 29 23:42:17 node-3 kernel: [    1.153231] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 29 23:42:17 node-3 kernel: [    1.158804] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 29 23:42:17 node-3 kernel: [    1.169696] ehci-pci 0000:00:1d.0: debug port 2
Jul 29 23:42:17 node-3 kernel: [    1.179013] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 29 23:42:17 node-3 kernel: [    1.179016] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 29 23:42:17 node-3 kernel: [    1.195413] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 29 23:42:17 node-3 kernel: [    1.200612] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 23:42:17 node-3 kernel: [    1.205909] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 23:42:17 node-3 kernel: [    1.216462] usb usb2: Product: EHCI Host Controller
Jul 29 23:42:17 node-3 kernel: [    1.221912] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 23:42:17 node-3 kernel: [    1.227440] usb usb2: SerialNumber: 0000:00:1d.0
Jul 29 23:42:17 node-3 kernel: [    1.232946] hub 2-0:1.0: USB hub found
Jul 29 23:42:17 node-3 kernel: [    1.238292] hub 2-0:1.0: 2 ports detected
Jul 29 23:42:17 node-3 kernel: [    1.243584] ehci-platform: EHCI generic platform driver
Jul 29 23:42:17 node-3 kernel: [    1.248808] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 29 23:42:17 node-3 kernel: [    1.254108] ohci-pci: OHCI PCI platform driver
Jul 29 23:42:17 node-3 kernel: [    1.259385] ohci-platform: OHCI generic platform driver
Jul 29 23:42:17 node-3 kernel: [    1.264566] uhci_hcd: USB Universal Host Controller Interface driver
Jul 29 23:42:17 node-3 kernel: [    1.269935] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 29 23:42:17 node-3 kernel: [    1.463194] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 29 23:42:17 node-3 kernel: [    1.774997] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 29 23:42:17 node-3 kernel: [    1.791200] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 29 23:42:17 node-3 kernel: [    1.796780] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 23:42:17 node-3 kernel: [    1.802467] hub 1-1:1.0: USB hub found
Jul 29 23:42:17 node-3 kernel: [    1.807936] hub 1-1:1.0: 6 ports detected
Jul 29 23:42:17 node-3 kernel: [    1.922827] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 29 23:42:17 node-3 kernel: [    2.308492] i8042: No controller found
Jul 29 23:42:17 node-3 kernel: [    2.313998] mousedev: PS/2 mouse device common for all mice
Jul 29 23:42:17 node-3 kernel: [    2.319734] rtc_cmos 00:02: RTC can wake from S4
Jul 29 23:42:17 node-3 kernel: [    2.323320] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 29 23:42:17 node-3 kernel: [    2.323321] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 23:42:17 node-3 kernel: [    2.323833] hub 2-1:1.0: USB hub found
Jul 29 23:42:17 node-3 kernel: [    2.324066] hub 2-1:1.0: 8 ports detected
Jul 29 23:42:17 node-3 kernel: [    2.348053] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 29 23:42:17 node-3 kernel: [    2.353873] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 29 23:42:17 node-3 kernel: [    2.365158] device-mapper: uevent: version 1.0.3
Jul 29 23:42:17 node-3 kernel: [    2.370863] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 29 23:42:17 node-3 kernel: [    2.382216] ledtrig-cpu: registered to indicate activity on CPUs
Jul 29 23:42:17 node-3 kernel: [    2.388185] TCP: cubic registered
Jul 29 23:42:17 node-3 kernel: [    2.394049] NET: Registered protocol family 10
Jul 29 23:42:17 node-3 kernel: [    2.400105] NET: Registered protocol family 17
Jul 29 23:42:17 node-3 kernel: [    2.405886] Key type dns_resolver registered
Jul 29 23:42:17 node-3 kernel: [    2.411948] Loading compiled-in X.509 certificates
Jul 29 23:42:17 node-3 kernel: [    2.418163] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 29 23:42:17 node-3 kernel: [    2.429806] registered taskstats version 1
Jul 29 23:42:17 node-3 kernel: [    2.437858] Key type trusted registered
Jul 29 23:42:17 node-3 kernel: [    2.445459] Key type encrypted registered
Jul 29 23:42:17 node-3 kernel: [    2.450979] AppArmor: AppArmor sha1 policy hashing enabled
Jul 29 23:42:17 node-3 kernel: [    2.456558] IMA: No TPM chip found, activating TPM-bypass!
Jul 29 23:42:17 node-3 kernel: [    2.462767] regulator-dummy: disabling
Jul 29 23:42:17 node-3 kernel: [    2.468309]   Magic number: 8:759:707
Jul 29 23:42:17 node-3 kernel: [    2.473934] acpi LNXCPU:44: hash matches
Jul 29 23:42:17 node-3 kernel: [    2.479446] rtc_cmos 00:02: setting system clock to 2016-07-29 23:41:44 UTC (1469835704)
Jul 29 23:42:17 node-3 kernel: [    2.491878] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 29 23:42:17 node-3 kernel: [    2.497491] EDD information not available.
Jul 29 23:42:17 node-3 kernel: [    2.503034] PM: Hibernation image not present or could not be loaded.
Jul 29 23:42:17 node-3 kernel: [    2.503901] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 29 23:42:17 node-3 kernel: [    2.515114] Write protecting the kernel read-only data: 12288k
Jul 29 23:42:17 node-3 kernel: [    2.521478] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 29 23:42:17 node-3 kernel: [    2.534305] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 29 23:42:17 node-3 kernel: [    2.566834] device-mapper: multipath: version 1.6.0 loaded
Jul 29 23:42:17 node-3 kernel: [    2.574638] systemd-udevd[216]: starting version 204
Jul 29 23:42:17 node-3 kernel: [    2.598240] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 29 23:42:17 node-3 kernel: [    2.610238] md: linear personality registered for level -1
Jul 29 23:42:17 node-3 kernel: [    2.619207] md: multipath personality registered for level -4
Jul 29 23:42:17 node-3 kernel: [    2.627113] md: raid0 personality registered for level 0
Jul 29 23:42:17 node-3 kernel: [    2.635332] md: raid1 personality registered for level 1
Jul 29 23:42:17 node-3 kernel: [    2.645289] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 29 23:42:17 node-3 kernel: [    2.651360] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 29 23:42:17 node-3 kernel: [    2.651956] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 29 23:42:17 node-3 kernel: [    2.654606] megasas: FW now in Ready state
Jul 29 23:42:17 node-3 kernel: [    2.655085] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.655265] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.655428] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.655572] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.655698] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.655789] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.655849] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656015] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656102] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656163] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656296] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656373] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656549] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656697] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656808] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.656951] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.657918] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 29 23:42:17 node-3 kernel: [    2.690301] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-3 kernel: [    2.703346] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-3 kernel: [    2.710193] raid6: sse2x1   11355 MB/s
Jul 29 23:42:17 node-3 kernel: [    2.723685] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-3 kernel: [    2.730563] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.730569] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.730574] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.730579] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.730618] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.751013] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 29 23:42:17 node-3 kernel: [    2.756782] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-3 kernel: [    2.756802] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-3 kernel: [    2.756806] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-3 kernel: [    2.758570] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.758703] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.759327] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.759373] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.759465] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.773535] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-3 kernel: [    2.773562] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-3 kernel: [    2.773564] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-3 kernel: [    2.774428] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.774596] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.774707] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.774890] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.775165] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-3 kernel: [    2.778296] raid6: sse2x2   13604 MB/s
Jul 29 23:42:17 node-3 kernel: [    2.846276] raid6: sse2x4    9582 MB/s
Jul 29 23:42:17 node-3 kernel: [    2.864674] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 23:42:17 node-3 kernel: [    2.878060] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 29 23:42:17 node-3 kernel: [    2.884832] usb 2-1.4: Manufacturer: Avocent
Jul 29 23:42:17 node-3 kernel: [    2.891441] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 29 23:42:17 node-3 kernel: [    2.913970] raid6: avx2x1   14371 MB/s
Jul 29 23:42:17 node-3 kernel: [    2.985912] raid6: avx2x2   18857 MB/s
Jul 29 23:42:17 node-3 kernel: [    3.057842] raid6: avx2x4   21361 MB/s
Jul 29 23:42:17 node-3 kernel: [    3.063767] raid6: using algorithm avx2x4 (21361 MB/s)
Jul 29 23:42:17 node-3 kernel: [    3.069684] raid6: using avx2x2 recovery algorithm
Jul 29 23:42:17 node-3 kernel: [    3.075503] megasas:IOC Init cmd success
Jul 29 23:42:17 node-3 kernel: [    3.075505] Switched to clocksource tsc
Jul 29 23:42:17 node-3 kernel: [    3.087483] hidraw: raw HID events driver (C) Jiri Kosina
Jul 29 23:42:17 node-3 kernel: [    3.089140] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-3 kernel: [    3.089142] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-3 kernel: [    3.089143] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-3 kernel: [    3.089205] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    3.089237] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    3.089266] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    3.089301] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 29 23:42:17 node-3 kernel: [    3.089391] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-3 kernel: [    3.109816] megasas: INIT adapter done
Jul 29 23:42:17 node-3 kernel: [    3.139117] xor: automatically using best checksumming function:
Jul 29 23:42:17 node-3 kernel: [    3.147468] usbcore: registered new interface driver usbhid
Jul 29 23:42:17 node-3 kernel: [    3.152914] usbhid: USB HID core driver
Jul 29 23:42:17 node-3 kernel: [    3.159077] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 29 23:42:17 node-3 kernel: [    3.170102] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 29 23:42:17 node-3 kernel: [    3.181586] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 29 23:42:17 node-3 kernel: [    3.181717]    avx       : 35850.000 MB/sec
Jul 29 23:42:17 node-3 kernel: [    3.181869] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 29 23:42:17 node-3 kernel: [    3.183483] scsi0 : LSI SAS based MegaRAID driver
Jul 29 23:42:17 node-3 kernel: [    3.191171] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 23:42:17 node-3 kernel: [    3.223366] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 29 23:42:17 node-3 kernel: [    3.236307] async_tx: api initialized (async)
Jul 29 23:42:17 node-3 kernel: [    3.236328] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 29 23:42:17 node-3 kernel: [    3.236726] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 29 23:42:17 node-3 kernel: [    3.242274] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 23:42:17 node-3 kernel: [    3.246429] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 29 23:42:17 node-3 kernel: [    3.246629] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 29 23:42:17 node-3 kernel: [    3.246773] sd 0:2:0:0: [sda] Write Protect is off
Jul 29 23:42:17 node-3 kernel: [    3.246774] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 29 23:42:17 node-3 kernel: [    3.246840] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 29 23:42:17 node-3 kernel: [    3.274478]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 29 23:42:17 node-3 kernel: [    3.275970] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 29 23:42:17 node-3 kernel: [    3.345501] md: raid6 personality registered for level 6
Jul 29 23:42:17 node-3 kernel: [    3.352670] md: raid5 personality registered for level 5
Jul 29 23:42:17 node-3 kernel: [    3.359638] md: raid4 personality registered for level 4
Jul 29 23:42:17 node-3 kernel: [    3.369414] md: raid10 personality registered for level 10
Jul 29 23:42:17 node-3 kernel: [    3.423106] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Jul 29 23:42:17 node-3 kernel: [    3.487880] random: lvm urandom read with 34 bits of entropy available
Jul 29 23:42:17 node-3 kernel: [    3.625585] bio: create slab <bio-1> at 1
Jul 29 23:42:17 node-3 kernel: [    4.375128] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 23:42:17 node-3 kernel: [    4.935077] init: plymouth-upstart-bridge main process (552) terminated with status 1
Jul 29 23:42:17 node-3 kernel: [    4.947252] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 23:42:17 node-3 kernel: [    5.071169] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 29 23:42:17 node-3 kernel: [    5.086226] random: nonblocking pool is initialized
Jul 29 23:42:17 node-3 kernel: [    5.117020] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 29 23:42:17 node-3 kernel: [    5.236071] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 29 23:42:17 node-3 kernel: [    5.272011] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 29 23:42:17 node-3 kernel: [    5.317219] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 23:42:17 node-3 kernel: [    5.511420] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 29 23:42:17 node-3 kernel: [    5.546430] XFS (dm-0): Mounting Filesystem
Jul 29 23:42:17 node-3 kernel: [    5.768438] XFS (dm-0): Ending clean mount
Jul 29 23:42:17 node-3 kernel: [    5.826194] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 23:42:17 node-3 kernel: [    5.849358] XFS (dm-1): Mounting Filesystem
Jul 29 23:42:17 node-3 kernel: [    5.984526] XFS (dm-1): Ending clean mount
Jul 29 23:42:17 node-3 kernel: [    7.762392] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 23:42:17 node-3 kernel: [    7.788676] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 23:42:17 node-3 kernel: [    7.897590] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 29 23:42:17 node-3 kernel: [    7.897596] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 29 23:42:17 node-3 kernel: [    7.897601] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 29 23:42:17 node-3 kernel: [    7.897606] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 29 23:42:17 node-3 kernel: [    7.936646] systemd-udevd[774]: starting version 204
Jul 29 23:42:17 node-3 kernel: [    8.167930] wmi: Mapper loaded
Jul 29 23:42:17 node-3 kernel: [    8.178202] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 29 23:42:17 node-3 kernel: [    8.178209] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 23:42:17 node-3 kernel: [    8.178211] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 29 23:42:17 node-3 kernel: [    8.178214] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 23:42:17 node-3 kernel: [    8.178280] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 29 23:42:17 node-3 kernel: [    8.182523] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 29 23:42:17 node-3 kernel: [    8.184827] power_meter ACPI000D:00: Found ACPI power meter.
Jul 29 23:42:17 node-3 kernel: [    8.184862] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 29 23:42:17 node-3 kernel: [    8.210321] IPMI System Interface driver.
Jul 29 23:42:17 node-3 kernel: [    8.210361] ipmi_si: probing via ACPI
Jul 29 23:42:17 node-3 kernel: [    8.210375] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 29 23:42:17 node-3 kernel: [    8.210376] ipmi_si: Adding ACPI-specified kcs state machine
Jul 29 23:42:17 node-3 kernel: [    8.210386] ipmi_si: probing via SMBIOS
Jul 29 23:42:17 node-3 kernel: [    8.210387] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 23:42:17 node-3 kernel: [    8.210387] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 29 23:42:17 node-3 kernel: [    8.210389] ipmi_si: probing via SPMI
Jul 29 23:42:17 node-3 kernel: [    8.210389] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 23:42:17 node-3 kernel: [    8.210390] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 29 23:42:17 node-3 kernel: [    8.210391] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 29 23:42:17 node-3 kernel: [    8.285908] systemd-udevd[796]: renamed network interface eth1 to enp7s0
Jul 29 23:42:17 node-3 kernel: [    8.317838] systemd-udevd[809]: renamed network interface eth0 to enp6s0
Jul 29 23:42:17 node-3 kernel: [    8.358308] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 29 23:42:17 node-3 kernel: [    8.358313] ipmi_si 00:09: IPMI kcs interface initialized
Jul 29 23:42:17 node-3 kernel: [    8.359630] systemd-udevd[815]: renamed network interface eth3 to enp9s0
Jul 29 23:42:17 node-3 kernel: [    8.389714] systemd-udevd[814]: renamed network interface eth2 to enp8s0
Jul 29 23:42:17 node-3 kernel: [    8.623975] type=1400 audit(1469835710.643:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1032 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.624146] type=1400 audit(1469835710.643:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1032 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.624279] type=1400 audit(1469835710.643:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1032 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.634267] type=1400 audit(1469835710.655:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1031 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.634407] type=1400 audit(1469835710.655:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1031 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.634526] type=1400 audit(1469835710.655:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1031 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.635927] type=1400 audit(1469835710.655:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1034 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.636078] type=1400 audit(1469835710.655:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1034 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.636196] type=1400 audit(1469835710.655:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1034 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    8.637021] type=1400 audit(1469835710.655:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1035 comm="apparmor_parser"
Jul 29 23:42:17 node-3 kernel: [    9.180230] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 23:42:17 node-3 kernel: [    9.194675] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 23:42:17 node-3 kernel: [    9.368682] enic 0000:06:00.0 enp6s0: Link UP
Jul 29 23:42:17 node-3 kernel: [   18.649487] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 23:42:18 node-3 failsafe: Failsafe of 120 seconds reached.
Jul 29 23:42:18 node-3 kernel: [   37.705451] init: failsafe main process (8398) killed by TERM signal
Jul 29 23:42:18 node-3 dbus[8441]: [system] AppArmor D-Bus mediation is enabled
Jul 29 23:42:19 node-3 kernel: [   37.928526] audit_printk_skb: 30 callbacks suppressed
Jul 29 23:42:19 node-3 kernel: [   37.928527] type=1400 audit(1469835739.041:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8526 comm="apparmor_parser"
Jul 29 23:42:19 node-3 kernel: [   37.928796] type=1400 audit(1469835739.041:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8525 comm="apparmor_parser"
Jul 29 23:42:19 node-3 kernel: [   37.928800] type=1400 audit(1469835739.041:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8525 comm="apparmor_parser"
Jul 29 23:42:19 node-3 kernel: [   37.928802] type=1400 audit(1469835739.041:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8525 comm="apparmor_parser"
Jul 29 23:42:19 node-3 kernel: [   37.929036] type=1400 audit(1469835739.041:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8525 comm="apparmor_parser"
Jul 29 23:42:19 node-3 kernel: [   37.929037] type=1400 audit(1469835739.041:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8525 comm="apparmor_parser"
Jul 29 23:42:19 node-3 kernel: [   37.929149] type=1400 audit(1469835739.041:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8525 comm="apparmor_parser"
Jul 29 23:42:19 node-3 kernel: [   38.048188] type=1400 audit(1469835739.161:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8528 comm="apparmor_parser"
Jul 29 23:42:19 node-3 cron[8557]: (CRON) INFO (pidfile fd = 3)
Jul 29 23:42:19 node-3 anacron[8574]: Anacron 2.3 started on 2016-07-29
Jul 29 23:42:19 node-3 cron[8582]: (CRON) STARTUP (fork ok)
Jul 29 23:42:19 node-3 cron[8582]: (CRON) INFO (Running @reboot jobs)
Jul 29 23:42:19 node-3 anacron[8574]: Will run job `cron.daily' in 5 min.
Jul 29 23:42:19 node-3 anacron[8574]: Will run job `cron.weekly' in 10 min.
Jul 29 23:42:19 node-3 anacron[8574]: Will run job `cron.monthly' in 15 min.
Jul 29 23:42:19 node-3 anacron[8574]: Jobs will be executed sequentially
Jul 29 23:42:19 node-3 multipathd: path checkers start up
Jul 29 23:42:19 node-3 postfix/master[8735]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 29 23:42:22 node-3 puppet-agent[8920]: Reopening log files
Jul 29 23:42:23 node-3 puppet-agent[8920]: Could not request certificate: Connection refused - connect(2)
Jul 29 23:42:38 node-3 puppet-user[9128]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 29 23:42:38 node-3 puppet-user[9128]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 29 23:42:39 node-3 puppet-user[9128]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 29 23:42:39 node-3 puppet-user[9128]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 29 23:42:39 node-3 puppet-user[9128]: Finished catalog run in 0.96 seconds
Jul 29 23:42:40 node-3 multipathd: uevent trigger error
Jul 29 23:42:41 node-3 puppet-user[9661]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 23:42:41 node-3 puppet-user[9661]: Compiled catalog for node-3.domain.tld in environment production in 0.09 seconds
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 29 23:42:41 node-3 puppet-user[9661]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 29 23:42:41 node-3 puppet-user[9661]: Finished catalog run in 0.05 seconds
Jul 29 23:42:42 node-3 puppet-user[10210]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 29 23:42:42 node-3 puppet-user[10210]: Compiled catalog for node-3.domain.tld in environment production in 0.07 seconds
Jul 29 23:42:42 node-3 puppet-user[10210]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 29 23:42:42 node-3 puppet-user[10210]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 29 23:42:42 node-3 puppet-user[10210]: Finished catalog run in 0.03 seconds
Jul 29 23:42:44 node-3 puppet-user[10673]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 29 23:42:44 node-3 puppet-user[10673]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 29 23:42:44 node-3 puppet-user[10673]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 29 23:42:44 node-3 puppet-user[10673]: Finished catalog run in 0.04 seconds
Jul 29 23:42:45 node-3 puppet-user[11130]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 29 23:42:45 node-3 puppet-user[11130]: Compiled catalog for node-3.domain.tld in environment production in 0.18 seconds
Jul 29 23:42:45 node-3 puppet-user[11130]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 29 23:42:46 node-3 puppet-user[11130]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Jul 29 23:42:46 node-3 puppet-user[11130]: Finished catalog run in 0.42 seconds
Jul 29 23:42:47 node-3 puppet-user[11614]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 29 23:42:47 node-3 puppet-user[11614]: Compiled catalog for node-3.domain.tld in environment production in 0.20 seconds
Jul 29 23:42:47 node-3 puppet-user[11614]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 29 23:42:47 node-3 puppet-user[11614]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 29 23:42:47 node-3 puppet-user[11614]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Jul 29 23:42:48 node-3 puppet-user[11614]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 29 23:42:48 node-3 puppet-user[11614]: Finished catalog run in 0.22 seconds
Jul 29 23:42:49 node-3 puppet-user[12093]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 29 23:42:49 node-3 puppet-user[12093]: Compiled catalog for node-3.domain.tld in environment production in 0.15 seconds
Jul 29 23:42:49 node-3 puppet-user[12093]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 29 23:42:49 node-3 kernel: [   68.187112] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 29 23:42:49 node-3 kernel: [   68.187163] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 29 23:42:49 node-3 puppet-user[12093]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 29 23:42:49 node-3 puppet-user[12093]: Finished catalog run in 0.05 seconds
Jul 29 23:42:51 node-3 puppet-user[12554]: (Scope(Class[main])) MODULAR: sync_time
Jul 29 23:42:51 node-3 puppet-user[12554]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 29 23:42:51 node-3 ntpdate[12970]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 29 23:42:52 node-3 kernel: [   70.636635] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 23:42:52 node-3 puppet-agent[8920]: Could not run: SIGTERM
Jul 29 23:42:52 node-3 kernel: [   70.954398] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 23:42:52 node-3 ec2: 
Jul 29 23:42:52 node-3 ec2: #############################################################
Jul 29 23:42:52 node-3 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 29 23:42:52 node-3 ec2: 1024 be:a2:17:98:86:5f:b7:b1:e0:6a:28:51:d0:bd:63:0a  root@node-3.domain.tld (DSA)
Jul 29 23:42:52 node-3 ec2: 256 9f:1e:35:c3:9c:46:33:07:f9:34:d8:81:35:ed:87:16  root@node-3.domain.tld (ECDSA)
Jul 29 23:42:52 node-3 ec2: 256 92:8b:a4:db:73:47:1e:c5:8f:43:a6:8f:07:73:6d:b8  root@node-3.domain.tld (ED25519)
Jul 29 23:42:52 node-3 ec2: 2048 56:3c:7e:cc:6a:4d:a0:2a:b1:c3:b1:12:7a:4e:06:66  root@node-3.domain.tld (RSA)
Jul 29 23:42:52 node-3 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 29 23:42:52 node-3 ec2: #############################################################
Jul 29 23:42:57 node-3 ntpdate[12970]: adjust time server 10.20.0.2 offset 0.000876 sec
Jul 29 23:42:57 node-3 puppet-user[12554]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 29 23:42:57 node-3 puppet-user[12554]: Finished catalog run in 6.17 seconds
Jul 29 23:43:01 node-3 CRON[13301]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:43:11 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:43:12 node-3 nailgun-agent: I, [2016-07-29T23:43:12.001578 #13304]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:43:24 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:43:24 node-3 nailgun-agent: I, [2016-07-29T23:43:24.924005 #13304]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 29 23:44:01 node-3 CRON[13642]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:44:20 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:44:20 node-3 nailgun-agent: I, [2016-07-29T23:44:20.097518 #13645]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:44:32 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:44:33 node-3 nailgun-agent: I, [2016-07-29T23:44:33.073087 #13645]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 29 23:45:01 node-3 CRON[13955]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:45:21 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:45:21 node-3 nailgun-agent: I, [2016-07-29T23:45:21.253213 #13958]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:45:34 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:45:34 node-3 nailgun-agent: I, [2016-07-29T23:45:34.238079 #13958]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 29 23:46:01 node-3 CRON[14268]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:46:06 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:46:06 node-3 nailgun-agent: I, [2016-07-29T23:46:06.421211 #14271]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:46:06 node-3 puppet-user[14298]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 23:46:06 node-3 puppet-user[14298]: Compiled catalog for node-3.domain.tld in environment production in 0.11 seconds
Jul 29 23:46:06 node-3 puppet-user[14298]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 29 23:46:06 node-3 puppet-user[14298]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Jul 29 23:46:06 node-3 puppet-user[14298]: Finished catalog run in 0.08 seconds
Jul 29 23:46:08 node-3 puppet-user[14881]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 29 23:46:09 node-3 puppet-user[14881]: Compiled catalog for node-3.domain.tld in environment production in 1.27 seconds
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 29 23:46:10 node-3 puppet-user[14881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 29 23:46:19 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:46:19 node-3 nailgun-agent: I, [2016-07-29T23:46:19.340361 #14271]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 29 23:46:26 node-3 puppet-user[14881]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 29 23:46:26 node-3 puppet-user[14881]: Finished catalog run in 16.94 seconds
Jul 29 23:46:29 node-3 puppet-user[16001]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 29 23:46:29 node-3 puppet-user[16001]: Compiled catalog for node-3.domain.tld in environment production in 0.15 seconds
Jul 29 23:46:33 node-3 puppet-user[16001]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 29 23:47:01 node-3 CRON[18312]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:47:03 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:47:03 node-3 nailgun-agent: I, [2016-07-29T23:47:03.531999 #18315]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:47:05 node-3 puppet-user[16001]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 29 23:47:05 node-3 puppet-user[16001]: Finished catalog run in 36.32 seconds
Jul 29 23:47:07 node-3 puppet-user[18695]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 29 23:47:07 node-3 puppet-user[18695]: Compiled catalog for node-3.domain.tld in environment production in 0.56 seconds
Jul 29 23:47:08 node-3 puppet-user[18695]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 29 23:47:08 node-3 puppet-user[18695]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 29 23:47:08 node-3 puppet-user[18695]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 29 23:47:08 node-3 puppet-user[18695]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 29 23:47:08 node-3 puppet-user[18695]: Finished catalog run in 0.07 seconds
Jul 29 23:47:09 node-3 puppet-user[19163]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 29 23:47:10 node-3 puppet-user[19163]: Compiled catalog for node-3.domain.tld in environment production in 0.80 seconds
Jul 29 23:47:10 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 29 23:47:11 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 29 23:47:11 node-3 crontab[19604]: (root) LIST (root)
Jul 29 23:47:11 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 29 23:47:11 node-3 crontab[19605]: (root) REPLACE (root)
Jul 29 23:47:13 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 29 23:47:14 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 29 23:47:15 node-3 puppet-user[19163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 29 23:47:15 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:15 node-3 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 29 23:47:17 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:17 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:17 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:17 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:39 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:39 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:39 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:39 node-3 multipathd: uevent trigger error
<27>Jul 29 23:47:40 node-3 multipathd: uevent trigger error
<27>Jul 29 23:48:40 node-3 ntpdate[31771]: no servers can be used, exiting
<27>Jul 29 23:49:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:14 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:29 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:29 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:29 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:29 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:29 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:29 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:36 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:36 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:36 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:36 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:36 node-3 multipathd: uevent trigger error
<43>Jul 29 23:49:55 node-3 apache2_error [Fri Jul 29 23:49:48.570178 2016] [mpm_event:notice] [pid 9576:tid 140149090957184] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 23:49:55 node-3 apache2_error [Fri Jul 29 23:49:48.570315 2016] [core:notice] [pid 9576:tid 140149090957184] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 23:49:55 node-3 apache2_error [Fri Jul 29 23:49:51.648841 2016] [mpm_event:notice] [pid 9576:tid 140149090957184] AH00491: caught SIGTERM, shutting down
<43>Jul 29 23:49:55 node-3 apache2_error [Fri Jul 29 23:49:52.741679 2016] [mpm_worker:notice] [pid 9952:tid 140159215470464] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 23:49:55 node-3 apache2_error [Fri Jul 29 23:49:52.741724 2016] [core:notice] [pid 9952:tid 140159215470464] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 23:49:56 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:56 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:56 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:56 node-3 multipathd: uevent trigger error
<27>Jul 29 23:49:56 node-3 multipathd: uevent trigger error
<27>Jul 29 23:50:33 node-3 multipathd: uevent trigger error
<27>Jul 29 23:50:33 node-3 multipathd: uevent trigger error
<27>Jul 29 23:50:33 node-3 multipathd: uevent trigger error
<27>Jul 29 23:50:33 node-3 multipathd: uevent trigger error
<27>Jul 29 23:50:33 node-3 multipathd: uevent trigger error
<43>Jul 29 23:50:35 node-3 apache2_error [Fri Jul 29 23:50:30.182387 2016] [mpm_worker:notice] [pid 9952:tid 140159215470464] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 23:50:35 node-3 apache2_error [Fri Jul 29 23:50:30.190134 2016] [mpm_worker:warn] [pid 9952:tid 140159215470464] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 23:50:35 node-3 apache2_error [Fri Jul 29 23:50:30.190855 2016] [mpm_worker:notice] [pid 9952:tid 140159215470464] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 23:50:35 node-3 apache2_error [Fri Jul 29 23:50:30.190866 2016] [core:notice] [pid 9952:tid 140159215470464] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 23:51:13 node-3 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 29 23:51:13 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:13 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:13 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:13 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:13 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:16 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:16 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:16 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:16 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:16 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:23 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:23 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:23 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:23 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:23 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:30 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:30 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:30 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:30 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:30 node-3 multipathd: uevent trigger error
<129>Jul 29 23:51:33 node-3 haproxy[22868]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:51:35 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:35 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:35 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:35 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:35 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:39 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:39 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:39 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:39 node-3 multipathd: uevent trigger error
<129>Jul 29 23:51:42 node-3 haproxy[25039]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:43 node-3 haproxy[25039]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:51:44 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:44 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:44 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:44 node-3 multipathd: uevent trigger error
<129>Jul 29 23:51:46 node-3 haproxy[26211]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:47 node-3 haproxy[26220]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:48 node-3 haproxy[26220]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:51:49 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:49 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:49 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:49 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:49 node-3 multipathd: uevent trigger error
<129>Jul 29 23:51:52 node-3 haproxy[27368]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:52 node-3 haproxy[27368]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:52 node-3 haproxy[27368]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:53 node-3 haproxy[27377]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:53 node-3 haproxy[27377]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:51:54 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:54 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:54 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:54 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:54 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:54 node-3 multipathd: uevent trigger error
<129>Jul 29 23:51:57 node-3 haproxy[28511]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:57 node-3 haproxy[28511]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:57 node-3 haproxy[28511]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:58 node-3 haproxy[28515]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:58 node-3 haproxy[28515]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:51:58 node-3 haproxy[28515]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:51:59 node-3 multipathd: uevent trigger error
<27>Jul 29 23:51:59 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:00 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:00 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:00 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:00 node-3 haproxy[28515]: 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>Jul 29 23:52:00 node-3 haproxy[28515]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:00 node-3 haproxy[28515]: proxy aodh has no server available!
<129>Jul 29 23:52:02 node-3 haproxy[29675]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:02 node-3 haproxy[29675]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:02 node-3 haproxy[29675]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:03 node-3 haproxy[29679]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:03 node-3 haproxy[29679]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:03 node-3 haproxy[29679]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:04 node-3 haproxy[29679]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:05 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:05 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:05 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:05 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:05 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:05 node-3 haproxy[29679]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:05 node-3 haproxy[29679]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:05 node-3 haproxy[29679]: proxy aodh has no server available!
<129>Jul 29 23:52:05 node-3 haproxy[29679]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:06 node-3 haproxy[29679]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:06 node-3 haproxy[29679]: proxy ceilometer has no server available!
<129>Jul 29 23:52:07 node-3 haproxy[30815]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:08 node-3 haproxy[30823]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:08 node-3 haproxy[30823]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:08 node-3 haproxy[30823]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:08 node-3 haproxy[30823]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:09 node-3 haproxy[30823]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:09 node-3 haproxy[30823]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:10 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:10 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:10 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:10 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:10 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:11 node-3 haproxy[30823]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:11 node-3 haproxy[30823]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:11 node-3 haproxy[30823]: proxy aodh has no server available!
<129>Jul 29 23:52:11 node-3 haproxy[30823]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:11 node-3 haproxy[30823]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:11 node-3 haproxy[30823]: proxy ceilometer has no server available!
<129>Jul 29 23:52:13 node-3 haproxy[31958]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:13 node-3 haproxy[31958]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:13 node-3 haproxy[31958]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:13 node-3 haproxy[31958]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:14 node-3 haproxy[31958]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:14 node-3 haproxy[31958]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:14 node-3 haproxy[31958]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:14 node-3 haproxy[31958]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:14 node-3 haproxy[31958]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:15 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:15 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:16 node-3 haproxy[31958]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:16 node-3 haproxy[31958]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:16 node-3 haproxy[31958]: proxy aodh has no server available!
<129>Jul 29 23:52:16 node-3 haproxy[31958]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:16 node-3 haproxy[31958]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:16 node-3 haproxy[31958]: proxy ceilometer has no server available!
<129>Jul 29 23:52:18 node-3 haproxy[726]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:18 node-3 haproxy[726]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:18 node-3 haproxy[726]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:19 node-3 haproxy[730]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:19 node-3 haproxy[730]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:19 node-3 haproxy[730]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:19 node-3 haproxy[730]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:19 node-3 haproxy[730]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:19 node-3 haproxy[730]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:20 node-3 haproxy[730]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:20 node-3 haproxy[730]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:20 node-3 haproxy[730]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:21 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:21 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:21 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:21 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:21 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:21 node-3 haproxy[730]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:21 node-3 haproxy[730]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:21 node-3 haproxy[730]: proxy glance-registry has no server available!
<129>Jul 29 23:52:21 node-3 haproxy[730]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:22 node-3 haproxy[730]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:22 node-3 haproxy[730]: proxy aodh has no server available!
<129>Jul 29 23:52:22 node-3 haproxy[730]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:22 node-3 haproxy[730]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:22 node-3 haproxy[730]: proxy ceilometer has no server available!
<129>Jul 29 23:52:24 node-3 haproxy[2012]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:24 node-3 haproxy[2012]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:24 node-3 haproxy[2012]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:24 node-3 haproxy[2012]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:24 node-3 haproxy[2012]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:24 node-3 haproxy[2012]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:25 node-3 haproxy[2016]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:25 node-3 haproxy[2016]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:25 node-3 haproxy[2016]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:25 node-3 haproxy[2016]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:25 node-3 haproxy[2016]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:25 node-3 haproxy[2016]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:25 node-3 haproxy[2016]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:26 node-3 haproxy[2016]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:26 node-3 haproxy[2016]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:26 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:26 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:27 node-3 haproxy[2016]: proxy glance-registry has no server available!
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:27 node-3 haproxy[2016]: proxy aodh has no server available!
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:27 node-3 haproxy[2016]: proxy ceilometer has no server available!
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:27 node-3 haproxy[2016]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:27 node-3 haproxy[2016]: proxy nova-novncproxy has no server available!
<129>Jul 29 23:52:29 node-3 haproxy[3176]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:29 node-3 haproxy[3176]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:29 node-3 haproxy[3176]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:29 node-3 haproxy[3176]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:29 node-3 haproxy[3176]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:29 node-3 haproxy[3176]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-3 haproxy[3182]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:31 node-3 haproxy[3182]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:31 node-3 haproxy[3182]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:32 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:32 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:32 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:32 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:32 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:32 node-3 haproxy[3182]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:32 node-3 haproxy[3182]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:32 node-3 haproxy[3182]: proxy glance-registry has no server available!
<129>Jul 29 23:52:32 node-3 haproxy[3182]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:32 node-3 haproxy[3182]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:32 node-3 haproxy[3182]: proxy aodh has no server available!
<129>Jul 29 23:52:32 node-3 haproxy[3182]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:32 node-3 haproxy[3182]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:32 node-3 haproxy[3182]: proxy ceilometer has no server available!
<129>Jul 29 23:52:32 node-3 haproxy[3182]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:33 node-3 haproxy[3182]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:33 node-3 haproxy[3182]: proxy nova-novncproxy has no server available!
<129>Jul 29 23:52:34 node-3 haproxy[4379]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:34 node-3 haproxy[4379]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-3 haproxy[4386]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-3 haproxy[4386]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:37 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:37 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:37 node-3 haproxy[4386]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:37 node-3 haproxy[4386]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:37 node-3 haproxy[4386]: proxy glance-registry has no server available!
<129>Jul 29 23:52:37 node-3 haproxy[4386]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:38 node-3 haproxy[4386]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:38 node-3 haproxy[4386]: proxy aodh has no server available!
<129>Jul 29 23:52:38 node-3 haproxy[4386]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:38 node-3 haproxy[4386]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:38 node-3 haproxy[4386]: proxy ceilometer has no server available!
<129>Jul 29 23:52:38 node-3 haproxy[4386]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:38 node-3 haproxy[4386]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:38 node-3 haproxy[4386]: proxy nova-novncproxy has no server available!
<27>Jul 29 23:52:40 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:40 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:40 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:40 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:40 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:43 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:43 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-3 multipathd: uevent trigger error
<129>Jul 29 23:52:44 node-3 haproxy[4386]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:44 node-3 haproxy[4386]: Server keystone-1/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:44 node-3 haproxy[4386]: proxy keystone-1 has no server available!
<129>Jul 29 23:52:44 node-3 haproxy[4386]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:44 node-3 haproxy[4386]: Server keystone-2/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:44 node-3 haproxy[4386]: proxy keystone-2 has no server available!
<129>Jul 29 23:52:44 node-3 haproxy[4386]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:45 node-3 haproxy[4386]: Server nova-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy nova-api has no server available!
<129>Jul 29 23:52:45 node-3 haproxy[4386]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:45 node-3 haproxy[4386]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy nova-metadata-api has no server available!
<129>Jul 29 23:52:45 node-3 haproxy[4386]: 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>Jul 29 23:52:45 node-3 haproxy[4386]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy cinder-api has no server available!
<129>Jul 29 23:52:45 node-3 haproxy[4386]: 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>Jul 29 23:52:45 node-3 haproxy[4386]: Server glance-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy glance-api has no server available!
<129>Jul 29 23:52:45 node-3 haproxy[4386]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:45 node-3 haproxy[4386]: Server glance-glare/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy glance-glare has no server available!
<129>Jul 29 23:52:45 node-3 haproxy[4386]: 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>Jul 29 23:52:45 node-3 haproxy[4386]: Server neutron/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy neutron has no server available!
<129>Jul 29 23:52:45 node-3 haproxy[4386]: 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>Jul 29 23:52:45 node-3 haproxy[4386]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy mysqld has no server available!
<129>Jul 29 23:52:45 node-3 haproxy[4386]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:45 node-3 haproxy[4386]: Server object-storage/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:45 node-3 haproxy[4386]: proxy object-storage has no server available!
<27>Jul 29 23:52:45 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 29 23:52:46 node-3 haproxy[4386]: 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>Jul 29 23:52:46 node-3 haproxy[4386]: Server heat-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:46 node-3 haproxy[4386]: proxy heat-api has no server available!
<129>Jul 29 23:52:46 node-3 haproxy[4386]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:46 node-3 haproxy[4386]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:46 node-3 haproxy[4386]: proxy heat-api-cfn has no server available!
<129>Jul 29 23:52:46 node-3 haproxy[4386]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:46 node-3 haproxy[4386]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:46 node-3 haproxy[4386]: proxy heat-api-cloudwatch has no server available!
<27>Jul 29 23:52:48 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:48 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:48 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:48 node-3 multipathd: uevent trigger error
<27>Jul 29 23:52:48 node-3 multipathd: uevent trigger error
<27>Jul 29 23:53:06 node-3 multipathd: uevent trigger error
<27>Jul 29 23:53:42 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 23:53:42 node-3 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 29 23:53:47 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 23:53:47 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 23:53:47 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 23:54:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-3 multipathd: uevent trigger error
<27>Jul 29 23:54:17 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 23:54:46 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 29 23:54:48 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 29 23:56:27 node-3 multipathd: uevent trigger error
<27>Jul 29 23:56:27 node-3 multipathd: uevent trigger error
<27>Jul 29 23:56:27 node-3 multipathd: uevent trigger error
<27>Jul 29 23:56:27 node-3 multipathd: uevent trigger error
<27>Jul 29 23:56:27 node-3 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-3 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-3 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-3 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-3 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-3 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-3 multipathd: uevent trigger error
<43>Jul 30 00:01:06 node-3 apache2_error [Sat Jul 30 00:01:03.390709 2016] [mpm_worker:notice] [pid 9952:tid 140159215470464] AH00295: caught SIGTERM, shutting down
<43>Jul 30 00:01:06 node-3 apache2_error [Sat Jul 30 00:01:04.142464 2016] [mpm_worker:notice] [pid 10334:tid 140659329759104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:01:06 node-3 apache2_error [Sat Jul 30 00:01:04.142489 2016] [core:notice] [pid 10334:tid 140659329759104] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 00:01:36 node-3 apache2_error [Sat Jul 30 00:01:36.154098 2016] [mpm_worker:notice] [pid 10334:tid 140659329759104] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 00:01:36 node-3 apache2_error [Sat Jul 30 00:01:36.171655 2016] [mpm_worker:warn] [pid 10334:tid 140659329759104] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 00:01:36 node-3 apache2_error [Sat Jul 30 00:01:36.175885 2016] [mpm_worker:notice] [pid 10334:tid 140659329759104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:01:36 node-3 apache2_error [Sat Jul 30 00:01:36.175901 2016] [core:notice] [pid 10334:tid 140659329759104] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 00:01:41 node-3 multipathd: uevent trigger error
<27>Jul 30 00:01:41 node-3 multipathd: uevent trigger error
<27>Jul 30 00:01:41 node-3 multipathd: uevent trigger error
<27>Jul 30 00:01:41 node-3 multipathd: uevent trigger error
<27>Jul 30 00:01:41 node-3 multipathd: uevent trigger error
<27>Jul 30 00:02:32 node-3 multipathd: uevent trigger error
<27>Jul 30 00:02:32 node-3 multipathd: uevent trigger error
<27>Jul 30 00:02:32 node-3 multipathd: uevent trigger error
<27>Jul 30 00:02:32 node-3 multipathd: uevent trigger error
<27>Jul 30 00:02:32 node-3 multipathd: uevent trigger error
<27>Jul 30 00:03:44 node-3 multipathd: uevent trigger error
<27>Jul 30 00:03:44 node-3 multipathd: uevent trigger error
<27>Jul 30 00:03:44 node-3 multipathd: uevent trigger error
<27>Jul 30 00:03:44 node-3 multipathd: uevent trigger error
<27>Jul 30 00:09:17 node-3 multipathd: uevent trigger error
<27>Jul 30 00:09:17 node-3 multipathd: uevent trigger error
<27>Jul 30 00:09:17 node-3 multipathd: uevent trigger error
<27>Jul 30 00:09:17 node-3 multipathd: uevent trigger error
<27>Jul 30 00:09:17 node-3 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:12:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:12:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:12:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:12:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:12:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:12:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:12:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:36 node-3 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 30 00:13:36 node-3 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 30 00:13:36 node-3 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 30 00:13:37 node-3 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 30 00:13:37 node-3 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 30 00:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-3 multipathd: uevent trigger error
<43>Jul 30 00:14:27 node-3 apache2_error [Sat Jul 30 00:14:25.786556 2016] [mpm_worker:notice] [pid 10334:tid 140659329759104] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 00:14:27 node-3 apache2_error [Sat Jul 30 00:14:26.171803 2016] [mpm_worker:warn] [pid 10334:tid 140659329759104] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 00:14:27 node-3 apache2_error [Sat Jul 30 00:14:26.176836 2016] [mpm_worker:notice] [pid 10334:tid 140659329759104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:14:27 node-3 apache2_error [Sat Jul 30 00:14:26.176853 2016] [core:notice] [pid 10334:tid 140659329759104] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 00:15:07 node-3 apache2_error [Sat Jul 30 00:15:03.047447 2016] [mpm_worker:notice] [pid 10334:tid 140659329759104] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 00:15:07 node-3 apache2_error [Sat Jul 30 00:15:03.434664 2016] [mpm_worker:warn] [pid 10334:tid 140659329759104] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 00:15:07 node-3 apache2_error [Sat Jul 30 00:15:03.448875 2016] [mpm_worker:notice] [pid 10334:tid 140659329759104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:15:07 node-3 apache2_error [Sat Jul 30 00:15:03.448913 2016] [core:notice] [pid 10334:tid 140659329759104] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 00:15:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:25 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:25 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:25 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:25 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:15:30 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:12 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:12 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:12 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:12 node-3 multipathd: uevent trigger error
<27>Jul 30 00:16:12 node-3 multipathd: uevent trigger error
<27>Jul 30 00:17:06 node-3 multipathd: uevent trigger error
<27>Jul 30 00:17:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:17:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:17:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:17:07 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:13 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:13 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-3 multipathd: uevent trigger error
<11>Jul 30 00:18:23 node-3 liberasurecode[13337]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-3 liberasurecode[13337]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-3 liberasurecode[13337]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-3 liberasurecode[13337]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-3 liberasurecode[13364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-3 liberasurecode[13364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-3 liberasurecode[13364]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-3 liberasurecode[13364]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-3 liberasurecode[13789]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-3 liberasurecode[13789]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-3 liberasurecode[13789]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-3 liberasurecode[13789]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16808]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16808]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16884]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16884]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16884]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:30 node-3 liberasurecode[16884]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[16930]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[16930]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[16930]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[16930]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17029]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17029]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17029]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17029]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17043]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17043]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17043]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17043]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17073]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17073]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17073]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17073]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17058]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17058]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17058]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-3 liberasurecode[17058]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 00:18:37 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:37 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:37 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:37 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-3 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-3 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-3 multipathd: uevent trigger error
<11>Jul 30 00:20:01 node-3 liberasurecode[32715]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:20:01 node-3 liberasurecode[32715]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:20:01 node-3 liberasurecode[32715]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:20:01 node-3 liberasurecode[32715]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 00:21:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-3 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:22 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:22 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:22 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:22 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:22 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:27 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:27 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:27 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:27 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:40 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:40 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:40 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:40 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:40 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:45 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:45 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:45 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:45 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:45 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:54 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:54 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:54 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:54 node-3 multipathd: uevent trigger error
<27>Jul 30 00:22:54 node-3 multipathd: uevent trigger error
<11>Jul 30 00:25:01 node-3 liberasurecode[18327]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:25:01 node-3 liberasurecode[18327]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:25:01 node-3 liberasurecode[18327]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:25:01 node-3 liberasurecode[18327]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
