Sep 18 08:23:00 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8385" x-info="http://www.rsyslog.com"] start
Sep 18 08:23:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 18 08:23:00 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 18 08:23:00 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 18 08:23:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 18 08:23:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 18 08:23:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 18 08:23:00 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 18 08:23:00 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1458e9ae-b3cd-4efd-89ee-8da94f85c276 nomdmonddf nomdmonisw
Sep 18 08:23:00 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 18 08:23:00 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 18 08:23:00 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 18 08:23:00 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 18 08:23:00 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 18 08:23:00 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 18 08:23:00 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 18 08:23:00 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 18 08:23:00 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 18 08:23:00 node-1 kernel: [    0.000000] No AGP bridge found
Sep 18 08:23:00 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 18 08:23:00 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 18 08:23:00 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 18 08:23:00 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 18 08:23:00 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 18 08:23:00 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 18 08:23:00 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 18 08:23:00 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 18 08:23:00 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 18 08:23:00 node-1 kernel: [    0.000000]   2 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000]   3 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000]   4 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000]   5 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000]   6 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000]   7 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000]   8 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000]   9 disabled
Sep 18 08:23:00 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 18 08:23:00 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 18 08:23:00 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 18 08:23:00 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 18 08:23:00 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 18 08:23:00 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 18 08:23:00 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 18 08:23:00 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 18 08:23:00 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 18 08:23:00 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 18 08:23:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 18 08:23:00 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 18 08:23:00 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 18 08:23:00 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 18 08:23:00 node-1 kernel: [    0.000000] Zone ranges:
Sep 18 08:23:00 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 18 08:23:00 node-1 kernel: [    0.000000] Early memory node ranges
Sep 18 08:23:00 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 18 08:23:00 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 18 08:23:00 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 18 08:23:00 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 18 08:23:00 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 18 08:23:00 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 18 08:23:00 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 18 08:23:00 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 18 08:23:00 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 18 08:23:00 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 18 08:23:00 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 18 08:23:00 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 18 08:23:00 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 18 08:23:00 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 18 08:23:00 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 18 08:23:00 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 18 08:23:00 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 18 08:23:00 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 18 08:23:00 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 18 08:23:00 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 18 08:23:00 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 18 08:23:00 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 18 08:23:00 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 18 08:23:00 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 18 08:23:00 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 18 08:23:00 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 18 08:23:00 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1458e9ae-b3cd-4efd-89ee-8da94f85c276 nomdmonddf nomdmonisw
Sep 18 08:23:00 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 18 08:23:00 node-1 kernel: [    0.000000] Checking aperture...
Sep 18 08:23:00 node-1 kernel: [    0.000000] No AGP bridge found
Sep 18 08:23:00 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 18 08:23:00 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 18 08:23:00 node-1 kernel: [    0.000000] Memory: 32653324K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Sep 18 08:23:00 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 18 08:23:00 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 18 08:23:00 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 18 08:23:00 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 18 08:23:00 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 18 08:23:00 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 18 08:23:00 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 18 08:23:00 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 18 08:23:00 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 18 08:23:00 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 18 08:23:00 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 18 08:23:00 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 18 08:23:00 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 18 08:23:00 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 18 08:23:00 node-1 kernel: [    0.004000] tsc: Detected 3492.174 MHz processor
Sep 18 08:23:00 node-1 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.34 BogoMIPS (lpj=13968696)
Sep 18 08:23:00 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 18 08:23:00 node-1 kernel: [    0.000046] Security Framework initialized
Sep 18 08:23:00 node-1 kernel: [    0.000064] AppArmor: AppArmor initialized
Sep 18 08:23:00 node-1 kernel: [    0.000065] Yama: becoming mindful.
Sep 18 08:23:00 node-1 kernel: [    0.001462] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.006406] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.008331] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.008360] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.008651] Initializing cgroup subsys memory
Sep 18 08:23:00 node-1 kernel: [    0.008658] Initializing cgroup subsys devices
Sep 18 08:23:00 node-1 kernel: [    0.008660] Initializing cgroup subsys freezer
Sep 18 08:23:00 node-1 kernel: [    0.008662] Initializing cgroup subsys blkio
Sep 18 08:23:00 node-1 kernel: [    0.008664] Initializing cgroup subsys perf_event
Sep 18 08:23:00 node-1 kernel: [    0.008666] Initializing cgroup subsys hugetlb
Sep 18 08:23:00 node-1 kernel: [    0.008685] CPU: Physical Processor ID: 0
Sep 18 08:23:00 node-1 kernel: [    0.008687] CPU: Processor Core ID: 0
Sep 18 08:23:00 node-1 kernel: [    0.008690] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 18 08:23:00 node-1 kernel: [    0.008690] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 18 08:23:00 node-1 kernel: [    0.009384] mce: CPU supports 22 MCE banks
Sep 18 08:23:00 node-1 kernel: [    0.009411] CPU0: Thermal monitoring enabled (TM1)
Sep 18 08:23:00 node-1 kernel: [    0.009432] process: using mwait in idle threads
Sep 18 08:23:00 node-1 kernel: [    0.009435] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 18 08:23:00 node-1 kernel: [    0.009435] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 18 08:23:00 node-1 kernel: [    0.009435] tlb_flushall_shift: 6
Sep 18 08:23:00 node-1 kernel: [    0.009523] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 18 08:23:00 node-1 kernel: [    0.010245] ACPI: Core revision 20131115
Sep 18 08:23:00 node-1 kernel: [    0.022906] ACPI: All ACPI Tables successfully acquired
Sep 18 08:23:00 node-1 kernel: [    0.023069] ftrace: allocating 28617 entries in 112 pages
Sep 18 08:23:00 node-1 kernel: [    0.032046] dmar: Host address width 46
Sep 18 08:23:00 node-1 kernel: [    0.032048] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 18 08:23:00 node-1 kernel: [    0.032054] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 18 08:23:00 node-1 kernel: [    0.032056] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 18 08:23:00 node-1 kernel: [    0.032060] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 18 08:23:00 node-1 kernel: [    0.032061] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 18 08:23:00 node-1 kernel: [    0.032063] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 18 08:23:00 node-1 kernel: [    0.032064] dmar: ATSR flags: 0x0
Sep 18 08:23:00 node-1 kernel: [    0.032065] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 18 08:23:00 node-1 kernel: [    0.032066] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 18 08:23:00 node-1 kernel: [    0.032181] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 18 08:23:00 node-1 kernel: [    0.032182] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 18 08:23:00 node-1 kernel: [    0.032183] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 18 08:23:00 node-1 kernel: [    0.032184] HPET id 0 under DRHD base 0xc7ffc000
Sep 18 08:23:00 node-1 kernel: [    0.032185] Your BIOS is broken and requested that x2apic be disabled.
Sep 18 08:23:00 node-1 kernel: [    0.032185] This will slightly decrease performance.
Sep 18 08:23:00 node-1 kernel: [    0.032185] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 18 08:23:00 node-1 kernel: [    0.032618] Enabled IRQ remapping in xapic mode
Sep 18 08:23:00 node-1 kernel: [    0.032619] x2apic not enabled, IRQ remapping is in xapic mode
Sep 18 08:23:00 node-1 kernel: [    0.032623] Switched APIC routing to physical flat.
Sep 18 08:23:00 node-1 kernel: [    0.033240] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 18 08:23:00 node-1 kernel: [    0.072892] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 18 08:23:00 node-1 kernel: [    0.072898] TSC deadline timer enabled
Sep 18 08:23:00 node-1 kernel: [    0.072905] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 18 08:23:00 node-1 kernel: [    0.072912] ... version:                3
Sep 18 08:23:00 node-1 kernel: [    0.072913] ... bit width:              48
Sep 18 08:23:00 node-1 kernel: [    0.072914] ... generic registers:      4
Sep 18 08:23:00 node-1 kernel: [    0.072915] ... value mask:             0000ffffffffffff
Sep 18 08:23:00 node-1 kernel: [    0.072916] ... max period:             0000ffffffffffff
Sep 18 08:23:00 node-1 kernel: [    0.072917] ... fixed-purpose events:   3
Sep 18 08:23:00 node-1 kernel: [    0.072918] ... event mask:             000000070000000f
Sep 18 08:23:00 node-1 kernel: [    0.074306] x86: Booting SMP configuration:
Sep 18 08:23:00 node-1 kernel: [    0.088411] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 18 08:23:00 node-1 kernel: [    0.074308] .... node  #0, CPUs:        #1  #2  #3
Sep 18 08:23:00 node-1 kernel: [    0.116322] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 18 08:23:00 node-1 kernel: [    0.270285] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 18 08:23:00 node-1 kernel: [    0.325904] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 18 08:23:00 node-1 kernel: [    0.382767] x86: Booted up 2 nodes, 16 CPUs
Sep 18 08:23:00 node-1 kernel: [    0.382770] smpboot: Total of 16 processors activated (111762.06 BogoMIPS)
Sep 18 08:23:00 node-1 kernel: [    0.406724] devtmpfs: initialized
Sep 18 08:23:00 node-1 kernel: [    0.409839] EVM: security.selinux
Sep 18 08:23:00 node-1 kernel: [    0.409841] EVM: security.SMACK64
Sep 18 08:23:00 node-1 kernel: [    0.409842] EVM: security.ima
Sep 18 08:23:00 node-1 kernel: [    0.409843] EVM: security.capability
Sep 18 08:23:00 node-1 kernel: [    0.409893] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.410585] pinctrl core: initialized pinctrl subsystem
Sep 18 08:23:00 node-1 kernel: [    0.410649] regulator-dummy: no parameters
Sep 18 08:23:00 node-1 kernel: [    0.410681] RTC time:  8:22:24, date: 09/18/16
Sep 18 08:23:00 node-1 kernel: [    0.410717] NET: Registered protocol family 16
Sep 18 08:23:00 node-1 kernel: [    0.410802] cpuidle: using governor ladder
Sep 18 08:23:00 node-1 kernel: [    0.410803] cpuidle: using governor menu
Sep 18 08:23:00 node-1 kernel: [    0.410838] ACPI: bus type PCI registered
Sep 18 08:23:00 node-1 kernel: [    0.410840] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 18 08:23:00 node-1 kernel: [    0.410885] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 18 08:23:00 node-1 kernel: [    0.410888] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 18 08:23:00 node-1 kernel: [    0.424619] PCI: Using configuration type 1 for base access
Sep 18 08:23:00 node-1 kernel: [    0.425622] bio: create slab <bio-0> at 0
Sep 18 08:23:00 node-1 kernel: [    0.425893] ACPI: Added _OSI(Module Device)
Sep 18 08:23:00 node-1 kernel: [    0.425895] ACPI: Added _OSI(Processor Device)
Sep 18 08:23:00 node-1 kernel: [    0.425896] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 18 08:23:00 node-1 kernel: [    0.425897] ACPI: Added _OSI(Processor Aggregator Device)
Sep 18 08:23:00 node-1 kernel: [    0.438543] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 18 08:23:00 node-1 kernel: [    0.449124] ACPI: Interpreter enabled
Sep 18 08:23:00 node-1 kernel: [    0.449130] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 18 08:23:00 node-1 kernel: [    0.449134] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 18 08:23:00 node-1 kernel: [    0.449136] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 18 08:23:00 node-1 kernel: [    0.449143] ACPI: (supports S0 S4 S5)
Sep 18 08:23:00 node-1 kernel: [    0.449145] ACPI: Using IOAPIC for interrupt routing
Sep 18 08:23:00 node-1 kernel: [    0.449187] HEST: Table parsing has been initialized.
Sep 18 08:23:00 node-1 kernel: [    0.449189] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 18 08:23:00 node-1 kernel: [    0.449746] ACPI: No dock devices found.
Sep 18 08:23:00 node-1 kernel: [    0.461457] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 18 08:23:00 node-1 kernel: [    0.461462] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 08:23:00 node-1 kernel: [    0.461465] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 18 08:23:00 node-1 kernel: [    0.461494] PCI host bridge to bus 0000:ff
Sep 18 08:23:00 node-1 kernel: [    0.461496] pci_bus 0000:ff: root bus resource [bus ff]
Sep 18 08:23:00 node-1 kernel: [    0.461504] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461542] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.461573] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461608] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461638] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.461668] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.461699] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461728] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461760] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461788] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461815] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461841] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461871] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461897] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461924] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461951] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.461980] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462007] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462034] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.462062] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462088] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.462114] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462140] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462171] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.462205] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462237] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462267] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462298] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462329] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462360] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462391] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462421] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462453] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462486] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462520] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462553] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462587] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462618] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462646] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462677] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462710] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462748] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462783] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462816] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462847] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462877] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462909] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462940] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.462973] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463004] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463036] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463066] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463095] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463124] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463154] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463185] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463216] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463274] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 18 08:23:00 node-1 kernel: [    0.463277] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 08:23:00 node-1 kernel: [    0.463280] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 18 08:23:00 node-1 kernel: [    0.463297] PCI host bridge to bus 0000:7f
Sep 18 08:23:00 node-1 kernel: [    0.463299] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 18 08:23:00 node-1 kernel: [    0.463304] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463334] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.463363] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463392] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463414] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.463438] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.463464] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463490] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463512] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463534] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463557] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463579] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463603] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463627] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463653] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463683] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463705] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463728] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463752] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.463776] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463798] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.463820] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463842] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463870] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 18 08:23:00 node-1 kernel: [    0.463903] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463929] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463958] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.463986] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464012] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464039] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464065] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464093] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464119] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464148] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464177] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464206] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464235] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464260] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464285] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464313] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464339] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464367] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464398] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464427] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464454] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464479] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464505] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464534] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464562] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464590] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464620] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464647] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464670] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464697] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464723] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464756] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.464783] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.466033] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 18 08:23:00 node-1 kernel: [    0.466036] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 08:23:00 node-1 kernel: [    0.467151] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 18 08:23:00 node-1 kernel: [    0.467662] PCI host bridge to bus 0000:00
Sep 18 08:23:00 node-1 kernel: [    0.467665] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 18 08:23:00 node-1 kernel: [    0.467667] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 18 08:23:00 node-1 kernel: [    0.467668] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 18 08:23:00 node-1 kernel: [    0.467669] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 18 08:23:00 node-1 kernel: [    0.467671] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 18 08:23:00 node-1 kernel: [    0.467672] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 18 08:23:00 node-1 kernel: [    0.467674] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 18 08:23:00 node-1 kernel: [    0.467679] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 18 08:23:00 node-1 kernel: [    0.467762] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.467793] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.467835] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 18 08:23:00 node-1 kernel: [    0.467855] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.467884] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.467925] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 18 08:23:00 node-1 kernel: [    0.467944] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.467973] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.468013] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 18 08:23:00 node-1 kernel: [    0.468031] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.468103] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.468181] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.468259] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 18 08:23:00 node-1 kernel: [    0.468264] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 18 08:23:00 node-1 kernel: [    0.468349] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 18 08:23:00 node-1 kernel: [    0.468498] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 18 08:23:00 node-1 kernel: [    0.468515] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 18 08:23:00 node-1 kernel: [    0.468593] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.468646] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 18 08:23:00 node-1 kernel: [    0.468668] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.468723] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.468766] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 18 08:23:00 node-1 kernel: [    0.468795] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.468851] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.468894] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 18 08:23:00 node-1 kernel: [    0.468918] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 18 08:23:00 node-1 kernel: [    0.468936] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 18 08:23:00 node-1 kernel: [    0.469013] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.469063] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 18 08:23:00 node-1 kernel: [    0.469089] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 18 08:23:00 node-1 kernel: [    0.469338] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 18 08:23:00 node-1 kernel: [    0.469344] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 18 08:23:00 node-1 kernel: [    0.469350] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.469355] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.469363] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 18 08:23:00 node-1 kernel: [    0.469393] pci 0000:01:00.0: supports D1 D2
Sep 18 08:23:00 node-1 kernel: [    0.479336] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 18 08:23:00 node-1 kernel: [    0.479343] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 18 08:23:00 node-1 kernel: [    0.479347] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 18 08:23:00 node-1 kernel: [    0.479611] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.479671] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 18 08:23:00 node-1 kernel: [    0.487334] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 18 08:23:00 node-1 kernel: [    0.487340] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.487344] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 08:23:00 node-1 kernel: [    0.487428] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.487510] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.487587] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.487632] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 18 08:23:00 node-1 kernel: [    0.487635] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.487637] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 08:23:00 node-1 kernel: [    0.487695] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.487819] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.487873] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 18 08:23:00 node-1 kernel: [    0.487876] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.487878] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.487926] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.488046] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.488088] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.488207] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.488243] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.488365] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.488401] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 18 08:23:00 node-1 kernel: [    0.488520] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 18 08:23:00 node-1 kernel: [    0.488561] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 18 08:23:00 node-1 kernel: [    0.488564] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.488566] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.488631] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 18 08:23:00 node-1 kernel: [    0.488695] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.488750] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.488791] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 18 08:23:00 node-1 kernel: [    0.488873] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 18 08:23:00 node-1 kernel: [    0.488980] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 18 08:23:00 node-1 kernel: [    0.488982] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.488984] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.489040] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 18 08:23:00 node-1 kernel: [    0.489093] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.489142] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.489356] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 18 08:23:00 node-1 kernel: [    0.489360] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 18 08:23:00 node-1 kernel: [    0.489425] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 18 08:23:00 node-1 kernel: [    0.489478] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.489527] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.489763] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 18 08:23:00 node-1 kernel: [    0.489766] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 18 08:23:00 node-1 kernel: [    0.489824] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 18 08:23:00 node-1 kernel: [    0.489884] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.489936] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 18 08:23:00 node-1 kernel: [    0.490157] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 18 08:23:00 node-1 kernel: [    0.490160] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 18 08:23:00 node-1 kernel: [    0.490335] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 18 08:23:00 node-1 kernel: [    0.490374] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 18 08:23:00 node-1 kernel: [    0.490452] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 18 08:23:00 node-1 kernel: [    0.490471] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 18 08:23:00 node-1 kernel: [    0.490484] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 18 08:23:00 node-1 kernel: [    0.490498] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 18 08:23:00 node-1 kernel: [    0.490548] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 18 08:23:00 node-1 kernel: [    0.495341] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 18 08:23:00 node-1 kernel: [    0.495350] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 18 08:23:00 node-1 kernel: [    0.495403] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 18 08:23:00 node-1 kernel: [    0.496154] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 18 08:23:00 node-1 kernel: [    0.496157] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 08:23:00 node-1 kernel: [    0.496277] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 18 08:23:00 node-1 kernel: [    0.496387] PCI host bridge to bus 0000:80
Sep 18 08:23:00 node-1 kernel: [    0.496389] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 18 08:23:00 node-1 kernel: [    0.496390] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 18 08:23:00 node-1 kernel: [    0.496392] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 18 08:23:00 node-1 kernel: [    0.496400] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.496464] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.496533] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 18 08:23:00 node-1 kernel: [    0.496597] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 18 08:23:00 node-1 kernel: [    0.496602] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 18 08:23:00 node-1 kernel: [    0.496674] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 18 08:23:00 node-1 kernel: [    0.496972] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 18 08:23:00 node-1 kernel: [    0.497004] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 18 08:23:00 node-1 kernel: [    0.497034] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 18 08:23:00 node-1 kernel: [    0.497063] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 18 08:23:00 node-1 kernel: [    0.497093] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 08:23:00 node-1 kernel: [    0.497123] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 08:23:00 node-1 kernel: [    0.497153] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 08:23:00 node-1 kernel: [    0.497183] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 08:23:00 node-1 kernel: [    0.497267] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 18 08:23:00 node-1 kernel: [    0.497272] ACPI: \_SB_.UNC1: notify handler is installed
Sep 18 08:23:00 node-1 kernel: [    0.497273] ACPI: \_SB_.UNC0: notify handler is installed
Sep 18 08:23:00 node-1 kernel: [    0.497288] ACPI: \_SB_.PCI0: notify handler is installed
Sep 18 08:23:00 node-1 kernel: [    0.497341] ACPI: \_SB_.PCI1: notify handler is installed
Sep 18 08:23:00 node-1 kernel: [    0.497420] Found 4 acpi root devices
Sep 18 08:23:00 node-1 kernel: [    0.497527] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 18 08:23:00 node-1 kernel: [    0.497529] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 18 08:23:00 node-1 kernel: [    0.497531] vgaarb: loaded
Sep 18 08:23:00 node-1 kernel: [    0.497532] vgaarb: bridge control possible 0000:0c:00.0
Sep 18 08:23:00 node-1 kernel: [    0.497648] SCSI subsystem initialized
Sep 18 08:23:00 node-1 kernel: [    0.497713] libata version 3.00 loaded.
Sep 18 08:23:00 node-1 kernel: [    0.497728] ACPI: bus type USB registered
Sep 18 08:23:00 node-1 kernel: [    0.497739] usbcore: registered new interface driver usbfs
Sep 18 08:23:00 node-1 kernel: [    0.497744] usbcore: registered new interface driver hub
Sep 18 08:23:00 node-1 kernel: [    0.497768] usbcore: registered new device driver usb
Sep 18 08:23:00 node-1 kernel: [    0.497936] PCI: Using ACPI for IRQ routing
Sep 18 08:23:00 node-1 kernel: [    0.501543] PCI: pci_cache_line_size set to 64 bytes
Sep 18 08:23:00 node-1 kernel: [    0.501764] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 18 08:23:00 node-1 kernel: [    0.501765] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 18 08:23:00 node-1 kernel: [    0.501766] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 18 08:23:00 node-1 kernel: [    0.501832] NetLabel: Initializing
Sep 18 08:23:00 node-1 kernel: [    0.501833] NetLabel:  domain hash size = 128
Sep 18 08:23:00 node-1 kernel: [    0.501834] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 18 08:23:00 node-1 kernel: [    0.501844] NetLabel:  unlabeled traffic allowed by default
Sep 18 08:23:00 node-1 kernel: [    0.501902] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 18 08:23:00 node-1 kernel: [    0.501906] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 18 08:23:00 node-1 kernel: [    0.503964] Switched to clocksource hpet
Sep 18 08:23:00 node-1 kernel: [    0.507997] AppArmor: AppArmor Filesystem Enabled
Sep 18 08:23:00 node-1 kernel: [    0.508011] pnp: PnP ACPI init
Sep 18 08:23:00 node-1 kernel: [    0.508018] ACPI: bus type PNP registered
Sep 18 08:23:00 node-1 kernel: [    0.508127] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508135] pnp 00:01: [dma 4]
Sep 18 08:23:00 node-1 kernel: [    0.508146] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508173] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508192] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508210] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508243] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508294] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508296] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 18 08:23:00 node-1 kernel: [    0.508297] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508299] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508300] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508305] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508307] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 18 08:23:00 node-1 kernel: [    0.508308] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508310] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508311] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508313] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508314] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508316] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 18 08:23:00 node-1 kernel: [    0.508318] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508402] pnp 00:07: [dma 0 disabled]
Sep 18 08:23:00 node-1 kernel: [    0.508431] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508506] pnp 00:08: [dma 0 disabled]
Sep 18 08:23:00 node-1 kernel: [    0.508537] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508588] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 18 08:23:00 node-1 kernel: [    0.508938] pnp: PnP ACPI: found 10 devices
Sep 18 08:23:00 node-1 kernel: [    0.508940] ACPI: bus type PNP unregistered
Sep 18 08:23:00 node-1 kernel: [    0.515156] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 18 08:23:00 node-1 kernel: [    0.515159] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 18 08:23:00 node-1 kernel: [    0.515162] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 18 08:23:00 node-1 kernel: [    0.515166] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 18 08:23:00 node-1 kernel: [    0.515168] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515183] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515212] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 18 08:23:00 node-1 kernel: [    0.515226] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515259] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 18 08:23:00 node-1 kernel: [    0.515273] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 18 08:23:00 node-1 kernel: [    0.515302] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 18 08:23:00 node-1 kernel: [    0.515316] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 18 08:23:00 node-1 kernel: [    0.515345] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 18 08:23:00 node-1 kernel: [    0.515347] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515361] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515390] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 18 08:23:00 node-1 kernel: [    0.515392] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515406] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515435] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 18 08:23:00 node-1 kernel: [    0.515437] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515439] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515443] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 18 08:23:00 node-1 kernel: [    0.515445] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515447] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515451] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 18 08:23:00 node-1 kernel: [    0.515456] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 18 08:23:00 node-1 kernel: [    0.515464] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 18 08:23:00 node-1 kernel: [    0.515467] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 18 08:23:00 node-1 kernel: [    0.515473] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 18 08:23:00 node-1 kernel: [    0.515474] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 18 08:23:00 node-1 kernel: [    0.515475] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 18 08:23:00 node-1 kernel: [    0.515476] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 18 08:23:00 node-1 kernel: [    0.515477] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 18 08:23:00 node-1 kernel: [    0.515478] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 18 08:23:00 node-1 kernel: [    0.515479] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 18 08:23:00 node-1 kernel: [    0.515480] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 18 08:23:00 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 18 08:23:00 node-1 kernel: [    0.515481] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515482] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515482] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515483] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515484] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515485] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515486] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515487] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515488] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 18 08:23:00 node-1 kernel: [    0.515488] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515490] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 18 08:23:00 node-1 kernel: [    0.515491] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 18 08:23:00 node-1 kernel: [    0.515491] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 18 08:23:00 node-1 kernel: [    0.515493] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 18 08:23:00 node-1 kernel: [    0.515494] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 18 08:23:00 node-1 kernel: [    0.515495] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 18 08:23:00 node-1 kernel: [    0.515535] NET: Registered protocol family 2
Sep 18 08:23:00 node-1 kernel: [    0.515789] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.516127] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.516274] TCP: Hash tables configured (established 262144 bind 65536)
Sep 18 08:23:00 node-1 kernel: [    0.516316] TCP: reno registered
Sep 18 08:23:00 node-1 kernel: [    0.516345] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.516440] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.516590] NET: Registered protocol family 1
Sep 18 08:23:00 node-1 kernel: [    0.552067] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 18 08:23:00 node-1 kernel: [    0.552083] PCI: CLS 64 bytes, default 64
Sep 18 08:23:00 node-1 kernel: [    0.552159] Trying to unpack rootfs image as initramfs...
Sep 18 08:23:00 node-1 kernel: [    0.772221] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Sep 18 08:23:00 node-1 kernel: [    0.772261] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 18 08:23:00 node-1 kernel: [    0.772264] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 18 08:23:00 node-1 kernel: [    0.772665] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772671] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772676] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772682] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772691] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772702] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772711] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772720] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772728] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772738] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772744] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772750] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772757] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772765] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772773] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772780] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 08:23:00 node-1 kernel: [    0.772858] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 18 08:23:00 node-1 kernel: [    0.772860] Scanning for low memory corruption every 60 seconds
Sep 18 08:23:00 node-1 kernel: [    0.773263] Initialise system trusted keyring
Sep 18 08:23:00 node-1 kernel: [    0.773317] audit: initializing netlink socket (disabled)
Sep 18 08:23:00 node-1 kernel: [    0.773333] type=2000 audit(1474186943.728:1): initialized
Sep 18 08:23:00 node-1 kernel: [    0.791208] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 18 08:23:00 node-1 kernel: [    0.792734] zbud: loaded
Sep 18 08:23:00 node-1 kernel: [    0.792861] VFS: Disk quotas dquot_6.5.2
Sep 18 08:23:00 node-1 kernel: [    0.792898] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 18 08:23:00 node-1 kernel: [    0.793270] fuse init (API version 7.22)
Sep 18 08:23:00 node-1 kernel: [    0.793326] msgmni has been set to 32768
Sep 18 08:23:00 node-1 kernel: [    0.793378] Key type big_key registered
Sep 18 08:23:00 node-1 kernel: [    0.793886] Key type asymmetric registered
Sep 18 08:23:00 node-1 kernel: [    0.793888] Asymmetric key parser 'x509' registered
Sep 18 08:23:00 node-1 kernel: [    0.793910] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 18 08:23:00 node-1 kernel: [    0.793975] io scheduler noop registered
Sep 18 08:23:00 node-1 kernel: [    0.793977] io scheduler deadline registered (default)
Sep 18 08:23:00 node-1 kernel: [    0.793994] io scheduler cfq registered
Sep 18 08:23:00 node-1 kernel: [    0.794506] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    0.794661] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    0.794779] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    0.794891] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    0.795007] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    0.795101] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    0.795517] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 18 08:23:00 node-1 kernel: [    0.795558] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 18 08:23:00 node-1 kernel: [    0.795574] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 18 08:23:00 node-1 kernel: [    0.795587] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795589] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795592] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 18 08:23:00 node-1 kernel: [    0.795597] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795598] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795600] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795601] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795603] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795605] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795606] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795607] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795609] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795610] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795612] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795613] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795615] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 18 08:23:00 node-1 kernel: [    0.795620] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795623] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 18 08:23:00 node-1 kernel: [    0.795634] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795637] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 18 08:23:00 node-1 kernel: [    0.795648] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795649] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 18 08:23:00 node-1 kernel: [    0.795652] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 18 08:23:00 node-1 kernel: [    0.795705] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 18 08:23:00 node-1 kernel: [    0.795718] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 18 08:23:00 node-1 kernel: [    0.795722] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 18 08:23:00 node-1 kernel: [    0.795740] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 18 08:23:00 node-1 kernel: [    0.795781] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 18 08:23:00 node-1 kernel: [    0.795783] vesafb: scrolling: redraw
Sep 18 08:23:00 node-1 kernel: [    0.795784] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 18 08:23:00 node-1 kernel: [    0.816398] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 18 08:23:00 node-1 kernel: [    0.824906] Console: switching to colour frame buffer device 80x30
Sep 18 08:23:00 node-1 kernel: [    0.833577] fb0: VESA VGA frame buffer device
Sep 18 08:23:00 node-1 kernel: [    0.833778] intel_idle: MWAIT substates: 0x2120
Sep 18 08:23:00 node-1 kernel: [    0.833779] intel_idle: v0.4 model 0x3F
Sep 18 08:23:00 node-1 kernel: [    0.833779] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 18 08:23:00 node-1 kernel: [    0.834030] ipmi message handler version 39.2
Sep 18 08:23:00 node-1 kernel: [    0.834297] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 18 08:23:00 node-1 kernel: [    0.834731] ACPI: AC Adapter [P111] (on-line)
Sep 18 08:23:00 node-1 kernel: [    0.839968] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 18 08:23:00 node-1 kernel: [    0.851136] ACPI: Power Button [PWRB]
Sep 18 08:23:00 node-1 kernel: [    0.856988] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 18 08:23:00 node-1 kernel: [    0.868722] ACPI: Power Button [PWRF]
Sep 18 08:23:00 node-1 kernel: [    0.885477] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 18 08:23:00 node-1 kernel: [    0.897128] pstore: Registered erst as persistent store backend
Sep 18 08:23:00 node-1 kernel: [    0.903322] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 18 08:23:00 node-1 kernel: [    0.915268] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 18 08:23:00 node-1 kernel: [    0.942016] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 18 08:23:00 node-1 kernel: [    0.975300] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 18 08:23:00 node-1 kernel: [    0.989373] Linux agpgart interface v0.103
Sep 18 08:23:00 node-1 kernel: [    0.997059] brd: module loaded
Sep 18 08:23:00 node-1 kernel: [    1.004129] loop: module loaded
Sep 18 08:23:00 node-1 kernel: [    1.010860] libphy: Fixed MDIO Bus: probed
Sep 18 08:23:00 node-1 kernel: [    1.017339] tun: Universal TUN/TAP device driver, 1.6
Sep 18 08:23:00 node-1 kernel: [    1.023823] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 18 08:23:00 node-1 kernel: [    1.030374] PPP generic driver version 2.4.2
Sep 18 08:23:00 node-1 kernel: [    1.036785] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 18 08:23:00 node-1 kernel: [    1.043239] ehci-pci: EHCI PCI platform driver
Sep 18 08:23:00 node-1 kernel: [    1.049765] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 18 08:23:00 node-1 kernel: [    1.056170] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 18 08:23:00 node-1 kernel: [    1.068888] ehci-pci 0000:00:1a.0: debug port 2
Sep 18 08:23:00 node-1 kernel: [    1.079185] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 18 08:23:00 node-1 kernel: [    1.079204] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 18 08:23:00 node-1 kernel: [    1.095466] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 18 08:23:00 node-1 kernel: [    1.101659] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 18 08:23:00 node-1 kernel: [    1.107935] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 18 08:23:00 node-1 kernel: [    1.120053] usb usb1: Product: EHCI Host Controller
Sep 18 08:23:00 node-1 kernel: [    1.126177] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 18 08:23:00 node-1 kernel: [    1.132313] usb usb1: SerialNumber: 0000:00:1a.0
Sep 18 08:23:00 node-1 kernel: [    1.138300] hub 1-0:1.0: USB hub found
Sep 18 08:23:00 node-1 kernel: [    1.144077] hub 1-0:1.0: 2 ports detected
Sep 18 08:23:00 node-1 kernel: [    1.149876] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 18 08:23:00 node-1 kernel: [    1.155470] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 18 08:23:00 node-1 kernel: [    1.166378] ehci-pci 0000:00:1d.0: debug port 2
Sep 18 08:23:00 node-1 kernel: [    1.175690] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 18 08:23:00 node-1 kernel: [    1.175696] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 18 08:23:00 node-1 kernel: [    1.191385] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 18 08:23:00 node-1 kernel: [    1.196628] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 18 08:23:00 node-1 kernel: [    1.201948] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 18 08:23:00 node-1 kernel: [    1.212586] usb usb2: Product: EHCI Host Controller
Sep 18 08:23:00 node-1 kernel: [    1.218079] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 18 08:23:00 node-1 kernel: [    1.223673] usb usb2: SerialNumber: 0000:00:1d.0
Sep 18 08:23:00 node-1 kernel: [    1.229283] hub 2-0:1.0: USB hub found
Sep 18 08:23:00 node-1 kernel: [    1.234713] hub 2-0:1.0: 2 ports detected
Sep 18 08:23:00 node-1 kernel: [    1.240060] ehci-platform: EHCI generic platform driver
Sep 18 08:23:00 node-1 kernel: [    1.245305] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 18 08:23:00 node-1 kernel: [    1.250647] ohci-pci: OHCI PCI platform driver
Sep 18 08:23:00 node-1 kernel: [    1.255966] ohci-platform: OHCI generic platform driver
Sep 18 08:23:00 node-1 kernel: [    1.261189] uhci_hcd: USB Universal Host Controller Interface driver
Sep 18 08:23:00 node-1 kernel: [    1.266545] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 18 08:23:00 node-1 kernel: [    1.459164] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 18 08:23:00 node-1 kernel: [    1.631348] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 18 08:23:00 node-1 kernel: [    1.636918] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 18 08:23:00 node-1 kernel: [    1.642741] hub 1-1:1.0: USB hub found
Sep 18 08:23:00 node-1 kernel: [    1.648211] hub 1-1:1.0: 6 ports detected
Sep 18 08:23:00 node-1 kernel: [    1.762900] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 18 08:23:00 node-1 kernel: [    1.770940] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 18 08:23:00 node-1 kernel: [    2.031010] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 18 08:23:00 node-1 kernel: [    2.036533] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 18 08:23:00 node-1 kernel: [    2.042403] hub 2-1:1.0: USB hub found
Sep 18 08:23:00 node-1 kernel: [    2.047998] hub 2-1:1.0: 8 ports detected
Sep 18 08:23:00 node-1 kernel: [    2.307979] i8042: No controller found
Sep 18 08:23:00 node-1 kernel: [    2.313401] mousedev: PS/2 mouse device common for all mice
Sep 18 08:23:00 node-1 kernel: [    2.318910] rtc_cmos 00:02: RTC can wake from S4
Sep 18 08:23:00 node-1 kernel: [    2.324510] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 18 08:23:00 node-1 kernel: [    2.326488] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 18 08:23:00 node-1 kernel: [    2.335659] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 18 08:23:00 node-1 kernel: [    2.346860] device-mapper: uevent: version 1.0.3
Sep 18 08:23:00 node-1 kernel: [    2.352559] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 18 08:23:00 node-1 kernel: [    2.363859] ledtrig-cpu: registered to indicate activity on CPUs
Sep 18 08:23:00 node-1 kernel: [    2.369788] TCP: cubic registered
Sep 18 08:23:00 node-1 kernel: [    2.375666] NET: Registered protocol family 10
Sep 18 08:23:00 node-1 kernel: [    2.381631] NET: Registered protocol family 17
Sep 18 08:23:00 node-1 kernel: [    2.387296] Key type dns_resolver registered
Sep 18 08:23:00 node-1 kernel: [    2.393222] Loading compiled-in X.509 certificates
Sep 18 08:23:00 node-1 kernel: [    2.399375] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 18 08:23:00 node-1 kernel: [    2.410713] registered taskstats version 1
Sep 18 08:23:00 node-1 kernel: [    2.418627] Key type trusted registered
Sep 18 08:23:00 node-1 kernel: [    2.426140] Key type encrypted registered
Sep 18 08:23:00 node-1 kernel: [    2.431566] AppArmor: AppArmor sha1 policy hashing enabled
Sep 18 08:23:00 node-1 kernel: [    2.437031] IMA: No TPM chip found, activating TPM-bypass!
Sep 18 08:23:00 node-1 kernel: [    2.443160] regulator-dummy: disabling
Sep 18 08:23:00 node-1 kernel: [    2.448705]   Magic number: 0:42:372
Sep 18 08:23:00 node-1 kernel: [    2.454120] pcieport 0000:02:00.0: hash matches
Sep 18 08:23:00 node-1 kernel: [    2.459668] rtc_cmos 00:02: setting system clock to 2016-09-18 08:22:26 UTC (1474186946)
Sep 18 08:23:00 node-1 kernel: [    2.467656] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 18 08:23:00 node-1 kernel: [    2.467659] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 18 08:23:00 node-1 kernel: [    2.467661] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 18 08:23:00 node-1 kernel: [    2.467662] usb 2-1.4: Manufacturer: Avocent
Sep 18 08:23:00 node-1 kernel: [    2.467664] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 18 08:23:00 node-1 kernel: [    2.506197] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 18 08:23:00 node-1 kernel: [    2.511862] EDD information not available.
Sep 18 08:23:00 node-1 kernel: [    2.517413] PM: Hibernation image not present or could not be loaded.
Sep 18 08:23:00 node-1 kernel: [    2.518274] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 18 08:23:00 node-1 kernel: [    2.529510] Write protecting the kernel read-only data: 12288k
Sep 18 08:23:00 node-1 kernel: [    2.535699] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 18 08:23:00 node-1 kernel: [    2.548065] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 18 08:23:00 node-1 kernel: [    2.579306] device-mapper: multipath: version 1.6.0 loaded
Sep 18 08:23:00 node-1 kernel: [    2.587308] systemd-udevd[215]: starting version 204
Sep 18 08:23:00 node-1 kernel: [    2.612394] md: linear personality registered for level -1
Sep 18 08:23:00 node-1 kernel: [    2.626343] md: multipath personality registered for level -4
Sep 18 08:23:00 node-1 kernel: [    2.634262] md: raid0 personality registered for level 0
Sep 18 08:23:00 node-1 kernel: [    2.642639] md: raid1 personality registered for level 1
Sep 18 08:23:00 node-1 kernel: [    2.648996] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 18 08:23:00 node-1 kernel: [    2.655343] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 18 08:23:00 node-1 kernel: [    2.661733] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 18 08:23:00 node-1 kernel: [    2.663315] megasas: FW now in Ready state
Sep 18 08:23:00 node-1 kernel: [    2.663639] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.663730] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.663875] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.663983] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.664091] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.664240] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.664390] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.664529] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.664667] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.664802] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.664930] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.665053] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.665225] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.665356] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.665453] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.665586] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.666442] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 18 08:23:00 node-1 kernel: [    2.687392] hidraw: raw HID events driver (C) Jiri Kosina
Sep 18 08:23:00 node-1 kernel: [    2.695741] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 18 08:23:00 node-1 kernel: [    2.708678] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 08:23:00 node-1 kernel: [    2.722032] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 08:23:00 node-1 kernel: [    2.726513] raid6: sse2x1    1973 MB/s
Sep 18 08:23:00 node-1 kernel: [    2.735852] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.735859] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.735864] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.735869] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.735916] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 08:23:00 node-1 kernel: [    2.743498] usbcore: registered new interface driver usbhid
Sep 18 08:23:00 node-1 kernel: [    2.743499] usbhid: USB HID core driver
Sep 18 08:23:00 node-1 kernel: [    2.764530] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 18 08:23:00 node-1 kernel: [    2.773209] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 18 08:23:00 node-1 kernel: [    2.773211] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 08:23:00 node-1 kernel: [    2.773212] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 18 08:23:00 node-1 kernel: [    2.794325] raid6: sse2x2    5377 MB/s
Sep 18 08:23:00 node-1 kernel: [    2.861982] raid6: sse2x4    9891 MB/s
Sep 18 08:23:00 node-1 kernel: [    2.933922] raid6: avx2x1   14948 MB/s
Sep 18 08:23:00 node-1 kernel: [    3.005858] raid6: avx2x2   18882 MB/s
Sep 18 08:23:00 node-1 kernel: [    3.077792] raid6: avx2x4   21409 MB/s
Sep 18 08:23:00 node-1 kernel: [    3.084220] raid6: using algorithm avx2x4 (21409 MB/s)
Sep 18 08:23:00 node-1 kernel: [    3.090650] raid6: using avx2x2 recovery algorithm
Sep 18 08:23:00 node-1 kernel: [    3.097009] megasas:IOC Init cmd success
Sep 18 08:23:00 node-1 kernel: [    3.097012] Switched to clocksource tsc
Sep 18 08:23:00 node-1 kernel: [    3.097087] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 18 08:23:00 node-1 kernel: [    3.097165] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 18 08:23:00 node-1 kernel: [    3.097170] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.097184] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.097222] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 18 08:23:00 node-1 kernel: [    3.097254] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.097278] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 18 08:23:00 node-1 kernel: [    3.097338] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 18 08:23:00 node-1 kernel: [    3.097362] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.097447] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.097641] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.098343] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.116763] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 18 08:23:00 node-1 kernel: [    3.116765] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 08:23:00 node-1 kernel: [    3.116766] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 08:23:00 node-1 kernel: [    3.117016] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.117103] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.117203] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.117328] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.117480] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.131061] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 18 08:23:00 node-1 kernel: [    3.131062] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 08:23:00 node-1 kernel: [    3.131091] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 08:23:00 node-1 kernel: [    3.131461] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.131588] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.131747] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.131870] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.132218] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 08:23:00 node-1 kernel: [    3.281513] xor: automatically using best checksumming function:
Sep 18 08:23:00 node-1 kernel: [    3.301595] megasas: INIT adapter done
Sep 18 08:23:00 node-1 kernel: [    3.325563]    avx       : 35724.000 MB/sec
Sep 18 08:23:00 node-1 kernel: [    3.333498] async_tx: api initialized (async)
Sep 18 08:23:00 node-1 kernel: [    3.344460] md: raid6 personality registered for level 6
Sep 18 08:23:00 node-1 kernel: [    3.351655] md: raid5 personality registered for level 5
Sep 18 08:23:00 node-1 kernel: [    3.358604] md: raid4 personality registered for level 4
Sep 18 08:23:00 node-1 kernel: [    3.368246] md: raid10 personality registered for level 10
Sep 18 08:23:00 node-1 kernel: [    3.377528] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 18 08:23:00 node-1 kernel: [    3.377881] scsi0 : LSI SAS based MegaRAID driver
Sep 18 08:23:00 node-1 kernel: [    3.384868] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 18 08:23:00 node-1 kernel: [    3.395654] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 18 08:23:00 node-1 kernel: [    3.399772] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 18 08:23:00 node-1 kernel: [    3.399977] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 18 08:23:00 node-1 kernel: [    3.400448] sd 0:2:0:0: [sda] Write Protect is off
Sep 18 08:23:00 node-1 kernel: [    3.400449] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 18 08:23:00 node-1 kernel: [    3.400500] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 18 08:23:00 node-1 kernel: [    3.430239]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 18 08:23:00 node-1 kernel: [    3.431774] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 18 08:23:00 node-1 kernel: [    3.504821] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Sep 18 08:23:00 node-1 kernel: [    3.624449] random: lvm urandom read with 27 bits of entropy available
Sep 18 08:23:00 node-1 kernel: [    3.760730] bio: create slab <bio-1> at 1
Sep 18 08:23:00 node-1 kernel: [    4.474382] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 08:23:00 node-1 kernel: [    5.039712] init: plymouth-upstart-bridge main process (548) terminated with status 1
Sep 18 08:23:00 node-1 kernel: [    5.052762] init: plymouth-upstart-bridge main process ended, respawning
Sep 18 08:23:00 node-1 kernel: [    5.197349] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 18 08:23:00 node-1 kernel: [    5.226073] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 18 08:23:00 node-1 kernel: [    5.305949] random: nonblocking pool is initialized
Sep 18 08:23:00 node-1 kernel: [    5.345054] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 18 08:23:00 node-1 kernel: [    5.386987] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 18 08:23:00 node-1 kernel: [    5.510949] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 08:23:00 node-1 kernel: [    5.719639] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 18 08:23:00 node-1 kernel: [    5.761358] XFS (dm-0): Mounting Filesystem
Sep 18 08:23:00 node-1 kernel: [    5.993278] XFS (dm-0): Ending clean mount
Sep 18 08:23:00 node-1 kernel: [    6.083516] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 08:23:00 node-1 kernel: [    6.111354] XFS (dm-1): Mounting Filesystem
Sep 18 08:23:00 node-1 kernel: [    6.200555] XFS (dm-1): Ending clean mount
Sep 18 08:23:00 node-1 kernel: [    8.161835] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 18 08:23:00 node-1 kernel: [    8.175772] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 18 08:23:00 node-1 kernel: [    8.329825] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 18 08:23:00 node-1 kernel: [    8.329831] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 18 08:23:00 node-1 kernel: [    8.329836] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 18 08:23:00 node-1 kernel: [    8.329840] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 18 08:23:00 node-1 kernel: [    8.361409] systemd-udevd[773]: starting version 204
Sep 18 08:23:00 node-1 kernel: [    8.516257] power_meter ACPI000D:00: Found ACPI power meter.
Sep 18 08:23:00 node-1 kernel: [    8.516266] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 18 08:23:00 node-1 kernel: [    8.535636] wmi: Mapper loaded
Sep 18 08:23:00 node-1 kernel: [    8.571577] IPMI System Interface driver.
Sep 18 08:23:00 node-1 kernel: [    8.571614] ipmi_si: probing via ACPI
Sep 18 08:23:00 node-1 kernel: [    8.571626] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 18 08:23:00 node-1 kernel: [    8.571627] ipmi_si: Adding ACPI-specified kcs state machine
Sep 18 08:23:00 node-1 kernel: [    8.571635] ipmi_si: probing via SMBIOS
Sep 18 08:23:00 node-1 kernel: [    8.571636] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 18 08:23:00 node-1 kernel: [    8.571636] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 18 08:23:00 node-1 kernel: [    8.571638] ipmi_si: probing via SPMI
Sep 18 08:23:00 node-1 kernel: [    8.571639] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 18 08:23:00 node-1 kernel: [    8.571639] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 18 08:23:00 node-1 kernel: [    8.571641] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 18 08:23:00 node-1 kernel: [    8.572822] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 18 08:23:00 node-1 kernel: [    8.572826] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 18 08:23:00 node-1 kernel: [    8.572828] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 18 08:23:00 node-1 kernel: [    8.572829] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 18 08:23:00 node-1 kernel: [    8.572842] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 18 08:23:00 node-1 kernel: [    8.575201] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 18 08:23:00 node-1 kernel: [    8.657547] systemd-udevd[791]: renamed network interface eth2 to enp8s0
Sep 18 08:23:00 node-1 kernel: [    8.681405] systemd-udevd[790]: renamed network interface eth1 to enp7s0
Sep 18 08:23:00 node-1 kernel: [    8.709395] systemd-udevd[802]: renamed network interface eth0 to enp6s0
Sep 18 08:23:00 node-1 kernel: [    8.709459] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 18 08:23:00 node-1 kernel: [    8.709465] ipmi_si 00:09: IPMI kcs interface initialized
Sep 18 08:23:00 node-1 kernel: [    8.741350] systemd-udevd[792]: renamed network interface eth3 to enp9s0
Sep 18 08:23:00 node-1 kernel: [    9.101172] type=1400 audit(1474186953.143:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1039 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.101339] type=1400 audit(1474186953.143:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1039 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.101474] type=1400 audit(1474186953.143:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1039 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.102855] type=1400 audit(1474186953.143:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1040 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.103007] type=1400 audit(1474186953.143:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1040 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.103131] type=1400 audit(1474186953.143:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1040 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.126293] type=1400 audit(1474186953.167:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1038 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.126445] type=1400 audit(1474186953.167:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1038 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.126564] type=1400 audit(1474186953.167:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1038 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.131392] type=1400 audit(1474186953.171:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1035 comm="apparmor_parser"
Sep 18 08:23:00 node-1 kernel: [    9.669414] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 18 08:23:00 node-1 kernel: [    9.670400] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 18 08:23:00 node-1 kernel: [    9.891592] enic 0000:06:00.0 enp6s0: Link UP
Sep 18 08:23:00 node-1 kernel: [    9.892043] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 18 08:23:00 node-1 kernel: [    9.892059] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 18 08:23:00 node-1 kernel: [   20.024098] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 18 08:23:02 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 18 08:23:02 node-1 kernel: [   38.515902] init: failsafe main process (8412) killed by TERM signal
Sep 18 08:23:02 node-1 dbus[8451]: [system] AppArmor D-Bus mediation is enabled
Sep 18 08:23:02 node-1 kernel: [   38.816800] audit_printk_skb: 30 callbacks suppressed
Sep 18 08:23:02 node-1 kernel: [   38.816802] type=1400 audit(1474186982.346:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8538 comm="apparmor_parser"
Sep 18 08:23:02 node-1 kernel: [   38.817073] type=1400 audit(1474186982.346:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8537 comm="apparmor_parser"
Sep 18 08:23:02 node-1 kernel: [   38.817078] type=1400 audit(1474186982.346:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Sep 18 08:23:02 node-1 kernel: [   38.817081] type=1400 audit(1474186982.346:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Sep 18 08:23:02 node-1 kernel: [   38.817304] type=1400 audit(1474186982.346:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Sep 18 08:23:02 node-1 kernel: [   38.817306] type=1400 audit(1474186982.346:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Sep 18 08:23:02 node-1 kernel: [   38.817422] type=1400 audit(1474186982.346:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Sep 18 08:23:02 node-1 kernel: [   38.904161] type=1400 audit(1474186982.434:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8540 comm="apparmor_parser"
Sep 18 08:23:02 node-1 cron[8570]: (CRON) INFO (pidfile fd = 3)
Sep 18 08:23:02 node-1 anacron[8605]: Anacron 2.3 started on 2016-09-18
Sep 18 08:23:02 node-1 cron[8608]: (CRON) STARTUP (fork ok)
Sep 18 08:23:02 node-1 anacron[8605]: Will run job `cron.daily' in 5 min.
Sep 18 08:23:02 node-1 anacron[8605]: Will run job `cron.weekly' in 10 min.
Sep 18 08:23:02 node-1 anacron[8605]: Will run job `cron.monthly' in 15 min.
Sep 18 08:23:02 node-1 anacron[8605]: Jobs will be executed sequentially
Sep 18 08:23:02 node-1 cron[8608]: (CRON) INFO (Running @reboot jobs)
Sep 18 08:23:02 node-1 multipathd: path checkers start up
Sep 18 08:23:03 node-1 postfix/master[8749]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 18 08:23:05 node-1 puppet-agent[8934]: Reopening log files
Sep 18 08:23:06 node-1 puppet-agent[8934]: Could not request certificate: Connection refused - connect(2)
Sep 18 08:23:18 node-1 puppet-user[9142]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 18 08:23:18 node-1 puppet-user[9142]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 18 08:23:19 node-1 puppet-user[9142]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 18 08:23:19 node-1 puppet-user[9142]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 18 08:23:19 node-1 puppet-user[9142]: Finished catalog run in 1.05 seconds
Sep 18 08:23:21 node-1 multipathd: uevent trigger error
Sep 18 08:23:21 node-1 puppet-user[9572]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 18 08:23:21 node-1 puppet-user[9572]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 18 08:23:21 node-1 puppet-user[9572]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 18 08:23:21 node-1 puppet-user[9572]: Finished catalog run in 0.07 seconds
Sep 18 08:23:22 node-1 puppet-user[10024]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 18 08:23:22 node-1 puppet-user[10024]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 18 08:23:22 node-1 puppet-user[10024]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 18 08:23:22 node-1 puppet-user[10024]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 18 08:23:22 node-1 puppet-user[10024]: Finished catalog run in 0.04 seconds
Sep 18 08:23:24 node-1 puppet-user[10662]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 18 08:23:24 node-1 puppet-user[10662]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 18 08:23:24 node-1 puppet-user[10662]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 18 08:23:24 node-1 puppet-user[10662]: Finished catalog run in 0.04 seconds
Sep 18 08:23:25 node-1 puppet-user[11108]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 18 08:23:25 node-1 puppet-user[11108]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 18 08:23:25 node-1 puppet-user[11108]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 18 08:23:26 node-1 puppet-user[11108]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep 18 08:23:26 node-1 puppet-user[11108]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 18 08:23:26 node-1 puppet-user[11108]: Finished catalog run in 0.78 seconds
Sep 18 08:23:27 node-1 puppet-user[11615]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 18 08:23:27 node-1 puppet-user[11615]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Sep 18 08:23:28 node-1 puppet-user[11615]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep 18 08:23:28 node-1 puppet-user[11615]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 18 08:23:28 node-1 puppet-user[11615]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 18 08:23:28 node-1 puppet-user[11615]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 18 08:23:28 node-1 puppet-user[11615]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 18 08:23:28 node-1 puppet-user[11615]: Finished catalog run in 0.32 seconds
Sep 18 08:23:29 node-1 puppet-user[12097]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 18 08:23:29 node-1 puppet-user[12097]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Sep 18 08:23:29 node-1 puppet-user[12097]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 18 08:23:29 node-1 kernel: [   66.108859] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 18 08:23:29 node-1 kernel: [   66.108910] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 18 08:23:29 node-1 puppet-user[12097]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 18 08:23:29 node-1 puppet-user[12097]: Finished catalog run in 0.06 seconds
Sep 18 08:23:31 node-1 puppet-user[12569]: (Scope(Class[main])) MODULAR: sync_time
Sep 18 08:23:31 node-1 puppet-user[12569]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 18 08:23:32 node-1 ntpdate[12980]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 18 08:23:34 node-1 kernel: [   70.623636] init: plymouth-upstart-bridge main process ended, respawning
Sep 18 08:23:34 node-1 puppet-agent[8934]: Could not run: SIGTERM
Sep 18 08:23:34 node-1 kernel: [   70.876777] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 18 08:23:34 node-1 ec2: 
Sep 18 08:23:34 node-1 ec2: #############################################################
Sep 18 08:23:34 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 18 08:23:34 node-1 ec2: 1024 32:57:e8:e7:7e:5b:1d:75:e5:c5:75:4b:bf:9c:74:7b  root@node-1.domain.tld (DSA)
Sep 18 08:23:34 node-1 ec2: 256 c2:c3:db:a6:13:71:e3:60:f8:99:ee:dc:5b:79:97:78  root@node-1.domain.tld (ECDSA)
Sep 18 08:23:34 node-1 ec2: 256 bc:68:94:da:bd:c1:1e:8e:8a:9d:13:63:c8:5a:e6:17  root@node-1.domain.tld (ED25519)
Sep 18 08:23:34 node-1 ec2: 2048 fe:f0:b3:4a:bb:92:55:02:8b:e1:97:f2:0c:9f:b5:e2  root@node-1.domain.tld (RSA)
Sep 18 08:23:34 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 18 08:23:34 node-1 ec2: #############################################################
Sep 18 08:23:38 node-1 ntpdate[12980]: adjust time server 10.20.0.2 offset 0.000491 sec
Sep 18 08:23:38 node-1 puppet-user[12569]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 18 08:23:38 node-1 puppet-user[12569]: Finished catalog run in 6.17 seconds
Sep 18 08:23:44 node-1 puppet-user[13347]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 18 08:23:44 node-1 puppet-user[13347]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Sep 18 08:23:44 node-1 puppet-user[13347]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 18 08:23:44 node-1 puppet-user[13347]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep 18 08:23:44 node-1 puppet-user[13347]: Finished catalog run in 0.08 seconds
Sep 18 08:23:45 node-1 puppet-user[13805]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 18 08:23:46 node-1 puppet-user[13805]: Compiled catalog for node-1.domain.tld in environment production in 0.47 seconds
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 18 08:23:46 node-1 puppet-user[13805]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 18 08:23:47 node-1 puppet-user[13805]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 18 08:23:47 node-1 puppet-user[13805]: Finished catalog run in 0.86 seconds
Sep 18 08:23:49 node-1 puppet-user[14315]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 18 08:23:49 node-1 puppet-user[14315]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Sep 18 08:23:52 node-1 puppet-user[14315]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 18 08:24:01 node-1 CRON[15807]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 18 08:24:04 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 18 08:24:04 node-1 nailgun-agent: I, [2016-09-18T08:24:04.103647 #15810]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 18 08:24:17 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 18 08:24:17 node-1 nailgun-agent: I, [2016-09-18T08:24:17.197417 #15810]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 18 08:24:17 node-1 puppet-user[14315]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 18 08:24:17 node-1 puppet-user[14315]: Finished catalog run in 28.36 seconds
Sep 18 08:24:19 node-1 puppet-user[17021]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 18 08:24:20 node-1 puppet-user[17021]: Compiled catalog for node-1.domain.tld in environment production in 0.61 seconds
Sep 18 08:24:20 node-1 puppet-user[17021]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 18 08:24:20 node-1 puppet-user[17021]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 18 08:24:20 node-1 puppet-user[17021]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 18 08:24:20 node-1 puppet-user[17021]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 18 08:24:20 node-1 puppet-user[17021]: Finished catalog run in 0.09 seconds
Sep 18 08:24:22 node-1 puppet-user[17479]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 18 08:24:23 node-1 puppet-user[17479]: Compiled catalog for node-1.domain.tld in environment production in 0.89 seconds
Sep 18 08:24:23 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 18 08:24:23 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 18 08:24:23 node-1 crontab[17916]: (root) LIST (root)
Sep 18 08:24:23 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 18 08:24:23 node-1 crontab[17917]: (root) REPLACE (root)
Sep 18 08:24:24 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 18 08:24:25 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 18 08:24:26 node-1 puppet-user[17479]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 18 08:24: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 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 08:24:26 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 18 08:24:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:24:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:25:40 node-1 ntpdate[28929]: no servers can be used, exiting
<27>Sep 18 08:26:12 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:12 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:12 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:12 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:12 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:12 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:15 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:15 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:15 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:15 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:15 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:26:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:34 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 08:27:34 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 08:27:40 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 08:27:40 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 08:27:46 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 08:27:51 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 08:27:51 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 08:27:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:27:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:00 node-1 ntpdate[14068]: the NTP socket is in use, exiting
<27>Sep 18 08:28:00 node-1 ntpdate[14120]: the NTP socket is in use, exiting
<27>Sep 18 08:28:00 node-1 ntpdate[14173]: the NTP socket is in use, exiting
<27>Sep 18 08:28:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:28:45 node-1 multipathd: uevent trigger error
<129>Sep 18 08:28:48 node-1 haproxy[23238]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 48ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 08:28:48 node-1 haproxy[23238]: proxy odl-neutron-endpoint has no server available!
<129>Sep 18 08:28:49 node-1 haproxy[23244]: Server odl-jetty/node-1 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 18 08:28:49 node-1 haproxy[23244]: proxy odl-jetty has no server available!
<27>Sep 18 08:29:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:11 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:14 node-1 haproxy[25724]: 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 18 08:29:14 node-1 haproxy[25724]: 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 18 08:29:14 node-1 haproxy[25724]: 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 18 08:29:14 node-1 haproxy[25724]: proxy mysqld has no server available!
<27>Sep 18 08:29:17 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:17 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:17 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:17 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:17 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:20 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:23 node-1 haproxy[28452]: 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 18 08:29:23 node-1 haproxy[28452]: 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 18 08:29:23 node-1 haproxy[28452]: 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 18 08:29:23 node-1 haproxy[28452]: proxy mysqld has no server available!
<129>Sep 18 08:29:24 node-1 haproxy[28459]: 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 18 08:29:24 node-1 haproxy[28459]: 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 18 08:29:24 node-1 haproxy[28459]: 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 18 08:29:24 node-1 haproxy[28459]: proxy object-storage has no server available!
<27>Sep 18 08:29:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:26 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:26 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:28 node-1 haproxy[29827]: 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 18 08:29:29 node-1 haproxy[29836]: 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 18 08:29:29 node-1 haproxy[29836]: 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 18 08:29:29 node-1 haproxy[29836]: proxy neutron has no server available!
<129>Sep 18 08:29:29 node-1 haproxy[29836]: 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 18 08:29:29 node-1 haproxy[29836]: 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 18 08:29:29 node-1 haproxy[29836]: 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 18 08:29:29 node-1 haproxy[29836]: proxy mysqld has no server available!
<129>Sep 18 08:29:30 node-1 haproxy[29836]: 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 18 08:29:30 node-1 haproxy[29836]: 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 18 08:29:30 node-1 haproxy[29836]: 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 18 08:29:30 node-1 haproxy[29836]: proxy object-storage has no server available!
<27>Sep 18 08:29:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:32 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:34 node-1 haproxy[31221]: 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 18 08:29:34 node-1 haproxy[31221]: 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 18 08:29:34 node-1 haproxy[31221]: 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 18 08:29:34 node-1 haproxy[31221]: proxy keystone-1 has no server available!
<129>Sep 18 08:29:34 node-1 haproxy[31221]: 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 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: proxy keystone-2 has no server available!
<129>Sep 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: proxy neutron has no server available!
<129>Sep 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: 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 18 08:29:35 node-1 haproxy[31232]: proxy mysqld has no server available!
<129>Sep 18 08:29:36 node-1 haproxy[31232]: 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 18 08:29:36 node-1 haproxy[31232]: 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 18 08:29:36 node-1 haproxy[31232]: 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 18 08:29:36 node-1 haproxy[31232]: proxy object-storage has no server available!
<27>Sep 18 08:29:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:37 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: proxy keystone-1 has no server available!
<129>Sep 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: proxy keystone-2 has no server available!
<129>Sep 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:40 node-1 haproxy[32553]: proxy neutron has no server available!
<129>Sep 18 08:29:40 node-1 haproxy[32553]: 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 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: proxy mysqld has no server available!
<129>Sep 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: proxy object-storage has no server available!
<129>Sep 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: 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 18 08:29:41 node-1 haproxy[32557]: proxy aodh has no server available!
<27>Sep 18 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:43 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:43 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:45 node-1 haproxy[1506]: 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 18 08:29:45 node-1 haproxy[1506]: 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 18 08:29:45 node-1 haproxy[1506]: 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 18 08:29:45 node-1 haproxy[1506]: proxy keystone-1 has no server available!
<129>Sep 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: proxy keystone-2 has no server available!
<129>Sep 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: proxy neutron has no server available!
<129>Sep 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: proxy mysqld has no server available!
<129>Sep 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:46 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: proxy object-storage has no server available!
<129>Sep 18 08:29:47 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: proxy aodh has no server available!
<129>Sep 18 08:29:47 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: 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 18 08:29:47 node-1 haproxy[1510]: proxy ceilometer has no server available!
<27>Sep 18 08:29:48 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:48 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:48 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:48 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: proxy keystone-1 has no server available!
<129>Sep 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: proxy keystone-2 has no server available!
<129>Sep 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:51 node-1 haproxy[2810]: proxy neutron has no server available!
<129>Sep 18 08:29:51 node-1 haproxy[2810]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: proxy mysqld has no server available!
<129>Sep 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: proxy object-storage has no server available!
<129>Sep 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: proxy aodh has no server available!
<129>Sep 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: 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 18 08:29:52 node-1 haproxy[2814]: proxy ceilometer has no server available!
<27>Sep 18 08:29:54 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:54 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:54 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:54 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:54 node-1 multipathd: uevent trigger error
<129>Sep 18 08:29:56 node-1 haproxy[4213]: 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 18 08:29:56 node-1 haproxy[4213]: 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 18 08:29:56 node-1 haproxy[4213]: 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 18 08:29:56 node-1 haproxy[4213]: 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 18 08:29:56 node-1 haproxy[4213]: proxy keystone-1 has no server available!
<129>Sep 18 08:29:56 node-1 haproxy[4213]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: proxy keystone-2 has no server available!
<129>Sep 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: proxy neutron has no server available!
<129>Sep 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: proxy mysqld has no server available!
<129>Sep 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: proxy object-storage has no server available!
<129>Sep 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:57 node-1 haproxy[4217]: 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 18 08:29:58 node-1 haproxy[4217]: 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 18 08:29:58 node-1 haproxy[4217]: proxy aodh has no server available!
<129>Sep 18 08:29:58 node-1 haproxy[4217]: 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 18 08:29:58 node-1 haproxy[4217]: 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 18 08:29:58 node-1 haproxy[4217]: 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 18 08:29:58 node-1 haproxy[4217]: proxy ceilometer has no server available!
<27>Sep 18 08:29:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:29:59 node-1 multipathd: uevent trigger error
<129>Sep 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: proxy keystone-1 has no server available!
<129>Sep 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: proxy keystone-2 has no server available!
<129>Sep 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:02 node-1 haproxy[5706]: proxy glance-api has no server available!
<129>Sep 18 08:30:02 node-1 haproxy[5706]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: proxy glance-glare has no server available!
<129>Sep 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: proxy neutron has no server available!
<129>Sep 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: proxy glance-registry has no server available!
<129>Sep 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: proxy mysqld has no server available!
<129>Sep 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: proxy object-storage has no server available!
<129>Sep 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: 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 18 08:30:03 node-1 haproxy[5710]: proxy aodh has no server available!
<129>Sep 18 08:30:04 node-1 haproxy[5710]: 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 18 08:30:04 node-1 haproxy[5710]: 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 18 08:30:04 node-1 haproxy[5710]: 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 18 08:30:04 node-1 haproxy[5710]: proxy ceilometer has no server available!
<27>Sep 18 08:30:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:05 node-1 multipathd: uevent trigger error
<129>Sep 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: proxy keystone-1 has no server available!
<129>Sep 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: proxy keystone-2 has no server available!
<129>Sep 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: proxy nova-api has no server available!
<129>Sep 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:08 node-1 haproxy[7353]: proxy nova-metadata-api has no server available!
<129>Sep 18 08:30:08 node-1 haproxy[7353]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: proxy glance-api has no server available!
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: proxy glance-glare has no server available!
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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.
<27>Sep 18 08:30:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: proxy neutron has no server available!
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: proxy glance-registry has no server available!
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: proxy mysqld has no server available!
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: proxy object-storage has no server available!
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: proxy aodh has no server available!
<129>Sep 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:09 node-1 haproxy[7357]: 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 18 08:30:10 node-1 haproxy[7357]: 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 18 08:30:10 node-1 haproxy[7357]: proxy ceilometer has no server available!
<129>Sep 18 08:30:10 node-1 haproxy[7357]: 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 18 08:30:10 node-1 haproxy[7357]: 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 18 08:30:10 node-1 haproxy[7357]: 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 18 08:30:10 node-1 haproxy[7357]: proxy nova-novncproxy has no server available!
<27>Sep 18 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:11 node-1 multipathd: uevent trigger error
<129>Sep 18 08:30:13 node-1 haproxy[8818]: 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 18 08:30:13 node-1 haproxy[8818]: 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 18 08:30:13 node-1 haproxy[8818]: 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 18 08:30:13 node-1 haproxy[8818]: 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 18 08:30:13 node-1 haproxy[8818]: proxy keystone-1 has no server available!
<129>Sep 18 08:30:13 node-1 haproxy[8818]: 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 18 08:30:13 node-1 haproxy[8818]: 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 18 08:30:13 node-1 haproxy[8818]: 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 18 08:30:13 node-1 haproxy[8818]: proxy keystone-2 has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy nova-api has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy nova-metadata-api has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy cinder-api has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy glance-api has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy glance-glare has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy neutron has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy glance-registry has no server available!
<129>Sep 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: 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 18 08:30:14 node-1 haproxy[8822]: proxy mysqld has no server available!
<129>Sep 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: proxy object-storage has no server available!
<129>Sep 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: proxy aodh has no server available!
<129>Sep 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: proxy ceilometer has no server available!
<129>Sep 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: 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 18 08:30:15 node-1 haproxy[8822]: proxy nova-novncproxy has no server available!
<27>Sep 18 08:30:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 08:30:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:16 node-1 multipathd: uevent trigger error
<129>Sep 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: proxy keystone-1 has no server available!
<129>Sep 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: proxy keystone-2 has no server available!
<129>Sep 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: 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 18 08:30:19 node-1 haproxy[10594]: proxy nova-api has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy nova-metadata-api has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy cinder-api has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy glance-api has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy glance-glare has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy neutron has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy glance-registry has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy mysqld has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy object-storage has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:20 node-1 haproxy[10598]: proxy aodh has no server available!
<129>Sep 18 08:30:20 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: proxy ceilometer has no server available!
<129>Sep 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: proxy heat-api has no server available!
<129>Sep 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: proxy heat-api-cfn has no server available!
<129>Sep 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: proxy heat-api-cloudwatch has no server available!
<129>Sep 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: 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 18 08:30:21 node-1 haproxy[10598]: proxy nova-novncproxy has no server available!
<27>Sep 18 08:30:22 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:22 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:22 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:22 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:22 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:22 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:30:33 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 18 08:30:58 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 18 08:31:00 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 18 08:31:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:31:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:31:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:31:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:31:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 08:33:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:28 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:34 node-1 multipathd: uevent trigger error
<43>Sep 18 08:33:47 node-1 apache2_error [Sun Sep 18 08:33:45.052283 2016] [mpm_event:notice] [pid 17909:tid 140687966631808] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 18 08:33:47 node-1 apache2_error [Sun Sep 18 08:33:45.052439 2016] [core:notice] [pid 17909:tid 140687966631808] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 08:33:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:53 node-1 multipathd: uevent trigger error
<43>Sep 18 08:33:57 node-1 apache2_error [Sun Sep 18 08:33:48.039856 2016] [mpm_event:notice] [pid 17909:tid 140687966631808] AH00491: caught SIGTERM, shutting down
<43>Sep 18 08:33:57 node-1 apache2_error [Sun Sep 18 08:33:49.128595 2016] [mpm_worker:notice] [pid 19576:tid 139895014868864] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 18 08:33:57 node-1 apache2_error [Sun Sep 18 08:33:49.128638 2016] [core:notice] [pid 19576:tid 139895014868864] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 08:33:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:33:58 node-1 multipathd: uevent trigger error
<27>Sep 18 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:34:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:34:02 node-1 multipathd: uevent trigger error
<43>Sep 18 08:35:07 node-1 apache2_error [Sun Sep 18 08:35:04.170545 2016] [mpm_worker:notice] [pid 19576:tid 139895014868864] AH00295: caught SIGTERM, shutting down
<43>Sep 18 08:35:07 node-1 apache2_error [Sun Sep 18 08:35:04.923663 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 08:35:07 node-1 apache2_error [Sun Sep 18 08:35:04.923707 2016] [core:notice] [pid 381:tid 140009670072192] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 18 08:35:57 node-1 apache2_error [Sun Sep 18 08:35:48.708769 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 08:35:57 node-1 apache2_error [Sun Sep 18 08:35:48.904435 2016] [mpm_worker:warn] [pid 381:tid 140009670072192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 08:35:57 node-1 apache2_error [Sun Sep 18 08:35:48.909281 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 08:35:57 node-1 apache2_error [Sun Sep 18 08:35:48.909308 2016] [core:notice] [pid 381:tid 140009670072192] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 08:36:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 08:36:33 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:33 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:33 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:33 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:33 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:36:54 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:37:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:38:27 node-1 multipathd: uevent trigger error
<27>Sep 18 08:38:27 node-1 multipathd: uevent trigger error
<27>Sep 18 08:38:27 node-1 multipathd: uevent trigger error
<27>Sep 18 08:38:27 node-1 multipathd: uevent trigger error
<27>Sep 18 08:38:27 node-1 multipathd: uevent trigger error
<27>Sep 18 08:39:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 08:39:36 node-1 multipathd: uevent trigger error
<27>Sep 18 08:39:36 node-1 multipathd: uevent trigger error
<27>Sep 18 08:39:36 node-1 multipathd: uevent trigger error
<27>Sep 18 08:39:36 node-1 multipathd: uevent trigger error
<27>Sep 18 08:39:36 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:40:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:41:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:41:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:41:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:41:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:41:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:42:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 08:43:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:23 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:46 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:46 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:46 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:46 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:46 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:52 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:52 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:52 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:52 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:52 node-1 multipathd: uevent trigger error
<27>Sep 18 08:43:52 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:44:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 08:45:47 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:47 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:47 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:47 node-1 multipathd: uevent trigger error
<27>Sep 18 08:45:47 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:02 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:46:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:48:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 08:48:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:48:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:48:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:48:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:48:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:03 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:03 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:03 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:03 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:03 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:08 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:08 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:08 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:08 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:08 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:40 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:44 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:44 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:44 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:44 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:44 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:48 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:48 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:48 node-1 multipathd: uevent trigger error
<27>Sep 18 08:49:48 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:00 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:00 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:00 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:00 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:00 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:07 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:07 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:07 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:07 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:07 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:49 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:49 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:49 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:49 node-1 multipathd: uevent trigger error
<27>Sep 18 08:50:49 node-1 multipathd: uevent trigger error
<27>Sep 18 08:51:25 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 08:51:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:51:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:51:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:51:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:51:53 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:09 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:09 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:09 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:09 node-1 multipathd: uevent trigger error
<11>Sep 18 08:52:21 node-1 liberasurecode[14504]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:21 node-1 liberasurecode[14504]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:21 node-1 liberasurecode[14504]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:21 node-1 liberasurecode[14504]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:22 node-1 liberasurecode[14532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:22 node-1 liberasurecode[14532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:22 node-1 liberasurecode[14532]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:22 node-1 liberasurecode[14532]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:23 node-1 liberasurecode[14953]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:23 node-1 liberasurecode[14953]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:23 node-1 liberasurecode[14953]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:23 node-1 liberasurecode[14953]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15635]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15635]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15635]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15635]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15681]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15681]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15681]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15681]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15723]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15723]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15723]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:27 node-1 liberasurecode[15723]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15816]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15816]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15816]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15816]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15803]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15803]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15803]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15803]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15832]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15832]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15832]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15832]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15846]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15846]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15846]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:28 node-1 liberasurecode[15846]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:37 node-1 liberasurecode[16461]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:37 node-1 liberasurecode[16461]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:37 node-1 liberasurecode[16461]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:52:37 node-1 liberasurecode[16461]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 18 08:52:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:45 node-1 multipathd: uevent trigger error
<27>Sep 18 08:52:45 node-1 multipathd: uevent trigger error
<43>Sep 18 08:53:38 node-1 apache2_error [Sun Sep 18 08:53:32.216270 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 08:53:38 node-1 apache2_error [Sun Sep 18 08:53:32.597105 2016] [mpm_worker:warn] [pid 381:tid 140009670072192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 08:53:38 node-1 apache2_error [Sun Sep 18 08:53:32.600702 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 08:53:38 node-1 apache2_error [Sun Sep 18 08:53:32.600726 2016] [core:notice] [pid 381:tid 140009670072192] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 08:54:13 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:13 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:13 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:13 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:13 node-1 multipathd: uevent trigger error
<43>Sep 18 08:54:18 node-1 apache2_error [Sun Sep 18 08:54:09.590710 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 08:54:18 node-1 apache2_error [Sun Sep 18 08:54:09.786308 2016] [mpm_worker:warn] [pid 381:tid 140009670072192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 08:54:18 node-1 apache2_error [Sun Sep 18 08:54:09.797323 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 08:54:18 node-1 apache2_error [Sun Sep 18 08:54:09.797359 2016] [core:notice] [pid 381:tid 140009670072192] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 08:54:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 18 08:54:58 node-1 apache2_error [Sun Sep 18 08:54:54.930489 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 08:54:58 node-1 apache2_error [Sun Sep 18 08:54:56.444442 2016] [mpm_worker:warn] [pid 381:tid 140009670072192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 08:54:58 node-1 apache2_error [Sun Sep 18 08:54:56.458934 2016] [mpm_worker:notice] [pid 381:tid 140009670072192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 08:54:58 node-1 apache2_error [Sun Sep 18 08:54:56.458982 2016] [core:notice] [pid 381:tid 140009670072192] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 08:54:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:59 node-1 multipathd: uevent trigger error
<27>Sep 18 08:54:59 node-1 multipathd: uevent trigger error
<11>Sep 18 08:55:01 node-1 liberasurecode[9264]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:55:01 node-1 liberasurecode[9264]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:55:01 node-1 liberasurecode[9264]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 08:55:01 node-1 liberasurecode[9264]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 18 08:55:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:35 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:35 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:35 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:35 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:35 node-1 multipathd: uevent trigger error
<27>Sep 18 08:55:55 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:01 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 18 08:56:10 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:10 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:10 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:10 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:10 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:10 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:14 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:14 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:14 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:14 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:14 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:32 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:37 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:38 node-1 multipathd: uevent trigger error
<27>Sep 18 08:56:55 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:04 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:05 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:18 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:57:41 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:11 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:16 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:20 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:24 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:24 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:25 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:29 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:34 node-1 multipathd: uevent trigger error
<27>Sep 18 08:58:34 node-1 multipathd: uevent trigger error
<11>Sep 18 09:00:01 node-1 liberasurecode[12824]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 09:00:01 node-1 liberasurecode[12824]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 09:00:01 node-1 liberasurecode[12824]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 09:00:01 node-1 liberasurecode[12824]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
