Nov 13 14:56:29 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8422" x-info="http://www.rsyslog.com"] start
Nov 13 14:56:29 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov 13 14:56:29 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov 13 14:56:29 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov 13 14:56:29 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 13 14:56:29 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 13 14:56:29 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov 13 14:56:29 node-1 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Nov 13 14:56:29 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=bfb799e5-04cd-4029-ad68-050d788f38ff nomdmonddf nomdmonisw
Nov 13 14:56:29 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov 13 14:56:29 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov 13 14:56:29 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov 13 14:56:29 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov 13 14:56:29 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov 13 14:56:29 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov 13 14:56:29 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov 13 14:56:29 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
Nov 13 14:56:29 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 13 14:56:29 node-1 kernel: [    0.000000] No AGP bridge found
Nov 13 14:56:29 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov 13 14:56:29 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov 13 14:56:29 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov 13 14:56:29 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov 13 14:56:29 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov 13 14:56:29 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov 13 14:56:29 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov 13 14:56:29 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov 13 14:56:29 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov 13 14:56:29 node-1 kernel: [    0.000000]   2 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000]   3 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000]   4 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000]   5 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000]   6 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000]   7 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000]   8 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000]   9 disabled
Nov 13 14:56:29 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 13 14:56:29 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov 13 14:56:29 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov 13 14:56:29 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov 13 14:56:29 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov 13 14:56:29 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov 13 14:56:29 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov 13 14:56:29 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov 13 14:56:29 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov 13 14:56:29 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov 13 14:56:29 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov 13 14:56:29 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov 13 14:56:29 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov 13 14:56:29 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov 13 14:56:29 node-1 kernel: [    0.000000] Zone ranges:
Nov 13 14:56:29 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] Movable zone start for each node
Nov 13 14:56:29 node-1 kernel: [    0.000000] Early memory node ranges
Nov 13 14:56:29 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Nov 13 14:56:29 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov 13 14:56:29 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov 13 14:56:29 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov 13 14:56:29 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Nov 13 14:56:29 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Nov 13 14:56:29 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov 13 14:56:29 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov 13 14:56:29 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov 13 14:56:29 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov 13 14:56:29 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov 13 14:56:29 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov 13 14:56:29 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov 13 14:56:29 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov 13 14:56:29 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov 13 14:56:29 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov 13 14:56:29 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov 13 14:56:29 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov 13 14:56:29 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov 13 14:56:29 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov 13 14:56:29 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov 13 14:56:29 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov 13 14:56:29 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov 13 14:56:29 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 
Nov 13 14:56:29 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Nov 13 14:56:29 node-1 kernel: [    0.000000] Policy zone: Normal
Nov 13 14:56:29 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=bfb799e5-04cd-4029-ad68-050d788f38ff nomdmonddf nomdmonisw
Nov 13 14:56:29 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov 13 14:56:29 node-1 kernel: [    0.000000] Checking aperture...
Nov 13 14:56:29 node-1 kernel: [    0.000000] No AGP bridge found
Nov 13 14:56:29 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov 13 14:56:29 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov 13 14:56:29 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627180K reserved)
Nov 13 14:56:29 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov 13 14:56:29 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov 13 14:56:29 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov 13 14:56:29 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov 13 14:56:29 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov 13 14:56:29 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov 13 14:56:29 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov 13 14:56:29 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov 13 14:56:29 node-1 kernel: [    0.000000] console [tty0] enabled
Nov 13 14:56:29 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov 13 14:56:29 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 13 14:56:29 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov 13 14:56:29 node-1 kernel: [    0.000000] hpet clockevent registered
Nov 13 14:56:29 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov 13 14:56:29 node-1 kernel: [    0.004000] tsc: Detected 3492.137 MHz processor
Nov 13 14:56:29 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.27 BogoMIPS (lpj=13968548)
Nov 13 14:56:29 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov 13 14:56:29 node-1 kernel: [    0.000043] Security Framework initialized
Nov 13 14:56:29 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Nov 13 14:56:29 node-1 kernel: [    0.000062] Yama: becoming mindful.
Nov 13 14:56:29 node-1 kernel: [    0.001463] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.006330] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.008257] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.008286] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.008573] Initializing cgroup subsys memory
Nov 13 14:56:29 node-1 kernel: [    0.008580] Initializing cgroup subsys devices
Nov 13 14:56:29 node-1 kernel: [    0.008582] Initializing cgroup subsys freezer
Nov 13 14:56:29 node-1 kernel: [    0.008584] Initializing cgroup subsys blkio
Nov 13 14:56:29 node-1 kernel: [    0.008586] Initializing cgroup subsys perf_event
Nov 13 14:56:29 node-1 kernel: [    0.008588] Initializing cgroup subsys hugetlb
Nov 13 14:56:29 node-1 kernel: [    0.008607] CPU: Physical Processor ID: 0
Nov 13 14:56:29 node-1 kernel: [    0.008608] CPU: Processor Core ID: 0
Nov 13 14:56:29 node-1 kernel: [    0.008612] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov 13 14:56:29 node-1 kernel: [    0.008612] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov 13 14:56:29 node-1 kernel: [    0.009306] mce: CPU supports 22 MCE banks
Nov 13 14:56:29 node-1 kernel: [    0.009333] CPU0: Thermal monitoring enabled (TM1)
Nov 13 14:56:29 node-1 kernel: [    0.009354] process: using mwait in idle threads
Nov 13 14:56:29 node-1 kernel: [    0.009357] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov 13 14:56:29 node-1 kernel: [    0.009357] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov 13 14:56:29 node-1 kernel: [    0.009357] tlb_flushall_shift: 6
Nov 13 14:56:29 node-1 kernel: [    0.009445] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov 13 14:56:29 node-1 kernel: [    0.010169] ACPI: Core revision 20131115
Nov 13 14:56:29 node-1 kernel: [    0.022969] ACPI: All ACPI Tables successfully acquired
Nov 13 14:56:29 node-1 kernel: [    0.023129] ftrace: allocating 28622 entries in 112 pages
Nov 13 14:56:29 node-1 kernel: [    0.031879] dmar: Host address width 46
Nov 13 14:56:29 node-1 kernel: [    0.031882] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov 13 14:56:29 node-1 kernel: [    0.031888] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 14:56:29 node-1 kernel: [    0.031889] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov 13 14:56:29 node-1 kernel: [    0.031893] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 14:56:29 node-1 kernel: [    0.031895] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov 13 14:56:29 node-1 kernel: [    0.031896] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov 13 14:56:29 node-1 kernel: [    0.031897] dmar: ATSR flags: 0x0
Nov 13 14:56:29 node-1 kernel: [    0.031898] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov 13 14:56:29 node-1 kernel: [    0.031899] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov 13 14:56:29 node-1 kernel: [    0.032015] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov 13 14:56:29 node-1 kernel: [    0.032016] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 14:56:29 node-1 kernel: [    0.032017] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 14:56:29 node-1 kernel: [    0.032018] HPET id 0 under DRHD base 0xc7ffc000
Nov 13 14:56:29 node-1 kernel: [    0.032019] Your BIOS is broken and requested that x2apic be disabled.
Nov 13 14:56:29 node-1 kernel: [    0.032019] This will slightly decrease performance.
Nov 13 14:56:29 node-1 kernel: [    0.032019] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov 13 14:56:29 node-1 kernel: [    0.032450] Enabled IRQ remapping in xapic mode
Nov 13 14:56:29 node-1 kernel: [    0.032451] x2apic not enabled, IRQ remapping is in xapic mode
Nov 13 14:56:29 node-1 kernel: [    0.032455] Switched APIC routing to physical flat.
Nov 13 14:56:29 node-1 kernel: [    0.033092] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 13 14:56:29 node-1 kernel: [    0.072744] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov 13 14:56:29 node-1 kernel: [    0.072749] TSC deadline timer enabled
Nov 13 14:56:29 node-1 kernel: [    0.072757] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov 13 14:56:29 node-1 kernel: [    0.072763] ... version:                3
Nov 13 14:56:29 node-1 kernel: [    0.072764] ... bit width:              48
Nov 13 14:56:29 node-1 kernel: [    0.072765] ... generic registers:      4
Nov 13 14:56:29 node-1 kernel: [    0.072766] ... value mask:             0000ffffffffffff
Nov 13 14:56:29 node-1 kernel: [    0.072767] ... max period:             0000ffffffffffff
Nov 13 14:56:29 node-1 kernel: [    0.072768] ... fixed-purpose events:   3
Nov 13 14:56:29 node-1 kernel: [    0.072769] ... event mask:             000000070000000f
Nov 13 14:56:29 node-1 kernel: [    0.074187] x86: Booting SMP configuration:
Nov 13 14:56:29 node-1 kernel: [    0.088293] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 13 14:56:29 node-1 kernel: [    0.074189] .... node  #0, CPUs:        #1  #2  #3
Nov 13 14:56:29 node-1 kernel: [    0.116208] .... node  #1, CPUs:    #4  #5  #6  #7
Nov 13 14:56:29 node-1 kernel: [    0.270360] .... node  #0, CPUs:    #8  #9 #10 #11
Nov 13 14:56:29 node-1 kernel: [    0.325986] .... node  #1, CPUs:   #12 #13 #14 #15
Nov 13 14:56:29 node-1 kernel: [    0.382233] x86: Booted up 2 nodes, 16 CPUs
Nov 13 14:56:29 node-1 kernel: [    0.382236] smpboot: Total of 16 processors activated (111760.60 BogoMIPS)
Nov 13 14:56:29 node-1 kernel: [    0.404717] devtmpfs: initialized
Nov 13 14:56:29 node-1 kernel: [    0.407245] EVM: security.selinux
Nov 13 14:56:29 node-1 kernel: [    0.407247] EVM: security.SMACK64
Nov 13 14:56:29 node-1 kernel: [    0.407248] EVM: security.ima
Nov 13 14:56:29 node-1 kernel: [    0.407248] EVM: security.capability
Nov 13 14:56:29 node-1 kernel: [    0.407297] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.407953] pinctrl core: initialized pinctrl subsystem
Nov 13 14:56:29 node-1 kernel: [    0.408012] regulator-dummy: no parameters
Nov 13 14:56:29 node-1 kernel: [    0.408043] RTC time: 14:55:52, date: 11/13/16
Nov 13 14:56:29 node-1 kernel: [    0.408076] NET: Registered protocol family 16
Nov 13 14:56:29 node-1 kernel: [    0.408159] cpuidle: using governor ladder
Nov 13 14:56:29 node-1 kernel: [    0.408160] cpuidle: using governor menu
Nov 13 14:56:29 node-1 kernel: [    0.408193] ACPI: bus type PCI registered
Nov 13 14:56:29 node-1 kernel: [    0.408195] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 13 14:56:29 node-1 kernel: [    0.408238] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov 13 14:56:29 node-1 kernel: [    0.408241] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov 13 14:56:29 node-1 kernel: [    0.421978] PCI: Using configuration type 1 for base access
Nov 13 14:56:29 node-1 kernel: [    0.422960] bio: create slab <bio-0> at 0
Nov 13 14:56:29 node-1 kernel: [    0.423225] ACPI: Added _OSI(Module Device)
Nov 13 14:56:29 node-1 kernel: [    0.423227] ACPI: Added _OSI(Processor Device)
Nov 13 14:56:29 node-1 kernel: [    0.423228] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 13 14:56:29 node-1 kernel: [    0.423229] ACPI: Added _OSI(Processor Aggregator Device)
Nov 13 14:56:29 node-1 kernel: [    0.435937] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov 13 14:56:29 node-1 kernel: [    0.446440] ACPI: Interpreter enabled
Nov 13 14:56:29 node-1 kernel: [    0.446446] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov 13 14:56:29 node-1 kernel: [    0.446450] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov 13 14:56:29 node-1 kernel: [    0.446453] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov 13 14:56:29 node-1 kernel: [    0.446460] ACPI: (supports S0 S4 S5)
Nov 13 14:56:29 node-1 kernel: [    0.446461] ACPI: Using IOAPIC for interrupt routing
Nov 13 14:56:29 node-1 kernel: [    0.446504] HEST: Table parsing has been initialized.
Nov 13 14:56:29 node-1 kernel: [    0.446507] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 13 14:56:29 node-1 kernel: [    0.447078] ACPI: No dock devices found.
Nov 13 14:56:29 node-1 kernel: [    0.459002] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov 13 14:56:29 node-1 kernel: [    0.459006] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 14:56:29 node-1 kernel: [    0.459010] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 14:56:29 node-1 kernel: [    0.459038] PCI host bridge to bus 0000:ff
Nov 13 14:56:29 node-1 kernel: [    0.459040] pci_bus 0000:ff: root bus resource [bus ff]
Nov 13 14:56:29 node-1 kernel: [    0.459048] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459086] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.459116] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459148] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459176] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.459204] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.459234] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459262] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459292] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459323] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459351] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459377] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459406] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459432] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459457] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459483] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459511] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459537] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459563] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.459590] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459616] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.459641] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459666] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459695] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.459728] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459758] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459787] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459817] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459847] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459876] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459906] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459935] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459966] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.459996] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460026] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460055] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460086] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460114] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460140] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460170] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460202] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460239] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460273] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460305] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460335] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460363] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460394] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460422] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460453] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460484] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460514] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460542] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460570] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460599] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460628] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460659] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460690] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460752] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov 13 14:56:29 node-1 kernel: [    0.460755] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 14:56:29 node-1 kernel: [    0.460758] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 14:56:29 node-1 kernel: [    0.460776] PCI host bridge to bus 0000:7f
Nov 13 14:56:29 node-1 kernel: [    0.460778] pci_bus 0000:7f: root bus resource [bus 7f]
Nov 13 14:56:29 node-1 kernel: [    0.460783] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460813] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.460843] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460875] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460899] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.460925] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.460954] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.460982] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461008] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461033] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461057] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461081] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461107] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461131] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461156] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461184] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461207] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461231] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461256] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.461281] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461305] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.461332] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461356] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461385] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 14:56:29 node-1 kernel: [    0.461420] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461449] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461477] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461507] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461534] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461564] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461593] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461622] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461648] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461678] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461708] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461738] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461768] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461794] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461820] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461850] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461877] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461905] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461937] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461967] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.461995] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462024] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462051] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462079] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462108] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 14:56:29 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov 13 14:56:29 node-1 kernel: [    0.462137] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462169] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462195] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462219] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462247] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462275] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462309] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.462337] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.463628] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov 13 14:56:29 node-1 kernel: [    0.463631] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 14:56:29 node-1 kernel: [    0.464836] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 14:56:29 node-1 kernel: [    0.465347] PCI host bridge to bus 0000:00
Nov 13 14:56:29 node-1 kernel: [    0.465349] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov 13 14:56:29 node-1 kernel: [    0.465351] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov 13 14:56:29 node-1 kernel: [    0.465352] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov 13 14:56:29 node-1 kernel: [    0.465354] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov 13 14:56:29 node-1 kernel: [    0.465355] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov 13 14:56:29 node-1 kernel: [    0.465356] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 13 14:56:29 node-1 kernel: [    0.465358] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov 13 14:56:29 node-1 kernel: [    0.465364] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov 13 14:56:29 node-1 kernel: [    0.465446] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.465477] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.465519] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov 13 14:56:29 node-1 kernel: [    0.465538] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.465568] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.465608] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov 13 14:56:29 node-1 kernel: [    0.465627] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.465656] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.465696] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov 13 14:56:29 node-1 kernel: [    0.465713] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.465784] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.465861] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.465938] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 14:56:29 node-1 kernel: [    0.465943] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov 13 14:56:29 node-1 kernel: [    0.466027] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov 13 14:56:29 node-1 kernel: [    0.466167] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov 13 14:56:29 node-1 kernel: [    0.466185] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov 13 14:56:29 node-1 kernel: [    0.466262] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.466317] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov 13 14:56:29 node-1 kernel: [    0.466338] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.466393] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.466436] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 13 14:56:29 node-1 kernel: [    0.466463] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.466519] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.466562] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov 13 14:56:29 node-1 kernel: [    0.466585] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov 13 14:56:29 node-1 kernel: [    0.466602] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov 13 14:56:29 node-1 kernel: [    0.466680] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.466730] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 13 14:56:29 node-1 kernel: [    0.466755] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov 13 14:56:29 node-1 kernel: [    0.467000] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov 13 14:56:29 node-1 kernel: [    0.467006] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov 13 14:56:29 node-1 kernel: [    0.467012] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.467018] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.467026] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov 13 14:56:29 node-1 kernel: [    0.467056] pci 0000:01:00.0: supports D1 D2
Nov 13 14:56:29 node-1 kernel: [    0.476728] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 14:56:29 node-1 kernel: [    0.476735] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 14:56:29 node-1 kernel: [    0.476739] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 14:56:29 node-1 kernel: [    0.476979] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.477012] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov 13 14:56:29 node-1 kernel: [    0.484740] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 14:56:29 node-1 kernel: [    0.484746] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.484750] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 14:56:29 node-1 kernel: [    0.484842] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.484910] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.485010] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.485055] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 14:56:29 node-1 kernel: [    0.485058] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.485060] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 14:56:29 node-1 kernel: [    0.485112] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.485234] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.485287] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 14:56:29 node-1 kernel: [    0.485290] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.485292] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.485341] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.485459] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.485497] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.485616] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.485652] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.485772] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.485809] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov 13 14:56:29 node-1 kernel: [    0.485929] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov 13 14:56:29 node-1 kernel: [    0.485989] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 14:56:29 node-1 kernel: [    0.485992] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.485994] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.486054] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov 13 14:56:29 node-1 kernel: [    0.486117] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.486169] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.486211] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov 13 14:56:29 node-1 kernel: [    0.486292] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov 13 14:56:29 node-1 kernel: [    0.486398] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 14:56:29 node-1 kernel: [    0.486400] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.486402] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.486458] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov 13 14:56:29 node-1 kernel: [    0.486515] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.486564] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.486775] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 14:56:29 node-1 kernel: [    0.486779] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 14:56:29 node-1 kernel: [    0.486843] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov 13 14:56:29 node-1 kernel: [    0.486896] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.486977] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.487200] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 14:56:29 node-1 kernel: [    0.487204] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 14:56:29 node-1 kernel: [    0.487265] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov 13 14:56:29 node-1 kernel: [    0.487327] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.487378] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov 13 14:56:29 node-1 kernel: [    0.487600] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 14:56:29 node-1 kernel: [    0.487603] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 14:56:29 node-1 kernel: [    0.487779] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 14:56:29 node-1 kernel: [    0.487817] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 14:56:29 node-1 kernel: [    0.487895] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov 13 14:56:29 node-1 kernel: [    0.487914] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov 13 14:56:29 node-1 kernel: [    0.487927] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov 13 14:56:29 node-1 kernel: [    0.487940] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov 13 14:56:29 node-1 kernel: [    0.487990] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov 13 14:56:29 node-1 kernel: [    0.492738] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 14:56:29 node-1 kernel: [    0.492743] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 14:56:29 node-1 kernel: [    0.492775] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov 13 14:56:29 node-1 kernel: [    0.493263] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov 13 14:56:29 node-1 kernel: [    0.493266] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 14:56:29 node-1 kernel: [    0.493386] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 14:56:29 node-1 kernel: [    0.493493] PCI host bridge to bus 0000:80
Nov 13 14:56:29 node-1 kernel: [    0.493495] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov 13 14:56:29 node-1 kernel: [    0.493497] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov 13 14:56:29 node-1 kernel: [    0.493498] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov 13 14:56:29 node-1 kernel: [    0.493506] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.493568] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.493635] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 14:56:29 node-1 kernel: [    0.493696] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 14:56:29 node-1 kernel: [    0.493701] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov 13 14:56:29 node-1 kernel: [    0.493773] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov 13 14:56:29 node-1 kernel: [    0.494069] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 13 14:56:29 node-1 kernel: [    0.494100] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 13 14:56:29 node-1 kernel: [    0.494130] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov 13 14:56:29 node-1 kernel: [    0.494159] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov 13 14:56:29 node-1 kernel: [    0.494188] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 14:56:29 node-1 kernel: [    0.494218] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 14:56:29 node-1 kernel: [    0.494247] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 14:56:29 node-1 kernel: [    0.494277] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 14:56:29 node-1 kernel: [    0.494362] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov 13 14:56:29 node-1 kernel: [    0.494366] ACPI: \_SB_.UNC1: notify handler is installed
Nov 13 14:56:29 node-1 kernel: [    0.494367] ACPI: \_SB_.UNC0: notify handler is installed
Nov 13 14:56:29 node-1 kernel: [    0.494382] ACPI: \_SB_.PCI0: notify handler is installed
Nov 13 14:56:29 node-1 kernel: [    0.494435] ACPI: \_SB_.PCI1: notify handler is installed
Nov 13 14:56:29 node-1 kernel: [    0.494514] Found 4 acpi root devices
Nov 13 14:56:29 node-1 kernel: [    0.494625] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov 13 14:56:29 node-1 kernel: [    0.494627] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov 13 14:56:29 node-1 kernel: [    0.494628] vgaarb: loaded
Nov 13 14:56:29 node-1 kernel: [    0.494630] vgaarb: bridge control possible 0000:0c:00.0
Nov 13 14:56:29 node-1 kernel: [    0.494750] SCSI subsystem initialized
Nov 13 14:56:29 node-1 kernel: [    0.494813] libata version 3.00 loaded.
Nov 13 14:56:29 node-1 kernel: [    0.494828] ACPI: bus type USB registered
Nov 13 14:56:29 node-1 kernel: [    0.494839] usbcore: registered new interface driver usbfs
Nov 13 14:56:29 node-1 kernel: [    0.494844] usbcore: registered new interface driver hub
Nov 13 14:56:29 node-1 kernel: [    0.494867] usbcore: registered new device driver usb
Nov 13 14:56:29 node-1 kernel: [    0.495035] PCI: Using ACPI for IRQ routing
Nov 13 14:56:29 node-1 kernel: [    0.498622] PCI: pci_cache_line_size set to 64 bytes
Nov 13 14:56:29 node-1 kernel: [    0.498827] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov 13 14:56:29 node-1 kernel: [    0.498828] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Nov 13 14:56:29 node-1 kernel: [    0.498829] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov 13 14:56:29 node-1 kernel: [    0.498893] NetLabel: Initializing
Nov 13 14:56:29 node-1 kernel: [    0.498895] NetLabel:  domain hash size = 128
Nov 13 14:56:29 node-1 kernel: [    0.498896] NetLabel:  protocols = UNLABELED CIPSOv4
Nov 13 14:56:29 node-1 kernel: [    0.498905] NetLabel:  unlabeled traffic allowed by default
Nov 13 14:56:29 node-1 kernel: [    0.498962] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov 13 14:56:29 node-1 kernel: [    0.498966] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov 13 14:56:29 node-1 kernel: [    0.501020] Switched to clocksource hpet
Nov 13 14:56:29 node-1 kernel: [    0.504886] AppArmor: AppArmor Filesystem Enabled
Nov 13 14:56:29 node-1 kernel: [    0.504901] pnp: PnP ACPI init
Nov 13 14:56:29 node-1 kernel: [    0.504908] ACPI: bus type PNP registered
Nov 13 14:56:29 node-1 kernel: [    0.505030] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505038] pnp 00:01: [dma 4]
Nov 13 14:56:29 node-1 kernel: [    0.505050] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505076] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505096] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505113] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505146] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505200] system 00:06: [io  0x0500-0x057f] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505202] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov 13 14:56:29 node-1 kernel: [    0.505204] system 00:06: [io  0x0580-0x059f] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505206] system 00:06: [io  0x0600-0x061f] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505207] system 00:06: [io  0x0880-0x0883] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505214] system 00:06: [io  0x0800-0x081f] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505216] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov 13 14:56:29 node-1 kernel: [    0.505218] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505219] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505221] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505222] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505224] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505225] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov 13 14:56:29 node-1 kernel: [    0.505227] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505311] pnp 00:07: [dma 0 disabled]
Nov 13 14:56:29 node-1 kernel: [    0.505339] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505413] pnp 00:08: [dma 0 disabled]
Nov 13 14:56:29 node-1 kernel: [    0.505446] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505497] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov 13 14:56:29 node-1 kernel: [    0.505842] pnp: PnP ACPI: found 10 devices
Nov 13 14:56:29 node-1 kernel: [    0.505844] ACPI: bus type PNP unregistered
Nov 13 14:56:29 node-1 kernel: [    0.512178] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 14:56:29 node-1 kernel: [    0.512180] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 14:56:29 node-1 kernel: [    0.512183] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 14:56:29 node-1 kernel: [    0.512187] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 14:56:29 node-1 kernel: [    0.512189] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512204] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512233] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 14:56:29 node-1 kernel: [    0.512247] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512276] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 14:56:29 node-1 kernel: [    0.512290] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 14:56:29 node-1 kernel: [    0.512319] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 14:56:29 node-1 kernel: [    0.512334] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 14:56:29 node-1 kernel: [    0.512363] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 14:56:29 node-1 kernel: [    0.512364] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512379] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512408] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 14:56:29 node-1 kernel: [    0.512410] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512424] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512456] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 14:56:29 node-1 kernel: [    0.512457] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512460] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512464] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 14:56:29 node-1 kernel: [    0.512466] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512468] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512472] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 14:56:29 node-1 kernel: [    0.512477] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 14:56:29 node-1 kernel: [    0.512484] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 14:56:29 node-1 kernel: [    0.512488] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 14:56:29 node-1 kernel: [    0.512494] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov 13 14:56:29 node-1 kernel: [    0.512495] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov 13 14:56:29 node-1 kernel: [    0.512496] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov 13 14:56:29 node-1 kernel: [    0.512497] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov 13 14:56:29 node-1 kernel: [    0.512498] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov 13 14:56:29 node-1 kernel: [    0.512499] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov 13 14:56:29 node-1 kernel: [    0.512500] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov 13 14:56:29 node-1 kernel: [    0.512500] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov 13 14:56:29 node-1 kernel: [    0.512501] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512502] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512503] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512504] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512505] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512506] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512507] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512508] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512509] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov 13 14:56:29 node-1 kernel: [    0.512510] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512511] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov 13 14:56:29 node-1 kernel: [    0.512512] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov 13 14:56:29 node-1 kernel: [    0.512513] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov 13 14:56:29 node-1 kernel: [    0.512514] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov 13 14:56:29 node-1 kernel: [    0.512516] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov 13 14:56:29 node-1 kernel: [    0.512517] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov 13 14:56:29 node-1 kernel: [    0.512552] NET: Registered protocol family 2
Nov 13 14:56:29 node-1 kernel: [    0.512808] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.513144] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.513290] TCP: Hash tables configured (established 262144 bind 65536)
Nov 13 14:56:29 node-1 kernel: [    0.513326] TCP: reno registered
Nov 13 14:56:29 node-1 kernel: [    0.513356] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.513451] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.513599] NET: Registered protocol family 1
Nov 13 14:56:29 node-1 kernel: [    0.553118] pci 0000:0c:00.0: Video device with shadowed ROM
Nov 13 14:56:29 node-1 kernel: [    0.553131] PCI: CLS 64 bytes, default 64
Nov 13 14:56:29 node-1 kernel: [    0.553208] Trying to unpack rootfs image as initramfs...
Nov 13 14:56:29 node-1 kernel: [    0.772509] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Nov 13 14:56:29 node-1 kernel: [    0.772543] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov 13 14:56:29 node-1 kernel: [    0.772546] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Nov 13 14:56:29 node-1 kernel: [    0.772994] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773000] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773005] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773010] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773020] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773031] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773040] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773049] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773057] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773066] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773072] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773079] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773086] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773094] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773101] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773109] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 14:56:29 node-1 kernel: [    0.773182] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 13 14:56:29 node-1 kernel: [    0.773184] Scanning for low memory corruption every 60 seconds
Nov 13 14:56:29 node-1 kernel: [    0.773546] Initialise system trusted keyring
Nov 13 14:56:29 node-1 kernel: [    0.773599] audit: initializing netlink socket (disabled)
Nov 13 14:56:29 node-1 kernel: [    0.773615] type=2000 audit(1479048951.728:1): initialized
Nov 13 14:56:29 node-1 kernel: [    0.791367] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 13 14:56:29 node-1 kernel: [    0.792891] zbud: loaded
Nov 13 14:56:29 node-1 kernel: [    0.793016] VFS: Disk quotas dquot_6.5.2
Nov 13 14:56:29 node-1 kernel: [    0.793055] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 13 14:56:29 node-1 kernel: [    0.793445] fuse init (API version 7.22)
Nov 13 14:56:29 node-1 kernel: [    0.793508] msgmni has been set to 32768
Nov 13 14:56:29 node-1 kernel: [    0.793557] Key type big_key registered
Nov 13 14:56:29 node-1 kernel: [    0.794053] Key type asymmetric registered
Nov 13 14:56:29 node-1 kernel: [    0.794055] Asymmetric key parser 'x509' registered
Nov 13 14:56:29 node-1 kernel: [    0.794077] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 13 14:56:29 node-1 kernel: [    0.794148] io scheduler noop registered
Nov 13 14:56:29 node-1 kernel: [    0.794150] io scheduler deadline registered (default)
Nov 13 14:56:29 node-1 kernel: [    0.794171] io scheduler cfq registered
Nov 13 14:56:29 node-1 kernel: [    0.794559] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    0.794677] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    0.794788] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    0.794899] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    0.795014] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    0.795110] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    0.795549] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov 13 14:56:29 node-1 kernel: [    0.795575] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov 13 14:56:29 node-1 kernel: [    0.795591] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov 13 14:56:29 node-1 kernel: [    0.795601] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795603] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795606] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov 13 14:56:29 node-1 kernel: [    0.795611] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795612] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795614] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795615] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795617] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795618] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795620] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795622] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795623] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795625] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795626] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795627] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795630] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov 13 14:56:29 node-1 kernel: [    0.795635] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795637] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov 13 14:56:29 node-1 kernel: [    0.795652] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795655] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov 13 14:56:29 node-1 kernel: [    0.795666] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795668] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov 13 14:56:29 node-1 kernel: [    0.795671] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov 13 14:56:29 node-1 kernel: [    0.795708] ioapic: probe of 0000:00:05.4 failed with error -22
Nov 13 14:56:29 node-1 kernel: [    0.795714] ioapic: probe of 0000:80:05.4 failed with error -22
Nov 13 14:56:29 node-1 kernel: [    0.795718] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 13 14:56:29 node-1 kernel: [    0.795727] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 13 14:56:29 node-1 kernel: [    0.795767] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov 13 14:56:29 node-1 kernel: [    0.795768] vesafb: scrolling: redraw
Nov 13 14:56:29 node-1 kernel: [    0.795770] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 13 14:56:29 node-1 kernel: [    0.816399] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov 13 14:56:29 node-1 kernel: [    0.825185] Console: switching to colour frame buffer device 80x30
Nov 13 14:56:29 node-1 kernel: [    0.834016] fb0: VESA VGA frame buffer device
Nov 13 14:56:29 node-1 kernel: [    0.834214] intel_idle: MWAIT substates: 0x2120
Nov 13 14:56:29 node-1 kernel: [    0.834215] intel_idle: v0.4 model 0x3F
Nov 13 14:56:29 node-1 kernel: [    0.834216] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov 13 14:56:29 node-1 kernel: [    0.834456] ipmi message handler version 39.2
Nov 13 14:56:29 node-1 kernel: [    0.834732] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov 13 14:56:29 node-1 kernel: [    0.835178] ACPI: AC Adapter [P111] (on-line)
Nov 13 14:56:29 node-1 kernel: [    0.840449] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov 13 14:56:29 node-1 kernel: [    0.851585] ACPI: Power Button [PWRB]
Nov 13 14:56:29 node-1 kernel: [    0.857348] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov 13 14:56:29 node-1 kernel: [    0.868972] ACPI: Power Button [PWRF]
Nov 13 14:56:29 node-1 kernel: [    0.886521] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov 13 14:56:29 node-1 kernel: [    0.898168] pstore: Registered erst as persistent store backend
Nov 13 14:56:29 node-1 kernel: [    0.904355] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov 13 14:56:29 node-1 kernel: [    0.916314] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 13 14:56:29 node-1 kernel: [    0.943051] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov 13 14:56:29 node-1 kernel: [    0.976314] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov 13 14:56:29 node-1 kernel: [    0.990324] Linux agpgart interface v0.103
Nov 13 14:56:29 node-1 kernel: [    0.997993] brd: module loaded
Nov 13 14:56:29 node-1 kernel: [    1.005013] loop: module loaded
Nov 13 14:56:29 node-1 kernel: [    1.011747] libphy: Fixed MDIO Bus: probed
Nov 13 14:56:29 node-1 kernel: [    1.018212] tun: Universal TUN/TAP device driver, 1.6
Nov 13 14:56:29 node-1 kernel: [    1.024682] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 13 14:56:29 node-1 kernel: [    1.031192] PPP generic driver version 2.4.2
Nov 13 14:56:29 node-1 kernel: [    1.037559] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 13 14:56:29 node-1 kernel: [    1.043993] ehci-pci: EHCI PCI platform driver
Nov 13 14:56:29 node-1 kernel: [    1.050498] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov 13 14:56:29 node-1 kernel: [    1.056903] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov 13 14:56:29 node-1 kernel: [    1.069432] ehci-pci 0000:00:1a.0: debug port 2
Nov 13 14:56:29 node-1 kernel: [    1.079613] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov 13 14:56:29 node-1 kernel: [    1.079632] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov 13 14:56:29 node-1 kernel: [    1.096521] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov 13 14:56:29 node-1 kernel: [    1.102601] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 14:56:29 node-1 kernel: [    1.108775] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 14:56:29 node-1 kernel: [    1.120845] usb usb1: Product: EHCI Host Controller
Nov 13 14:56:29 node-1 kernel: [    1.126858] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 14:56:29 node-1 kernel: [    1.132895] usb usb1: SerialNumber: 0000:00:1a.0
Nov 13 14:56:29 node-1 kernel: [    1.138842] hub 1-0:1.0: USB hub found
Nov 13 14:56:29 node-1 kernel: [    1.144684] hub 1-0:1.0: 2 ports detected
Nov 13 14:56:29 node-1 kernel: [    1.150554] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov 13 14:56:29 node-1 kernel: [    1.156129] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov 13 14:56:29 node-1 kernel: [    1.167058] ehci-pci 0000:00:1d.0: debug port 2
Nov 13 14:56:29 node-1 kernel: [    1.176358] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov 13 14:56:29 node-1 kernel: [    1.176362] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov 13 14:56:29 node-1 kernel: [    1.192440] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov 13 14:56:29 node-1 kernel: [    1.197642] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 14:56:29 node-1 kernel: [    1.202941] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 14:56:29 node-1 kernel: [    1.213529] usb usb2: Product: EHCI Host Controller
Nov 13 14:56:29 node-1 kernel: [    1.219015] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 14:56:29 node-1 kernel: [    1.224571] usb usb2: SerialNumber: 0000:00:1d.0
Nov 13 14:56:29 node-1 kernel: [    1.230111] hub 2-0:1.0: USB hub found
Nov 13 14:56:29 node-1 kernel: [    1.235499] hub 2-0:1.0: 2 ports detected
Nov 13 14:56:29 node-1 kernel: [    1.240823] ehci-platform: EHCI generic platform driver
Nov 13 14:56:29 node-1 kernel: [    1.246080] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 13 14:56:29 node-1 kernel: [    1.251422] ohci-pci: OHCI PCI platform driver
Nov 13 14:56:29 node-1 kernel: [    1.256740] ohci-platform: OHCI generic platform driver
Nov 13 14:56:29 node-1 kernel: [    1.261960] uhci_hcd: USB Universal Host Controller Interface driver
Nov 13 14:56:29 node-1 kernel: [    1.267352] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov 13 14:56:29 node-1 kernel: [    1.460219] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov 13 14:56:29 node-1 kernel: [    1.768008] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov 13 14:56:29 node-1 kernel: [    1.784268] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov 13 14:56:29 node-1 kernel: [    1.789947] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 14:56:29 node-1 kernel: [    1.795785] hub 1-1:1.0: USB hub found
Nov 13 14:56:29 node-1 kernel: [    1.801380] hub 1-1:1.0: 6 ports detected
Nov 13 14:56:29 node-1 kernel: [    1.915855] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov 13 14:56:29 node-1 kernel: [    2.306227] i8042: No controller found
Nov 13 14:56:29 node-1 kernel: [    2.311850] mousedev: PS/2 mouse device common for all mice
Nov 13 14:56:29 node-1 kernel: [    2.317639] rtc_cmos 00:02: RTC can wake from S4
Nov 13 14:56:29 node-1 kernel: [    2.320380] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov 13 14:56:29 node-1 kernel: [    2.320381] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 14:56:29 node-1 kernel: [    2.320900] hub 2-1:1.0: USB hub found
Nov 13 14:56:29 node-1 kernel: [    2.321131] hub 2-1:1.0: 8 ports detected
Nov 13 14:56:29 node-1 kernel: [    2.346218] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov 13 14:56:29 node-1 kernel: [    2.351968] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 13 14:56:29 node-1 kernel: [    2.363299] device-mapper: uevent: version 1.0.3
Nov 13 14:56:29 node-1 kernel: [    2.369028] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov 13 14:56:29 node-1 kernel: [    2.380429] ledtrig-cpu: registered to indicate activity on CPUs
Nov 13 14:56:29 node-1 kernel: [    2.386394] TCP: cubic registered
Nov 13 14:56:29 node-1 kernel: [    2.392286] NET: Registered protocol family 10
Nov 13 14:56:29 node-1 kernel: [    2.398349] NET: Registered protocol family 17
Nov 13 14:56:29 node-1 kernel: [    2.404129] Key type dns_resolver registered
Nov 13 14:56:29 node-1 kernel: [    2.410216] Loading compiled-in X.509 certificates
Nov 13 14:56:29 node-1 kernel: [    2.416437] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov 13 14:56:29 node-1 kernel: [    2.428085] registered taskstats version 1
Nov 13 14:56:29 node-1 kernel: [    2.436185] Key type trusted registered
Nov 13 14:56:29 node-1 kernel: [    2.443858] Key type encrypted registered
Nov 13 14:56:29 node-1 kernel: [    2.449350] AppArmor: AppArmor sha1 policy hashing enabled
Nov 13 14:56:29 node-1 kernel: [    2.454861] IMA: No TPM chip found, activating TPM-bypass!
Nov 13 14:56:29 node-1 kernel: [    2.460940] regulator-dummy: disabling
Nov 13 14:56:29 node-1 kernel: [    2.466446]   Magic number: 8:383:940
Nov 13 14:56:29 node-1 kernel: [    2.472191] rtc_cmos 00:02: setting system clock to 2016-11-13 14:55:54 UTC (1479048954)
Nov 13 14:56:29 node-1 kernel: [    2.484738] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov 13 14:56:29 node-1 kernel: [    2.490410] EDD information not available.
Nov 13 14:56:29 node-1 kernel: [    2.496056] PM: Hibernation image not present or could not be loaded.
Nov 13 14:56:29 node-1 kernel: [    2.496917] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov 13 14:56:29 node-1 kernel: [    2.508239] Write protecting the kernel read-only data: 12288k
Nov 13 14:56:29 node-1 kernel: [    2.514528] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov 13 14:56:29 node-1 kernel: [    2.527464] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov 13 14:56:29 node-1 kernel: [    2.560464] device-mapper: multipath: version 1.6.0 loaded
Nov 13 14:56:29 node-1 kernel: [    2.568581] systemd-udevd[217]: starting version 204
Nov 13 14:56:29 node-1 kernel: [    2.592776] md: linear personality registered for level -1
Nov 13 14:56:29 node-1 kernel: [    2.599372] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov 13 14:56:29 node-1 kernel: [    2.612889] md: multipath personality registered for level -4
Nov 13 14:56:29 node-1 kernel: [    2.621055] md: raid0 personality registered for level 0
Nov 13 14:56:29 node-1 kernel: [    2.629453] md: raid1 personality registered for level 1
Nov 13 14:56:29 node-1 kernel: [    2.638222] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov 13 14:56:29 node-1 kernel: [    2.644623] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov 13 14:56:29 node-1 kernel: [    2.650920] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov 13 14:56:29 node-1 kernel: [    2.654524] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Nov 13 14:56:29 node-1 kernel: [    2.654525] 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
Nov 13 14:56:29 node-1 kernel: [    2.654531] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 14:56:29 node-1 kernel: [    2.654890] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.654999] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.655283] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.655411] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.655534] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.668732] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Nov 13 14:56:29 node-1 kernel: [    2.668741] 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
Nov 13 14:56:29 node-1 kernel: [    2.668752] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov 13 14:56:29 node-1 kernel: [    2.669030] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.669166] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.669270] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.669451] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.669576] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.669766] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.670041] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.688691] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Nov 13 14:56:29 node-1 kernel: [    2.688692] 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
Nov 13 14:56:29 node-1 kernel: [    2.688693] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 14:56:29 node-1 kernel: [    2.688997] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.689094] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.689195] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.689268] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.689434] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.703281] raid6: sse2x1    3013 MB/s
Nov 13 14:56:29 node-1 kernel: [    2.705359] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Nov 13 14:56:29 node-1 kernel: [    2.705362] 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
Nov 13 14:56:29 node-1 kernel: [    2.705393] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 14:56:29 node-1 kernel: [    2.709576] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.709676] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.709841] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.709976] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.710247] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 14:56:29 node-1 kernel: [    2.771331] raid6: sse2x2   12977 MB/s
Nov 13 14:56:29 node-1 kernel: [    2.839273] raid6: sse2x4    9520 MB/s
Nov 13 14:56:29 node-1 kernel: [    2.906997] raid6: avx2x1   14624 MB/s
Nov 13 14:56:29 node-1 kernel: [    2.978942] raid6: avx2x2   18863 MB/s
Nov 13 14:56:29 node-1 kernel: [    3.050876] raid6: avx2x4   21378 MB/s
Nov 13 14:56:29 node-1 kernel: [    3.056752] raid6: using algorithm avx2x4 (21378 MB/s)
Nov 13 14:56:29 node-1 kernel: [    3.062791] raid6: using avx2x2 recovery algorithm
Nov 13 14:56:29 node-1 kernel: [    3.068781] Switched to clocksource tsc
Nov 13 14:56:29 node-1 kernel: [    3.070486] megasas: FW now in Ready state
Nov 13 14:56:29 node-1 kernel: [    3.070918] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.071186] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.071330] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.071472] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.071562] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.071747] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.071816] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.071924] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072029] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072157] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072270] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072395] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072501] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072663] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072725] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.072871] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Nov 13 14:56:29 node-1 kernel: [    3.073597] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov 13 14:56:29 node-1 kernel: [    3.092150] xor: automatically using best checksumming function:
Nov 13 14:56:29 node-1 kernel: [    3.127250] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov 13 14:56:29 node-1 kernel: [    3.133103] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 14:56:29 node-1 kernel: [    3.134780]    avx       : 35595.000 MB/sec
Nov 13 14:56:29 node-1 kernel: [    3.149966] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov 13 14:56:29 node-1 kernel: [    3.155516] usb 2-1.4: Manufacturer: Avocent
Nov 13 14:56:29 node-1 kernel: [    3.160818] usb 2-1.4: SerialNumber: 20111102-00000001
Nov 13 14:56:29 node-1 kernel: [    3.166056] async_tx: api initialized (async)
Nov 13 14:56:29 node-1 kernel: [    3.173011] hidraw: raw HID events driver (C) Jiri Kosina
Nov 13 14:56:29 node-1 kernel: [    3.180271] md: raid6 personality registered for level 6
Nov 13 14:56:29 node-1 kernel: [    3.181664] usbcore: registered new interface driver usbhid
Nov 13 14:56:29 node-1 kernel: [    3.181664] usbhid: USB HID core driver
Nov 13 14:56:29 node-1 kernel: [    3.195950] md: raid5 personality registered for level 5
Nov 13 14:56:29 node-1 kernel: [    3.201070] md: raid4 personality registered for level 4
Nov 13 14:56:29 node-1 kernel: [    3.206934] 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
Nov 13 14:56:29 node-1 kernel: [    3.216965] md: raid10 personality registered for level 10
Nov 13 14:56:29 node-1 kernel: [    3.217006] 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
Nov 13 14:56:29 node-1 kernel: [    3.217068] 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
Nov 13 14:56:29 node-1 kernel: [    3.217336] 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
Nov 13 14:56:29 node-1 kernel: [    3.217414] 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
Nov 13 14:56:29 node-1 kernel: [    3.217637] 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
Nov 13 14:56:29 node-1 kernel: [    3.331066] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Nov 13 14:56:29 node-1 kernel: [    3.422589] megasas:IOC Init cmd success
Nov 13 14:56:29 node-1 kernel: [    3.474558] megasas: INIT adapter done
Nov 13 14:56:29 node-1 kernel: [    3.550486] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov 13 14:56:29 node-1 kernel: [    3.557490] scsi0 : LSI SAS based MegaRAID driver
Nov 13 14:56:29 node-1 kernel: [    3.564998] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 14:56:29 node-1 kernel: [    3.590804] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 14:56:29 node-1 kernel: [    3.607247] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov 13 14:56:29 node-1 kernel: [    3.614265] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov 13 14:56:29 node-1 kernel: [    3.628255] sd 0:2:0:0: [sda] Write Protect is off
Nov 13 14:56:29 node-1 kernel: [    3.635071] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov 13 14:56:29 node-1 kernel: [    3.635091] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov 13 14:56:29 node-1 kernel: [    3.669226]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov 13 14:56:29 node-1 kernel: [    3.676400] sd 0:2:0:0: [sda] Attached SCSI disk
Nov 13 14:56:29 node-1 kernel: [    3.801701] random: lvm urandom read with 30 bits of entropy available
Nov 13 14:56:29 node-1 kernel: [    3.991909] bio: create slab <bio-1> at 1
Nov 13 14:56:29 node-1 kernel: [    4.944435] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 14:56:29 node-1 kernel: [    5.373068] random: nonblocking pool is initialized
Nov 13 14:56:29 node-1 kernel: [    5.608127] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Nov 13 14:56:29 node-1 kernel: [    5.700720] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov 13 14:56:29 node-1 kernel: [    5.855688] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov 13 14:56:29 node-1 kernel: [    5.909650] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov 13 14:56:29 node-1 kernel: [    6.003126] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 14:56:29 node-1 kernel: [    6.178616] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov 13 14:56:29 node-1 kernel: [    6.221587] XFS (dm-1): Mounting Filesystem
Nov 13 14:56:29 node-1 kernel: [    6.453637] XFS (dm-1): Ending clean mount
Nov 13 14:56:29 node-1 kernel: [    6.506324] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 14:56:29 node-1 kernel: [    6.543078] XFS (dm-2): Mounting Filesystem
Nov 13 14:56:29 node-1 kernel: [    6.629037] XFS (dm-2): Ending clean mount
Nov 13 14:56:29 node-1 kernel: [    6.821729] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 14:56:29 node-1 kernel: [    8.598694] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov 13 14:56:29 node-1 kernel: [    8.613368] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov 13 14:56:29 node-1 kernel: [    8.797110] systemd-udevd[805]: starting version 204
Nov 13 14:56:29 node-1 kernel: [    9.051222] IPMI System Interface driver.
Nov 13 14:56:29 node-1 kernel: [    9.051286] ipmi_si: probing via ACPI
Nov 13 14:56:29 node-1 kernel: [    9.051299] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov 13 14:56:29 node-1 kernel: [    9.051300] ipmi_si: Adding ACPI-specified kcs state machine
Nov 13 14:56:29 node-1 kernel: [    9.051314] ipmi_si: probing via SMBIOS
Nov 13 14:56:29 node-1 kernel: [    9.051315] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 14:56:29 node-1 kernel: [    9.051316] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov 13 14:56:29 node-1 kernel: [    9.051317] ipmi_si: probing via SPMI
Nov 13 14:56:29 node-1 kernel: [    9.051318] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 14:56:29 node-1 kernel: [    9.051319] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov 13 14:56:29 node-1 kernel: [    9.051320] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov 13 14:56:29 node-1 kernel: [    9.052900] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov 13 14:56:29 node-1 kernel: [    9.052906] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 14:56:29 node-1 kernel: [    9.052909] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov 13 14:56:29 node-1 kernel: [    9.052911] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 14:56:29 node-1 kernel: [    9.052950] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 13 14:56:29 node-1 kernel: [    9.061550] wmi: Mapper loaded
Nov 13 14:56:29 node-1 kernel: [    9.067231] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov 13 14:56:29 node-1 kernel: [    9.137105] power_meter ACPI000D:00: Found ACPI power meter.
Nov 13 14:56:29 node-1 kernel: [    9.137114] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov 13 14:56:29 node-1 kernel: [    9.180574] systemd-udevd[823]: renamed network interface eth0 to enp6s0
Nov 13 14:56:29 node-1 kernel: [    9.198577] systemd-udevd[857]: renamed network interface eth1 to enp7s0
Nov 13 14:56:29 node-1 kernel: [    9.230096] systemd-udevd[830]: renamed network interface eth2 to enp8s0
Nov 13 14:56:29 node-1 kernel: [    9.232848] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov 13 14:56:29 node-1 kernel: [    9.232857] ipmi_si 00:09: IPMI kcs interface initialized
Nov 13 14:56:29 node-1 kernel: [    9.253957] systemd-udevd[824]: renamed network interface eth3 to enp9s0
Nov 13 14:56:29 node-1 kernel: [    9.706625] type=1400 audit(1479048961.737:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1097 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.706782] type=1400 audit(1479048961.737:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1097 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.706909] type=1400 audit(1479048961.737:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1097 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.712610] type=1400 audit(1479048961.741:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1099 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.712751] type=1400 audit(1479048961.741:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1099 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.712873] type=1400 audit(1479048961.741:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1099 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.713089] type=1400 audit(1479048961.741:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1095 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.713245] type=1400 audit(1479048961.745:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1095 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.713454] type=1400 audit(1479048961.745:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1095 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [    9.724130] type=1400 audit(1479048961.753:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Nov 13 14:56:29 node-1 kernel: [   10.273885] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov 13 14:56:29 node-1 kernel: [   10.275115] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov 13 14:56:29 node-1 kernel: [   10.518363] enic 0000:06:00.0 enp6s0: Link UP
Nov 13 14:56:29 node-1 kernel: [   10.519386] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov 13 14:56:29 node-1 kernel: [   10.519391] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov 13 14:56:29 node-1 kernel: [   20.508646] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov 13 14:56:31 node-1 failsafe: Failsafe of 120 seconds reached.
Nov 13 14:56:31 node-1 kernel: [   39.685253] init: failsafe main process (8449) killed by TERM signal
Nov 13 14:56:31 node-1 dbus[8504]: [system] AppArmor D-Bus mediation is enabled
Nov 13 14:56:31 node-1 kernel: [   39.863885] audit_printk_skb: 30 callbacks suppressed
Nov 13 14:56:31 node-1 kernel: [   39.863886] type=1400 audit(1479048991.331:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8567 comm="apparmor_parser"
Nov 13 14:56:31 node-1 kernel: [   39.865401] type=1400 audit(1479048991.331:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8566 comm="apparmor_parser"
Nov 13 14:56:31 node-1 kernel: [   39.865405] type=1400 audit(1479048991.331:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8566 comm="apparmor_parser"
Nov 13 14:56:31 node-1 kernel: [   39.865408] type=1400 audit(1479048991.331:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8566 comm="apparmor_parser"
Nov 13 14:56:31 node-1 kernel: [   39.865627] type=1400 audit(1479048991.331:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8566 comm="apparmor_parser"
Nov 13 14:56:31 node-1 kernel: [   39.865629] type=1400 audit(1479048991.331:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8566 comm="apparmor_parser"
Nov 13 14:56:31 node-1 kernel: [   39.865742] type=1400 audit(1479048991.331:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8566 comm="apparmor_parser"
Nov 13 14:56:31 node-1 kernel: [   39.965123] type=1400 audit(1479048991.431:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8569 comm="apparmor_parser"
Nov 13 14:56:31 node-1 anacron[8645]: Anacron 2.3 started on 2016-11-13
Nov 13 14:56:31 node-1 cron[8606]: (CRON) INFO (pidfile fd = 3)
Nov 13 14:56:31 node-1 anacron[8645]: Will run job `cron.daily' in 5 min.
Nov 13 14:56:31 node-1 anacron[8645]: Will run job `cron.weekly' in 10 min.
Nov 13 14:56:31 node-1 anacron[8645]: Will run job `cron.monthly' in 15 min.
Nov 13 14:56:31 node-1 anacron[8645]: Jobs will be executed sequentially
Nov 13 14:56:31 node-1 cron[8649]: (CRON) STARTUP (fork ok)
Nov 13 14:56:31 node-1 multipathd: path checkers start up
Nov 13 14:56:31 node-1 cron[8649]: (CRON) INFO (Running @reboot jobs)
Nov 13 14:56:32 node-1 postfix/master[8786]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov 13 14:56:35 node-1 puppet-agent[9100]: Reopening log files
Nov 13 14:56:36 node-1 puppet-agent[9100]: Could not request certificate: Connection refused - connect(2)
Nov 13 14:56:49 node-1 puppet-user[9361]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov 13 14:56:49 node-1 puppet-user[9361]: Compiled catalog for node-1.domain.tld in environment production in 0.01 seconds
Nov 13 14:56:50 node-1 puppet-user[9361]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov 13 14:56:50 node-1 puppet-user[9361]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov 13 14:56:50 node-1 puppet-user[9361]: Finished catalog run in 1.45 seconds
Nov 13 14:56:52 node-1 multipathd: uevent trigger error
Nov 13 14:56:52 node-1 puppet-user[9816]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 14:56:52 node-1 puppet-user[9816]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Nov 13 14:56:52 node-1 puppet-user[9816]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov 13 14:56:52 node-1 puppet-user[9816]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov 13 14:56:52 node-1 puppet-user[9816]: (/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"]'
Nov 13 14:56:52 node-1 puppet-user[9816]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov 13 14:56:52 node-1 puppet-user[9816]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov 13 14:56:52 node-1 puppet-user[9816]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov 13 14:56:52 node-1 puppet-user[9816]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov 13 14:56:52 node-1 puppet-user[9816]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov 13 14:56:52 node-1 puppet-user[9816]: Finished catalog run in 0.09 seconds
Nov 13 14:56:53 node-1 puppet-user[10279]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov 13 14:56:54 node-1 puppet-user[10279]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov 13 14:56:54 node-1 puppet-user[10279]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov 13 14:56:54 node-1 puppet-user[10279]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov 13 14:56:54 node-1 puppet-user[10279]: Finished catalog run in 0.03 seconds
Nov 13 14:56:56 node-1 puppet-user[10744]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov 13 14:56:56 node-1 puppet-user[10744]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov 13 14:56:56 node-1 puppet-user[10744]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov 13 14:56:56 node-1 puppet-user[10744]: Finished catalog run in 0.04 seconds
Nov 13 14:56:57 node-1 puppet-user[11198]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov 13 14:56:57 node-1 puppet-user[11198]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Nov 13 14:56:57 node-1 puppet-user[11198]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov 13 14:56:58 node-1 puppet-user[11198]: (/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
Nov 13 14:56:58 node-1 puppet-user[11198]: (/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
Nov 13 14:56:58 node-1 puppet-user[11198]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Nov 13 14:56:58 node-1 puppet-user[11198]: Finished catalog run in 1.22 seconds
Nov 13 14:57:00 node-1 kernel: [   68.613807] init: plymouth-upstart-bridge main process ended, respawning
Nov 13 14:57:00 node-1 puppet-user[11730]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov 13 14:57:00 node-1 puppet-agent[9100]: Could not run: SIGTERM
Nov 13 14:57:00 node-1 puppet-user[11730]: Compiled catalog for node-1.domain.tld in environment production in 0.24 seconds
Nov 13 14:57:00 node-1 kernel: [   68.941558] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 13 14:57:00 node-1 ec2: 
Nov 13 14:57:00 node-1 ec2: #############################################################
Nov 13 14:57:00 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov 13 14:57:00 node-1 ec2: 1024 33:1f:5e:92:76:6b:55:48:34:77:69:17:e5:93:cc:52  root@node-1.domain.tld (DSA)
Nov 13 14:57:00 node-1 ec2: 256 34:88:17:21:c4:10:b2:be:a8:ec:bc:af:a5:07:12:55  root@node-1.domain.tld (ECDSA)
Nov 13 14:57:00 node-1 ec2: 256 ef:19:4d:df:25:90:80:01:71:16:f3:39:e5:3d:5a:e4  root@node-1.domain.tld (ED25519)
Nov 13 14:57:00 node-1 ec2: 2048 f7:18:f1:ad:85:a5:5a:77:95:24:f8:7f:51:78:63:cb  root@node-1.domain.tld (RSA)
Nov 13 14:57:00 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov 13 14:57:00 node-1 ec2: #############################################################
Nov 13 14:57:00 node-1 puppet-user[11730]: (/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
Nov 13 14:57:00 node-1 puppet-user[11730]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Nov 13 14:57:00 node-1 puppet-user[11730]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov 13 14:57:00 node-1 puppet-user[11730]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov 13 14:57:00 node-1 puppet-user[11730]: (/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
Nov 13 14:57:00 node-1 puppet-user[11730]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov 13 14:57:00 node-1 puppet-user[11730]: Finished catalog run in 0.40 seconds
Nov 13 14:57:01 node-1 CRON[12404]: (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")
Nov 13 14:57:02 node-1 puppet-user[12389]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov 13 14:57:02 node-1 puppet-user[12389]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Nov 13 14:57:02 node-1 puppet-user[12389]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov 13 14:57:02 node-1 kernel: [   71.208564] nr_pdflush_threads exported in /proc is scheduled for removal
Nov 13 14:57:02 node-1 kernel: [   71.208619] 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.
Nov 13 14:57:02 node-1 puppet-user[12389]: (/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'
Nov 13 14:57:02 node-1 puppet-user[12389]: Finished catalog run in 0.06 seconds
Nov 13 14:57:04 node-1 puppet-user[12859]: (Scope(Class[main])) MODULAR: sync_time
Nov 13 14:57:04 node-1 puppet-user[12859]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov 13 14:57:04 node-1 ntpdate[13287]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov 13 14:57:04 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 14:57:04 node-1 nailgun-agent: I, [2016-11-13T14:57:04.831588 #12409]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov 13 14:57:10 node-1 ntpdate[13287]: adjust time server 10.20.0.2 offset 0.297190 sec
Nov 13 14:57:10 node-1 puppet-user[12859]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov 13 14:57:10 node-1 puppet-user[12859]: Finished catalog run in 6.18 seconds
Nov 13 14:57:14 node-1 puppet-user[13633]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 14:57:14 node-1 puppet-user[13633]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov 13 14:57:14 node-1 puppet-user[13633]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov 13 14:57:14 node-1 puppet-user[13633]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Nov 13 14:57:14 node-1 puppet-user[13633]: Finished catalog run in 0.07 seconds
Nov 13 14:57:16 node-1 puppet-user[14088]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov 13 14:57:16 node-1 puppet-user[14088]: Compiled catalog for node-1.domain.tld in environment production in 0.49 seconds
Nov 13 14:57:16 node-1 puppet-user[14088]: (/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
Nov 13 14:57:16 node-1 puppet-user[14088]: (/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
Nov 13 14:57:16 node-1 puppet-user[14088]: (/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
Nov 13 14:57:16 node-1 puppet-user[14088]: (/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
Nov 13 14:57:16 node-1 puppet-user[14088]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov 13 14:57:16 node-1 puppet-user[14088]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov 13 14:57:16 node-1 puppet-user[14088]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov 13 14:57:16 node-1 puppet-user[14088]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov 13 14:57:16 node-1 puppet-user[14088]: (/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
Nov 13 14:57:16 node-1 puppet-user[14088]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov 13 14:57:17 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 14:57:17 node-1 nailgun-agent: I, [2016-11-13T14:57:17.359511 #12409]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Nov 13 14:57:17 node-1 puppet-user[14088]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov 13 14:57:17 node-1 puppet-user[14088]: Finished catalog run in 1.03 seconds
Nov 13 14:57:19 node-1 puppet-user[14780]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov 13 14:57:19 node-1 puppet-user[14780]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Nov 13 14:57:22 node-1 puppet-user[14780]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov 13 14:57:53 node-1 puppet-user[14780]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov 13 14:57:53 node-1 puppet-user[14780]: Finished catalog run in 33.52 seconds
Nov 13 14:57:55 node-1 puppet-user[17252]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov 13 14:57:55 node-1 puppet-user[17252]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Nov 13 14:57:55 node-1 puppet-user[17252]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov 13 14:57:55 node-1 puppet-user[17252]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov 13 14:57:55 node-1 puppet-user[17252]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov 13 14:57:55 node-1 puppet-user[17252]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov 13 14:57:55 node-1 puppet-user[17252]: Finished catalog run in 0.13 seconds
Nov 13 14:57:57 node-1 puppet-user[17722]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov 13 14:57:58 node-1 puppet-user[17722]: Compiled catalog for node-1.domain.tld in environment production in 0.86 seconds
Nov 13 14:57:58 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov 13 14:57:58 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov 13 14:57:58 node-1 crontab[18155]: (root) LIST (root)
Nov 13 14:57:58 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov 13 14:57:58 node-1 crontab[18156]: (root) REPLACE (root)
Nov 13 14:58:00 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov 13 14:58:00 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov 13 14:58:00 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov 13 14:58:00 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov 13 14:58:00 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov 13 14:58:00 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov 13 14:58:01 node-1 CRON[18291]: (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")
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/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
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov 13 14:58:01 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov 13 14:58:02 node-1 puppet-user[17722]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov 13 14:58:02 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8422" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 14:58:02 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov 13 14:58:03 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:17 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:17 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:17 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:17 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:17 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:17 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:19 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:19 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:19 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:19 node-1 multipathd: uevent trigger error
<27>Nov 13 14:58:19 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:15 node-1 ntpdate[27937]: no servers can be used, exiting
<27>Nov 13 14:59:48 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:48 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:48 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:48 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:48 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:51 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:51 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:51 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:51 node-1 multipathd: uevent trigger error
<27>Nov 13 14:59:51 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:00:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:11 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:11 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:11 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:11 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:11 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:14 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 15:01:14 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 15:01:20 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 15:01:20 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 15:01:25 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 15:01:31 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 15:01:31 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 15:01:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:01:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:07 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:07 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:07 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:07 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:07 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:09 node-1 haproxy[17525]: 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>Nov 13 15:02:09 node-1 haproxy[17525]: Backup Server mysqld/node-3 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>Nov 13 15:02:10 node-1 haproxy[17529]: Backup Server mysqld/node-4 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>Nov 13 15:02:10 node-1 haproxy[17529]: proxy mysqld has no server available!
<27>Nov 13 15:02:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:15 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:17 node-1 haproxy[20011]: 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>Nov 13 15:02:18 node-1 haproxy[20015]: Backup Server mysqld/node-3 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>Nov 13 15:02:18 node-1 haproxy[20015]: Backup Server mysqld/node-4 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>Nov 13 15:02:18 node-1 haproxy[20015]: proxy mysqld has no server available!
<129>Nov 13 15:02:18 node-1 haproxy[20015]: 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>Nov 13 15:02:18 node-1 haproxy[20015]: Server object-storage/node-3 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>Nov 13 15:02:19 node-1 haproxy[20015]: Server object-storage/node-4 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>Nov 13 15:02:19 node-1 haproxy[20015]: proxy object-storage has no server available!
<27>Nov 13 15:02:20 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:20 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:21 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:21 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:21 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:23 node-1 haproxy[21407]: 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>Nov 13 15:02:23 node-1 haproxy[21407]: Server neutron/node-3 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>Nov 13 15:02:23 node-1 haproxy[21407]: Server neutron/node-4 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>Nov 13 15:02:23 node-1 haproxy[21407]: proxy neutron has no server available!
<129>Nov 13 15:02:23 node-1 haproxy[21407]: 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>Nov 13 15:02:23 node-1 haproxy[21407]: Backup Server mysqld/node-3 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>Nov 13 15:02:23 node-1 haproxy[21407]: Backup Server mysqld/node-4 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>Nov 13 15:02:23 node-1 haproxy[21407]: proxy mysqld has no server available!
<129>Nov 13 15:02:24 node-1 haproxy[21411]: 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>Nov 13 15:02:24 node-1 haproxy[21411]: Server object-storage/node-3 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>Nov 13 15:02:24 node-1 haproxy[21411]: Server object-storage/node-4 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>Nov 13 15:02:24 node-1 haproxy[21411]: proxy object-storage has no server available!
<27>Nov 13 15:02:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:26 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:26 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:26 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:26 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:28 node-1 haproxy[22688]: 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>Nov 13 15:02:28 node-1 haproxy[22688]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 15:02:28 node-1 haproxy[22688]: Server keystone-1/node-4 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>Nov 13 15:02:28 node-1 haproxy[22688]: proxy keystone-1 has no server available!
<129>Nov 13 15:02:28 node-1 haproxy[22688]: 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>Nov 13 15:02:28 node-1 haproxy[22688]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 15:02:29 node-1 haproxy[22692]: Server keystone-2/node-4 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>Nov 13 15:02:29 node-1 haproxy[22692]: proxy keystone-2 has no server available!
<129>Nov 13 15:02:29 node-1 haproxy[22692]: 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>Nov 13 15:02:29 node-1 haproxy[22692]: Server neutron/node-3 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>Nov 13 15:02:29 node-1 haproxy[22692]: Server neutron/node-4 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>Nov 13 15:02:29 node-1 haproxy[22692]: proxy neutron has no server available!
<129>Nov 13 15:02:29 node-1 haproxy[22692]: 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>Nov 13 15:02:29 node-1 haproxy[22692]: Backup Server mysqld/node-3 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>Nov 13 15:02:29 node-1 haproxy[22692]: Backup Server mysqld/node-4 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>Nov 13 15:02:29 node-1 haproxy[22692]: proxy mysqld has no server available!
<129>Nov 13 15:02:29 node-1 haproxy[22692]: 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>Nov 13 15:02:30 node-1 haproxy[22692]: Server object-storage/node-3 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>Nov 13 15:02:30 node-1 haproxy[22692]: Server object-storage/node-4 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>Nov 13 15:02:30 node-1 haproxy[22692]: proxy object-storage has no server available!
<27>Nov 13 15:02:31 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:31 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:31 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:31 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:31 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:31 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:33 node-1 haproxy[23905]: 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>Nov 13 15:02:33 node-1 haproxy[23905]: Server keystone-1/node-3 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>Nov 13 15:02:33 node-1 haproxy[23905]: Server keystone-1/node-4 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>Nov 13 15:02:33 node-1 haproxy[23905]: proxy keystone-1 has no server available!
<129>Nov 13 15:02:33 node-1 haproxy[23905]: 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>Nov 13 15:02:34 node-1 haproxy[23909]: Server keystone-2/node-3 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>Nov 13 15:02:34 node-1 haproxy[23909]: Server keystone-2/node-4 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>Nov 13 15:02:34 node-1 haproxy[23909]: proxy keystone-2 has no server available!
<129>Nov 13 15:02:34 node-1 haproxy[23909]: 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>Nov 13 15:02:34 node-1 haproxy[23909]: Server neutron/node-3 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>Nov 13 15:02:34 node-1 haproxy[23909]: Server neutron/node-4 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>Nov 13 15:02:34 node-1 haproxy[23909]: proxy neutron has no server available!
<129>Nov 13 15:02:34 node-1 haproxy[23909]: 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>Nov 13 15:02:34 node-1 haproxy[23909]: Backup Server mysqld/node-3 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>Nov 13 15:02:34 node-1 haproxy[23909]: Backup Server mysqld/node-4 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>Nov 13 15:02:34 node-1 haproxy[23909]: proxy mysqld has no server available!
<129>Nov 13 15:02:34 node-1 haproxy[23909]: 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>Nov 13 15:02:34 node-1 haproxy[23909]: Server object-storage/node-3 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>Nov 13 15:02:35 node-1 haproxy[23909]: Server object-storage/node-4 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>Nov 13 15:02:35 node-1 haproxy[23909]: proxy object-storage has no server available!
<129>Nov 13 15:02:35 node-1 haproxy[23909]: 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>Nov 13 15:02:35 node-1 haproxy[23909]: Server aodh/node-3 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>Nov 13 15:02:35 node-1 haproxy[23909]: Server aodh/node-4 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>Nov 13 15:02:35 node-1 haproxy[23909]: proxy aodh has no server available!
<27>Nov 13 15:02:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:36 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:39 node-1 haproxy[25164]: 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>Nov 13 15:02:39 node-1 haproxy[25164]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 15:02:39 node-1 haproxy[25164]: Server keystone-1/node-4 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>Nov 13 15:02:39 node-1 haproxy[25164]: proxy keystone-1 has no server available!
<129>Nov 13 15:02:39 node-1 haproxy[25164]: 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>Nov 13 15:02:39 node-1 haproxy[25164]: Server keystone-2/node-3 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>Nov 13 15:02:39 node-1 haproxy[25164]: Server keystone-2/node-4 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>Nov 13 15:02:39 node-1 haproxy[25164]: proxy keystone-2 has no server available!
<129>Nov 13 15:02:39 node-1 haproxy[25164]: 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>Nov 13 15:02:39 node-1 haproxy[25164]: Server neutron/node-3 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>Nov 13 15:02:39 node-1 haproxy[25164]: Server neutron/node-4 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>Nov 13 15:02:39 node-1 haproxy[25164]: proxy neutron has no server available!
<129>Nov 13 15:02:39 node-1 haproxy[25164]: 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>Nov 13 15:02:40 node-1 haproxy[25168]: Backup Server mysqld/node-3 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>Nov 13 15:02:40 node-1 haproxy[25168]: Backup Server mysqld/node-4 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>Nov 13 15:02:40 node-1 haproxy[25168]: proxy mysqld has no server available!
<129>Nov 13 15:02:40 node-1 haproxy[25168]: 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>Nov 13 15:02:40 node-1 haproxy[25168]: Server object-storage/node-3 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>Nov 13 15:02:40 node-1 haproxy[25168]: Server object-storage/node-4 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>Nov 13 15:02:40 node-1 haproxy[25168]: proxy object-storage has no server available!
<129>Nov 13 15:02:40 node-1 haproxy[25168]: 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>Nov 13 15:02:40 node-1 haproxy[25168]: Server aodh/node-3 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>Nov 13 15:02:40 node-1 haproxy[25168]: Server aodh/node-4 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>Nov 13 15:02:40 node-1 haproxy[25168]: proxy aodh has no server available!
<129>Nov 13 15:02:40 node-1 haproxy[25168]: 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>Nov 13 15:02:40 node-1 haproxy[25168]: Server ceilometer/node-3 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>Nov 13 15:02:40 node-1 haproxy[25168]: Server ceilometer/node-4 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>Nov 13 15:02:40 node-1 haproxy[25168]: proxy ceilometer has no server available!
<27>Nov 13 15:02:42 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:42 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:42 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:42 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:42 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:44 node-1 haproxy[26392]: 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>Nov 13 15:02:44 node-1 haproxy[26392]: Server keystone-1/node-3 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>Nov 13 15:02:44 node-1 haproxy[26392]: Server keystone-1/node-4 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>Nov 13 15:02:44 node-1 haproxy[26392]: proxy keystone-1 has no server available!
<129>Nov 13 15:02:44 node-1 haproxy[26392]: 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>Nov 13 15:02:44 node-1 haproxy[26392]: Server keystone-2/node-3 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>Nov 13 15:02:44 node-1 haproxy[26392]: Server keystone-2/node-4 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>Nov 13 15:02:44 node-1 haproxy[26392]: proxy keystone-2 has no server available!
<129>Nov 13 15:02:44 node-1 haproxy[26392]: 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>Nov 13 15:02:45 node-1 haproxy[26403]: Server neutron/node-3 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>Nov 13 15:02:45 node-1 haproxy[26403]: Server neutron/node-4 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>Nov 13 15:02:45 node-1 haproxy[26403]: proxy neutron has no server available!
<129>Nov 13 15:02:45 node-1 haproxy[26403]: 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>Nov 13 15:02:45 node-1 haproxy[26403]: Backup Server mysqld/node-3 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>Nov 13 15:02:45 node-1 haproxy[26403]: Backup Server mysqld/node-4 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>Nov 13 15:02:45 node-1 haproxy[26403]: proxy mysqld has no server available!
<129>Nov 13 15:02:45 node-1 haproxy[26403]: 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>Nov 13 15:02:45 node-1 haproxy[26403]: Server object-storage/node-3 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>Nov 13 15:02:45 node-1 haproxy[26403]: Server object-storage/node-4 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>Nov 13 15:02:45 node-1 haproxy[26403]: proxy object-storage has no server available!
<129>Nov 13 15:02:45 node-1 haproxy[26403]: 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>Nov 13 15:02:45 node-1 haproxy[26403]: Server aodh/node-3 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>Nov 13 15:02:45 node-1 haproxy[26403]: Server aodh/node-4 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>Nov 13 15:02:45 node-1 haproxy[26403]: proxy aodh has no server available!
<129>Nov 13 15:02:46 node-1 haproxy[26403]: 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>Nov 13 15:02:46 node-1 haproxy[26403]: Server ceilometer/node-3 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>Nov 13 15:02:46 node-1 haproxy[26403]: Server ceilometer/node-4 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>Nov 13 15:02:46 node-1 haproxy[26403]: proxy ceilometer has no server available!
<27>Nov 13 15:02:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:47 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:49 node-1 haproxy[27622]: 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>Nov 13 15:02:49 node-1 haproxy[27622]: 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>Nov 13 15:02:49 node-1 haproxy[27622]: Server keystone-1/node-3 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>Nov 13 15:02:50 node-1 haproxy[27626]: Server keystone-1/node-4 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>Nov 13 15:02:50 node-1 haproxy[27626]: proxy keystone-1 has no server available!
<129>Nov 13 15:02:50 node-1 haproxy[27626]: 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>Nov 13 15:02:50 node-1 haproxy[27626]: Server keystone-2/node-3 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>Nov 13 15:02:50 node-1 haproxy[27626]: Server keystone-2/node-4 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>Nov 13 15:02:50 node-1 haproxy[27626]: proxy keystone-2 has no server available!
<129>Nov 13 15:02:50 node-1 haproxy[27626]: 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>Nov 13 15:02:50 node-1 haproxy[27626]: Server neutron/node-3 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>Nov 13 15:02:50 node-1 haproxy[27626]: Server neutron/node-4 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>Nov 13 15:02:50 node-1 haproxy[27626]: proxy neutron has no server available!
<129>Nov 13 15:02:50 node-1 haproxy[27626]: 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>Nov 13 15:02:50 node-1 haproxy[27626]: Backup Server mysqld/node-3 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>Nov 13 15:02:50 node-1 haproxy[27626]: Backup Server mysqld/node-4 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>Nov 13 15:02:50 node-1 haproxy[27626]: proxy mysqld has no server available!
<129>Nov 13 15:02:50 node-1 haproxy[27626]: 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>Nov 13 15:02:50 node-1 haproxy[27626]: Server object-storage/node-3 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>Nov 13 15:02:50 node-1 haproxy[27626]: Server object-storage/node-4 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>Nov 13 15:02:50 node-1 haproxy[27626]: proxy object-storage has no server available!
<129>Nov 13 15:02:51 node-1 haproxy[27626]: 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>Nov 13 15:02:51 node-1 haproxy[27626]: Server aodh/node-3 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>Nov 13 15:02:51 node-1 haproxy[27626]: Server aodh/node-4 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>Nov 13 15:02:51 node-1 haproxy[27626]: proxy aodh has no server available!
<129>Nov 13 15:02:51 node-1 haproxy[27626]: 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>Nov 13 15:02:51 node-1 haproxy[27626]: Server ceilometer/node-3 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>Nov 13 15:02:51 node-1 haproxy[27626]: Server ceilometer/node-4 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>Nov 13 15:02:51 node-1 haproxy[27626]: proxy ceilometer has no server available!
<27>Nov 13 15:02:52 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:52 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:52 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:52 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:52 node-1 multipathd: uevent trigger error
<129>Nov 13 15:02:55 node-1 haproxy[28883]: 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>Nov 13 15:02:55 node-1 haproxy[28883]: 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>Nov 13 15:02:55 node-1 haproxy[28883]: Server keystone-1/node-3 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>Nov 13 15:02:55 node-1 haproxy[28883]: Server keystone-1/node-4 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>Nov 13 15:02:55 node-1 haproxy[28883]: proxy keystone-1 has no server available!
<129>Nov 13 15:02:55 node-1 haproxy[28883]: 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>Nov 13 15:02:55 node-1 haproxy[28883]: Server keystone-2/node-3 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>Nov 13 15:02:55 node-1 haproxy[28883]: Server keystone-2/node-4 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>Nov 13 15:02:55 node-1 haproxy[28883]: proxy keystone-2 has no server available!
<129>Nov 13 15:02:55 node-1 haproxy[28883]: 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>Nov 13 15:02:55 node-1 haproxy[28883]: Server glance-api/node-3 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>Nov 13 15:02:55 node-1 haproxy[28883]: Server glance-api/node-4 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>Nov 13 15:02:55 node-1 haproxy[28883]: proxy glance-api has no server available!
<129>Nov 13 15:02:56 node-1 haproxy[28889]: 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server glance-glare/node-3 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server glance-glare/node-4 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>Nov 13 15:02:56 node-1 haproxy[28889]: proxy glance-glare has no server available!
<129>Nov 13 15:02:56 node-1 haproxy[28889]: 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server neutron/node-3 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server neutron/node-4 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>Nov 13 15:02:56 node-1 haproxy[28889]: proxy neutron has no server available!
<129>Nov 13 15:02:56 node-1 haproxy[28889]: 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server glance-registry/node-3 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server glance-registry/node-4 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>Nov 13 15:02:56 node-1 haproxy[28889]: proxy glance-registry has no server available!
<129>Nov 13 15:02:56 node-1 haproxy[28889]: 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>Nov 13 15:02:56 node-1 haproxy[28889]: Backup Server mysqld/node-3 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>Nov 13 15:02:56 node-1 haproxy[28889]: Backup Server mysqld/node-4 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>Nov 13 15:02:56 node-1 haproxy[28889]: proxy mysqld has no server available!
<129>Nov 13 15:02:56 node-1 haproxy[28889]: 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server object-storage/node-3 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server object-storage/node-4 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>Nov 13 15:02:56 node-1 haproxy[28889]: proxy object-storage has no server available!
<129>Nov 13 15:02:56 node-1 haproxy[28889]: 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server aodh/node-3 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>Nov 13 15:02:56 node-1 haproxy[28889]: Server aodh/node-4 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>Nov 13 15:02:56 node-1 haproxy[28889]: proxy aodh has no server available!
<129>Nov 13 15:02:57 node-1 haproxy[28889]: 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>Nov 13 15:02:57 node-1 haproxy[28889]: Server ceilometer/node-3 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>Nov 13 15:02:57 node-1 haproxy[28889]: Server ceilometer/node-4 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>Nov 13 15:02:57 node-1 haproxy[28889]: proxy ceilometer has no server available!
<27>Nov 13 15:02:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:02:58 node-1 multipathd: uevent trigger error
<129>Nov 13 15:03:01 node-1 haproxy[30160]: 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>Nov 13 15:03:01 node-1 haproxy[30160]: 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server keystone-1/node-3 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server keystone-1/node-4 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>Nov 13 15:03:01 node-1 haproxy[30160]: proxy keystone-1 has no server available!
<129>Nov 13 15:03:01 node-1 haproxy[30160]: 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server keystone-2/node-3 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server keystone-2/node-4 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>Nov 13 15:03:01 node-1 haproxy[30160]: proxy keystone-2 has no server available!
<129>Nov 13 15:03:01 node-1 haproxy[30160]: 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server nova-api/node-3 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server nova-api/node-4 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>Nov 13 15:03:01 node-1 haproxy[30160]: proxy nova-api has no server available!
<129>Nov 13 15:03:01 node-1 haproxy[30160]: 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server nova-metadata-api/node-3 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server nova-metadata-api/node-4 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>Nov 13 15:03:01 node-1 haproxy[30160]: proxy nova-metadata-api has no server available!
<129>Nov 13 15:03:01 node-1 haproxy[30160]: 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server glance-api/node-3 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>Nov 13 15:03:01 node-1 haproxy[30160]: Server glance-api/node-4 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>Nov 13 15:03:01 node-1 haproxy[30160]: proxy glance-api has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server glance-glare/node-3 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server glance-glare/node-4 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>Nov 13 15:03:02 node-1 haproxy[30164]: proxy glance-glare has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server neutron/node-3 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server neutron/node-4 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>Nov 13 15:03:02 node-1 haproxy[30164]: proxy neutron has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server glance-registry/node-3 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server glance-registry/node-4 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>Nov 13 15:03:02 node-1 haproxy[30164]: proxy glance-registry has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:02 node-1 haproxy[30164]: Backup Server mysqld/node-3 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>Nov 13 15:03:02 node-1 haproxy[30164]: Backup Server mysqld/node-4 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>Nov 13 15:03:02 node-1 haproxy[30164]: proxy mysqld has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server object-storage/node-3 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server object-storage/node-4 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>Nov 13 15:03:02 node-1 haproxy[30164]: proxy object-storage has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server aodh/node-3 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server aodh/node-4 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>Nov 13 15:03:02 node-1 haproxy[30164]: proxy aodh has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server ceilometer/node-3 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>Nov 13 15:03:02 node-1 haproxy[30164]: Server ceilometer/node-4 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>Nov 13 15:03:02 node-1 haproxy[30164]: proxy ceilometer has no server available!
<129>Nov 13 15:03:02 node-1 haproxy[30164]: 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>Nov 13 15:03:03 node-1 haproxy[30164]: Server nova-novncproxy/node-3 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>Nov 13 15:03:03 node-1 haproxy[30164]: Server nova-novncproxy/node-4 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>Nov 13 15:03:03 node-1 haproxy[30164]: proxy nova-novncproxy has no server available!
<27>Nov 13 15:03:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:04 node-1 multipathd: uevent trigger error
<129>Nov 13 15:03:06 node-1 haproxy[31402]: 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>Nov 13 15:03:06 node-1 haproxy[31402]: 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>Nov 13 15:03:06 node-1 haproxy[31402]: Server keystone-1/node-3 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>Nov 13 15:03:06 node-1 haproxy[31402]: Server keystone-1/node-4 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>Nov 13 15:03:06 node-1 haproxy[31402]: proxy keystone-1 has no server available!
<129>Nov 13 15:03:06 node-1 haproxy[31402]: 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>Nov 13 15:03:06 node-1 haproxy[31402]: Server keystone-2/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server keystone-2/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy keystone-2 has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server nova-api/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server nova-api/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy nova-api has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server nova-metadata-api/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server nova-metadata-api/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy nova-metadata-api has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Backup Server cinder-api/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Backup Server cinder-api/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy cinder-api has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server glance-api/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server glance-api/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy glance-api has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server glance-glare/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server glance-glare/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy glance-glare has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server neutron/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server neutron/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy neutron has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server glance-registry/node-3 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>Nov 13 15:03:07 node-1 haproxy[31406]: Server glance-registry/node-4 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>Nov 13 15:03:07 node-1 haproxy[31406]: proxy glance-registry has no server available!
<129>Nov 13 15:03:07 node-1 haproxy[31406]: 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>Nov 13 15:03:07 node-1 haproxy[31406]: Backup Server mysqld/node-3 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>Nov 13 15:03:08 node-1 haproxy[31406]: Backup Server mysqld/node-4 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>Nov 13 15:03:08 node-1 haproxy[31406]: proxy mysqld has no server available!
<129>Nov 13 15:03:08 node-1 haproxy[31406]: 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server object-storage/node-3 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server object-storage/node-4 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>Nov 13 15:03:08 node-1 haproxy[31406]: proxy object-storage has no server available!
<129>Nov 13 15:03:08 node-1 haproxy[31406]: 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server aodh/node-3 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server aodh/node-4 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>Nov 13 15:03:08 node-1 haproxy[31406]: proxy aodh has no server available!
<129>Nov 13 15:03:08 node-1 haproxy[31406]: 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server ceilometer/node-3 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server ceilometer/node-4 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>Nov 13 15:03:08 node-1 haproxy[31406]: proxy ceilometer has no server available!
<129>Nov 13 15:03:08 node-1 haproxy[31406]: 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server nova-novncproxy/node-3 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>Nov 13 15:03:08 node-1 haproxy[31406]: Server nova-novncproxy/node-4 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>Nov 13 15:03:08 node-1 haproxy[31406]: proxy nova-novncproxy has no server available!
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:09 node-1 multipathd: uevent trigger error
<129>Nov 13 15:03:12 node-1 haproxy[372]: 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>Nov 13 15:03:12 node-1 haproxy[372]: 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>Nov 13 15:03:12 node-1 haproxy[372]: Server keystone-1/node-3 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>Nov 13 15:03:12 node-1 haproxy[372]: Server keystone-1/node-4 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>Nov 13 15:03:12 node-1 haproxy[372]: proxy keystone-1 has no server available!
<129>Nov 13 15:03:12 node-1 haproxy[372]: 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>Nov 13 15:03:12 node-1 haproxy[372]: Server keystone-2/node-3 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>Nov 13 15:03:12 node-1 haproxy[372]: Server keystone-2/node-4 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>Nov 13 15:03:12 node-1 haproxy[372]: proxy keystone-2 has no server available!
<129>Nov 13 15:03:12 node-1 haproxy[372]: 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>Nov 13 15:03:12 node-1 haproxy[372]: Server nova-api/node-3 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>Nov 13 15:03:12 node-1 haproxy[372]: Server nova-api/node-4 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>Nov 13 15:03:12 node-1 haproxy[372]: proxy nova-api has no server available!
<129>Nov 13 15:03:12 node-1 haproxy[372]: 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>Nov 13 15:03:12 node-1 haproxy[372]: Server nova-metadata-api/node-3 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>Nov 13 15:03:12 node-1 haproxy[372]: Server nova-metadata-api/node-4 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>Nov 13 15:03:12 node-1 haproxy[372]: proxy nova-metadata-api has no server available!
<129>Nov 13 15:03:12 node-1 haproxy[372]: 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>Nov 13 15:03:12 node-1 haproxy[372]: Backup Server cinder-api/node-3 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>Nov 13 15:03:12 node-1 haproxy[372]: Backup Server cinder-api/node-4 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>Nov 13 15:03:12 node-1 haproxy[372]: proxy cinder-api has no server available!
<129>Nov 13 15:03:12 node-1 haproxy[372]: 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>Nov 13 15:03:12 node-1 haproxy[372]: Server glance-api/node-3 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>Nov 13 15:03:12 node-1 haproxy[372]: Server glance-api/node-4 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>Nov 13 15:03:12 node-1 haproxy[372]: proxy glance-api has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server glance-glare/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server glance-glare/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy glance-glare has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server neutron/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server neutron/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy neutron has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server glance-registry/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server glance-registry/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy glance-registry has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Backup Server mysqld/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Backup Server mysqld/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy mysqld has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server object-storage/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server object-storage/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy object-storage has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server aodh/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server aodh/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy aodh has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server ceilometer/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server ceilometer/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy ceilometer has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server heat-api/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server heat-api/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy heat-api has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:13 node-1 haproxy[376]: Server heat-api-cfn/node-3 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>Nov 13 15:03:13 node-1 haproxy[376]: Server heat-api-cfn/node-4 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>Nov 13 15:03:13 node-1 haproxy[376]: proxy heat-api-cfn has no server available!
<129>Nov 13 15:03:13 node-1 haproxy[376]: 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>Nov 13 15:03:14 node-1 haproxy[376]: Server heat-api-cloudwatch/node-3 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>Nov 13 15:03:14 node-1 haproxy[376]: Server heat-api-cloudwatch/node-4 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>Nov 13 15:03:14 node-1 haproxy[376]: proxy heat-api-cloudwatch has no server available!
<129>Nov 13 15:03:14 node-1 haproxy[376]: 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>Nov 13 15:03:14 node-1 haproxy[376]: Server nova-novncproxy/node-3 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>Nov 13 15:03:14 node-1 haproxy[376]: Server nova-novncproxy/node-4 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>Nov 13 15:03:14 node-1 haproxy[376]: proxy nova-novncproxy has no server available!
<27>Nov 13 15:03:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:15 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:03:25 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov 13 15:03:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:03:51 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Nov 13 15:03:53 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov 13 15:04:24 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 15:04:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:04:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:04:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:04:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:04:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:04:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:06:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:07:00 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:00 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:00 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:00 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:00 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:00 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:06 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:06 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:06 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:06 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:06 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:06 node-1 multipathd: uevent trigger error
<43>Nov 13 15:07:23 node-1 apache2_error [Sun Nov 13 15:07:18.302356 2016] [mpm_event:notice] [pid 9507:tid 140184782829440] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 15:07:23 node-1 apache2_error [Sun Nov 13 15:07:18.302498 2016] [core:notice] [pid 9507:tid 140184782829440] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 15:07:23 node-1 apache2_error [Sun Nov 13 15:07:20.383015 2016] [mpm_event:notice] [pid 9507:tid 140184782829440] AH00491: caught SIGTERM, shutting down
<43>Nov 13 15:07:23 node-1 apache2_error [Sun Nov 13 15:07:21.474919 2016] [mpm_worker:notice] [pid 10945:tid 139651757578112] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 15:07:23 node-1 apache2_error [Sun Nov 13 15:07:21.474954 2016] [core:notice] [pid 10945:tid 139651757578112] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 15:07:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:07:33 node-1 multipathd: uevent trigger error
<43>Nov 13 15:08:43 node-1 apache2_error [Sun Nov 13 15:08:42.755947 2016] [mpm_worker:notice] [pid 10945:tid 139651757578112] AH00295: caught SIGTERM, shutting down
<43>Nov 13 15:08:53 node-1 apache2_error [Sun Nov 13 15:08:43.515567 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 15:08:53 node-1 apache2_error [Sun Nov 13 15:08:43.515612 2016] [core:notice] [pid 24520:tid 140362769438592] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 15:09:33 node-1 apache2_error [Sun Nov 13 15:09:29.477297 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 15:09:33 node-1 apache2_error [Sun Nov 13 15:09:29.671509 2016] [mpm_worker:warn] [pid 24520:tid 140362769438592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 15:09:33 node-1 apache2_error [Sun Nov 13 15:09:29.676164 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 15:09:33 node-1 apache2_error [Sun Nov 13 15:09:29.676195 2016] [core:notice] [pid 24520:tid 140362769438592] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 15:09:49 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:10:13 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:13 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:13 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:13 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:11:48 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:50 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:12:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:12:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:14:03 node-1 multipathd: uevent trigger error
<27>Nov 13 15:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:15:52 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:18:53 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:19:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:01 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:45 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:45 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:45 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:45 node-1 multipathd: uevent trigger error
<27>Nov 13 15:19:45 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:35 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:35 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:35 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:35 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:35 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:35 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 15:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 15:21:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:21:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:21:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:21:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:21:09 node-1 multipathd: uevent trigger error
<27>Nov 13 15:21:55 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:23:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:25 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:23:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:39 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:43 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:43 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:43 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:43 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:43 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:47 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:56 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 15:24:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:24:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:25:36 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:54 node-1 multipathd: uevent trigger error
<27>Nov 13 15:26:54 node-1 multipathd: uevent trigger error
<11>Nov 13 15:27:07 node-1 liberasurecode[923]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:07 node-1 liberasurecode[923]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:07 node-1 liberasurecode[923]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:07 node-1 liberasurecode[923]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:07 node-1 liberasurecode[947]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:07 node-1 liberasurecode[947]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:07 node-1 liberasurecode[947]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:07 node-1 liberasurecode[947]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:09 node-1 liberasurecode[1348]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:09 node-1 liberasurecode[1348]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:09 node-1 liberasurecode[1348]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:09 node-1 liberasurecode[1348]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3192]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3192]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3192]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3192]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3232]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3232]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3232]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:13 node-1 liberasurecode[3232]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3280]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3280]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3280]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3280]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3485]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3485]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3485]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3485]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3499]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3499]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3523]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3523]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3523]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3523]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3511]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:14 node-1 liberasurecode[3511]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:31 node-1 liberasurecode[4532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:31 node-1 liberasurecode[4532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:31 node-1 liberasurecode[4532]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:27:31 node-1 liberasurecode[4532]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 15:27:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:27:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:27:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:27:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:27:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:27:38 node-1 multipathd: uevent trigger error
<27>Nov 13 15:27:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov 13 15:28:24 node-1 apache2_error [Sun Nov 13 15:28:24.418057 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 15:28:24 node-1 apache2_error [Sun Nov 13 15:28:24.805143 2016] [mpm_worker:warn] [pid 24520:tid 140362769438592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 15:28:24 node-1 apache2_error [Sun Nov 13 15:28:24.810114 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 15:28:24 node-1 apache2_error [Sun Nov 13 15:28:24.810149 2016] [core:notice] [pid 24520:tid 140362769438592] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 15:29:04 node-1 apache2_error [Sun Nov 13 15:29:01.411471 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 15:29:04 node-1 apache2_error [Sun Nov 13 15:29:01.607559 2016] [mpm_worker:warn] [pid 24520:tid 140362769438592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 15:29:04 node-1 apache2_error [Sun Nov 13 15:29:01.613381 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 15:29:04 node-1 apache2_error [Sun Nov 13 15:29:01.613416 2016] [core:notice] [pid 24520:tid 140362769438592] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 15:29:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:05 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:18 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:18 node-1 multipathd: uevent trigger error
<43>Nov 13 15:29:55 node-1 apache2_error [Sun Nov 13 15:29:52.930303 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 15:29:55 node-1 apache2_error [Sun Nov 13 15:29:53.124123 2016] [mpm_worker:warn] [pid 24520:tid 140362769438592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 15:29:55 node-1 apache2_error [Sun Nov 13 15:29:53.128276 2016] [mpm_worker:notice] [pid 24520:tid 140362769438592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 15:29:55 node-1 apache2_error [Sun Nov 13 15:29:53.128301 2016] [core:notice] [pid 24520:tid 140362769438592] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 15:29:56 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:56 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:56 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:56 node-1 multipathd: uevent trigger error
<27>Nov 13 15:29:56 node-1 multipathd: uevent trigger error
<11>Nov 13 15:30:01 node-1 liberasurecode[29925]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:30:01 node-1 liberasurecode[29925]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:30:01 node-1 liberasurecode[29925]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:30:01 node-1 liberasurecode[29925]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 15:30:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:30 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:52 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:52 node-1 multipathd: uevent trigger error
<27>Nov 13 15:30:59 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov 13 15:31:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:08 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:12 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:32 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:32 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:32 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:32 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:32 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:31:59 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:04 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:17 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:21 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:22 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:22 node-1 multipathd: uevent trigger error
<129>Nov 13 15:32:28 node-1 haproxy[376]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Nov 13 15:32:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:33 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:49 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:53 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:53 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:53 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:53 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:53 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:32:58 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:10 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:10 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:10 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:10 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:10 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:10 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:14 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:19 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:20 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:20 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:20 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:20 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:24 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:28 node-1 multipathd: uevent trigger error
<27>Nov 13 15:33:28 node-1 multipathd: uevent trigger error
<11>Nov 13 15:35:01 node-1 liberasurecode[1734]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:35:01 node-1 liberasurecode[1734]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:35:01 node-1 liberasurecode[1734]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 15:35:01 node-1 liberasurecode[1734]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
