Sep 26 08:23:58 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8385" x-info="http://www.rsyslog.com"] start
Sep 26 08:23:58 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 26 08:23:58 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 26 08:23:58 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 26 08:23:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 26 08:23:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 26 08:23:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 26 08:23:58 node-1 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Sep 26 08:23:58 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=04f3c8b4-d5b9-44a7-a2e2-0d486c093575 nomdmonddf nomdmonisw
Sep 26 08:23:58 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 26 08:23:58 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 26 08:23:58 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 26 08:23:58 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 26 08:23:58 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 26 08:23:58 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 26 08:23:58 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 26 08:23:58 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 26 08:23:58 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 26 08:23:58 node-1 kernel: [    0.000000] No AGP bridge found
Sep 26 08:23:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 26 08:23:58 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 26 08:23:58 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 26 08:23:58 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 26 08:23:58 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 26 08:23:58 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 26 08:23:58 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 26 08:23:58 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 26 08:23:58 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 26 08:23:58 node-1 kernel: [    0.000000]   2 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000]   3 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000]   4 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000]   5 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000]   6 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000]   7 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000]   8 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000]   9 disabled
Sep 26 08:23:58 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 26 08:23:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 26 08:23:58 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 26 08:23:58 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 26 08:23:58 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 26 08:23:58 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 26 08:23:58 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 26 08:23:58 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 26 08:23:58 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 26 08:23:58 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 26 08:23:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 26 08:23:58 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35828000-0x36c0bfff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 26 08:23:58 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 26 08:23:58 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 26 08:23:58 node-1 kernel: [    0.000000] Zone ranges:
Sep 26 08:23:58 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 26 08:23:58 node-1 kernel: [    0.000000] Early memory node ranges
Sep 26 08:23:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep 26 08:23:58 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 26 08:23:58 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 26 08:23:58 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 26 08:23:58 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep 26 08:23:58 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep 26 08:23:58 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 26 08:23:58 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 26 08:23:58 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 26 08:23:58 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 26 08:23:58 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 26 08:23:58 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 26 08:23:58 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 26 08:23:58 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 26 08:23:58 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 26 08:23:58 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 26 08:23:58 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 26 08:23:58 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 26 08:23:58 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 26 08:23:58 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 26 08:23:58 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 26 08:23:58 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 26 08:23:58 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 26 08:23:58 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 26 08:23:58 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep 26 08:23:58 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 26 08:23:58 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=04f3c8b4-d5b9-44a7-a2e2-0d486c093575 nomdmonddf nomdmonisw
Sep 26 08:23:58 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 26 08:23:58 node-1 kernel: [    0.000000] Checking aperture...
Sep 26 08:23:58 node-1 kernel: [    0.000000] No AGP bridge found
Sep 26 08:23:58 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 26 08:23:58 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 26 08:23:58 node-1 kernel: [    0.000000] Memory: 32653468K/33280636K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627168K reserved)
Sep 26 08:23:58 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 26 08:23:58 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 26 08:23:58 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 26 08:23:58 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 26 08:23:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 26 08:23:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 26 08:23:58 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 26 08:23:58 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 26 08:23:58 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 26 08:23:58 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 26 08:23:58 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 26 08:23:58 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 26 08:23:58 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 26 08:23:58 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 26 08:23:58 node-1 kernel: [    0.004000] tsc: Detected 3491.622 MHz processor
Sep 26 08:23:58 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.24 BogoMIPS (lpj=13966488)
Sep 26 08:23:58 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 26 08:23:58 node-1 kernel: [    0.000043] Security Framework initialized
Sep 26 08:23:58 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Sep 26 08:23:58 node-1 kernel: [    0.000062] Yama: becoming mindful.
Sep 26 08:23:58 node-1 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.006332] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.008262] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.008289] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.008580] Initializing cgroup subsys memory
Sep 26 08:23:58 node-1 kernel: [    0.008588] Initializing cgroup subsys devices
Sep 26 08:23:58 node-1 kernel: [    0.008590] Initializing cgroup subsys freezer
Sep 26 08:23:58 node-1 kernel: [    0.008592] Initializing cgroup subsys blkio
Sep 26 08:23:58 node-1 kernel: [    0.008593] Initializing cgroup subsys perf_event
Sep 26 08:23:58 node-1 kernel: [    0.008595] Initializing cgroup subsys hugetlb
Sep 26 08:23:58 node-1 kernel: [    0.008614] CPU: Physical Processor ID: 0
Sep 26 08:23:58 node-1 kernel: [    0.008616] CPU: Processor Core ID: 0
Sep 26 08:23:58 node-1 kernel: [    0.008619] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 26 08:23:58 node-1 kernel: [    0.008619] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 26 08:23:58 node-1 kernel: [    0.009313] mce: CPU supports 22 MCE banks
Sep 26 08:23:58 node-1 kernel: [    0.009341] CPU0: Thermal monitoring enabled (TM1)
Sep 26 08:23:58 node-1 kernel: [    0.009361] process: using mwait in idle threads
Sep 26 08:23:58 node-1 kernel: [    0.009365] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 26 08:23:58 node-1 kernel: [    0.009365] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 26 08:23:58 node-1 kernel: [    0.009365] tlb_flushall_shift: 6
Sep 26 08:23:58 node-1 kernel: [    0.009453] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 26 08:23:58 node-1 kernel: [    0.010177] ACPI: Core revision 20131115
Sep 26 08:23:58 node-1 kernel: [    0.022846] ACPI: All ACPI Tables successfully acquired
Sep 26 08:23:58 node-1 kernel: [    0.023006] ftrace: allocating 28614 entries in 112 pages
Sep 26 08:23:58 node-1 kernel: [    0.031707] dmar: Host address width 46
Sep 26 08:23:58 node-1 kernel: [    0.031709] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 26 08:23:58 node-1 kernel: [    0.031715] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 26 08:23:58 node-1 kernel: [    0.031717] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 26 08:23:58 node-1 kernel: [    0.031721] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 26 08:23:58 node-1 kernel: [    0.031723] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 26 08:23:58 node-1 kernel: [    0.031724] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 26 08:23:58 node-1 kernel: [    0.031725] dmar: ATSR flags: 0x0
Sep 26 08:23:58 node-1 kernel: [    0.031726] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 26 08:23:58 node-1 kernel: [    0.031727] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 26 08:23:58 node-1 kernel: [    0.031843] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 26 08:23:58 node-1 kernel: [    0.031844] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 26 08:23:58 node-1 kernel: [    0.031845] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 26 08:23:58 node-1 kernel: [    0.031846] HPET id 0 under DRHD base 0xc7ffc000
Sep 26 08:23:58 node-1 kernel: [    0.031847] Your BIOS is broken and requested that x2apic be disabled.
Sep 26 08:23:58 node-1 kernel: [    0.031847] This will slightly decrease performance.
Sep 26 08:23:58 node-1 kernel: [    0.031847] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 26 08:23:58 node-1 kernel: [    0.032278] Enabled IRQ remapping in xapic mode
Sep 26 08:23:58 node-1 kernel: [    0.032279] x2apic not enabled, IRQ remapping is in xapic mode
Sep 26 08:23:58 node-1 kernel: [    0.032283] Switched APIC routing to physical flat.
Sep 26 08:23:58 node-1 kernel: [    0.032855] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 26 08:23:58 node-1 kernel: [    0.072502] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 26 08:23:58 node-1 kernel: [    0.072507] TSC deadline timer enabled
Sep 26 08:23:58 node-1 kernel: [    0.072515] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 26 08:23:58 node-1 kernel: [    0.072520] ... version:                3
Sep 26 08:23:58 node-1 kernel: [    0.072521] ... bit width:              48
Sep 26 08:23:58 node-1 kernel: [    0.072522] ... generic registers:      4
Sep 26 08:23:58 node-1 kernel: [    0.072523] ... value mask:             0000ffffffffffff
Sep 26 08:23:58 node-1 kernel: [    0.072524] ... max period:             0000ffffffffffff
Sep 26 08:23:58 node-1 kernel: [    0.072525] ... fixed-purpose events:   3
Sep 26 08:23:58 node-1 kernel: [    0.072526] ... event mask:             000000070000000f
Sep 26 08:23:58 node-1 kernel: [    0.073916] x86: Booting SMP configuration:
Sep 26 08:23:58 node-1 kernel: [    0.088019] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 26 08:23:58 node-1 kernel: [    0.073918] .... node  #0, CPUs:        #1  #2  #3
Sep 26 08:23:58 node-1 kernel: [    0.115925] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 26 08:23:58 node-1 kernel: [    0.270063] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 26 08:23:58 node-1 kernel: [    0.325687] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 26 08:23:58 node-1 kernel: [    0.382736] x86: Booted up 2 nodes, 16 CPUs
Sep 26 08:23:58 node-1 kernel: [    0.382739] smpboot: Total of 16 processors activated (111744.55 BogoMIPS)
Sep 26 08:23:58 node-1 kernel: [    0.407117] devtmpfs: initialized
Sep 26 08:23:58 node-1 kernel: [    0.409902] EVM: security.selinux
Sep 26 08:23:58 node-1 kernel: [    0.409904] EVM: security.SMACK64
Sep 26 08:23:58 node-1 kernel: [    0.409905] EVM: security.ima
Sep 26 08:23:58 node-1 kernel: [    0.409906] EVM: security.capability
Sep 26 08:23:58 node-1 kernel: [    0.409957] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.410648] pinctrl core: initialized pinctrl subsystem
Sep 26 08:23:58 node-1 kernel: [    0.410712] regulator-dummy: no parameters
Sep 26 08:23:58 node-1 kernel: [    0.410744] RTC time:  8:23:22, date: 09/26/16
Sep 26 08:23:58 node-1 kernel: [    0.410779] NET: Registered protocol family 16
Sep 26 08:23:58 node-1 kernel: [    0.410862] cpuidle: using governor ladder
Sep 26 08:23:58 node-1 kernel: [    0.410863] cpuidle: using governor menu
Sep 26 08:23:58 node-1 kernel: [    0.410898] ACPI: bus type PCI registered
Sep 26 08:23:58 node-1 kernel: [    0.410900] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 26 08:23:58 node-1 kernel: [    0.410944] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 26 08:23:58 node-1 kernel: [    0.410947] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 26 08:23:58 node-1 kernel: [    0.424697] PCI: Using configuration type 1 for base access
Sep 26 08:23:58 node-1 kernel: [    0.425697] bio: create slab <bio-0> at 0
Sep 26 08:23:58 node-1 kernel: [    0.425977] ACPI: Added _OSI(Module Device)
Sep 26 08:23:58 node-1 kernel: [    0.425979] ACPI: Added _OSI(Processor Device)
Sep 26 08:23:58 node-1 kernel: [    0.425980] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 26 08:23:58 node-1 kernel: [    0.425981] ACPI: Added _OSI(Processor Aggregator Device)
Sep 26 08:23:58 node-1 kernel: [    0.438834] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 26 08:23:58 node-1 kernel: [    0.449576] ACPI: Interpreter enabled
Sep 26 08:23:58 node-1 kernel: [    0.449581] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 26 08:23:58 node-1 kernel: [    0.449585] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 26 08:23:58 node-1 kernel: [    0.449588] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 26 08:23:58 node-1 kernel: [    0.449595] ACPI: (supports S0 S4 S5)
Sep 26 08:23:58 node-1 kernel: [    0.449596] ACPI: Using IOAPIC for interrupt routing
Sep 26 08:23:58 node-1 kernel: [    0.449637] HEST: Table parsing has been initialized.
Sep 26 08:23:58 node-1 kernel: [    0.449640] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 26 08:23:58 node-1 kernel: [    0.450199] ACPI: No dock devices found.
Sep 26 08:23:58 node-1 kernel: [    0.461872] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 26 08:23:58 node-1 kernel: [    0.461876] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 08:23:58 node-1 kernel: [    0.461880] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 26 08:23:58 node-1 kernel: [    0.461907] PCI host bridge to bus 0000:ff
Sep 26 08:23:58 node-1 kernel: [    0.461909] pci_bus 0000:ff: root bus resource [bus ff]
Sep 26 08:23:58 node-1 kernel: [    0.461917] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.461956] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.461987] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462022] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462051] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.462081] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.462112] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462141] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462170] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462199] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462226] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462252] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462281] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462307] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462334] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462361] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462390] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462417] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462444] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.462473] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462499] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.462525] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462551] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462582] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.462618] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462650] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462680] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462711] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462742] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462774] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462807] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462840] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462871] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462903] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462937] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.462970] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463005] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463036] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463064] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463097] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463133] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463171] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463205] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463238] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463270] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463299] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463330] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463359] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463390] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463424] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463456] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463484] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463513] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463544] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463574] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463605] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463642] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463701] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 26 08:23:58 node-1 kernel: [    0.463704] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 08:23:58 node-1 kernel: [    0.463707] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 26 08:23:58 node-1 kernel: [    0.463726] PCI host bridge to bus 0000:7f
Sep 26 08:23:58 node-1 kernel: [    0.463727] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 26 08:23:58 node-1 kernel: [    0.463732] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463760] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.463787] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463817] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463839] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.463864] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.463891] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463918] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463941] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463964] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.463987] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464009] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464033] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464055] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464079] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464105] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464127] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464150] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464173] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.464197] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464219] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.464241] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464264] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464291] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 26 08:23:58 node-1 kernel: [    0.464327] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464353] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464380] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464406] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464432] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464460] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464489] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464519] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464544] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464570] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464597] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464623] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464650] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464675] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464699] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464728] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464753] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464779] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464808] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464834] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464860] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464886] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464911] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464937] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464963] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.464989] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.465019] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.465044] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.465066] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.465089] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.465114] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.465143] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.465169] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.466413] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 26 08:23:58 node-1 kernel: [    0.466416] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 08:23:58 node-1 kernel: [    0.467549] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 26 08:23:58 node-1 kernel: [    0.468058] PCI host bridge to bus 0000:00
Sep 26 08:23:58 node-1 kernel: [    0.468060] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 26 08:23:58 node-1 kernel: [    0.468062] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 26 08:23:58 node-1 kernel: [    0.468063] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 26 08:23:58 node-1 kernel: [    0.468064] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 26 08:23:58 node-1 kernel: [    0.468066] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 26 08:23:58 node-1 kernel: [    0.468067] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 26 08:23:58 node-1 kernel: [    0.468068] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 26 08:23:58 node-1 kernel: [    0.468074] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 26 08:23:58 node-1 kernel: [    0.468157] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.468188] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.468229] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 26 08:23:58 node-1 kernel: [    0.468249] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.468278] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.468319] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 26 08:23:58 node-1 kernel: [    0.468337] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.468367] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.468409] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 26 08:23:58 node-1 kernel: [    0.468426] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.468496] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.468574] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.468651] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 26 08:23:58 node-1 kernel: [    0.468656] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 26 08:23:58 node-1 kernel: [    0.468742] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 26 08:23:58 node-1 kernel: [    0.468888] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 26 08:23:58 node-1 kernel: [    0.468906] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 26 08:23:58 node-1 kernel: [    0.468983] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.469039] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 26 08:23:58 node-1 kernel: [    0.469061] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.469116] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.469160] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 26 08:23:58 node-1 kernel: [    0.469188] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.469244] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.469287] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 26 08:23:58 node-1 kernel: [    0.469309] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 26 08:23:58 node-1 kernel: [    0.469327] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 26 08:23:58 node-1 kernel: [    0.469404] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.469454] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 26 08:23:58 node-1 kernel: [    0.469481] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 26 08:23:58 node-1 kernel: [    0.469731] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 26 08:23:58 node-1 kernel: [    0.469737] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 26 08:23:58 node-1 kernel: [    0.469743] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.469749] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.469756] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 26 08:23:58 node-1 kernel: [    0.469801] pci 0000:01:00.0: supports D1 D2
Sep 26 08:23:58 node-1 kernel: [    0.475634] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 26 08:23:58 node-1 kernel: [    0.475637] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 26 08:23:58 node-1 kernel: [    0.475639] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 26 08:23:58 node-1 kernel: [    0.475748] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.475781] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 26 08:23:58 node-1 kernel: [    0.483624] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 26 08:23:58 node-1 kernel: [    0.483630] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.483634] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 08:23:58 node-1 kernel: [    0.483718] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.483799] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.483880] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.483926] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 26 08:23:58 node-1 kernel: [    0.483929] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.483931] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 08:23:58 node-1 kernel: [    0.483989] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.484112] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.484166] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 26 08:23:58 node-1 kernel: [    0.484168] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.484171] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.484219] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.484342] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.484380] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.484498] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.484534] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.484654] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.484692] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 26 08:23:58 node-1 kernel: [    0.484813] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 26 08:23:58 node-1 kernel: [    0.484857] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 26 08:23:58 node-1 kernel: [    0.484859] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.484861] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.484920] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 26 08:23:58 node-1 kernel: [    0.484999] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.485050] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.485090] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 26 08:23:58 node-1 kernel: [    0.485170] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 26 08:23:58 node-1 kernel: [    0.485277] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 26 08:23:58 node-1 kernel: [    0.485280] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.485282] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.485341] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 26 08:23:58 node-1 kernel: [    0.485395] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.485443] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.485654] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 26 08:23:58 node-1 kernel: [    0.485658] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 26 08:23:58 node-1 kernel: [    0.485724] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 26 08:23:58 node-1 kernel: [    0.485776] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.485828] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.486083] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 26 08:23:58 node-1 kernel: [    0.486087] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 26 08:23:58 node-1 kernel: [    0.486149] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 26 08:23:58 node-1 kernel: [    0.486212] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.486263] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 26 08:23:58 node-1 kernel: [    0.486491] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 26 08:23:58 node-1 kernel: [    0.486494] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 26 08:23:58 node-1 kernel: [    0.486672] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 26 08:23:58 node-1 kernel: [    0.486711] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 26 08:23:58 node-1 kernel: [    0.486786] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 26 08:23:58 node-1 kernel: [    0.486804] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 26 08:23:58 node-1 kernel: [    0.486817] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 26 08:23:58 node-1 kernel: [    0.486831] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 26 08:23:58 node-1 kernel: [    0.486881] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 26 08:23:58 node-1 kernel: [    0.491630] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 26 08:23:58 node-1 kernel: [    0.491639] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 26 08:23:58 node-1 kernel: [    0.491691] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 26 08:23:58 node-1 kernel: [    0.492368] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 26 08:23:58 node-1 kernel: [    0.492371] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 08:23:58 node-1 kernel: [    0.492496] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 26 08:23:58 node-1 kernel: [    0.492604] PCI host bridge to bus 0000:80
Sep 26 08:23:58 node-1 kernel: [    0.492606] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 26 08:23:58 node-1 kernel: [    0.492607] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 26 08:23:58 node-1 kernel: [    0.492609] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 26 08:23:58 node-1 kernel: [    0.492617] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.492680] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.492749] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 26 08:23:58 node-1 kernel: [    0.492811] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 26 08:23:58 node-1 kernel: [    0.492816] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 26 08:23:58 node-1 kernel: [    0.492889] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 26 08:23:58 node-1 kernel: [    0.493191] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 26 08:23:58 node-1 kernel: [    0.493223] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 26 08:23:58 node-1 kernel: [    0.493253] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 26 08:23:58 node-1 kernel: [    0.493282] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 26 08:23:58 node-1 kernel: [    0.493311] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 08:23:58 node-1 kernel: [    0.493341] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 08:23:58 node-1 kernel: [    0.493371] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 08:23:58 node-1 kernel: [    0.493401] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 08:23:58 node-1 kernel: [    0.493486] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 26 08:23:58 node-1 kernel: [    0.493490] ACPI: \_SB_.UNC1: notify handler is installed
Sep 26 08:23:58 node-1 kernel: [    0.493492] ACPI: \_SB_.UNC0: notify handler is installed
Sep 26 08:23:58 node-1 kernel: [    0.493507] ACPI: \_SB_.PCI0: notify handler is installed
Sep 26 08:23:58 node-1 kernel: [    0.493560] ACPI: \_SB_.PCI1: notify handler is installed
Sep 26 08:23:58 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 26 08:23:58 node-1 kernel: [    0.493639] Found 4 acpi root devices
Sep 26 08:23:58 node-1 kernel: [    0.493749] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 26 08:23:58 node-1 kernel: [    0.493751] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 26 08:23:58 node-1 kernel: [    0.493752] vgaarb: loaded
Sep 26 08:23:58 node-1 kernel: [    0.493753] vgaarb: bridge control possible 0000:0c:00.0
Sep 26 08:23:58 node-1 kernel: [    0.493879] SCSI subsystem initialized
Sep 26 08:23:58 node-1 kernel: [    0.493943] libata version 3.00 loaded.
Sep 26 08:23:58 node-1 kernel: [    0.493959] ACPI: bus type USB registered
Sep 26 08:23:58 node-1 kernel: [    0.493969] usbcore: registered new interface driver usbfs
Sep 26 08:23:58 node-1 kernel: [    0.493974] usbcore: registered new interface driver hub
Sep 26 08:23:58 node-1 kernel: [    0.493997] usbcore: registered new device driver usb
Sep 26 08:23:58 node-1 kernel: [    0.494171] PCI: Using ACPI for IRQ routing
Sep 26 08:23:58 node-1 kernel: [    0.497749] PCI: pci_cache_line_size set to 64 bytes
Sep 26 08:23:58 node-1 kernel: [    0.497969] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 26 08:23:58 node-1 kernel: [    0.497970] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep 26 08:23:58 node-1 kernel: [    0.497971] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 26 08:23:58 node-1 kernel: [    0.498036] NetLabel: Initializing
Sep 26 08:23:58 node-1 kernel: [    0.498038] NetLabel:  domain hash size = 128
Sep 26 08:23:58 node-1 kernel: [    0.498039] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 26 08:23:58 node-1 kernel: [    0.498048] NetLabel:  unlabeled traffic allowed by default
Sep 26 08:23:58 node-1 kernel: [    0.498105] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 26 08:23:58 node-1 kernel: [    0.498109] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 26 08:23:58 node-1 kernel: [    0.500177] Switched to clocksource hpet
Sep 26 08:23:58 node-1 kernel: [    0.504619] AppArmor: AppArmor Filesystem Enabled
Sep 26 08:23:58 node-1 kernel: [    0.504657] pnp: PnP ACPI init
Sep 26 08:23:58 node-1 kernel: [    0.504669] ACPI: bus type PNP registered
Sep 26 08:23:58 node-1 kernel: [    0.504851] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 26 08:23:58 node-1 kernel: [    0.504862] pnp 00:01: [dma 4]
Sep 26 08:23:58 node-1 kernel: [    0.504881] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 26 08:23:58 node-1 kernel: [    0.504915] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 26 08:23:58 node-1 kernel: [    0.504940] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 26 08:23:58 node-1 kernel: [    0.504962] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 26 08:23:58 node-1 kernel: [    0.505009] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 26 08:23:58 node-1 kernel: [    0.505121] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505123] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 26 08:23:58 node-1 kernel: [    0.505125] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505127] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505128] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505129] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505133] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 26 08:23:58 node-1 kernel: [    0.505134] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505136] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505137] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505139] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505140] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505142] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 26 08:23:58 node-1 kernel: [    0.505144] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 26 08:23:58 node-1 kernel: [    0.505246] pnp 00:07: [dma 0 disabled]
Sep 26 08:23:58 node-1 kernel: [    0.505280] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 26 08:23:58 node-1 kernel: [    0.505361] pnp 00:08: [dma 0 disabled]
Sep 26 08:23:58 node-1 kernel: [    0.505397] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 26 08:23:58 node-1 kernel: [    0.505456] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 26 08:23:58 node-1 kernel: [    0.505902] pnp: PnP ACPI: found 10 devices
Sep 26 08:23:58 node-1 kernel: [    0.505904] ACPI: bus type PNP unregistered
Sep 26 08:23:58 node-1 kernel: [    0.511926] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 26 08:23:58 node-1 kernel: [    0.511930] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 26 08:23:58 node-1 kernel: [    0.511933] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 26 08:23:58 node-1 kernel: [    0.511938] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 26 08:23:58 node-1 kernel: [    0.511940] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.511958] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.511987] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 26 08:23:58 node-1 kernel: [    0.512002] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512031] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 26 08:23:58 node-1 kernel: [    0.512046] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 26 08:23:58 node-1 kernel: [    0.512075] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 26 08:23:58 node-1 kernel: [    0.512089] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 26 08:23:58 node-1 kernel: [    0.512118] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 26 08:23:58 node-1 kernel: [    0.512120] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512135] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512168] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 26 08:23:58 node-1 kernel: [    0.512170] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512185] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512214] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 26 08:23:58 node-1 kernel: [    0.512215] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512218] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512223] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 26 08:23:58 node-1 kernel: [    0.512225] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512228] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512232] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 26 08:23:58 node-1 kernel: [    0.512238] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 26 08:23:58 node-1 kernel: [    0.512247] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 26 08:23:58 node-1 kernel: [    0.512251] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 26 08:23:58 node-1 kernel: [    0.512258] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 26 08:23:58 node-1 kernel: [    0.512259] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 26 08:23:58 node-1 kernel: [    0.512260] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 26 08:23:58 node-1 kernel: [    0.512261] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 26 08:23:58 node-1 kernel: [    0.512261] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 26 08:23:58 node-1 kernel: [    0.512262] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 26 08:23:58 node-1 kernel: [    0.512263] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 26 08:23:58 node-1 kernel: [    0.512264] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 26 08:23:58 node-1 kernel: [    0.512265] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512266] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512267] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512268] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512269] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512270] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512271] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512272] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512273] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 26 08:23:58 node-1 kernel: [    0.512274] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512275] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 26 08:23:58 node-1 kernel: [    0.512277] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 26 08:23:58 node-1 kernel: [    0.512278] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 26 08:23:58 node-1 kernel: [    0.512279] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 26 08:23:58 node-1 kernel: [    0.512282] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 26 08:23:58 node-1 kernel: [    0.512283] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 26 08:23:58 node-1 kernel: [    0.512323] NET: Registered protocol family 2
Sep 26 08:23:58 node-1 kernel: [    0.512620] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.512989] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.513172] TCP: Hash tables configured (established 262144 bind 65536)
Sep 26 08:23:58 node-1 kernel: [    0.513212] TCP: reno registered
Sep 26 08:23:58 node-1 kernel: [    0.513242] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.513347] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.513512] NET: Registered protocol family 1
Sep 26 08:23:58 node-1 kernel: [    0.552273] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 26 08:23:58 node-1 kernel: [    0.552289] PCI: CLS 64 bytes, default 64
Sep 26 08:23:58 node-1 kernel: [    0.552373] Trying to unpack rootfs image as initramfs...
Sep 26 08:23:58 node-1 kernel: [    0.773622] Freeing initrd memory: 20368K (ffff880035828000 - ffff880036c0c000)
Sep 26 08:23:58 node-1 kernel: [    0.773676] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 26 08:23:58 node-1 kernel: [    0.773685] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep 26 08:23:58 node-1 kernel: [    0.774141] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774147] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774154] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774160] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774168] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774177] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774187] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774194] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774202] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774209] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774215] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774221] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774228] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774234] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774241] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774247] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 08:23:58 node-1 kernel: [    0.774332] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 26 08:23:58 node-1 kernel: [    0.774335] Scanning for low memory corruption every 60 seconds
Sep 26 08:23:58 node-1 kernel: [    0.774679] Initialise system trusted keyring
Sep 26 08:23:58 node-1 kernel: [    0.774726] audit: initializing netlink socket (disabled)
Sep 26 08:23:58 node-1 kernel: [    0.774739] type=2000 audit(1474878202.728:1): initialized
Sep 26 08:23:58 node-1 kernel: [    0.792408] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 26 08:23:58 node-1 kernel: [    0.793881] zbud: loaded
Sep 26 08:23:58 node-1 kernel: [    0.793999] VFS: Disk quotas dquot_6.5.2
Sep 26 08:23:58 node-1 kernel: [    0.794036] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 26 08:23:58 node-1 kernel: [    0.794387] fuse init (API version 7.22)
Sep 26 08:23:58 node-1 kernel: [    0.794443] msgmni has been set to 32768
Sep 26 08:23:58 node-1 kernel: [    0.794491] Key type big_key registered
Sep 26 08:23:58 node-1 kernel: [    0.794982] Key type asymmetric registered
Sep 26 08:23:58 node-1 kernel: [    0.794984] Asymmetric key parser 'x509' registered
Sep 26 08:23:58 node-1 kernel: [    0.795004] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 26 08:23:58 node-1 kernel: [    0.795069] io scheduler noop registered
Sep 26 08:23:58 node-1 kernel: [    0.795071] io scheduler deadline registered (default)
Sep 26 08:23:58 node-1 kernel: [    0.795091] io scheduler cfq registered
Sep 26 08:23:58 node-1 kernel: [    0.795428] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    0.795551] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    0.795696] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    0.795812] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    0.795945] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    0.796037] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    0.796411] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 26 08:23:58 node-1 kernel: [    0.796437] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 26 08:23:58 node-1 kernel: [    0.796453] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 26 08:23:58 node-1 kernel: [    0.796462] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796464] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796466] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 26 08:23:58 node-1 kernel: [    0.796472] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796473] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796474] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796476] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796478] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796479] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796480] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796482] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796483] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796485] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796486] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796487] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796490] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 26 08:23:58 node-1 kernel: [    0.796495] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796497] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 26 08:23:58 node-1 kernel: [    0.796511] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796514] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 26 08:23:58 node-1 kernel: [    0.796525] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796527] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 26 08:23:58 node-1 kernel: [    0.796530] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 26 08:23:58 node-1 kernel: [    0.796564] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 26 08:23:58 node-1 kernel: [    0.796577] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 26 08:23:58 node-1 kernel: [    0.796581] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 26 08:23:58 node-1 kernel: [    0.796591] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 26 08:23:58 node-1 kernel: [    0.796628] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 26 08:23:58 node-1 kernel: [    0.796629] vesafb: scrolling: redraw
Sep 26 08:23:58 node-1 kernel: [    0.796631] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 26 08:23:58 node-1 kernel: [    0.816977] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 26 08:23:58 node-1 kernel: [    0.825458] Console: switching to colour frame buffer device 80x30
Sep 26 08:23:58 node-1 kernel: [    0.834117] fb0: VESA VGA frame buffer device
Sep 26 08:23:58 node-1 kernel: [    0.834312] intel_idle: MWAIT substates: 0x2120
Sep 26 08:23:58 node-1 kernel: [    0.834313] intel_idle: v0.4 model 0x3F
Sep 26 08:23:58 node-1 kernel: [    0.834314] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 26 08:23:58 node-1 kernel: [    0.834553] ipmi message handler version 39.2
Sep 26 08:23:58 node-1 kernel: [    0.834832] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 26 08:23:58 node-1 kernel: [    0.835263] ACPI: AC Adapter [P111] (on-line)
Sep 26 08:23:58 node-1 kernel: [    0.840475] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 26 08:23:58 node-1 kernel: [    0.851488] ACPI: Power Button [PWRB]
Sep 26 08:23:58 node-1 kernel: [    0.857246] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 26 08:23:58 node-1 kernel: [    0.868860] ACPI: Power Button [PWRF]
Sep 26 08:23:58 node-1 kernel: [    0.889731] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 26 08:23:58 node-1 kernel: [    0.901382] pstore: Registered erst as persistent store backend
Sep 26 08:23:58 node-1 kernel: [    0.907579] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 26 08:23:58 node-1 kernel: [    0.919508] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 26 08:23:58 node-1 kernel: [    0.946233] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 26 08:23:58 node-1 kernel: [    0.979534] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 26 08:23:58 node-1 kernel: [    0.993597] Linux agpgart interface v0.103
Sep 26 08:23:58 node-1 kernel: [    1.001248] brd: module loaded
Sep 26 08:23:58 node-1 kernel: [    1.008283] loop: module loaded
Sep 26 08:23:58 node-1 kernel: [    1.014994] libphy: Fixed MDIO Bus: probed
Sep 26 08:23:58 node-1 kernel: [    1.021494] tun: Universal TUN/TAP device driver, 1.6
Sep 26 08:23:58 node-1 kernel: [    1.027973] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 26 08:23:58 node-1 kernel: [    1.034487] PPP generic driver version 2.4.2
Sep 26 08:23:58 node-1 kernel: [    1.040878] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 26 08:23:58 node-1 kernel: [    1.047306] ehci-pci: EHCI PCI platform driver
Sep 26 08:23:58 node-1 kernel: [    1.053827] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 26 08:23:58 node-1 kernel: [    1.060240] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 26 08:23:58 node-1 kernel: [    1.072765] ehci-pci 0000:00:1a.0: debug port 2
Sep 26 08:23:58 node-1 kernel: [    1.082942] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 26 08:23:58 node-1 kernel: [    1.082960] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 26 08:23:58 node-1 kernel: [    1.099660] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 26 08:23:58 node-1 kernel: [    1.105744] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 26 08:23:58 node-1 kernel: [    1.111921] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 26 08:23:58 node-1 kernel: [    1.123850] usb usb1: Product: EHCI Host Controller
Sep 26 08:23:58 node-1 kernel: [    1.129904] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 26 08:23:58 node-1 kernel: [    1.135953] usb usb1: SerialNumber: 0000:00:1a.0
Sep 26 08:23:58 node-1 kernel: [    1.141942] hub 1-0:1.0: USB hub found
Sep 26 08:23:58 node-1 kernel: [    1.147720] hub 1-0:1.0: 2 ports detected
Sep 26 08:23:58 node-1 kernel: [    1.153534] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 26 08:23:58 node-1 kernel: [    1.159137] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 26 08:23:58 node-1 kernel: [    1.170068] ehci-pci 0000:00:1d.0: debug port 2
Sep 26 08:23:58 node-1 kernel: [    1.179386] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 26 08:23:58 node-1 kernel: [    1.179389] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 26 08:23:58 node-1 kernel: [    1.195578] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 26 08:23:58 node-1 kernel: [    1.200822] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 26 08:23:58 node-1 kernel: [    1.206168] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 26 08:23:58 node-1 kernel: [    1.216890] usb usb2: Product: EHCI Host Controller
Sep 26 08:23:58 node-1 kernel: [    1.222411] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 26 08:23:58 node-1 kernel: [    1.228026] usb usb2: SerialNumber: 0000:00:1d.0
Sep 26 08:23:58 node-1 kernel: [    1.233607] hub 2-0:1.0: USB hub found
Sep 26 08:23:58 node-1 kernel: [    1.238959] hub 2-0:1.0: 2 ports detected
Sep 26 08:23:58 node-1 kernel: [    1.244378] ehci-platform: EHCI generic platform driver
Sep 26 08:23:58 node-1 kernel: [    1.249713] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 26 08:23:58 node-1 kernel: [    1.255070] ohci-pci: OHCI PCI platform driver
Sep 26 08:23:58 node-1 kernel: [    1.260477] ohci-platform: OHCI generic platform driver
Sep 26 08:23:58 node-1 kernel: [    1.265729] uhci_hcd: USB Universal Host Controller Interface driver
Sep 26 08:23:58 node-1 kernel: [    1.271130] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 26 08:23:58 node-1 kernel: [    1.463356] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 26 08:23:58 node-1 kernel: [    1.795069] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 26 08:23:58 node-1 kernel: [    1.807373] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 26 08:23:58 node-1 kernel: [    1.812992] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 26 08:23:58 node-1 kernel: [    1.818766] hub 1-1:1.0: USB hub found
Sep 26 08:23:58 node-1 kernel: [    1.824360] hub 1-1:1.0: 6 ports detected
Sep 26 08:23:58 node-1 kernel: [    1.938969] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 26 08:23:58 node-1 kernel: [    2.309855] i8042: No controller found
Sep 26 08:23:58 node-1 kernel: [    2.315404] mousedev: PS/2 mouse device common for all mice
Sep 26 08:23:58 node-1 kernel: [    2.321130] rtc_cmos 00:02: RTC can wake from S4
Sep 26 08:23:58 node-1 kernel: [    2.323377] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 26 08:23:58 node-1 kernel: [    2.323378] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 26 08:23:58 node-1 kernel: [    2.324145] hub 2-1:1.0: USB hub found
Sep 26 08:23:58 node-1 kernel: [    2.324376] hub 2-1:1.0: 8 ports detected
Sep 26 08:23:58 node-1 kernel: [    2.349490] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 26 08:23:58 node-1 kernel: [    2.355272] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 26 08:23:58 node-1 kernel: [    2.366611] device-mapper: uevent: version 1.0.3
Sep 26 08:23:58 node-1 kernel: [    2.372341] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 26 08:23:58 node-1 kernel: [    2.383751] ledtrig-cpu: registered to indicate activity on CPUs
Sep 26 08:23:58 node-1 kernel: [    2.389729] TCP: cubic registered
Sep 26 08:23:58 node-1 kernel: [    2.395613] NET: Registered protocol family 10
Sep 26 08:23:58 node-1 kernel: [    2.401686] NET: Registered protocol family 17
Sep 26 08:23:58 node-1 kernel: [    2.407479] Key type dns_resolver registered
Sep 26 08:23:58 node-1 kernel: [    2.413544] Loading compiled-in X.509 certificates
Sep 26 08:23:58 node-1 kernel: [    2.419773] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Sep 26 08:23:58 node-1 kernel: [    2.431455] registered taskstats version 1
Sep 26 08:23:58 node-1 kernel: [    2.439556] Key type trusted registered
Sep 26 08:23:58 node-1 kernel: [    2.447287] Key type encrypted registered
Sep 26 08:23:58 node-1 kernel: [    2.452785] AppArmor: AppArmor sha1 policy hashing enabled
Sep 26 08:23:58 node-1 kernel: [    2.458293] IMA: No TPM chip found, activating TPM-bypass!
Sep 26 08:23:58 node-1 kernel: [    2.464370] regulator-dummy: disabling
Sep 26 08:23:58 node-1 kernel: [    2.469883]   Magic number: 0:642:372
Sep 26 08:23:58 node-1 kernel: [    2.475373] pcieport 0000:02:00.0: hash matches
Sep 26 08:23:58 node-1 kernel: [    2.481058] rtc_cmos 00:02: setting system clock to 2016-09-26 08:23:24 UTC (1474878204)
Sep 26 08:23:58 node-1 kernel: [    2.493438] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 26 08:23:58 node-1 kernel: [    2.499053] EDD information not available.
Sep 26 08:23:58 node-1 kernel: [    2.504595] PM: Hibernation image not present or could not be loaded.
Sep 26 08:23:58 node-1 kernel: [    2.505457] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 26 08:23:58 node-1 kernel: [    2.516793] Write protecting the kernel read-only data: 12288k
Sep 26 08:23:58 node-1 kernel: [    2.523195] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 26 08:23:58 node-1 kernel: [    2.536032] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 26 08:23:58 node-1 kernel: [    2.569159] device-mapper: multipath: version 1.6.0 loaded
Sep 26 08:23:58 node-1 kernel: [    2.577103] systemd-udevd[217]: starting version 204
Sep 26 08:23:58 node-1 kernel: [    2.598414] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 26 08:23:58 node-1 kernel: [    2.607068] md: linear personality registered for level -1
Sep 26 08:23:58 node-1 kernel: [    2.621544] md: multipath personality registered for level -4
Sep 26 08:23:58 node-1 kernel: [    2.629658] md: raid0 personality registered for level 0
Sep 26 08:23:58 node-1 kernel: [    2.638407] md: raid1 personality registered for level 1
Sep 26 08:23:58 node-1 kernel: [    2.647448] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 26 08:23:58 node-1 kernel: [    2.653638] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 26 08:23:58 node-1 kernel: [    2.659819] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 26 08:23:58 node-1 kernel: [    2.661126] megasas: FW now in Ready state
Sep 26 08:23:58 node-1 kernel: [    2.661594] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.661688] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.661803] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.661880] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.662010] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.662142] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.662282] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.662542] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.662691] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.662828] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.662915] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.663081] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.663182] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.663308] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.663433] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.663519] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.664148] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 26 08:23:58 node-1 kernel: [    2.692837] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep 26 08:23:58 node-1 kernel: [    2.705968] 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 26 08:23:58 node-1 kernel: [    2.714400] raid6: sse2x1   11401 MB/s
Sep 26 08:23:58 node-1 kernel: [    2.726489] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 26 08:23:58 node-1 kernel: [    2.733372] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.733376] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.733380] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.733385] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.733423] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 26 08:23:58 node-1 kernel: [    2.739042] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 26 08:23:58 node-1 kernel: [    2.739045] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 26 08:23:58 node-1 kernel: [    2.739046] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 26 08:23:58 node-1 kernel: [    2.739048] usb 2-1.4: Manufacturer: Avocent
Sep 26 08:23:58 node-1 kernel: [    2.739053] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 26 08:23:58 node-1 kernel: [    2.782331] raid6: sse2x2   14365 MB/s
Sep 26 08:23:58 node-1 kernel: [    2.850184] raid6: sse2x4   10377 MB/s
Sep 26 08:23:58 node-1 kernel: [    2.922123] raid6: avx2x1   14945 MB/s
Sep 26 08:23:58 node-1 kernel: [    2.994065] raid6: avx2x2   18857 MB/s
Sep 26 08:23:58 node-1 kernel: [    3.066010] raid6: avx2x4   21286 MB/s
Sep 26 08:23:58 node-1 kernel: [    3.071554] raid6: using algorithm avx2x4 (21286 MB/s)
Sep 26 08:23:58 node-1 kernel: [    3.077048] raid6: using avx2x2 recovery algorithm
Sep 26 08:23:58 node-1 kernel: [    3.082436] megasas:IOC Init cmd success
Sep 26 08:23:58 node-1 kernel: [    3.082438] Switched to clocksource tsc
Sep 26 08:23:58 node-1 kernel: [    3.093362] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep 26 08:23:58 node-1 kernel: [    3.104309] 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 26 08:23:58 node-1 kernel: [    3.114003] megasas: INIT adapter done
Sep 26 08:23:58 node-1 kernel: [    3.121335] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 26 08:23:58 node-1 kernel: [    3.127133] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.127143] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.127149] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.127152] xor: automatically using best checksumming function:
Sep 26 08:23:58 node-1 kernel: [    3.127156] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.127248] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.127351] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.127723] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.142376] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep 26 08:23:58 node-1 kernel: [    3.142378] 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 26 08:23:58 node-1 kernel: [    3.142379] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 26 08:23:58 node-1 kernel: [    3.142437] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.142477] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.142516] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.142558] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.142639] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.149928] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep 26 08:23:58 node-1 kernel: [    3.149930] 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 26 08:23:58 node-1 kernel: [    3.149930] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 26 08:23:58 node-1 kernel: [    3.149984] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.150020] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.150053] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.150087] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.150178] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 26 08:23:58 node-1 kernel: [    3.185903] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 26 08:23:58 node-1 kernel: [    3.186250] scsi0 : LSI SAS based MegaRAID driver
Sep 26 08:23:58 node-1 kernel: [    3.193273] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 26 08:23:58 node-1 kernel: [    3.204187] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 26 08:23:58 node-1 kernel: [    3.207957] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 26 08:23:58 node-1 kernel: [    3.208067] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 26 08:23:58 node-1 kernel: [    3.208379] sd 0:2:0:0: [sda] Write Protect is off
Sep 26 08:23:58 node-1 kernel: [    3.208380] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 26 08:23:58 node-1 kernel: [    3.208446] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 26 08:23:58 node-1 kernel: [    3.241164]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 26 08:23:58 node-1 kernel: [    3.241703] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 26 08:23:58 node-1 kernel: [    3.321114] hidraw: raw HID events driver (C) Jiri Kosina
Sep 26 08:23:58 node-1 kernel: [    3.330887] usbcore: registered new interface driver usbhid
Sep 26 08:23:58 node-1 kernel: [    3.337507] usbhid: USB HID core driver
Sep 26 08:23:58 node-1 kernel: [    3.344898] 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 26 08:23:58 node-1 kernel: [    3.357922]    avx       : 56050.000 MB/sec
Sep 26 08:23:58 node-1 kernel: [    3.358139] 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 26 08:23:58 node-1 kernel: [    3.358204] 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 26 08:23:58 node-1 kernel: [    3.358258] 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 26 08:23:58 node-1 kernel: [    3.358308] 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 26 08:23:58 node-1 kernel: [    3.358347] 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 26 08:23:58 node-1 kernel: [    3.433201] async_tx: api initialized (async)
Sep 26 08:23:58 node-1 kernel: [    3.444256] md: raid6 personality registered for level 6
Sep 26 08:23:58 node-1 kernel: [    3.451439] md: raid5 personality registered for level 5
Sep 26 08:23:58 node-1 kernel: [    3.458431] md: raid4 personality registered for level 4
Sep 26 08:23:58 node-1 kernel: [    3.468399] md: raid10 personality registered for level 10
Sep 26 08:23:58 node-1 kernel: [    3.478169] random: lvm urandom read with 31 bits of entropy available
Sep 26 08:23:58 node-1 kernel: [    3.530847] multipathd (369): /proc/369/oom_adj is deprecated, please use /proc/369/oom_score_adj instead.
Sep 26 08:23:58 node-1 kernel: [    3.608292] bio: create slab <bio-1> at 1
Sep 26 08:23:58 node-1 kernel: [    4.399812] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 26 08:23:58 node-1 kernel: [    4.967795] init: plymouth-upstart-bridge main process (551) terminated with status 1
Sep 26 08:23:58 node-1 kernel: [    4.980611] init: plymouth-upstart-bridge main process ended, respawning
Sep 26 08:23:58 node-1 kernel: [    5.102122] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 26 08:23:58 node-1 kernel: [    5.108512] random: nonblocking pool is initialized
Sep 26 08:23:58 node-1 kernel: [    5.147651] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 26 08:23:58 node-1 kernel: [    5.344849] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 26 08:23:58 node-1 kernel: [    5.398718] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 26 08:23:58 node-1 kernel: [    5.485819] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 26 08:23:58 node-1 kernel: [    5.697971] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 26 08:23:58 node-1 kernel: [    5.740517] XFS (dm-0): Mounting Filesystem
Sep 26 08:23:58 node-1 kernel: [    6.032787] XFS (dm-0): Ending clean mount
Sep 26 08:23:58 node-1 kernel: [    6.078686] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 26 08:23:58 node-1 kernel: [    6.121182] XFS (dm-1): Mounting Filesystem
Sep 26 08:23:58 node-1 kernel: [    6.212974] XFS (dm-1): Ending clean mount
Sep 26 08:23:58 node-1 kernel: [    8.027291] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 26 08:23:58 node-1 kernel: [    8.041271] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 26 08:23:58 node-1 kernel: [    8.197096] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 26 08:23:58 node-1 kernel: [    8.197102] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 26 08:23:58 node-1 kernel: [    8.197107] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 26 08:23:58 node-1 kernel: [    8.197111] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 26 08:23:58 node-1 kernel: [    8.224602] systemd-udevd[775]: starting version 204
Sep 26 08:23:58 node-1 kernel: [    8.379744] power_meter ACPI000D:00: Found ACPI power meter.
Sep 26 08:23:58 node-1 kernel: [    8.379756] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 26 08:23:58 node-1 kernel: [    8.433063] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 26 08:23:58 node-1 kernel: [    8.433068] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 26 08:23:58 node-1 kernel: [    8.433071] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 26 08:23:58 node-1 kernel: [    8.433072] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 26 08:23:58 node-1 kernel: [    8.433085] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 26 08:23:58 node-1 kernel: [    8.436930] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 26 08:23:58 node-1 kernel: [    8.440436] wmi: Mapper loaded
Sep 26 08:23:58 node-1 kernel: [    8.478433] IPMI System Interface driver.
Sep 26 08:23:58 node-1 kernel: [    8.478462] ipmi_si: probing via ACPI
Sep 26 08:23:58 node-1 kernel: [    8.478476] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 26 08:23:58 node-1 kernel: [    8.478477] ipmi_si: Adding ACPI-specified kcs state machine
Sep 26 08:23:58 node-1 kernel: [    8.478484] ipmi_si: probing via SMBIOS
Sep 26 08:23:58 node-1 kernel: [    8.478485] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 26 08:23:58 node-1 kernel: [    8.478486] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 26 08:23:58 node-1 kernel: [    8.478487] ipmi_si: probing via SPMI
Sep 26 08:23:58 node-1 kernel: [    8.478488] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 26 08:23:58 node-1 kernel: [    8.478489] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 26 08:23:58 node-1 kernel: [    8.478490] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 26 08:23:58 node-1 kernel: [    8.505934] systemd-udevd[803]: renamed network interface eth0 to enp6s0
Sep 26 08:23:58 node-1 kernel: [    8.534166] systemd-udevd[818]: renamed network interface eth1 to enp7s0
Sep 26 08:23:58 node-1 kernel: [    8.557746] systemd-udevd[794]: renamed network interface eth2 to enp8s0
Sep 26 08:23:58 node-1 kernel: [    8.601743] systemd-udevd[793]: renamed network interface eth3 to enp9s0
Sep 26 08:23:58 node-1 kernel: [    8.614461] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 26 08:23:58 node-1 kernel: [    8.614474] ipmi_si 00:09: IPMI kcs interface initialized
Sep 26 08:23:58 node-1 kernel: [    8.867248] type=1400 audit(1474878210.886:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1023 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.867398] type=1400 audit(1474878210.886:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1023 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.867521] type=1400 audit(1474878210.886:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1023 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.877436] type=1400 audit(1474878210.898:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1024 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.877588] type=1400 audit(1474878210.898:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1024 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.877713] type=1400 audit(1474878210.898:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1024 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.887613] type=1400 audit(1474878210.906:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1026 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.887759] type=1400 audit(1474878210.906:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1026 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.887883] type=1400 audit(1474878210.906:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1026 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    8.898576] type=1400 audit(1474878210.918:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1025 comm="apparmor_parser"
Sep 26 08:23:58 node-1 kernel: [    9.352864] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 26 08:23:58 node-1 kernel: [    9.357253] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 26 08:23:58 node-1 kernel: [    9.587178] enic 0000:06:00.0 enp6s0: Link UP
Sep 26 08:23:58 node-1 kernel: [    9.588295] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 26 08:23:58 node-1 kernel: [    9.588300] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 26 08:23:58 node-1 kernel: [   18.836717] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 26 08:23:59 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 26 08:23:59 node-1 kernel: [   37.404729] init: failsafe main process (8412) killed by TERM signal
Sep 26 08:24:00 node-1 dbus[8445]: [system] AppArmor D-Bus mediation is enabled
Sep 26 08:24:00 node-1 kernel: [   37.617400] audit_printk_skb: 30 callbacks suppressed
Sep 26 08:24:00 node-1 kernel: [   37.617403] type=1400 audit(1474878240.184:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8540 comm="apparmor_parser"
Sep 26 08:24:00 node-1 kernel: [   37.619824] type=1400 audit(1474878240.184:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8539 comm="apparmor_parser"
Sep 26 08:24:00 node-1 kernel: [   37.619868] type=1400 audit(1474878240.184:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8539 comm="apparmor_parser"
Sep 26 08:24:00 node-1 kernel: [   37.619914] type=1400 audit(1474878240.184:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Sep 26 08:24:00 node-1 kernel: [   37.621327] type=1400 audit(1474878240.188:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8539 comm="apparmor_parser"
Sep 26 08:24:00 node-1 kernel: [   37.621328] type=1400 audit(1474878240.188:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Sep 26 08:24:00 node-1 kernel: [   37.621443] type=1400 audit(1474878240.188:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8539 comm="apparmor_parser"
Sep 26 08:24:00 node-1 kernel: [   37.744769] type=1400 audit(1474878240.312:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8542 comm="apparmor_parser"
Sep 26 08:24:00 node-1 anacron[8607]: Anacron 2.3 started on 2016-09-26
Sep 26 08:24:00 node-1 anacron[8607]: Will run job `cron.daily' in 5 min.
Sep 26 08:24:00 node-1 anacron[8607]: Will run job `cron.weekly' in 10 min.
Sep 26 08:24:00 node-1 anacron[8607]: Will run job `cron.monthly' in 15 min.
Sep 26 08:24:00 node-1 anacron[8607]: Jobs will be executed sequentially
Sep 26 08:24:00 node-1 cron[8572]: (CRON) INFO (pidfile fd = 3)
Sep 26 08:24:00 node-1 cron[8622]: (CRON) STARTUP (fork ok)
Sep 26 08:24:00 node-1 multipathd: path checkers start up
Sep 26 08:24:00 node-1 cron[8622]: (CRON) INFO (Running @reboot jobs)
Sep 26 08:24:01 node-1 postfix/master[8749]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 26 08:24:03 node-1 puppet-agent[8934]: Reopening log files
Sep 26 08:24:04 node-1 puppet-agent[8934]: Could not request certificate: Connection refused - connect(2)
Sep 26 08:24:18 node-1 puppet-user[9013]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 26 08:24:18 node-1 puppet-user[9013]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Sep 26 08:24:19 node-1 puppet-user[9013]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 26 08:24:19 node-1 puppet-user[9013]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 26 08:24:19 node-1 puppet-user[9013]: Finished catalog run in 1.06 seconds
Sep 26 08:24:20 node-1 multipathd: uevent trigger error
Sep 26 08:24:21 node-1 puppet-user[9471]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 26 08:24:21 node-1 puppet-user[9471]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Sep 26 08:24:21 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 26 08:24:21 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 26 08:24:21 node-1 puppet-user[9471]: (/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 26 08:24:21 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 26 08:24:21 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 26 08:24:21 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 26 08:24:21 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 26 08:24:21 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 26 08:24:21 node-1 puppet-user[9471]: Finished catalog run in 0.06 seconds
Sep 26 08:24:22 node-1 puppet-user[10033]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 26 08:24:22 node-1 puppet-user[10033]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 26 08:24:22 node-1 puppet-user[10033]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 26 08:24:22 node-1 puppet-user[10033]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 26 08:24:22 node-1 puppet-user[10033]: Finished catalog run in 0.03 seconds
Sep 26 08:24:24 node-1 puppet-user[10495]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 26 08:24:24 node-1 puppet-user[10495]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 26 08:24:24 node-1 puppet-user[10495]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 26 08:24:24 node-1 puppet-user[10495]: Finished catalog run in 0.03 seconds
Sep 26 08:24:25 node-1 puppet-user[10942]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 26 08:24:25 node-1 puppet-user[10942]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Sep 26 08:24:25 node-1 puppet-user[10942]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 26 08:24:26 node-1 puppet-user[10942]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Sep 26 08:24:26 node-1 puppet-user[10942]: Finished catalog run in 0.46 seconds
Sep 26 08:24:27 node-1 puppet-user[11425]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 26 08:24:27 node-1 puppet-user[11425]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Sep 26 08:24:27 node-1 puppet-user[11425]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 26 08:24:27 node-1 puppet-user[11425]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 26 08:24:27 node-1 puppet-user[11425]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Sep 26 08:24:28 node-1 puppet-user[11425]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 26 08:24:28 node-1 puppet-user[11425]: Finished catalog run in 0.20 seconds
Sep 26 08:24:29 node-1 puppet-user[11898]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 26 08:24:29 node-1 puppet-user[11898]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Sep 26 08:24:29 node-1 puppet-user[11898]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 26 08:24:29 node-1 kernel: [   67.200625] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 26 08:24:29 node-1 kernel: [   67.200677] 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 26 08:24:29 node-1 puppet-user[11898]: (/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 26 08:24:29 node-1 puppet-user[11898]: Finished catalog run in 0.05 seconds
Sep 26 08:24:31 node-1 puppet-user[12355]: (Scope(Class[main])) MODULAR: sync_time
Sep 26 08:24:31 node-1 puppet-user[12355]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 26 08:24:31 node-1 ntpdate[12766]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 26 08:24:37 node-1 ntpdate[12766]: adjust time server 10.20.0.2 offset -0.261116 sec
Sep 26 08:24:37 node-1 puppet-user[12355]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 26 08:24:37 node-1 puppet-user[12355]: Finished catalog run in 6.16 seconds
Sep 26 08:24:43 node-1 puppet-user[13148]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 26 08:24:43 node-1 puppet-user[13148]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 26 08:24:43 node-1 puppet-user[13148]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 26 08:24:43 node-1 puppet-user[13148]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Sep 26 08:24:43 node-1 puppet-user[13148]: Finished catalog run in 0.06 seconds
Sep 26 08:24:44 node-1 puppet-user[13601]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 26 08:24:45 node-1 kernel: [   82.521198] init: plymouth-upstart-bridge main process ended, respawning
Sep 26 08:24:45 node-1 puppet-agent[8934]: Could not run: SIGTERM
Sep 26 08:24:45 node-1 kernel: [   82.800978] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 26 08:24:45 node-1 puppet-user[13601]: Compiled catalog for node-1.domain.tld in environment production in 0.47 seconds
Sep 26 08:24:45 node-1 ec2: 
Sep 26 08:24:45 node-1 ec2: #############################################################
Sep 26 08:24:45 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 26 08:24:45 node-1 ec2: 1024 ab:3a:23:d4:2d:d1:19:5f:92:48:07:80:27:93:5e:84  root@node-1.domain.tld (DSA)
Sep 26 08:24:45 node-1 ec2: 256 5e:93:b8:32:be:7d:cb:b5:70:2f:d9:81:02:dd:e3:07  root@node-1.domain.tld (ECDSA)
Sep 26 08:24:45 node-1 ec2: 256 b8:7f:77:88:5f:7a:e2:95:14:2b:d0:12:da:5b:78:77  root@node-1.domain.tld (ED25519)
Sep 26 08:24:45 node-1 ec2: 2048 c1:52:24:81:a0:3f:e6:59:b2:58:01:ce:31:17:71:65  root@node-1.domain.tld (RSA)
Sep 26 08:24:45 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 26 08:24:45 node-1 ec2: #############################################################
Sep 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:45 node-1 puppet-user[13601]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:45 node-1 puppet-user[13601]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:45 node-1 puppet-user[13601]: (/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 26 08:24:46 node-1 puppet-user[13601]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 26 08:24:46 node-1 puppet-user[13601]: Finished catalog run in 0.76 seconds
Sep 26 08:24:47 node-1 puppet-user[14275]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 26 08:24:47 node-1 puppet-user[14275]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Sep 26 08:24:50 node-1 puppet-user[14275]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 26 08:25:01 node-1 CRON[15786]: (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 26 08:25:01 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 26 08:25:01 node-1 nailgun-agent: I, [2016-09-26T08:25:01.799093 #15789]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 26 08:25:14 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 26 08:25:14 node-1 nailgun-agent: I, [2016-09-26T08:25:14.889764 #15789]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 26 08:25:17 node-1 puppet-user[14275]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 26 08:25:17 node-1 puppet-user[14275]: Finished catalog run in 29.18 seconds
Sep 26 08:25:19 node-1 puppet-user[16999]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 26 08:25:19 node-1 puppet-user[16999]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Sep 26 08:25:19 node-1 puppet-user[16999]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 26 08:25:19 node-1 puppet-user[16999]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 26 08:25:19 node-1 puppet-user[16999]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 26 08:25:19 node-1 puppet-user[16999]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 26 08:25:19 node-1 puppet-user[16999]: Finished catalog run in 0.08 seconds
Sep 26 08:25:21 node-1 puppet-user[17453]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 26 08:25:22 node-1 puppet-user[17453]: Compiled catalog for node-1.domain.tld in environment production in 0.90 seconds
Sep 26 08:25:22 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 26 08:25:22 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 26 08:25:22 node-1 crontab[17894]: (root) LIST (root)
Sep 26 08:25:22 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 26 08:25:22 node-1 crontab[17895]: (root) REPLACE (root)
Sep 26 08:25:24 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 26 08:25:24 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/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 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 26 08:25:25 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 26 08:25:26 node-1 puppet-user[17453]: (/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 26 08:25:26 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 26 08:25:26 node-1 puppet-user[17453]: (/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 26 08:25:26 node-1 puppet-user[17453]: (/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 26 08:25:26 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 26 08:25:26 node-1 puppet-user[17453]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 26 08:25:26 node-1 puppet-user[17453]: (/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 26 08:25:26 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8385" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 08:25:26 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 26 08:25:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:40 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:40 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:40 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:40 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:40 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:25:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:26:38 node-1 ntpdate[28851]: no servers can be used, exiting
<27>Sep 26 08:27:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:12 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:12 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:12 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:12 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:12 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:26 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:26 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:26 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:26 node-1 multipathd: uevent trigger error
<27>Sep 26 08:27:26 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:30 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 08:28:30 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 08:28:36 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 08:28:36 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 08:28:42 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 08:28:48 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 08:28:48 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 08:28:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:28:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:08 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:10 node-1 haproxy[16419]: 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 26 08:29:10 node-1 haproxy[16419]: Backup Server mysqld/node-2 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 26 08:29:11 node-1 haproxy[16423]: Backup Server mysqld/node-3 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 26 08:29:11 node-1 haproxy[16423]: proxy mysqld has no server available!
<27>Sep 26 08:29:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:16 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:19 node-1 haproxy[18956]: 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 26 08:29:19 node-1 haproxy[18956]: Backup Server mysqld/node-2 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 26 08:29:19 node-1 haproxy[18956]: Backup Server mysqld/node-3 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 26 08:29:19 node-1 haproxy[18956]: proxy mysqld has no server available!
<129>Sep 26 08:29:20 node-1 haproxy[18960]: 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 26 08:29:20 node-1 haproxy[18960]: Server object-storage/node-2 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 26 08:29:20 node-1 haproxy[18960]: Server object-storage/node-3 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 26 08:29:20 node-1 haproxy[18960]: proxy object-storage has no server available!
<27>Sep 26 08:29:22 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:22 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:22 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:22 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:22 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:22 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:24 node-1 haproxy[20319]: 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 26 08:29:24 node-1 haproxy[20319]: Server neutron/node-2 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 26 08:29:24 node-1 haproxy[20319]: Server neutron/node-3 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 26 08:29:24 node-1 haproxy[20319]: proxy neutron has no server available!
<129>Sep 26 08:29:25 node-1 haproxy[20323]: 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 26 08:29:25 node-1 haproxy[20323]: Backup Server mysqld/node-2 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 26 08:29:25 node-1 haproxy[20323]: Backup Server mysqld/node-3 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 26 08:29:25 node-1 haproxy[20323]: proxy mysqld has no server available!
<129>Sep 26 08:29:25 node-1 haproxy[20323]: 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 26 08:29:26 node-1 haproxy[20323]: Server object-storage/node-2 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 26 08:29:26 node-1 haproxy[20323]: Server object-storage/node-3 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 26 08:29:26 node-1 haproxy[20323]: proxy object-storage has no server available!
<27>Sep 26 08:29:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:27 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:30 node-1 haproxy[21807]: 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 26 08:29:30 node-1 haproxy[21807]: Server keystone-1/node-2 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 26 08:29:30 node-1 haproxy[21807]: Server keystone-1/node-3 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 26 08:29:30 node-1 haproxy[21807]: proxy keystone-1 has no server available!
<129>Sep 26 08:29:30 node-1 haproxy[21807]: 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 26 08:29:30 node-1 haproxy[21807]: Server keystone-2/node-2 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 26 08:29:30 node-1 haproxy[21807]: Server keystone-2/node-3 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 26 08:29:30 node-1 haproxy[21807]: proxy keystone-2 has no server available!
<129>Sep 26 08:29:30 node-1 haproxy[21807]: 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 26 08:29:31 node-1 haproxy[21811]: Server neutron/node-2 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 26 08:29:31 node-1 haproxy[21811]: Server neutron/node-3 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 26 08:29:31 node-1 haproxy[21811]: proxy neutron has no server available!
<129>Sep 26 08:29:31 node-1 haproxy[21811]: 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 26 08:29:31 node-1 haproxy[21811]: Backup Server mysqld/node-2 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 26 08:29:31 node-1 haproxy[21811]: Backup Server mysqld/node-3 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 26 08:29:31 node-1 haproxy[21811]: proxy mysqld has no server available!
<129>Sep 26 08:29:31 node-1 haproxy[21811]: 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 26 08:29:31 node-1 haproxy[21811]: Server object-storage/node-2 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 26 08:29:31 node-1 haproxy[21811]: Server object-storage/node-3 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 26 08:29:31 node-1 haproxy[21811]: proxy object-storage has no server available!
<27>Sep 26 08:29:33 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:33 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:33 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:33 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:33 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:35 node-1 haproxy[23149]: 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 26 08:29:35 node-1 haproxy[23149]: Server keystone-1/node-2 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 26 08:29:35 node-1 haproxy[23149]: Server keystone-1/node-3 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 26 08:29:35 node-1 haproxy[23149]: proxy keystone-1 has no server available!
<129>Sep 26 08:29:35 node-1 haproxy[23149]: 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 26 08:29:35 node-1 haproxy[23149]: Server keystone-2/node-2 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 26 08:29:35 node-1 haproxy[23149]: Server keystone-2/node-3 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 26 08:29:35 node-1 haproxy[23149]: proxy keystone-2 has no server available!
<129>Sep 26 08:29:36 node-1 haproxy[23156]: 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 26 08:29:36 node-1 haproxy[23156]: Server neutron/node-2 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 26 08:29:36 node-1 haproxy[23156]: Server neutron/node-3 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 26 08:29:36 node-1 haproxy[23156]: proxy neutron has no server available!
<129>Sep 26 08:29:36 node-1 haproxy[23156]: 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 26 08:29:36 node-1 haproxy[23156]: Backup Server mysqld/node-2 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 26 08:29:36 node-1 haproxy[23156]: Backup Server mysqld/node-3 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 26 08:29:36 node-1 haproxy[23156]: proxy mysqld has no server available!
<129>Sep 26 08:29:36 node-1 haproxy[23156]: 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 26 08:29:36 node-1 haproxy[23156]: Server object-storage/node-2 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 26 08:29:36 node-1 haproxy[23156]: Server object-storage/node-3 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 26 08:29:36 node-1 haproxy[23156]: proxy object-storage has no server available!
<129>Sep 26 08:29:37 node-1 haproxy[23156]: 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 26 08:29:37 node-1 haproxy[23156]: Server aodh/node-2 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 26 08:29:37 node-1 haproxy[23156]: Server aodh/node-3 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 26 08:29:37 node-1 haproxy[23156]: proxy aodh has no server available!
<27>Sep 26 08:29:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:38 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:40 node-1 haproxy[24525]: 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 26 08:29:40 node-1 haproxy[24525]: Server keystone-1/node-2 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 26 08:29:41 node-1 haproxy[24529]: Server keystone-1/node-3 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 26 08:29:41 node-1 haproxy[24529]: proxy keystone-1 has no server available!
<129>Sep 26 08:29:41 node-1 haproxy[24529]: 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 26 08:29:41 node-1 haproxy[24529]: Server keystone-2/node-2 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 26 08:29:41 node-1 haproxy[24529]: Server keystone-2/node-3 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 26 08:29:41 node-1 haproxy[24529]: proxy keystone-2 has no server available!
<129>Sep 26 08:29:41 node-1 haproxy[24529]: 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 26 08:29:41 node-1 haproxy[24529]: Server neutron/node-2 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 26 08:29:41 node-1 haproxy[24529]: Server neutron/node-3 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 26 08:29:41 node-1 haproxy[24529]: proxy neutron has no server available!
<129>Sep 26 08:29:41 node-1 haproxy[24529]: 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 26 08:29:41 node-1 haproxy[24529]: Backup Server mysqld/node-2 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 26 08:29:41 node-1 haproxy[24529]: Backup Server mysqld/node-3 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 26 08:29:41 node-1 haproxy[24529]: proxy mysqld has no server available!
<129>Sep 26 08:29:41 node-1 haproxy[24529]: 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 26 08:29:42 node-1 haproxy[24529]: Server object-storage/node-2 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 26 08:29:42 node-1 haproxy[24529]: Server object-storage/node-3 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 26 08:29:42 node-1 haproxy[24529]: proxy object-storage has no server available!
<129>Sep 26 08:29:42 node-1 haproxy[24529]: 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 26 08:29:42 node-1 haproxy[24529]: Server aodh/node-2 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 26 08:29:42 node-1 haproxy[24529]: Server aodh/node-3 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 26 08:29:42 node-1 haproxy[24529]: proxy aodh has no server available!
<129>Sep 26 08:29:42 node-1 haproxy[24529]: 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 26 08:29:42 node-1 haproxy[24529]: Server ceilometer/node-2 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 26 08:29:42 node-1 haproxy[24529]: Server ceilometer/node-3 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 26 08:29:42 node-1 haproxy[24529]: proxy ceilometer has no server available!
<27>Sep 26 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:43 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:46 node-1 haproxy[26061]: 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 26 08:29:46 node-1 haproxy[26061]: Server keystone-1/node-2 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 26 08:29:46 node-1 haproxy[26061]: Server keystone-1/node-3 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 26 08:29:46 node-1 haproxy[26061]: proxy keystone-1 has no server available!
<129>Sep 26 08:29:46 node-1 haproxy[26061]: 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 26 08:29:46 node-1 haproxy[26061]: Server keystone-2/node-2 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 26 08:29:46 node-1 haproxy[26061]: Server keystone-2/node-3 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 26 08:29:46 node-1 haproxy[26061]: proxy keystone-2 has no server available!
<129>Sep 26 08:29:46 node-1 haproxy[26061]: 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 26 08:29:46 node-1 haproxy[26061]: Server neutron/node-2 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 26 08:29:46 node-1 haproxy[26061]: Server neutron/node-3 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 26 08:29:46 node-1 haproxy[26061]: proxy neutron has no server available!
<129>Sep 26 08:29:46 node-1 haproxy[26061]: 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 26 08:29:47 node-1 haproxy[26065]: Backup Server mysqld/node-2 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 26 08:29:47 node-1 haproxy[26065]: Backup Server mysqld/node-3 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 26 08:29:47 node-1 haproxy[26065]: proxy mysqld has no server available!
<129>Sep 26 08:29:47 node-1 haproxy[26065]: 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 26 08:29:47 node-1 haproxy[26065]: Server object-storage/node-2 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 26 08:29:47 node-1 haproxy[26065]: Server object-storage/node-3 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 26 08:29:47 node-1 haproxy[26065]: proxy object-storage has no server available!
<129>Sep 26 08:29:47 node-1 haproxy[26065]: 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 26 08:29:47 node-1 haproxy[26065]: Server aodh/node-2 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 26 08:29:47 node-1 haproxy[26065]: Server aodh/node-3 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 26 08:29:47 node-1 haproxy[26065]: proxy aodh has no server available!
<129>Sep 26 08:29:47 node-1 haproxy[26065]: 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 26 08:29:47 node-1 haproxy[26065]: Server ceilometer/node-2 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 26 08:29:47 node-1 haproxy[26065]: Server ceilometer/node-3 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 26 08:29:47 node-1 haproxy[26065]: proxy ceilometer has no server available!
<27>Sep 26 08:29:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:49 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:51 node-1 haproxy[27414]: 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 26 08:29:51 node-1 haproxy[27414]: 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 26 08:29:51 node-1 haproxy[27414]: Server keystone-1/node-2 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 26 08:29:51 node-1 haproxy[27414]: Server keystone-1/node-3 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 26 08:29:51 node-1 haproxy[27414]: proxy keystone-1 has no server available!
<129>Sep 26 08:29:51 node-1 haproxy[27414]: 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 26 08:29:52 node-1 haproxy[27423]: Server keystone-2/node-2 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 26 08:29:52 node-1 haproxy[27423]: Server keystone-2/node-3 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 26 08:29:52 node-1 haproxy[27423]: proxy keystone-2 has no server available!
<129>Sep 26 08:29:52 node-1 haproxy[27423]: 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 26 08:29:52 node-1 haproxy[27423]: Server neutron/node-2 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 26 08:29:52 node-1 haproxy[27423]: Server neutron/node-3 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 26 08:29:52 node-1 haproxy[27423]: proxy neutron has no server available!
<129>Sep 26 08:29:52 node-1 haproxy[27423]: 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 26 08:29:52 node-1 haproxy[27423]: Backup Server mysqld/node-2 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 26 08:29:52 node-1 haproxy[27423]: Backup Server mysqld/node-3 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 26 08:29:52 node-1 haproxy[27423]: proxy mysqld has no server available!
<129>Sep 26 08:29:52 node-1 haproxy[27423]: 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 26 08:29:52 node-1 haproxy[27423]: Server object-storage/node-2 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 26 08:29:52 node-1 haproxy[27423]: Server object-storage/node-3 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 26 08:29:52 node-1 haproxy[27423]: proxy object-storage has no server available!
<129>Sep 26 08:29:52 node-1 haproxy[27423]: 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 26 08:29:53 node-1 haproxy[27423]: Server aodh/node-2 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 26 08:29:53 node-1 haproxy[27423]: Server aodh/node-3 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 26 08:29:53 node-1 haproxy[27423]: proxy aodh has no server available!
<129>Sep 26 08:29:53 node-1 haproxy[27423]: 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 26 08:29:53 node-1 haproxy[27423]: Server ceilometer/node-2 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 26 08:29:53 node-1 haproxy[27423]: Server ceilometer/node-3 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 26 08:29:53 node-1 haproxy[27423]: proxy ceilometer has no server available!
<27>Sep 26 08:29:54 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:54 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:54 node-1 multipathd: uevent trigger error
<27>Sep 26 08:29:54 node-1 multipathd: uevent trigger error
<129>Sep 26 08:29:57 node-1 haproxy[28809]: 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 26 08:29:57 node-1 haproxy[28809]: 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 26 08:29:57 node-1 haproxy[28809]: Server keystone-1/node-2 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 26 08:29:57 node-1 haproxy[28809]: Server keystone-1/node-3 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 26 08:29:57 node-1 haproxy[28809]: proxy keystone-1 has no server available!
<129>Sep 26 08:29:57 node-1 haproxy[28809]: 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 26 08:29:57 node-1 haproxy[28809]: Server keystone-2/node-2 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 26 08:29:57 node-1 haproxy[28809]: Server keystone-2/node-3 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 26 08:29:57 node-1 haproxy[28809]: proxy keystone-2 has no server available!
<129>Sep 26 08:29:57 node-1 haproxy[28809]: 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 26 08:29:57 node-1 haproxy[28809]: Server glance-api/node-2 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 26 08:29:57 node-1 haproxy[28809]: Server glance-api/node-3 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 26 08:29:57 node-1 haproxy[28809]: proxy glance-api has no server available!
<129>Sep 26 08:29:57 node-1 haproxy[28809]: 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 26 08:29:58 node-1 haproxy[28813]: Server glance-glare/node-2 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 26 08:29:58 node-1 haproxy[28813]: Server glance-glare/node-3 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 26 08:29:58 node-1 haproxy[28813]: proxy glance-glare has no server available!
<129>Sep 26 08:29:58 node-1 haproxy[28813]: 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 26 08:29:58 node-1 haproxy[28813]: Server neutron/node-2 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 26 08:29:58 node-1 haproxy[28813]: Server neutron/node-3 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 26 08:29:58 node-1 haproxy[28813]: proxy neutron has no server available!
<129>Sep 26 08:29:58 node-1 haproxy[28813]: 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 26 08:29:58 node-1 haproxy[28813]: Server glance-registry/node-2 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 26 08:29:58 node-1 haproxy[28813]: Server glance-registry/node-3 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 26 08:29:58 node-1 haproxy[28813]: proxy glance-registry has no server available!
<129>Sep 26 08:29:58 node-1 haproxy[28813]: 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 26 08:29:58 node-1 haproxy[28813]: Backup Server mysqld/node-2 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 26 08:29:58 node-1 haproxy[28813]: Backup Server mysqld/node-3 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 26 08:29:58 node-1 haproxy[28813]: proxy mysqld has no server available!
<129>Sep 26 08:29:58 node-1 haproxy[28813]: 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 26 08:29:58 node-1 haproxy[28813]: Server object-storage/node-2 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 26 08:29:58 node-1 haproxy[28813]: Server object-storage/node-3 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 26 08:29:58 node-1 haproxy[28813]: proxy object-storage has no server available!
<129>Sep 26 08:29:58 node-1 haproxy[28813]: 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 26 08:29:58 node-1 haproxy[28813]: Server aodh/node-2 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 26 08:29:59 node-1 haproxy[28813]: Server aodh/node-3 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 26 08:29:59 node-1 haproxy[28813]: proxy aodh has no server available!
<129>Sep 26 08:29:59 node-1 haproxy[28813]: 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 26 08:29:59 node-1 haproxy[28813]: Server ceilometer/node-2 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 26 08:29:59 node-1 haproxy[28813]: Server ceilometer/node-3 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 26 08:29:59 node-1 haproxy[28813]: proxy ceilometer has no server available!
<27>Sep 26 08:30:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:00 node-1 multipathd: uevent trigger error
<129>Sep 26 08:30:03 node-1 haproxy[30224]: 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 26 08:30:03 node-1 haproxy[30224]: 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 26 08:30:03 node-1 haproxy[30224]: Server keystone-1/node-2 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 26 08:30:03 node-1 haproxy[30224]: Server keystone-1/node-3 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 26 08:30:03 node-1 haproxy[30224]: proxy keystone-1 has no server available!
<129>Sep 26 08:30:03 node-1 haproxy[30224]: 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 26 08:30:03 node-1 haproxy[30224]: Server keystone-2/node-2 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 26 08:30:03 node-1 haproxy[30224]: Server keystone-2/node-3 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 26 08:30:03 node-1 haproxy[30224]: proxy keystone-2 has no server available!
<129>Sep 26 08:30:03 node-1 haproxy[30224]: 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 26 08:30:03 node-1 haproxy[30224]: Server nova-api/node-2 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 26 08:30:03 node-1 haproxy[30224]: Server nova-api/node-3 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 26 08:30:03 node-1 haproxy[30224]: proxy nova-api has no server available!
<129>Sep 26 08:30:03 node-1 haproxy[30224]: 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 26 08:30:03 node-1 haproxy[30224]: Server nova-metadata-api/node-2 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 26 08:30:03 node-1 haproxy[30224]: Server nova-metadata-api/node-3 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 26 08:30:03 node-1 haproxy[30224]: proxy nova-metadata-api has no server available!
<129>Sep 26 08:30:03 node-1 haproxy[30224]: 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 26 08:30:03 node-1 haproxy[30224]: Server glance-api/node-2 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 26 08:30:03 node-1 haproxy[30224]: Server glance-api/node-3 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 26 08:30:03 node-1 haproxy[30224]: proxy glance-api has no server available!
<129>Sep 26 08:30:03 node-1 haproxy[30224]: 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 26 08:30:03 node-1 haproxy[30224]: Server glance-glare/node-2 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 26 08:30:03 node-1 haproxy[30224]: Server glance-glare/node-3 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 26 08:30:03 node-1 haproxy[30224]: proxy glance-glare has no server available!
<129>Sep 26 08:30:04 node-1 haproxy[30228]: 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 26 08:30:04 node-1 haproxy[30228]: Server neutron/node-2 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 26 08:30:04 node-1 haproxy[30228]: Server neutron/node-3 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 26 08:30:04 node-1 haproxy[30228]: proxy neutron has no server available!
<129>Sep 26 08:30:04 node-1 haproxy[30228]: 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 26 08:30:04 node-1 haproxy[30228]: Server glance-registry/node-2 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 26 08:30:04 node-1 haproxy[30228]: Server glance-registry/node-3 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 26 08:30:04 node-1 haproxy[30228]: proxy glance-registry has no server available!
<129>Sep 26 08:30:04 node-1 haproxy[30228]: 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 26 08:30:04 node-1 haproxy[30228]: Backup Server mysqld/node-2 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 26 08:30:04 node-1 haproxy[30228]: Backup Server mysqld/node-3 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 26 08:30:04 node-1 haproxy[30228]: proxy mysqld has no server available!
<129>Sep 26 08:30:04 node-1 haproxy[30228]: 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 26 08:30:04 node-1 haproxy[30228]: Server object-storage/node-2 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 26 08:30:04 node-1 haproxy[30228]: Server object-storage/node-3 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 26 08:30:04 node-1 haproxy[30228]: proxy object-storage has no server available!
<129>Sep 26 08:30:04 node-1 haproxy[30228]: 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 26 08:30:04 node-1 haproxy[30228]: Server aodh/node-2 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 26 08:30:04 node-1 haproxy[30228]: Server aodh/node-3 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 26 08:30:04 node-1 haproxy[30228]: proxy aodh has no server available!
<129>Sep 26 08:30:04 node-1 haproxy[30228]: 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 26 08:30:04 node-1 haproxy[30228]: Server ceilometer/node-2 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 26 08:30:04 node-1 haproxy[30228]: Server ceilometer/node-3 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 26 08:30:04 node-1 haproxy[30228]: proxy ceilometer has no server available!
<129>Sep 26 08:30:04 node-1 haproxy[30228]: 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 26 08:30:04 node-1 haproxy[30228]: Server nova-novncproxy/node-2 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 26 08:30:04 node-1 haproxy[30228]: Server nova-novncproxy/node-3 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 26 08:30:04 node-1 haproxy[30228]: proxy nova-novncproxy has no server available!
<27>Sep 26 08:30:06 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:06 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:06 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:06 node-1 multipathd: uevent trigger error
<129>Sep 26 08:30:08 node-1 haproxy[31532]: 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 26 08:30:08 node-1 haproxy[31532]: 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 26 08:30:08 node-1 haproxy[31532]: Server keystone-1/node-2 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 26 08:30:08 node-1 haproxy[31532]: Server keystone-1/node-3 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 26 08:30:08 node-1 haproxy[31532]: proxy keystone-1 has no server available!
<129>Sep 26 08:30:08 node-1 haproxy[31532]: 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 26 08:30:08 node-1 haproxy[31532]: Server keystone-2/node-2 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 26 08:30:08 node-1 haproxy[31532]: Server keystone-2/node-3 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 26 08:30:08 node-1 haproxy[31532]: proxy keystone-2 has no server available!
<129>Sep 26 08:30:08 node-1 haproxy[31532]: 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 26 08:30:08 node-1 haproxy[31532]: Server nova-api/node-2 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 26 08:30:08 node-1 haproxy[31532]: Server nova-api/node-3 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 26 08:30:08 node-1 haproxy[31532]: proxy nova-api has no server available!
<129>Sep 26 08:30:08 node-1 haproxy[31532]: 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 26 08:30:09 node-1 haproxy[31536]: Server nova-metadata-api/node-2 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 26 08:30:09 node-1 haproxy[31536]: Server nova-metadata-api/node-3 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 26 08:30:09 node-1 haproxy[31536]: proxy nova-metadata-api has no server available!
<129>Sep 26 08:30:09 node-1 haproxy[31536]: 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 26 08:30:09 node-1 haproxy[31536]: Backup Server cinder-api/node-2 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 26 08:30:09 node-1 haproxy[31536]: Backup Server cinder-api/node-3 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 26 08:30:09 node-1 haproxy[31536]: proxy cinder-api has no server available!
<129>Sep 26 08:30:09 node-1 haproxy[31536]: 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 26 08:30:09 node-1 haproxy[31536]: Server glance-api/node-2 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 26 08:30:09 node-1 haproxy[31536]: Server glance-api/node-3 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 26 08:30:09 node-1 haproxy[31536]: proxy glance-api has no server available!
<129>Sep 26 08:30:09 node-1 haproxy[31536]: 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 26 08:30:09 node-1 haproxy[31536]: Server glance-glare/node-2 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 26 08:30:09 node-1 haproxy[31536]: Server glance-glare/node-3 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 26 08:30:09 node-1 haproxy[31536]: proxy glance-glare has no server available!
<129>Sep 26 08:30:09 node-1 haproxy[31536]: 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 26 08:30:09 node-1 haproxy[31536]: Server neutron/node-2 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 26 08:30:09 node-1 haproxy[31536]: Server neutron/node-3 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 26 08:30:09 node-1 haproxy[31536]: proxy neutron has no server available!
<129>Sep 26 08:30:09 node-1 haproxy[31536]: 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 26 08:30:09 node-1 haproxy[31536]: Server glance-registry/node-2 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 26 08:30:09 node-1 haproxy[31536]: Server glance-registry/node-3 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 26 08:30:09 node-1 haproxy[31536]: proxy glance-registry has no server available!
<129>Sep 26 08:30:09 node-1 haproxy[31536]: 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 26 08:30:09 node-1 haproxy[31536]: Backup Server mysqld/node-2 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 26 08:30:09 node-1 haproxy[31536]: Backup Server mysqld/node-3 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 26 08:30:09 node-1 haproxy[31536]: proxy mysqld has no server available!
<129>Sep 26 08:30:09 node-1 haproxy[31536]: 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 26 08:30:09 node-1 haproxy[31536]: Server object-storage/node-2 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 26 08:30:10 node-1 haproxy[31536]: Server object-storage/node-3 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 26 08:30:10 node-1 haproxy[31536]: proxy object-storage has no server available!
<129>Sep 26 08:30:10 node-1 haproxy[31536]: 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 26 08:30:10 node-1 haproxy[31536]: Server aodh/node-2 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 26 08:30:10 node-1 haproxy[31536]: Server aodh/node-3 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 26 08:30:10 node-1 haproxy[31536]: proxy aodh has no server available!
<129>Sep 26 08:30:10 node-1 haproxy[31536]: 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 26 08:30:10 node-1 haproxy[31536]: Server ceilometer/node-2 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 26 08:30:10 node-1 haproxy[31536]: Server ceilometer/node-3 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 26 08:30:10 node-1 haproxy[31536]: proxy ceilometer has no server available!
<129>Sep 26 08:30:10 node-1 haproxy[31536]: 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 26 08:30:10 node-1 haproxy[31536]: Server nova-novncproxy/node-2 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 26 08:30:10 node-1 haproxy[31536]: Server nova-novncproxy/node-3 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 26 08:30:10 node-1 haproxy[31536]: proxy nova-novncproxy has no server available!
<27>Sep 26 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:11 node-1 multipathd: uevent trigger error
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Server keystone-1/node-2 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 26 08:30:14 node-1 haproxy[427]: Server keystone-1/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy keystone-1 has no server available!
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Server keystone-2/node-2 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 26 08:30:14 node-1 haproxy[427]: Server keystone-2/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy keystone-2 has no server available!
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Server nova-api/node-2 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 26 08:30:14 node-1 haproxy[427]: Server nova-api/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy nova-api has no server available!
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Server nova-metadata-api/node-2 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 26 08:30:14 node-1 haproxy[427]: Server nova-metadata-api/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy nova-metadata-api has no server available!
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Backup Server cinder-api/node-2 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 26 08:30:14 node-1 haproxy[427]: Backup Server cinder-api/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy cinder-api has no server available!
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Server glance-api/node-2 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 26 08:30:14 node-1 haproxy[427]: Server glance-api/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy glance-api has no server available!
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Server glance-glare/node-2 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 26 08:30:14 node-1 haproxy[427]: Server glance-glare/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy glance-glare has no server available!
<129>Sep 26 08:30:14 node-1 haproxy[427]: 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 26 08:30:14 node-1 haproxy[427]: Server neutron/node-2 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 26 08:30:14 node-1 haproxy[427]: Server neutron/node-3 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 26 08:30:14 node-1 haproxy[427]: proxy neutron has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server glance-registry/node-2 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 26 08:30:15 node-1 haproxy[434]: Server glance-registry/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy glance-registry has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Backup Server mysqld/node-2 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 26 08:30:15 node-1 haproxy[434]: Backup Server mysqld/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy mysqld has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server object-storage/node-2 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 26 08:30:15 node-1 haproxy[434]: Server object-storage/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy object-storage has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server aodh/node-2 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 26 08:30:15 node-1 haproxy[434]: Server aodh/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy aodh has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server ceilometer/node-2 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 26 08:30:15 node-1 haproxy[434]: Server ceilometer/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy ceilometer has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server heat-api/node-2 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 26 08:30:15 node-1 haproxy[434]: Server heat-api/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy heat-api has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server heat-api-cfn/node-2 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 26 08:30:15 node-1 haproxy[434]: Server heat-api-cfn/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy heat-api-cfn has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server heat-api-cloudwatch/node-2 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 26 08:30:15 node-1 haproxy[434]: Server heat-api-cloudwatch/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy heat-api-cloudwatch has no server available!
<129>Sep 26 08:30:15 node-1 haproxy[434]: 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 26 08:30:15 node-1 haproxy[434]: Server nova-novncproxy/node-2 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 26 08:30:15 node-1 haproxy[434]: Server nova-novncproxy/node-3 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 26 08:30:15 node-1 haproxy[434]: proxy nova-novncproxy has no server available!
<27>Sep 26 08:30:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:30:27 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 26 08:30:51 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 26 08:30:53 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 26 08:31:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 08:31:26 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 08:31:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:31:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:31:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:31:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:31:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:31:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 26 08:34:26 node-1 apache2_error [Mon Sep 26 08:34:19.555795 2016] [mpm_event:notice] [pid 8616:tid 140437757761408] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 26 08:34:26 node-1 apache2_error [Mon Sep 26 08:34:19.555899 2016] [core:notice] [pid 8616:tid 140437757761408] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 26 08:34:26 node-1 apache2_error [Mon Sep 26 08:34:22.321975 2016] [mpm_event:notice] [pid 8616:tid 140437757761408] AH00491: caught SIGTERM, shutting down
<43>Sep 26 08:34:26 node-1 apache2_error [Mon Sep 26 08:34:23.400538 2016] [mpm_worker:notice] [pid 9967:tid 140539583072128] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 26 08:34:26 node-1 apache2_error [Mon Sep 26 08:34:23.400589 2016] [core:notice] [pid 9967:tid 140539583072128] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 08:34:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:27 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:34:35 node-1 multipathd: uevent trigger error
<43>Sep 26 08:35:46 node-1 apache2_error [Mon Sep 26 08:35:37.134826 2016] [mpm_worker:notice] [pid 9967:tid 140539583072128] AH00295: caught SIGTERM, shutting down
<43>Sep 26 08:35:46 node-1 apache2_error [Mon Sep 26 08:35:37.899130 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 08:35:46 node-1 apache2_error [Mon Sep 26 08:35:37.899193 2016] [core:notice] [pid 23306:tid 140441580472192] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 26 08:36:27 node-1 apache2_error [Mon Sep 26 08:36:21.819355 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 26 08:36:27 node-1 apache2_error [Mon Sep 26 08:36:22.014495 2016] [mpm_worker:warn] [pid 23306:tid 140441580472192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 08:36:27 node-1 apache2_error [Mon Sep 26 08:36:22.020976 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 08:36:27 node-1 apache2_error [Mon Sep 26 08:36:22.021014 2016] [core:notice] [pid 23306:tid 140441580472192] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 08:37:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 08:37:31 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:31 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:31 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:31 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:31 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:37:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:01 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:01 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:01 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:01 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:01 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:38:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:39:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:39:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:39:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:39:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:40:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:40:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:40:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:40:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:40:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:40:25 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 08:41:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:16 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:41:38 node-1 multipathd: uevent trigger error
<27>Sep 26 08:43:27 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 08:43:57 node-1 multipathd: uevent trigger error
<27>Sep 26 08:43:57 node-1 multipathd: uevent trigger error
<27>Sep 26 08:43:57 node-1 multipathd: uevent trigger error
<27>Sep 26 08:43:57 node-1 multipathd: uevent trigger error
<27>Sep 26 08:43:57 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:13 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:18 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:18 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:18 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:18 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:18 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:18 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:44:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:25 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:25 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:25 node-1 multipathd: uevent trigger error
<27>Sep 26 08:45:25 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:08 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:15 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 26 08:46:15 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 26 08:46:15 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 26 08:46:16 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Sep 26 08:46:16 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Sep 26 08:46:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:17 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 08:46:29 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:29 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:29 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:29 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:29 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:44 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:44 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:44 node-1 multipathd: uevent trigger error
<27>Sep 26 08:46:44 node-1 multipathd: uevent trigger error
<27>Sep 26 08:47:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:47:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:47:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:47:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:47:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:47:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:19 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:30 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 08:49:52 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:52 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:52 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:52 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:58 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:58 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:58 node-1 multipathd: uevent trigger error
<27>Sep 26 08:49:58 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:21 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:37 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:37 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:47 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:47 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:47 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:47 node-1 multipathd: uevent trigger error
<27>Sep 26 08:50:47 node-1 multipathd: uevent trigger error
<27>Sep 26 08:51:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:51:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:51:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:51:35 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 08:52:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:43 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:59 node-1 multipathd: uevent trigger error
<27>Sep 26 08:52:59 node-1 multipathd: uevent trigger error
<11>Sep 26 08:53:12 node-1 liberasurecode[11945]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:12 node-1 liberasurecode[11945]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:12 node-1 liberasurecode[11945]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:12 node-1 liberasurecode[11945]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:12 node-1 liberasurecode[12076]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:12 node-1 liberasurecode[12076]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:12 node-1 liberasurecode[12076]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:12 node-1 liberasurecode[12076]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:14 node-1 liberasurecode[13176]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:14 node-1 liberasurecode[13176]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:14 node-1 liberasurecode[13176]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:14 node-1 liberasurecode[13176]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14285]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14285]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14285]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14285]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14326]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14326]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14326]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14326]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14372]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:18 node-1 liberasurecode[14372]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14467]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14467]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14467]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14467]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14491]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14491]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14491]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14491]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14520]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14520]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14566]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14566]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14566]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:19 node-1 liberasurecode[14566]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:28 node-1 liberasurecode[15217]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:28 node-1 liberasurecode[15217]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:28 node-1 liberasurecode[15217]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:53:28 node-1 liberasurecode[15217]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 26 08:53:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:53:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:53:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:53:37 node-1 multipathd: uevent trigger error
<43>Sep 26 08:54:28 node-1 apache2_error [Mon Sep 26 08:54:22.633014 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 26 08:54:28 node-1 apache2_error [Mon Sep 26 08:54:23.015096 2016] [mpm_worker:warn] [pid 23306:tid 140441580472192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 08:54:28 node-1 apache2_error [Mon Sep 26 08:54:23.019256 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 08:54:28 node-1 apache2_error [Mon Sep 26 08:54:23.019277 2016] [core:notice] [pid 23306:tid 140441580472192] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 26 08:55:01 node-1 liberasurecode[28808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:55:01 node-1 liberasurecode[28808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:55:01 node-1 liberasurecode[28808]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 08:55:01 node-1 liberasurecode[28808]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 26 08:55:03 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:03 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:03 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:03 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:04 node-1 multipathd: uevent trigger error
<43>Sep 26 08:55:08 node-1 apache2_error [Mon Sep 26 08:54:59.916827 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 26 08:55:08 node-1 apache2_error [Mon Sep 26 08:55:00.112059 2016] [mpm_worker:warn] [pid 23306:tid 140441580472192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 08:55:08 node-1 apache2_error [Mon Sep 26 08:55:00.119668 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 08:55:08 node-1 apache2_error [Mon Sep 26 08:55:00.119698 2016] [core:notice] [pid 23306:tid 140441580472192] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:34 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 26 08:55:48 node-1 apache2_error [Mon Sep 26 08:55:45.911663 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 26 08:55:48 node-1 apache2_error [Mon Sep 26 08:55:46.105515 2016] [mpm_worker:warn] [pid 23306:tid 140441580472192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 08:55:48 node-1 apache2_error [Mon Sep 26 08:55:46.113783 2016] [mpm_worker:notice] [pid 23306:tid 140441580472192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 08:55:48 node-1 apache2_error [Mon Sep 26 08:55:46.113817 2016] [core:notice] [pid 23306:tid 140441580472192] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 08:55:50 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:50 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:50 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:50 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:50 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:50 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:55:56 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:02 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:11 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:49 node-1 multipathd: uevent trigger error
<27>Sep 26 08:56:55 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 26 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:09 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:14 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:14 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:14 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:14 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:14 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:28 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:30 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 08:57:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:57:55 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:00 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:07 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:15 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:15 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:15 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:15 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:15 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:32 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:36 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:41 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:46 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:46 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:46 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:46 node-1 multipathd: uevent trigger error
<27>Sep 26 08:58:46 node-1 multipathd: uevent trigger error
<11>Sep 26 09:00:01 node-1 liberasurecode[32368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 09:00:01 node-1 liberasurecode[32368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 09:00:01 node-1 liberasurecode[32368]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 09:00:01 node-1 liberasurecode[32368]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
