Sep 17 20:18:16 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] start
Sep 17 20:18:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 17 20:18:16 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 17 20:18:16 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 17 20:18:16 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 17 20:18:16 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 17 20:18:16 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 17 20:18:16 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 17 20:18:16 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=fea696b0-f7c7-4d62-a462-bff3e77c4446 nomdmonddf nomdmonisw
Sep 17 20:18:16 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 17 20:18:16 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 17 20:18:16 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 17 20:18:16 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 17 20:18:16 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 17 20:18:16 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 17 20:18:16 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 17 20:18:16 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Sep 17 20:18:16 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 17 20:18:16 node-1 kernel: [    0.000000] No AGP bridge found
Sep 17 20:18:16 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 17 20:18:16 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 17 20:18:16 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 17 20:18:16 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 17 20:18:16 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 17 20:18:16 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 17 20:18:16 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 17 20:18:16 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 17 20:18:16 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 17 20:18:16 node-1 kernel: [    0.000000]   2 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000]   3 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000]   4 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000]   5 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000]   6 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000]   7 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000]   8 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000]   9 disabled
Sep 17 20:18:16 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 17 20:18:16 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 17 20:18:16 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 17 20:18:16 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 17 20:18:16 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 17 20:18:16 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 17 20:18:16 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 17 20:18:16 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 17 20:18:16 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 17 20:18:16 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 17 20:18:16 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 17 20:18:16 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 17 20:18:16 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 17 20:18:16 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 17 20:18:16 node-1 kernel: [    0.000000] Zone ranges:
Sep 17 20:18:16 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 17 20:18:16 node-1 kernel: [    0.000000] Early memory node ranges
Sep 17 20:18:16 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep 17 20:18:16 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 17 20:18:16 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 17 20:18:16 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 17 20:18:16 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep 17 20:18:16 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep 17 20:18:16 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 17 20:18:16 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 17 20:18:16 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 17 20:18:16 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 17 20:18:16 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 17 20:18:16 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 17 20:18:16 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 17 20:18:16 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 17 20:18:16 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 17 20:18:16 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 17 20:18:16 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 17 20:18:16 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 17 20:18:16 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 17 20:18:16 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 17 20:18:16 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 17 20:18:16 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 17 20:18:16 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 17 20:18:16 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Sep 17 20:18:16 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep 17 20:18:16 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 17 20:18:16 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=fea696b0-f7c7-4d62-a462-bff3e77c4446 nomdmonddf nomdmonisw
Sep 17 20:18:16 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 17 20:18:16 node-1 kernel: [    0.000000] Checking aperture...
Sep 17 20:18:16 node-1 kernel: [    0.000000] No AGP bridge found
Sep 17 20:18:16 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 17 20:18:16 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 17 20:18:16 node-1 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep 17 20:18:16 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 17 20:18:16 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 17 20:18:16 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 17 20:18:16 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 17 20:18:16 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 17 20:18:16 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 17 20:18:16 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 17 20:18:16 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 17 20:18:16 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 17 20:18:16 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 17 20:18:16 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 17 20:18:16 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 17 20:18:16 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 17 20:18:16 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 17 20:18:16 node-1 kernel: [    0.004000] tsc: Detected 3491.848 MHz processor
Sep 17 20:18:16 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.69 BogoMIPS (lpj=13967392)
Sep 17 20:18:16 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 17 20:18:16 node-1 kernel: [    0.000047] Security Framework initialized
Sep 17 20:18:16 node-1 kernel: [    0.000065] AppArmor: AppArmor initialized
Sep 17 20:18:16 node-1 kernel: [    0.000066] Yama: becoming mindful.
Sep 17 20:18:16 node-1 kernel: [    0.001466] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.006345] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.008274] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.008301] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.008592] Initializing cgroup subsys memory
Sep 17 20:18:16 node-1 kernel: [    0.008600] Initializing cgroup subsys devices
Sep 17 20:18:16 node-1 kernel: [    0.008602] Initializing cgroup subsys freezer
Sep 17 20:18:16 node-1 kernel: [    0.008604] Initializing cgroup subsys blkio
Sep 17 20:18:16 node-1 kernel: [    0.008605] Initializing cgroup subsys perf_event
Sep 17 20:18:16 node-1 kernel: [    0.008608] Initializing cgroup subsys hugetlb
Sep 17 20:18:16 node-1 kernel: [    0.008627] CPU: Physical Processor ID: 0
Sep 17 20:18:16 node-1 kernel: [    0.008628] CPU: Processor Core ID: 0
Sep 17 20:18:16 node-1 kernel: [    0.008632] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 17 20:18:16 node-1 kernel: [    0.008632] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 17 20:18:16 node-1 kernel: [    0.009325] mce: CPU supports 22 MCE banks
Sep 17 20:18:16 node-1 kernel: [    0.009353] CPU0: Thermal monitoring enabled (TM1)
Sep 17 20:18:16 node-1 kernel: [    0.009374] process: using mwait in idle threads
Sep 17 20:18:16 node-1 kernel: [    0.009377] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 17 20:18:16 node-1 kernel: [    0.009377] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 17 20:18:16 node-1 kernel: [    0.009377] tlb_flushall_shift: 6
Sep 17 20:18:16 node-1 kernel: [    0.009466] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 17 20:18:16 node-1 kernel: [    0.010190] ACPI: Core revision 20131115
Sep 17 20:18:16 node-1 kernel: [    0.022874] ACPI: All ACPI Tables successfully acquired
Sep 17 20:18:16 node-1 kernel: [    0.023035] ftrace: allocating 28617 entries in 112 pages
Sep 17 20:18:16 node-1 kernel: [    0.032004] dmar: Host address width 46
Sep 17 20:18:16 node-1 kernel: [    0.032006] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 17 20:18:16 node-1 kernel: [    0.032012] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 17 20:18:16 node-1 kernel: [    0.032014] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 17 20:18:16 node-1 kernel: [    0.032018] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 17 20:18:16 node-1 kernel: [    0.032019] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 17 20:18:16 node-1 kernel: [    0.032021] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 17 20:18:16 node-1 kernel: [    0.032022] dmar: ATSR flags: 0x0
Sep 17 20:18:16 node-1 kernel: [    0.032023] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 17 20:18:16 node-1 kernel: [    0.032024] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 17 20:18:16 node-1 kernel: [    0.032139] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 17 20:18:16 node-1 kernel: [    0.032141] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 17 20:18:16 node-1 kernel: [    0.032142] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 17 20:18:16 node-1 kernel: [    0.032143] HPET id 0 under DRHD base 0xc7ffc000
Sep 17 20:18:16 node-1 kernel: [    0.032144] Your BIOS is broken and requested that x2apic be disabled.
Sep 17 20:18:16 node-1 kernel: [    0.032144] This will slightly decrease performance.
Sep 17 20:18:16 node-1 kernel: [    0.032144] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 17 20:18:16 node-1 kernel: [    0.032576] Enabled IRQ remapping in xapic mode
Sep 17 20:18:16 node-1 kernel: [    0.032577] x2apic not enabled, IRQ remapping is in xapic mode
Sep 17 20:18:16 node-1 kernel: [    0.032581] Switched APIC routing to physical flat.
Sep 17 20:18:16 node-1 kernel: [    0.033168] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 17 20:18:16 node-1 kernel: [    0.072817] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 17 20:18:16 node-1 kernel: [    0.072822] TSC deadline timer enabled
Sep 17 20:18:16 node-1 kernel: [    0.072830] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 17 20:18:16 node-1 kernel: [    0.072836] ... version:                3
Sep 17 20:18:16 node-1 kernel: [    0.072837] ... bit width:              48
Sep 17 20:18:16 node-1 kernel: [    0.072838] ... generic registers:      4
Sep 17 20:18:16 node-1 kernel: [    0.072839] ... value mask:             0000ffffffffffff
Sep 17 20:18:16 node-1 kernel: [    0.072840] ... max period:             0000ffffffffffff
Sep 17 20:18:16 node-1 kernel: [    0.072841] ... fixed-purpose events:   3
Sep 17 20:18:16 node-1 kernel: [    0.072842] ... event mask:             000000070000000f
Sep 17 20:18:16 node-1 kernel: [    0.074254] x86: Booting SMP configuration:
Sep 17 20:18:16 node-1 kernel: [    0.088463] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 17 20:18:16 node-1 kernel: [    0.074256] .... node  #0, CPUs:        #1  #2  #3
Sep 17 20:18:16 node-1 kernel: [    0.116373] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 17 20:18:16 node-1 kernel: [    0.270328] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 17 20:18:16 node-1 kernel: [    0.325944] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 17 20:18:16 node-1 kernel: [    0.382796] x86: Booted up 2 nodes, 16 CPUs
Sep 17 20:18:16 node-1 kernel: [    0.382800] smpboot: Total of 16 processors activated (111751.14 BogoMIPS)
Sep 17 20:18:16 node-1 kernel: [    0.407408] devtmpfs: initialized
Sep 17 20:18:16 node-1 kernel: [    0.410784] EVM: security.selinux
Sep 17 20:18:16 node-1 kernel: [    0.410786] EVM: security.SMACK64
Sep 17 20:18:16 node-1 kernel: [    0.410787] EVM: security.ima
Sep 17 20:18:16 node-1 kernel: [    0.410788] EVM: security.capability
Sep 17 20:18:16 node-1 kernel: [    0.410837] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.411514] pinctrl core: initialized pinctrl subsystem
Sep 17 20:18:16 node-1 kernel: [    0.411573] regulator-dummy: no parameters
Sep 17 20:18:16 node-1 kernel: [    0.411605] RTC time: 20:17:40, date: 09/17/16
Sep 17 20:18:16 node-1 kernel: [    0.411637] NET: Registered protocol family 16
Sep 17 20:18:16 node-1 kernel: [    0.411722] cpuidle: using governor ladder
Sep 17 20:18:16 node-1 kernel: [    0.411723] cpuidle: using governor menu
Sep 17 20:18:16 node-1 kernel: [    0.411757] ACPI: bus type PCI registered
Sep 17 20:18:16 node-1 kernel: [    0.411758] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 17 20:18:16 node-1 kernel: [    0.411802] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 17 20:18:16 node-1 kernel: [    0.411805] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 17 20:18:16 node-1 kernel: [    0.425536] PCI: Using configuration type 1 for base access
Sep 17 20:18:16 node-1 kernel: [    0.426533] bio: create slab <bio-0> at 0
Sep 17 20:18:16 node-1 kernel: [    0.426811] ACPI: Added _OSI(Module Device)
Sep 17 20:18:16 node-1 kernel: [    0.426813] ACPI: Added _OSI(Processor Device)
Sep 17 20:18:16 node-1 kernel: [    0.426814] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 17 20:18:16 node-1 kernel: [    0.426815] ACPI: Added _OSI(Processor Aggregator Device)
Sep 17 20:18:16 node-1 kernel: [    0.439439] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 17 20:18:16 node-1 kernel: [    0.450093] ACPI: Interpreter enabled
Sep 17 20:18:16 node-1 kernel: [    0.450098] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 17 20:18:16 node-1 kernel: [    0.450102] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 17 20:18:16 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 17 20:18:16 node-1 kernel: [    0.450105] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 17 20:18:16 node-1 kernel: [    0.450112] ACPI: (supports S0 S4 S5)
Sep 17 20:18:16 node-1 kernel: [    0.450113] ACPI: Using IOAPIC for interrupt routing
Sep 17 20:18:16 node-1 kernel: [    0.450154] HEST: Table parsing has been initialized.
Sep 17 20:18:16 node-1 kernel: [    0.450157] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 17 20:18:16 node-1 kernel: [    0.450712] ACPI: No dock devices found.
Sep 17 20:18:16 node-1 kernel: [    0.462327] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 17 20:18:16 node-1 kernel: [    0.462332] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 20:18:16 node-1 kernel: [    0.462335] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 17 20:18:16 node-1 kernel: [    0.462361] PCI host bridge to bus 0000:ff
Sep 17 20:18:16 node-1 kernel: [    0.462363] pci_bus 0000:ff: root bus resource [bus ff]
Sep 17 20:18:16 node-1 kernel: [    0.462371] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462409] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.462440] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462474] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462503] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.462532] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.462562] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462591] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462619] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462646] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462672] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462698] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462726] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462752] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462779] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462805] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462833] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462860] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462887] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.462915] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462940] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.462966] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.462992] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463022] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.463057] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463089] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463118] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463149] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463180] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463211] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463243] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463275] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463305] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463336] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463367] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463399] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463432] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463462] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463490] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463521] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463554] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463591] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463626] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463659] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463690] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463721] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463754] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463785] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463820] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463851] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463884] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463914] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463944] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.463975] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464006] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464039] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464071] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464129] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 17 20:18:16 node-1 kernel: [    0.464132] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 20:18:16 node-1 kernel: [    0.464135] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 17 20:18:16 node-1 kernel: [    0.464153] PCI host bridge to bus 0000:7f
Sep 17 20:18:16 node-1 kernel: [    0.464155] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 17 20:18:16 node-1 kernel: [    0.464160] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464188] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.464216] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464250] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464272] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.464297] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.464324] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464351] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464373] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464396] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464418] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464441] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464465] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464487] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464511] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464540] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464562] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464585] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464607] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.464631] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464653] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.464675] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464698] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464726] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 17 20:18:16 node-1 kernel: [    0.464760] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464786] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464813] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464839] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464864] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464892] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464920] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464949] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.464974] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465002] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465029] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465059] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465087] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465112] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465136] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465164] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465190] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465218] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465248] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465275] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465301] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465328] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465353] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465382] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465408] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465435] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465464] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465490] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465512] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465538] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465563] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465592] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.465619] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.466860] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 17 20:18:16 node-1 kernel: [    0.466864] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 20:18:16 node-1 kernel: [    0.467981] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 17 20:18:16 node-1 kernel: [    0.468493] PCI host bridge to bus 0000:00
Sep 17 20:18:16 node-1 kernel: [    0.468496] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 17 20:18:16 node-1 kernel: [    0.468497] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 17 20:18:16 node-1 kernel: [    0.468499] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 17 20:18:16 node-1 kernel: [    0.468500] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 17 20:18:16 node-1 kernel: [    0.468501] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 17 20:18:16 node-1 kernel: [    0.468503] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 17 20:18:16 node-1 kernel: [    0.468504] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 17 20:18:16 node-1 kernel: [    0.468510] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 17 20:18:16 node-1 kernel: [    0.468592] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.468623] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.468664] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 17 20:18:16 node-1 kernel: [    0.468684] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.468713] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.468753] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 17 20:18:16 node-1 kernel: [    0.468772] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.468801] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.468841] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 17 20:18:16 node-1 kernel: [    0.468860] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.468930] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.469007] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.469083] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 17 20:18:16 node-1 kernel: [    0.469088] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 17 20:18:16 node-1 kernel: [    0.469172] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 17 20:18:16 node-1 kernel: [    0.469319] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 17 20:18:16 node-1 kernel: [    0.469336] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 17 20:18:16 node-1 kernel: [    0.469414] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.469468] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 17 20:18:16 node-1 kernel: [    0.469490] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.469545] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.469589] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 17 20:18:16 node-1 kernel: [    0.469616] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.469671] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.469714] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 17 20:18:16 node-1 kernel: [    0.469738] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 17 20:18:16 node-1 kernel: [    0.469756] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 17 20:18:16 node-1 kernel: [    0.469834] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.469884] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 17 20:18:16 node-1 kernel: [    0.469909] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 17 20:18:16 node-1 kernel: [    0.470156] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 17 20:18:16 node-1 kernel: [    0.470162] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 17 20:18:16 node-1 kernel: [    0.470168] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.470174] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.470181] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 17 20:18:16 node-1 kernel: [    0.470211] pci 0000:01:00.0: supports D1 D2
Sep 17 20:18:16 node-1 kernel: [    0.480233] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 17 20:18:16 node-1 kernel: [    0.480240] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 17 20:18:16 node-1 kernel: [    0.480244] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 17 20:18:16 node-1 kernel: [    0.480369] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.480402] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 17 20:18:16 node-1 kernel: [    0.488251] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 17 20:18:16 node-1 kernel: [    0.488254] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.488256] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 20:18:16 node-1 kernel: [    0.488311] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.488379] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.488455] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.488500] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 17 20:18:16 node-1 kernel: [    0.488503] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.488505] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 20:18:16 node-1 kernel: [    0.488557] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.488679] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.488733] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 17 20:18:16 node-1 kernel: [    0.488735] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.488737] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.488788] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.488907] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.488946] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.489090] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.489126] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.489248] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.489284] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 17 20:18:16 node-1 kernel: [    0.489403] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 17 20:18:16 node-1 kernel: [    0.489443] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 17 20:18:16 node-1 kernel: [    0.489446] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.489448] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.489506] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 17 20:18:16 node-1 kernel: [    0.489569] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.489621] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.489662] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 17 20:18:16 node-1 kernel: [    0.489746] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 17 20:18:16 node-1 kernel: [    0.489851] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 17 20:18:16 node-1 kernel: [    0.489854] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.489856] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.489912] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 17 20:18:16 node-1 kernel: [    0.489965] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.490014] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.490249] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 17 20:18:16 node-1 kernel: [    0.490253] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 17 20:18:16 node-1 kernel: [    0.490317] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 17 20:18:16 node-1 kernel: [    0.490370] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.490419] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.490628] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 17 20:18:16 node-1 kernel: [    0.490632] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 17 20:18:16 node-1 kernel: [    0.490690] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 17 20:18:16 node-1 kernel: [    0.490750] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.490805] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 17 20:18:16 node-1 kernel: [    0.491046] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 17 20:18:16 node-1 kernel: [    0.491049] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 17 20:18:16 node-1 kernel: [    0.491224] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 17 20:18:16 node-1 kernel: [    0.491262] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 17 20:18:16 node-1 kernel: [    0.491338] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 17 20:18:16 node-1 kernel: [    0.491357] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 17 20:18:16 node-1 kernel: [    0.491370] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 17 20:18:16 node-1 kernel: [    0.491383] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 17 20:18:16 node-1 kernel: [    0.491433] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 17 20:18:16 node-1 kernel: [    0.496241] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 17 20:18:16 node-1 kernel: [    0.496246] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 17 20:18:16 node-1 kernel: [    0.496278] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 17 20:18:16 node-1 kernel: [    0.496770] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 17 20:18:16 node-1 kernel: [    0.496773] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 20:18:16 node-1 kernel: [    0.496893] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 17 20:18:16 node-1 kernel: [    0.497000] PCI host bridge to bus 0000:80
Sep 17 20:18:16 node-1 kernel: [    0.497002] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 17 20:18:16 node-1 kernel: [    0.497004] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 17 20:18:16 node-1 kernel: [    0.497005] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 17 20:18:16 node-1 kernel: [    0.497013] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.497077] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.497144] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 17 20:18:16 node-1 kernel: [    0.497205] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 17 20:18:16 node-1 kernel: [    0.497211] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 17 20:18:16 node-1 kernel: [    0.497283] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 17 20:18:16 node-1 kernel: [    0.497581] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 17 20:18:16 node-1 kernel: [    0.497613] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 17 20:18:16 node-1 kernel: [    0.497642] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 17 20:18:16 node-1 kernel: [    0.497672] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 17 20:18:16 node-1 kernel: [    0.497701] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 20:18:16 node-1 kernel: [    0.497731] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 20:18:16 node-1 kernel: [    0.497761] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 20:18:16 node-1 kernel: [    0.497791] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 20:18:16 node-1 kernel: [    0.497876] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 17 20:18:16 node-1 kernel: [    0.497880] ACPI: \_SB_.UNC1: notify handler is installed
Sep 17 20:18:16 node-1 kernel: [    0.497882] ACPI: \_SB_.UNC0: notify handler is installed
Sep 17 20:18:16 node-1 kernel: [    0.497897] ACPI: \_SB_.PCI0: notify handler is installed
Sep 17 20:18:16 node-1 kernel: [    0.497950] ACPI: \_SB_.PCI1: notify handler is installed
Sep 17 20:18:16 node-1 kernel: [    0.498029] Found 4 acpi root devices
Sep 17 20:18:16 node-1 kernel: [    0.498136] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 17 20:18:16 node-1 kernel: [    0.498138] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 17 20:18:16 node-1 kernel: [    0.498140] vgaarb: loaded
Sep 17 20:18:16 node-1 kernel: [    0.498141] vgaarb: bridge control possible 0000:0c:00.0
Sep 17 20:18:16 node-1 kernel: [    0.498263] SCSI subsystem initialized
Sep 17 20:18:16 node-1 kernel: [    0.498327] libata version 3.00 loaded.
Sep 17 20:18:16 node-1 kernel: [    0.498343] ACPI: bus type USB registered
Sep 17 20:18:16 node-1 kernel: [    0.498353] usbcore: registered new interface driver usbfs
Sep 17 20:18:16 node-1 kernel: [    0.498358] usbcore: registered new interface driver hub
Sep 17 20:18:16 node-1 kernel: [    0.498382] usbcore: registered new device driver usb
Sep 17 20:18:16 node-1 kernel: [    0.498553] PCI: Using ACPI for IRQ routing
Sep 17 20:18:16 node-1 kernel: [    0.502161] PCI: pci_cache_line_size set to 64 bytes
Sep 17 20:18:16 node-1 kernel: [    0.502375] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 17 20:18:16 node-1 kernel: [    0.502376] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep 17 20:18:16 node-1 kernel: [    0.502377] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 17 20:18:16 node-1 kernel: [    0.502443] NetLabel: Initializing
Sep 17 20:18:16 node-1 kernel: [    0.502444] NetLabel:  domain hash size = 128
Sep 17 20:18:16 node-1 kernel: [    0.502445] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 17 20:18:16 node-1 kernel: [    0.502455] NetLabel:  unlabeled traffic allowed by default
Sep 17 20:18:16 node-1 kernel: [    0.502511] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 17 20:18:16 node-1 kernel: [    0.502515] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 17 20:18:16 node-1 kernel: [    0.504587] Switched to clocksource hpet
Sep 17 20:18:16 node-1 kernel: [    0.509165] AppArmor: AppArmor Filesystem Enabled
Sep 17 20:18:16 node-1 kernel: [    0.509205] pnp: PnP ACPI init
Sep 17 20:18:16 node-1 kernel: [    0.509216] ACPI: bus type PNP registered
Sep 17 20:18:16 node-1 kernel: [    0.509400] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509412] pnp 00:01: [dma 4]
Sep 17 20:18:16 node-1 kernel: [    0.509431] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509466] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509490] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509512] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509559] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509671] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509674] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 17 20:18:16 node-1 kernel: [    0.509675] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509677] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509678] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509680] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509683] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 17 20:18:16 node-1 kernel: [    0.509685] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509687] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509688] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509690] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509691] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509692] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 17 20:18:16 node-1 kernel: [    0.509695] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509798] pnp 00:07: [dma 0 disabled]
Sep 17 20:18:16 node-1 kernel: [    0.509831] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 17 20:18:16 node-1 kernel: [    0.509913] pnp 00:08: [dma 0 disabled]
Sep 17 20:18:16 node-1 kernel: [    0.509949] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 17 20:18:16 node-1 kernel: [    0.510008] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 17 20:18:16 node-1 kernel: [    0.510454] pnp: PnP ACPI: found 10 devices
Sep 17 20:18:16 node-1 kernel: [    0.510456] ACPI: bus type PNP unregistered
Sep 17 20:18:16 node-1 kernel: [    0.516473] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 17 20:18:16 node-1 kernel: [    0.516477] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 17 20:18:16 node-1 kernel: [    0.516480] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 17 20:18:16 node-1 kernel: [    0.516485] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 17 20:18:16 node-1 kernel: [    0.516487] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516502] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516531] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 17 20:18:16 node-1 kernel: [    0.516546] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516578] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 17 20:18:16 node-1 kernel: [    0.516593] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 17 20:18:16 node-1 kernel: [    0.516625] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 17 20:18:16 node-1 kernel: [    0.516640] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 17 20:18:16 node-1 kernel: [    0.516669] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 17 20:18:16 node-1 kernel: [    0.516671] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516685] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516714] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 17 20:18:16 node-1 kernel: [    0.516716] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516731] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516760] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 17 20:18:16 node-1 kernel: [    0.516761] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516764] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516769] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 17 20:18:16 node-1 kernel: [    0.516771] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516774] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516778] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 17 20:18:16 node-1 kernel: [    0.516784] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 17 20:18:16 node-1 kernel: [    0.516793] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 17 20:18:16 node-1 kernel: [    0.516797] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 17 20:18:16 node-1 kernel: [    0.516804] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 17 20:18:16 node-1 kernel: [    0.516805] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 17 20:18:16 node-1 kernel: [    0.516806] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 17 20:18:16 node-1 kernel: [    0.516807] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 17 20:18:16 node-1 kernel: [    0.516808] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 17 20:18:16 node-1 kernel: [    0.516809] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 17 20:18:16 node-1 kernel: [    0.516810] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 17 20:18:16 node-1 kernel: [    0.516811] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 17 20:18:16 node-1 kernel: [    0.516812] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516813] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516814] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516815] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516816] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516816] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516817] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516818] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516819] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 17 20:18:16 node-1 kernel: [    0.516820] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516821] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 17 20:18:16 node-1 kernel: [    0.516823] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 17 20:18:16 node-1 kernel: [    0.516824] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 17 20:18:16 node-1 kernel: [    0.516825] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 17 20:18:16 node-1 kernel: [    0.516828] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 17 20:18:16 node-1 kernel: [    0.516829] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 17 20:18:16 node-1 kernel: [    0.516869] NET: Registered protocol family 2
Sep 17 20:18:16 node-1 kernel: [    0.517168] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.517549] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.517717] TCP: Hash tables configured (established 262144 bind 65536)
Sep 17 20:18:16 node-1 kernel: [    0.517759] TCP: reno registered
Sep 17 20:18:16 node-1 kernel: [    0.517792] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.517903] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.518064] NET: Registered protocol family 1
Sep 17 20:18:16 node-1 kernel: [    0.556616] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 17 20:18:16 node-1 kernel: [    0.556623] PCI: CLS 64 bytes, default 64
Sep 17 20:18:16 node-1 kernel: [    0.556669] Trying to unpack rootfs image as initramfs...
Sep 17 20:18:16 node-1 kernel: [    0.779089] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep 17 20:18:16 node-1 kernel: [    0.779126] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 17 20:18:16 node-1 kernel: [    0.779129] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep 17 20:18:16 node-1 kernel: [    0.779551] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779564] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779578] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779591] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779604] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779613] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779619] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779626] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779635] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779647] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779662] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779675] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779683] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779690] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779696] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779701] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 20:18:16 node-1 kernel: [    0.779751] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 17 20:18:16 node-1 kernel: [    0.779753] Scanning for low memory corruption every 60 seconds
Sep 17 20:18:16 node-1 kernel: [    0.780089] Initialise system trusted keyring
Sep 17 20:18:16 node-1 kernel: [    0.780141] audit: initializing netlink socket (disabled)
Sep 17 20:18:16 node-1 kernel: [    0.780153] type=2000 audit(1474143460.728:1): initialized
Sep 17 20:18:16 node-1 kernel: [    0.798011] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 17 20:18:16 node-1 kernel: [    0.799501] zbud: loaded
Sep 17 20:18:16 node-1 kernel: [    0.799622] VFS: Disk quotas dquot_6.5.2
Sep 17 20:18:16 node-1 kernel: [    0.799663] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 17 20:18:16 node-1 kernel: [    0.800024] fuse init (API version 7.22)
Sep 17 20:18:16 node-1 kernel: [    0.800076] msgmni has been set to 32768
Sep 17 20:18:16 node-1 kernel: [    0.800120] Key type big_key registered
Sep 17 20:18:16 node-1 kernel: [    0.800635] Key type asymmetric registered
Sep 17 20:18:16 node-1 kernel: [    0.800637] Asymmetric key parser 'x509' registered
Sep 17 20:18:16 node-1 kernel: [    0.800668] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 17 20:18:16 node-1 kernel: [    0.800747] io scheduler noop registered
Sep 17 20:18:16 node-1 kernel: [    0.800748] io scheduler deadline registered (default)
Sep 17 20:18:16 node-1 kernel: [    0.800765] io scheduler cfq registered
Sep 17 20:18:16 node-1 kernel: [    0.801264] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    0.801507] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    0.801627] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    0.801743] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    0.801862] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    0.801953] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    0.802364] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 17 20:18:16 node-1 kernel: [    0.802389] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 17 20:18:16 node-1 kernel: [    0.802406] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 17 20:18:16 node-1 kernel: [    0.802418] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802428] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802431] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 17 20:18:16 node-1 kernel: [    0.802436] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802437] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802438] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802440] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802442] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802444] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802445] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802446] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802448] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802449] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802451] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802452] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802455] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 17 20:18:16 node-1 kernel: [    0.802465] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802467] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 17 20:18:16 node-1 kernel: [    0.802478] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802482] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 17 20:18:16 node-1 kernel: [    0.802492] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802493] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 17 20:18:16 node-1 kernel: [    0.802496] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 17 20:18:16 node-1 kernel: [    0.802525] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 17 20:18:16 node-1 kernel: [    0.802531] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 17 20:18:16 node-1 kernel: [    0.802535] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 17 20:18:16 node-1 kernel: [    0.802543] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 17 20:18:16 node-1 kernel: [    0.802579] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 17 20:18:16 node-1 kernel: [    0.802581] vesafb: scrolling: redraw
Sep 17 20:18:16 node-1 kernel: [    0.802582] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 17 20:18:16 node-1 kernel: [    0.822901] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 17 20:18:16 node-1 kernel: [    0.831405] Console: switching to colour frame buffer device 80x30
Sep 17 20:18:16 node-1 kernel: [    0.840083] fb0: VESA VGA frame buffer device
Sep 17 20:18:16 node-1 kernel: [    0.840282] intel_idle: MWAIT substates: 0x2120
Sep 17 20:18:16 node-1 kernel: [    0.840283] intel_idle: v0.4 model 0x3F
Sep 17 20:18:16 node-1 kernel: [    0.840290] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 17 20:18:16 node-1 kernel: [    0.840535] ipmi message handler version 39.2
Sep 17 20:18:16 node-1 kernel: [    0.840811] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 17 20:18:16 node-1 kernel: [    0.841247] ACPI: AC Adapter [P111] (on-line)
Sep 17 20:18:16 node-1 kernel: [    0.846486] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 17 20:18:16 node-1 kernel: [    0.857492] ACPI: Power Button [PWRB]
Sep 17 20:18:16 node-1 kernel: [    0.863292] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 17 20:18:16 node-1 kernel: [    0.874926] ACPI: Power Button [PWRF]
Sep 17 20:18:16 node-1 kernel: [    0.898161] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 17 20:18:16 node-1 kernel: [    0.909802] pstore: Registered erst as persistent store backend
Sep 17 20:18:16 node-1 kernel: [    0.915993] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 17 20:18:16 node-1 kernel: [    0.927925] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 17 20:18:16 node-1 kernel: [    0.954664] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 17 20:18:16 node-1 kernel: [    0.987942] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 17 20:18:16 node-1 kernel: [    1.002123] Linux agpgart interface v0.103
Sep 17 20:18:16 node-1 kernel: [    1.009800] brd: module loaded
Sep 17 20:18:16 node-1 kernel: [    1.016921] loop: module loaded
Sep 17 20:18:16 node-1 kernel: [    1.023618] libphy: Fixed MDIO Bus: probed
Sep 17 20:18:16 node-1 kernel: [    1.030089] tun: Universal TUN/TAP device driver, 1.6
Sep 17 20:18:16 node-1 kernel: [    1.036550] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 17 20:18:16 node-1 kernel: [    1.043071] PPP generic driver version 2.4.2
Sep 17 20:18:16 node-1 kernel: [    1.049450] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 17 20:18:16 node-1 kernel: [    1.055886] ehci-pci: EHCI PCI platform driver
Sep 17 20:18:16 node-1 kernel: [    1.062390] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 17 20:18:16 node-1 kernel: [    1.068790] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 17 20:18:16 node-1 kernel: [    1.081288] ehci-pci 0000:00:1a.0: debug port 2
Sep 17 20:18:16 node-1 kernel: [    1.091455] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 17 20:18:16 node-1 kernel: [    1.091473] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 17 20:18:16 node-1 kernel: [    1.108066] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 17 20:18:16 node-1 kernel: [    1.114128] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 17 20:18:16 node-1 kernel: [    1.120294] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 17 20:18:16 node-1 kernel: [    1.132186] usb usb1: Product: EHCI Host Controller
Sep 17 20:18:16 node-1 kernel: [    1.138203] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 17 20:18:16 node-1 kernel: [    1.144249] usb usb1: SerialNumber: 0000:00:1a.0
Sep 17 20:18:16 node-1 kernel: [    1.150200] hub 1-0:1.0: USB hub found
Sep 17 20:18:16 node-1 kernel: [    1.155961] hub 1-0:1.0: 2 ports detected
Sep 17 20:18:16 node-1 kernel: [    1.161747] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 17 20:18:16 node-1 kernel: [    1.167320] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 17 20:18:16 node-1 kernel: [    1.178248] ehci-pci 0000:00:1d.0: debug port 2
Sep 17 20:18:16 node-1 kernel: [    1.187532] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 17 20:18:16 node-1 kernel: [    1.187535] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 17 20:18:16 node-1 kernel: [    1.203984] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 17 20:18:16 node-1 kernel: [    1.209180] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 17 20:18:16 node-1 kernel: [    1.214480] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 17 20:18:16 node-1 kernel: [    1.225047] usb usb2: Product: EHCI Host Controller
Sep 17 20:18:16 node-1 kernel: [    1.230507] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 17 20:18:16 node-1 kernel: [    1.236045] usb usb2: SerialNumber: 0000:00:1d.0
Sep 17 20:18:16 node-1 kernel: [    1.241562] hub 2-0:1.0: USB hub found
Sep 17 20:18:16 node-1 kernel: [    1.246933] hub 2-0:1.0: 2 ports detected
Sep 17 20:18:16 node-1 kernel: [    1.252249] ehci-platform: EHCI generic platform driver
Sep 17 20:18:16 node-1 kernel: [    1.257501] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 17 20:18:16 node-1 kernel: [    1.262837] ohci-pci: OHCI PCI platform driver
Sep 17 20:18:16 node-1 kernel: [    1.268176] ohci-platform: OHCI generic platform driver
Sep 17 20:18:16 node-1 kernel: [    1.273390] uhci_hcd: USB Universal Host Controller Interface driver
Sep 17 20:18:16 node-1 kernel: [    1.278762] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 17 20:18:16 node-1 kernel: [    1.471763] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 17 20:18:16 node-1 kernel: [    1.667960] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 17 20:18:16 node-1 kernel: [    1.673465] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 17 20:18:16 node-1 kernel: [    1.679228] hub 1-1:1.0: USB hub found
Sep 17 20:18:16 node-1 kernel: [    1.684695] hub 1-1:1.0: 6 ports detected
Sep 17 20:18:16 node-1 kernel: [    1.775510] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 17 20:18:16 node-1 kernel: [    1.799478] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 17 20:18:16 node-1 kernel: [    2.067620] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 17 20:18:16 node-1 kernel: [    2.073124] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 17 20:18:16 node-1 kernel: [    2.079013] hub 2-1:1.0: USB hub found
Sep 17 20:18:16 node-1 kernel: [    2.084731] hub 2-1:1.0: 8 ports detected
Sep 17 20:18:16 node-1 kernel: [    2.320584] i8042: No controller found
Sep 17 20:18:16 node-1 kernel: [    2.326054] mousedev: PS/2 mouse device common for all mice
Sep 17 20:18:16 node-1 kernel: [    2.331547] rtc_cmos 00:02: RTC can wake from S4
Sep 17 20:18:16 node-1 kernel: [    2.337104] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 17 20:18:16 node-1 kernel: [    2.342647] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 17 20:18:16 node-1 kernel: [    2.353618] device-mapper: uevent: version 1.0.3
Sep 17 20:18:16 node-1 kernel: [    2.359163] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 17 20:18:16 node-1 kernel: [    2.367070] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 17 20:18:16 node-1 kernel: [    2.375988] ledtrig-cpu: registered to indicate activity on CPUs
Sep 17 20:18:16 node-1 kernel: [    2.381937] TCP: cubic registered
Sep 17 20:18:16 node-1 kernel: [    2.387835] NET: Registered protocol family 10
Sep 17 20:18:16 node-1 kernel: [    2.393814] NET: Registered protocol family 17
Sep 17 20:18:16 node-1 kernel: [    2.399480] Key type dns_resolver registered
Sep 17 20:18:16 node-1 kernel: [    2.405424] Loading compiled-in X.509 certificates
Sep 17 20:18:16 node-1 kernel: [    2.411588] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 17 20:18:16 node-1 kernel: [    2.422997] registered taskstats version 1
Sep 17 20:18:16 node-1 kernel: [    2.430912] Key type trusted registered
Sep 17 20:18:16 node-1 kernel: [    2.438417] Key type encrypted registered
Sep 17 20:18:16 node-1 kernel: [    2.443891] AppArmor: AppArmor sha1 policy hashing enabled
Sep 17 20:18:16 node-1 kernel: [    2.449361] IMA: No TPM chip found, activating TPM-bypass!
Sep 17 20:18:16 node-1 kernel: [    2.455505] regulator-dummy: disabling
Sep 17 20:18:16 node-1 kernel: [    2.461048]   Magic number: 0:139:296
Sep 17 20:18:16 node-1 kernel: [    2.466438] tty tty29: hash matches
Sep 17 20:18:16 node-1 kernel: [    2.471897] memory memory158: hash matches
Sep 17 20:18:16 node-1 kernel: [    2.477200] rtc_cmos 00:02: setting system clock to 2016-09-17 20:17:42 UTC (1474143462)
Sep 17 20:18:16 node-1 kernel: [    2.489372] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 17 20:18:16 node-1 kernel: [    2.494987] EDD information not available.
Sep 17 20:18:16 node-1 kernel: [    2.500576] PM: Hibernation image not present or could not be loaded.
Sep 17 20:18:16 node-1 kernel: [    2.501438] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 17 20:18:16 node-1 kernel: [    2.512438] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 17 20:18:16 node-1 kernel: [    2.512439] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 17 20:18:16 node-1 kernel: [    2.512440] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 17 20:18:16 node-1 kernel: [    2.512441] usb 2-1.4: Manufacturer: Avocent
Sep 17 20:18:16 node-1 kernel: [    2.512442] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 17 20:18:16 node-1 kernel: [    2.547661] Write protecting the kernel read-only data: 12288k
Sep 17 20:18:16 node-1 kernel: [    2.553757] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 17 20:18:16 node-1 kernel: [    2.566194] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 17 20:18:16 node-1 kernel: [    2.599595] device-mapper: multipath: version 1.6.0 loaded
Sep 17 20:18:16 node-1 kernel: [    2.607658] systemd-udevd[216]: starting version 204
Sep 17 20:18:16 node-1 kernel: [    2.630599] md: linear personality registered for level -1
Sep 17 20:18:16 node-1 kernel: [    2.644337] md: multipath personality registered for level -4
Sep 17 20:18:16 node-1 kernel: [    2.652412] md: raid0 personality registered for level 0
Sep 17 20:18:16 node-1 kernel: [    2.660521] md: raid1 personality registered for level 1
Sep 17 20:18:16 node-1 kernel: [    2.670209] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 17 20:18:16 node-1 kernel: [    2.676506] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 17 20:18:16 node-1 kernel: [    2.676880] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 17 20:18:16 node-1 kernel: [    2.679184] megasas: FW now in Ready state
Sep 17 20:18:16 node-1 kernel: [    2.679783] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.679899] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.679981] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680072] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680164] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680234] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680306] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680366] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680436] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680514] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680579] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680668] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680725] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680832] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680908] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.680985] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.681654] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 17 20:18:16 node-1 kernel: [    2.708754] hidraw: raw HID events driver (C) Jiri Kosina
Sep 17 20:18:16 node-1 kernel: [    2.718110] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep 17 20:18:16 node-1 kernel: [    2.721372] usbcore: registered new interface driver usbhid
Sep 17 20:18:16 node-1 kernel: [    2.721373] usbhid: USB HID core driver
Sep 17 20:18:16 node-1 kernel: [    2.734923] raid6: sse2x1    4281 MB/s
Sep 17 20:18:16 node-1 kernel: [    2.750289] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 20:18:16 node-1 kernel: [    2.763111] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 17 20:18:16 node-1 kernel: [    2.769760] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.769765] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.769769] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.769776] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.769814] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 17 20:18:16 node-1 kernel: [    2.769918] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 17 20:18:16 node-1 kernel: [    2.770301] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 17 20:18:16 node-1 kernel: [    2.770458] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 17 20:18:16 node-1 kernel: [    2.771118] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 17 20:18:16 node-1 kernel: [    2.771250] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 17 20:18:16 node-1 kernel: [    2.771648] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 17 20:18:16 node-1 kernel: [    2.802927] raid6: sse2x2   10157 MB/s
Sep 17 20:18:16 node-1 kernel: [    2.870732] raid6: sse2x4    9540 MB/s
Sep 17 20:18:16 node-1 kernel: [    2.938523] raid6: avx2x1   14819 MB/s
Sep 17 20:18:16 node-1 kernel: [    3.010459] raid6: avx2x2   18857 MB/s
Sep 17 20:18:16 node-1 kernel: [    3.082410] raid6: avx2x4   21400 MB/s
Sep 17 20:18:16 node-1 kernel: [    3.089015] raid6: using algorithm avx2x4 (21400 MB/s)
Sep 17 20:18:16 node-1 kernel: [    3.095534] raid6: using avx2x2 recovery algorithm
Sep 17 20:18:16 node-1 kernel: [    3.101964] megasas:IOC Init cmd success
Sep 17 20:18:16 node-1 kernel: [    3.101967] Switched to clocksource tsc
Sep 17 20:18:16 node-1 kernel: [    3.115155] xor: automatically using best checksumming function:
Sep 17 20:18:16 node-1 kernel: [    3.121583] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep 17 20:18:16 node-1 kernel: [    3.134179] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 20:18:16 node-1 kernel: [    3.147170] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 17 20:18:16 node-1 kernel: [    3.153731] megasas: INIT adapter done
Sep 17 20:18:16 node-1 kernel: [    3.158315]    avx       : 35729.000 MB/sec
Sep 17 20:18:16 node-1 kernel: [    3.166802] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.166808] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.166811] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.166816] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.166820] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.166824] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.166874] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.179770] async_tx: api initialized (async)
Sep 17 20:18:16 node-1 kernel: [    3.189149] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep 17 20:18:16 node-1 kernel: [    3.201638] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 20:18:16 node-1 kernel: [    3.214277] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 17 20:18:16 node-1 kernel: [    3.220654] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.220659] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.220662] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.220666] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.220698] md: raid6 personality registered for level 6
Sep 17 20:18:16 node-1 kernel: [    3.220715] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.229321] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep 17 20:18:16 node-1 kernel: [    3.229323] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 20:18:16 node-1 kernel: [    3.229323] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 17 20:18:16 node-1 kernel: [    3.229382] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.229419] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.229453] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.229489] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.229565] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 17 20:18:16 node-1 kernel: [    3.266300] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 17 20:18:16 node-1 kernel: [    3.266701] scsi0 : LSI SAS based MegaRAID driver
Sep 17 20:18:16 node-1 kernel: [    3.273647] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 17 20:18:16 node-1 kernel: [    3.284469] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 17 20:18:16 node-1 kernel: [    3.288374] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 17 20:18:16 node-1 kernel: [    3.288576] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 17 20:18:16 node-1 kernel: [    3.288701] sd 0:2:0:0: [sda] Write Protect is off
Sep 17 20:18:16 node-1 kernel: [    3.288702] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 17 20:18:16 node-1 kernel: [    3.288778] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 17 20:18:16 node-1 kernel: [    3.316366]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 17 20:18:16 node-1 kernel: [    3.317900] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 17 20:18:16 node-1 kernel: [    3.381489] md: raid5 personality registered for level 5
Sep 17 20:18:16 node-1 kernel: [    3.388339] md: raid4 personality registered for level 4
Sep 17 20:18:16 node-1 kernel: [    3.398199] md: raid10 personality registered for level 10
Sep 17 20:18:16 node-1 kernel: [    3.452444] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Sep 17 20:18:16 node-1 kernel: [    3.534388] random: lvm urandom read with 31 bits of entropy available
Sep 17 20:18:16 node-1 kernel: [    3.656895] bio: create slab <bio-1> at 1
Sep 17 20:18:16 node-1 kernel: [    4.291625] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 17 20:18:16 node-1 kernel: [    5.010936] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 17 20:18:16 node-1 kernel: [    5.044601] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 17 20:18:16 node-1 kernel: [    5.253589] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 17 20:18:16 node-1 kernel: [    5.295514] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 17 20:18:16 node-1 kernel: [    5.388725] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 17 20:18:16 node-1 kernel: [    5.504648] random: nonblocking pool is initialized
Sep 17 20:18:16 node-1 kernel: [    5.654269] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 17 20:18:16 node-1 kernel: [    5.735632] XFS (dm-0): Mounting Filesystem
Sep 17 20:18:16 node-1 kernel: [    5.979717] XFS (dm-0): Ending clean mount
Sep 17 20:18:16 node-1 kernel: [    6.035253] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 17 20:18:16 node-1 kernel: [    6.100663] XFS (dm-1): Mounting Filesystem
Sep 17 20:18:16 node-1 kernel: [    6.217586] XFS (dm-1): Ending clean mount
Sep 17 20:18:16 node-1 kernel: [    7.827151] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 17 20:18:16 node-1 kernel: [    7.853251] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 17 20:18:16 node-1 kernel: [    8.012335] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 17 20:18:16 node-1 kernel: [    8.012342] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 17 20:18:16 node-1 kernel: [    8.012347] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 17 20:18:16 node-1 kernel: [    8.012351] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 17 20:18:16 node-1 kernel: [    8.041523] systemd-udevd[772]: starting version 204
Sep 17 20:18:16 node-1 kernel: [    8.243771] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 17 20:18:16 node-1 kernel: [    8.243777] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 17 20:18:16 node-1 kernel: [    8.243780] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 17 20:18:16 node-1 kernel: [    8.243782] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 17 20:18:16 node-1 kernel: [    8.243832] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 17 20:18:16 node-1 kernel: [    8.248485] power_meter ACPI000D:00: Found ACPI power meter.
Sep 17 20:18:16 node-1 kernel: [    8.248517] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 17 20:18:16 node-1 kernel: [    8.262808] wmi: Mapper loaded
Sep 17 20:18:16 node-1 kernel: [    8.268377] IPMI System Interface driver.
Sep 17 20:18:16 node-1 kernel: [    8.268431] ipmi_si: probing via ACPI
Sep 17 20:18:16 node-1 kernel: [    8.268443] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 17 20:18:16 node-1 kernel: [    8.268443] ipmi_si: Adding ACPI-specified kcs state machine
Sep 17 20:18:16 node-1 kernel: [    8.268453] ipmi_si: probing via SMBIOS
Sep 17 20:18:16 node-1 kernel: [    8.268454] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 17 20:18:16 node-1 kernel: [    8.268454] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 17 20:18:16 node-1 kernel: [    8.268456] ipmi_si: probing via SPMI
Sep 17 20:18:16 node-1 kernel: [    8.268457] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 17 20:18:16 node-1 kernel: [    8.268457] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 17 20:18:16 node-1 kernel: [    8.268458] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 17 20:18:16 node-1 kernel: [    8.269643] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 17 20:18:16 node-1 kernel: [    8.330428] systemd-udevd[794]: renamed network interface eth3 to enp9s0
Sep 17 20:18:16 node-1 kernel: [    8.354344] systemd-udevd[819]: renamed network interface eth1 to enp7s0
Sep 17 20:18:16 node-1 kernel: [    8.378589] systemd-udevd[790]: renamed network interface eth2 to enp8s0
Sep 17 20:18:16 node-1 kernel: [    8.410277] systemd-udevd[802]: renamed network interface eth0 to enp6s0
Sep 17 20:18:16 node-1 kernel: [    8.410528] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 17 20:18:16 node-1 kernel: [    8.410534] ipmi_si 00:09: IPMI kcs interface initialized
Sep 17 20:18:16 node-1 kernel: [    8.696473] type=1400 audit(1474143468.720:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1028 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.696612] type=1400 audit(1474143468.720:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1028 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.696740] type=1400 audit(1474143468.720:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1028 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.700550] type=1400 audit(1474143468.724:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1013 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.700578] type=1400 audit(1474143468.724:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1029 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.700718] type=1400 audit(1474143468.724:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1013 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.700742] type=1400 audit(1474143468.724:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1029 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.700867] type=1400 audit(1474143468.724:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1013 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.700889] type=1400 audit(1474143468.724:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1029 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    8.722554] type=1400 audit(1474143468.748:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Sep 17 20:18:16 node-1 kernel: [    9.317726] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 17 20:18:16 node-1 kernel: [    9.331015] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 17 20:18:16 node-1 kernel: [    9.518459] enic 0000:06:00.0 enp6s0: Link UP
Sep 17 20:18:16 node-1 kernel: [    9.518897] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 17 20:18:16 node-1 kernel: [    9.518902] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 17 20:18:16 node-1 kernel: [   18.595146] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 17 20:18:17 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 17 20:18:17 node-1 kernel: [   37.164067] init: failsafe main process (8407) killed by TERM signal
Sep 17 20:18:18 node-1 dbus[8447]: [system] AppArmor D-Bus mediation is enabled
Sep 17 20:18:18 node-1 kernel: [   37.413011] audit_printk_skb: 30 callbacks suppressed
Sep 17 20:18:18 node-1 kernel: [   37.413013] type=1400 audit(1474143498.181:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8535 comm="apparmor_parser"
Sep 17 20:18:18 node-1 kernel: [   37.413180] type=1400 audit(1474143498.181:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8534 comm="apparmor_parser"
Sep 17 20:18:18 node-1 kernel: [   37.413186] type=1400 audit(1474143498.181:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Sep 17 20:18:18 node-1 kernel: [   37.413190] type=1400 audit(1474143498.181:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Sep 17 20:18:18 node-1 kernel: [   37.413419] type=1400 audit(1474143498.181:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Sep 17 20:18:18 node-1 kernel: [   37.413421] type=1400 audit(1474143498.181:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Sep 17 20:18:18 node-1 kernel: [   37.413547] type=1400 audit(1474143498.181:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Sep 17 20:18:18 node-1 kernel: [   37.492821] type=1400 audit(1474143498.257:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8537 comm="apparmor_parser"
Sep 17 20:18:18 node-1 anacron[8599]: Anacron 2.3 started on 2016-09-17
Sep 17 20:18:18 node-1 cron[8565]: (CRON) INFO (pidfile fd = 3)
Sep 17 20:18:18 node-1 cron[8607]: (CRON) STARTUP (fork ok)
Sep 17 20:18:18 node-1 anacron[8599]: Will run job `cron.daily' in 5 min.
Sep 17 20:18:18 node-1 anacron[8599]: Will run job `cron.weekly' in 10 min.
Sep 17 20:18:18 node-1 anacron[8599]: Will run job `cron.monthly' in 15 min.
Sep 17 20:18:18 node-1 anacron[8599]: Jobs will be executed sequentially
Sep 17 20:18:18 node-1 multipathd: path checkers start up
Sep 17 20:18:18 node-1 cron[8607]: (CRON) INFO (Running @reboot jobs)
Sep 17 20:18:18 node-1 postfix/master[8744]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 17 20:18:22 node-1 puppet-agent[8988]: Reopening log files
Sep 17 20:18:22 node-1 puppet-agent[8988]: Could not request certificate: Connection refused - connect(2)
Sep 17 20:18:47 node-1 kernel: [   66.513838] init: plymouth-upstart-bridge main process ended, respawning
Sep 17 20:18:47 node-1 puppet-agent[8988]: Could not run: SIGTERM
Sep 17 20:18:47 node-1 kernel: [   66.807146] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 17 20:18:47 node-1 ec2: 
Sep 17 20:18:47 node-1 ec2: #############################################################
Sep 17 20:18:47 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 17 20:18:47 node-1 ec2: 1024 81:ff:c8:8f:9a:c2:99:4f:0d:11:8c:55:7e:02:cb:26  root@node-1.domain.tld (DSA)
Sep 17 20:18:47 node-1 ec2: 256 df:8f:11:41:23:ee:52:f0:eb:f4:0b:fd:85:1c:75:cc  root@node-1.domain.tld (ECDSA)
Sep 17 20:18:47 node-1 ec2: 256 d9:ea:26:94:5b:84:d6:b8:3d:20:16:51:a3:4a:5f:50  root@node-1.domain.tld (ED25519)
Sep 17 20:18:47 node-1 ec2: 2048 0e:7b:dc:95:03:fa:61:6a:d0:6d:e8:53:eb:58:d4:cd  root@node-1.domain.tld (RSA)
Sep 17 20:18:47 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 17 20:18:47 node-1 ec2: #############################################################
Sep 17 20:18:54 node-1 puppet-user[9487]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 17 20:18:54 node-1 puppet-user[9487]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Sep 17 20:18:55 node-1 puppet-user[9487]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 17 20:18:55 node-1 puppet-user[9487]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 17 20:18:56 node-1 puppet-user[9487]: Finished catalog run in 1.08 seconds
Sep 17 20:18:57 node-1 multipathd: uevent trigger error
Sep 17 20:18:57 node-1 puppet-user[9917]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 17 20:18:57 node-1 puppet-user[9917]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 17 20:18:57 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 17 20:18:57 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 17 20:18:57 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 17 20:18:57 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 17 20:18:57 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 17 20:18:58 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 17 20:18:58 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 17 20:18:58 node-1 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 17 20:18:58 node-1 puppet-user[9917]: Finished catalog run in 0.06 seconds
Sep 17 20:18:59 node-1 puppet-user[10382]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 17 20:18:59 node-1 puppet-user[10382]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 17 20:18:59 node-1 puppet-user[10382]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 17 20:18:59 node-1 puppet-user[10382]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 17 20:18:59 node-1 puppet-user[10382]: Finished catalog run in 0.06 seconds
Sep 17 20:19:01 node-1 puppet-user[10853]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 17 20:19:01 node-1 puppet-user[10853]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 17 20:19:01 node-1 puppet-user[10853]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 17 20:19:01 node-1 CRON[11282]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 17 20:19:01 node-1 puppet-user[10853]: Finished catalog run in 0.03 seconds
Sep 17 20:19:02 node-1 puppet-user[11320]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 17 20:19:03 node-1 puppet-user[11320]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Sep 17 20:19:03 node-1 puppet-user[11320]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 17 20:19:03 node-1 puppet-user[11320]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 17 20:19:03 node-1 puppet-user[11320]: Finished catalog run in 0.47 seconds
Sep 17 20:19:05 node-1 puppet-user[11803]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 17 20:19:05 node-1 puppet-user[11803]: Compiled catalog for node-1.domain.tld in environment production in 0.25 seconds
Sep 17 20:19:05 node-1 puppet-user[11803]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 17 20:19:05 node-1 puppet-user[11803]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 17 20:19:05 node-1 puppet-user[11803]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 17 20:19:05 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 17 20:19:05 node-1 nailgun-agent: I, [2016-09-17T20:19:05.725351 #11285]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 17 20:19:05 node-1 puppet-user[11803]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 17 20:19:05 node-1 puppet-user[11803]: Finished catalog run in 0.25 seconds
Sep 17 20:19:07 node-1 puppet-user[12409]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 17 20:19:07 node-1 puppet-user[12409]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Sep 17 20:19:07 node-1 puppet-user[12409]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 17 20:19:07 node-1 kernel: [   86.862813] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 17 20:19:07 node-1 kernel: [   86.862862] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 17 20:19:07 node-1 puppet-user[12409]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 17 20:19:07 node-1 puppet-user[12409]: Finished catalog run in 0.07 seconds
Sep 17 20:19:09 node-1 puppet-user[12860]: (Scope(Class[main])) MODULAR: sync_time
Sep 17 20:19:09 node-1 puppet-user[12860]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 17 20:19:09 node-1 ntpdate[13270]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 17 20:19:15 node-1 ntpdate[13270]: adjust time server 10.20.0.2 offset -0.360999 sec
Sep 17 20:19:15 node-1 puppet-user[12860]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 17 20:19:15 node-1 puppet-user[12860]: Finished catalog run in 6.18 seconds
Sep 17 20:19:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 17 20:19:18 node-1 nailgun-agent: I, [2016-09-17T20:19:18.452613 #11285]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 17 20:19:21 node-1 puppet-user[13606]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 17 20:19:21 node-1 puppet-user[13606]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Sep 17 20:19:21 node-1 puppet-user[13606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 17 20:19:21 node-1 puppet-user[13606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Sep 17 20:19:21 node-1 puppet-user[13606]: Finished catalog run in 0.09 seconds
Sep 17 20:19:23 node-1 puppet-user[14067]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 17 20:19:23 node-1 puppet-user[14067]: Compiled catalog for node-1.domain.tld in environment production in 0.67 seconds
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 17 20:19:24 node-1 puppet-user[14067]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 17 20:19:24 node-1 puppet-user[14067]: Finished catalog run in 0.88 seconds
Sep 17 20:19:27 node-1 puppet-user[14566]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 17 20:19:27 node-1 puppet-user[14566]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Sep 17 20:19:30 node-1 puppet-user[14566]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 17 20:19:58 node-1 puppet-user[14566]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 17 20:19:58 node-1 puppet-user[14566]: Finished catalog run in 30.78 seconds
Sep 17 20:20:00 node-1 puppet-user[16912]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 17 20:20:00 node-1 puppet-user[16912]: Compiled catalog for node-1.domain.tld in environment production in 0.60 seconds
Sep 17 20:20:01 node-1 puppet-user[16912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 17 20:20:01 node-1 puppet-user[16912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 17 20:20:01 node-1 puppet-user[16912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 17 20:20:01 node-1 puppet-user[16912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 17 20:20:01 node-1 puppet-user[16912]: Finished catalog run in 0.11 seconds
Sep 17 20:20:01 node-1 CRON[17363]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 17 20:20:02 node-1 puppet-user[17385]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 17 20:20:03 node-1 puppet-user[17385]: Compiled catalog for node-1.domain.tld in environment production in 0.91 seconds
Sep 17 20:20:04 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 17 20:20:04 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 17 20:20:04 node-1 crontab[17830]: (root) LIST (root)
Sep 17 20:20:04 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 17 20:20:04 node-1 crontab[17831]: (root) REPLACE (root)
Sep 17 20:20:05 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 17 20:20:05 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 17 20:20:05 node-1 nailgun-agent: I, [2016-09-17T20:20:05.615128 #17366]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 17 20:20:06 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 17 20:20:07 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 17 20:20:07 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 17 20:20:07 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 17 20:20:07 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 17 20:20:07 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 17 20:20:07 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 17 20:20:07 node-1 puppet-user[17385]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 17 20:20:07 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 20:20:07 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 17 20:20:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:21 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:21 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:21 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:21 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:21 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:20:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:21 node-1 ntpdate[29425]: no servers can be used, exiting
<27>Sep 17 20:21:21 node-1 ntpdate[29722]: no servers can be used, exiting
<27>Sep 17 20:21:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:21:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:22:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 20:23:16 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 20:23:21 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 20:23:21 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 20:23:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 20:23:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 20:23:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 20:23:39 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:23:58 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:01 node-1 haproxy[19376]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:01 node-1 haproxy[19376]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:01 node-1 haproxy[19376]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:01 node-1 haproxy[19376]: proxy mysqld has no server available!
<27>Sep 17 20:24:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:07 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:10 node-1 haproxy[22043]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:10 node-1 haproxy[22043]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:10 node-1 haproxy[22043]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:10 node-1 haproxy[22043]: proxy mysqld has no server available!
<129>Sep 17 20:24:11 node-1 haproxy[22047]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:11 node-1 haproxy[22047]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:11 node-1 haproxy[22047]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:11 node-1 haproxy[22047]: proxy object-storage has no server available!
<27>Sep 17 20:24:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:13 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:15 node-1 haproxy[23551]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:16 node-1 haproxy[23555]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:16 node-1 haproxy[23555]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:16 node-1 haproxy[23555]: proxy neutron has no server available!
<129>Sep 17 20:24:16 node-1 haproxy[23555]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:16 node-1 haproxy[23555]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:16 node-1 haproxy[23555]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:16 node-1 haproxy[23555]: proxy mysqld has no server available!
<129>Sep 17 20:24:16 node-1 haproxy[23555]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:17 node-1 haproxy[23555]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:17 node-1 haproxy[23555]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:17 node-1 haproxy[23555]: proxy object-storage has no server available!
<27>Sep 17 20:24:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:18 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:21 node-1 haproxy[24934]: proxy keystone-1 has no server available!
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:21 node-1 haproxy[24934]: proxy keystone-2 has no server available!
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:21 node-1 haproxy[24934]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:22 node-1 haproxy[24938]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:22 node-1 haproxy[24938]: proxy neutron has no server available!
<129>Sep 17 20:24:22 node-1 haproxy[24938]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:22 node-1 haproxy[24938]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:22 node-1 haproxy[24938]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:22 node-1 haproxy[24938]: proxy mysqld has no server available!
<129>Sep 17 20:24:22 node-1 haproxy[24938]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:22 node-1 haproxy[24938]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:22 node-1 haproxy[24938]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:22 node-1 haproxy[24938]: proxy object-storage has no server available!
<27>Sep 17 20:24:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:24 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:26 node-1 haproxy[26312]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:26 node-1 haproxy[26312]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:26 node-1 haproxy[26312]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:26 node-1 haproxy[26312]: proxy keystone-1 has no server available!
<129>Sep 17 20:24:26 node-1 haproxy[26312]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:26 node-1 haproxy[26312]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:27 node-1 haproxy[26316]: proxy keystone-2 has no server available!
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:27 node-1 haproxy[26316]: proxy neutron has no server available!
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:27 node-1 haproxy[26316]: proxy mysqld has no server available!
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:27 node-1 haproxy[26316]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:27 node-1 haproxy[26316]: proxy object-storage has no server available!
<129>Sep 17 20:24:28 node-1 haproxy[26316]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:28 node-1 haproxy[26316]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:28 node-1 haproxy[26316]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:28 node-1 haproxy[26316]: proxy aodh has no server available!
<27>Sep 17 20:24:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:29 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:31 node-1 haproxy[27852]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:32 node-1 haproxy[27856]: proxy keystone-1 has no server available!
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:32 node-1 haproxy[27856]: proxy keystone-2 has no server available!
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:32 node-1 haproxy[27856]: proxy neutron has no server available!
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:32 node-1 haproxy[27856]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:32 node-1 haproxy[27856]: proxy mysqld has no server available!
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:33 node-1 haproxy[27856]: proxy object-storage has no server available!
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:33 node-1 haproxy[27856]: proxy aodh has no server available!
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:33 node-1 haproxy[27856]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:33 node-1 haproxy[27856]: proxy ceilometer has no server available!
<27>Sep 17 20:24:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:35 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:37 node-1 haproxy[29241]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:37 node-1 haproxy[29241]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:37 node-1 haproxy[29241]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:37 node-1 haproxy[29241]: proxy keystone-1 has no server available!
<129>Sep 17 20:24:37 node-1 haproxy[29241]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:37 node-1 haproxy[29241]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:38 node-1 haproxy[29245]: proxy keystone-2 has no server available!
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:38 node-1 haproxy[29245]: proxy neutron has no server available!
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:38 node-1 haproxy[29245]: proxy mysqld has no server available!
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:38 node-1 haproxy[29245]: proxy object-storage has no server available!
<129>Sep 17 20:24:38 node-1 haproxy[29245]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:39 node-1 haproxy[29245]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:39 node-1 haproxy[29245]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:39 node-1 haproxy[29245]: proxy aodh has no server available!
<129>Sep 17 20:24:39 node-1 haproxy[29245]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:39 node-1 haproxy[29245]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:39 node-1 haproxy[29245]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:39 node-1 haproxy[29245]: proxy ceilometer has no server available!
<27>Sep 17 20:24:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:40 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:40 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:42 node-1 haproxy[30583]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:43 node-1 haproxy[30592]: proxy keystone-1 has no server available!
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:43 node-1 haproxy[30592]: proxy keystone-2 has no server available!
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:43 node-1 haproxy[30592]: proxy neutron has no server available!
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:43 node-1 haproxy[30592]: proxy mysqld has no server available!
<129>Sep 17 20:24:43 node-1 haproxy[30592]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:44 node-1 haproxy[30592]: proxy object-storage has no server available!
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:44 node-1 haproxy[30592]: proxy aodh has no server available!
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:44 node-1 haproxy[30592]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:44 node-1 haproxy[30592]: proxy ceilometer has no server available!
<27>Sep 17 20:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:45 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:48 node-1 haproxy[32009]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:48 node-1 haproxy[32009]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:48 node-1 haproxy[32009]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:48 node-1 haproxy[32009]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:48 node-1 haproxy[32009]: proxy keystone-1 has no server available!
<129>Sep 17 20:24:48 node-1 haproxy[32009]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:48 node-1 haproxy[32009]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:49 node-1 haproxy[32016]: proxy keystone-2 has no server available!
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:49 node-1 haproxy[32016]: proxy glance-api has no server available!
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:49 node-1 haproxy[32016]: proxy glance-glare has no server available!
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:49 node-1 haproxy[32016]: proxy neutron has no server available!
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:49 node-1 haproxy[32016]: proxy glance-registry has no server available!
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:49 node-1 haproxy[32016]: proxy mysqld has no server available!
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:49 node-1 haproxy[32016]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:50 node-1 haproxy[32016]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:50 node-1 haproxy[32016]: proxy object-storage has no server available!
<129>Sep 17 20:24:50 node-1 haproxy[32016]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:50 node-1 haproxy[32016]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:50 node-1 haproxy[32016]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:50 node-1 haproxy[32016]: proxy aodh has no server available!
<129>Sep 17 20:24:50 node-1 haproxy[32016]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:50 node-1 haproxy[32016]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:50 node-1 haproxy[32016]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:50 node-1 haproxy[32016]: proxy ceilometer has no server available!
<27>Sep 17 20:24:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:51 node-1 multipathd: uevent trigger error
<129>Sep 17 20:24:54 node-1 haproxy[1001]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:54 node-1 haproxy[1001]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:54 node-1 haproxy[1001]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:54 node-1 haproxy[1001]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:54 node-1 haproxy[1001]: proxy keystone-1 has no server available!
<129>Sep 17 20:24:54 node-1 haproxy[1001]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:54 node-1 haproxy[1001]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy keystone-2 has no server available!
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy nova-api has no server available!
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy nova-metadata-api has no server available!
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy glance-api has no server available!
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy glance-glare has no server available!
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy neutron has no server available!
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy glance-registry has no server available!
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:55 node-1 haproxy[1005]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:55 node-1 haproxy[1005]: proxy mysqld has no server available!
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:56 node-1 haproxy[1005]: proxy object-storage has no server available!
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:56 node-1 haproxy[1005]: proxy aodh has no server available!
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:56 node-1 haproxy[1005]: proxy ceilometer has no server available!
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:24:56 node-1 haproxy[1005]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:24:56 node-1 haproxy[1005]: proxy nova-novncproxy has no server available!
<27>Sep 17 20:24:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:24:57 node-1 multipathd: uevent trigger error
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:00 node-1 haproxy[2354]: proxy keystone-1 has no server available!
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:00 node-1 haproxy[2354]: proxy keystone-2 has no server available!
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:00 node-1 haproxy[2354]: proxy nova-api has no server available!
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:00 node-1 haproxy[2354]: proxy nova-metadata-api has no server available!
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:00 node-1 haproxy[2354]: proxy cinder-api has no server available!
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:00 node-1 haproxy[2354]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy glance-api has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy glance-glare has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy neutron has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy glance-registry has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy mysqld has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy object-storage has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy aodh has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:01 node-1 haproxy[2358]: proxy ceilometer has no server available!
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:01 node-1 haproxy[2358]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:02 node-1 haproxy[2358]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:02 node-1 haproxy[2358]: proxy nova-novncproxy has no server available!
<27>Sep 17 20:25:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:03 node-1 multipathd: uevent trigger error
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:06 node-1 haproxy[3750]: proxy keystone-1 has no server available!
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:06 node-1 haproxy[3750]: proxy keystone-2 has no server available!
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:06 node-1 haproxy[3750]: proxy nova-api has no server available!
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:06 node-1 haproxy[3750]: proxy nova-metadata-api has no server available!
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:06 node-1 haproxy[3750]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:06 node-1 haproxy[3750]: proxy cinder-api has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy glance-api has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy glance-glare has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy neutron has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy glance-registry has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy mysqld has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy object-storage has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy aodh has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy ceilometer has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:07 node-1 haproxy[3754]: proxy heat-api has no server available!
<129>Sep 17 20:25:07 node-1 haproxy[3754]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:08 node-1 haproxy[3754]: proxy heat-api-cfn has no server available!
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:08 node-1 haproxy[3754]: proxy heat-api-cloudwatch has no server available!
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 20:25:08 node-1 haproxy[3754]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 20:25:08 node-1 haproxy[3754]: proxy nova-novncproxy has no server available!
<27>Sep 17 20:25:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:12 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:12 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:12 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:12 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:12 node-1 multipathd: uevent trigger error
<27>Sep 17 20:25:20 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 17 20:25:44 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Sep 17 20:25:46 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 17 20:26:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:26:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 20:26:42 node-1 multipathd: uevent trigger error
<27>Sep 17 20:26:42 node-1 multipathd: uevent trigger error
<27>Sep 17 20:26:42 node-1 multipathd: uevent trigger error
<27>Sep 17 20:26:42 node-1 multipathd: uevent trigger error
<27>Sep 17 20:26:42 node-1 multipathd: uevent trigger error
<27>Sep 17 20:26:42 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:35 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:35 node-1 multipathd: uevent trigger error
<43>Sep 17 20:28:47 node-1 apache2_error [Sat Sep 17 20:28:46.164614 2016] [mpm_event:notice] [pid 9286:tid 140702775809920] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 17 20:28:47 node-1 apache2_error [Sat Sep 17 20:28:46.164771 2016] [core:notice] [pid 9286:tid 140702775809920] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 20:28:54 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:54 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:54 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:54 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:54 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:54 node-1 multipathd: uevent trigger error
<43>Sep 17 20:28:57 node-1 apache2_error [Sat Sep 17 20:28:49.161902 2016] [mpm_event:notice] [pid 9286:tid 140702775809920] AH00491: caught SIGTERM, shutting down
<43>Sep 17 20:28:57 node-1 apache2_error [Sat Sep 17 20:28:50.251157 2016] [mpm_worker:notice] [pid 9653:tid 140660721706880] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 17 20:28:57 node-1 apache2_error [Sat Sep 17 20:28:50.251205 2016] [core:notice] [pid 9653:tid 140660721706880] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 20:28:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:28:57 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:29:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:46 node-1 multipathd: uevent trigger error
<43>Sep 17 20:29:47 node-1 apache2_error [Sat Sep 17 20:29:43.035446 2016] [mpm_worker:notice] [pid 9653:tid 140660721706880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 20:29:47 node-1 apache2_error [Sat Sep 17 20:29:43.043279 2016] [mpm_worker:warn] [pid 9653:tid 140660721706880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 20:29:47 node-1 apache2_error [Sat Sep 17 20:29:43.044027 2016] [mpm_worker:notice] [pid 9653:tid 140660721706880] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 17 20:29:47 node-1 apache2_error [Sat Sep 17 20:29:43.044041 2016] [core:notice] [pid 9653:tid 140660721706880] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 20:29:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:29:51 node-1 multipathd: uevent trigger error
<43>Sep 17 20:30:57 node-1 apache2_error [Sat Sep 17 20:30:53.785388 2016] [mpm_worker:notice] [pid 9653:tid 140660721706880] AH00295: caught SIGTERM, shutting down
<43>Sep 17 20:30:57 node-1 apache2_error [Sat Sep 17 20:30:54.540658 2016] [mpm_worker:notice] [pid 31890:tid 140001305261952] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 20:30:57 node-1 apache2_error [Sat Sep 17 20:30:54.540698 2016] [core:notice] [pid 31890:tid 140001305261952] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 17 20:31:47 node-1 apache2_error [Sat Sep 17 20:31:39.078481 2016] [mpm_worker:notice] [pid 31890:tid 140001305261952] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 20:31:47 node-1 apache2_error [Sat Sep 17 20:31:39.088920 2016] [mpm_worker:warn] [pid 31890:tid 140001305261952] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 20:31:47 node-1 apache2_error [Sat Sep 17 20:31:39.095596 2016] [mpm_worker:notice] [pid 31890:tid 140001305261952] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 20:31:47 node-1 apache2_error [Sat Sep 17 20:31:39.095618 2016] [core:notice] [pid 31890:tid 140001305261952] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 20:32:34 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:33:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:04 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:09 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:45 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:45 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:46 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:33:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:34:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:35:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:36:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:36:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:36:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:36:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:36:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:00 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:28 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:28 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:28 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:28 node-1 multipathd: uevent trigger error
<27>Sep 17 20:37:28 node-1 multipathd: uevent trigger error
<27>Sep 17 20:38:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:39:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:39:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:39:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:39:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:39:50 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:06 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:06 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:06 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:06 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:06 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:06 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:06 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:40:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:41:19 node-1 multipathd: uevent trigger error
<27>Sep 17 20:41:19 node-1 multipathd: uevent trigger error
<27>Sep 17 20:41:19 node-1 multipathd: uevent trigger error
<27>Sep 17 20:41:19 node-1 multipathd: uevent trigger error
<27>Sep 17 20:41:19 node-1 multipathd: uevent trigger error
<27>Sep 17 20:41:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:42:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:34 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:34 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:34 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:34 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:34 node-1 multipathd: uevent trigger error
<27>Sep 17 20:42:34 node-1 multipathd: uevent trigger error
<27>Sep 17 20:44:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:44:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:44:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:44:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:44:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:44:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:44:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:45:18 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Sep 17 20:46:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:27 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:27 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:27 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:27 node-1 multipathd: uevent trigger error
<27>Sep 17 20:46:27 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:07 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:23 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:29 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 20:47:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:47:53 node-1 multipathd: uevent trigger error
<27>Sep 17 20:48:59 node-1 multipathd: uevent trigger error
<27>Sep 17 20:48:59 node-1 multipathd: uevent trigger error
<27>Sep 17 20:48:59 node-1 multipathd: uevent trigger error
<27>Sep 17 20:48:59 node-1 multipathd: uevent trigger error
<27>Sep 17 20:48:59 node-1 multipathd: uevent trigger error
<27>Sep 17 20:48:59 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:13 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:13 node-1 multipathd: uevent trigger error
<11>Sep 17 20:49:26 node-1 liberasurecode[83051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:26 node-1 liberasurecode[83051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:26 node-1 liberasurecode[83051]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:26 node-1 liberasurecode[83051]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:26 node-1 liberasurecode[83075]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:26 node-1 liberasurecode[83075]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:26 node-1 liberasurecode[83075]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:26 node-1 liberasurecode[83075]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:28 node-1 liberasurecode[83475]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:28 node-1 liberasurecode[83475]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:28 node-1 liberasurecode[83475]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:28 node-1 liberasurecode[83475]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85330]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85330]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85330]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85330]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85425]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85425]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85425]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85425]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85596]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:32 node-1 liberasurecode[85596]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85671]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85671]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85683]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85683]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85683]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85683]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85702]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85702]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85702]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85702]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85714]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:33 node-1 liberasurecode[85714]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:49 node-1 liberasurecode[86480]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:49 node-1 liberasurecode[86480]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:49 node-1 liberasurecode[86480]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:49:49 node-1 liberasurecode[86480]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 17 20:49:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:49:58 node-1 multipathd: uevent trigger error
<11>Sep 17 20:50:02 node-1 liberasurecode[88882]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:50:02 node-1 liberasurecode[88882]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:50:02 node-1 liberasurecode[88882]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:50:02 node-1 liberasurecode[88882]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 17 20:50:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 17 20:50:49 node-1 apache2_error [Sat Sep 17 20:50:45.219344 2016] [mpm_worker:notice] [pid 31890:tid 140001305261952] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 20:50:49 node-1 apache2_error [Sat Sep 17 20:50:45.603548 2016] [mpm_worker:warn] [pid 31890:tid 140001305261952] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 20:50:49 node-1 apache2_error [Sat Sep 17 20:50:45.609440 2016] [mpm_worker:notice] [pid 31890:tid 140001305261952] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 20:50:49 node-1 apache2_error [Sat Sep 17 20:50:45.609462 2016] [core:notice] [pid 31890:tid 140001305261952] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 20:51:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:26 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:26 node-1 multipathd: uevent trigger error
<43>Sep 17 20:51:29 node-1 apache2_error [Sat Sep 17 20:51:22.572295 2016] [mpm_worker:notice] [pid 31890:tid 140001305261952] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 20:51:29 node-1 apache2_error [Sat Sep 17 20:51:22.768335 2016] [mpm_worker:warn] [pid 31890:tid 140001305261952] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 20:51:29 node-1 apache2_error [Sat Sep 17 20:51:22.779318 2016] [mpm_worker:notice] [pid 31890:tid 140001305261952] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 20:51:29 node-1 apache2_error [Sat Sep 17 20:51:22.779350 2016] [core:notice] [pid 31890:tid 140001305261952] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 20:51:32 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:32 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:32 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:32 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:32 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:32 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:32 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:37 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:37 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:37 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:37 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:37 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:54 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:54 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:51:55 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:17 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:24 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:30 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 17 20:52:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:38 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:39 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:39 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:39 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:52 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:52:58 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:15 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 20:53:16 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:16 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:16 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:16 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:16 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:43 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:53:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:03 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:08 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:22 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:51 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:54:56 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:01 node-1 multipathd: uevent trigger error
<11>Sep 17 20:55:02 node-1 liberasurecode[156528]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:55:02 node-1 liberasurecode[156528]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:55:02 node-1 liberasurecode[156528]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 20:55:02 node-1 liberasurecode[156528]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 17 20:55:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:05 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:10 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:18 node-1 multipathd: uevent trigger error
<27>Sep 17 20:55:18 node-1 multipathd: uevent trigger error
