Nov 13 05:56:14 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8392" x-info="http://www.rsyslog.com"] start
Nov 13 05:56:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov 13 05:56:14 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov 13 05:56:14 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov 13 05:56:14 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 13 05:56:14 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 13 05:56:14 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov 13 05:56:14 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 05:56:14 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=4d578815-1f78-4432-819f-fb58b21aa868 nomdmonddf nomdmonisw
Nov 13 05:56:14 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov 13 05:56:14 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov 13 05:56:14 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov 13 05:56:14 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov 13 05:56:14 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov 13 05:56:14 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov 13 05:56:14 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov 13 05:56:14 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 05:56:14 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 13 05:56:14 node-1 kernel: [    0.000000] No AGP bridge found
Nov 13 05:56:14 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov 13 05:56:14 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov 13 05:56:14 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov 13 05:56:14 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov 13 05:56:14 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov 13 05:56:14 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov 13 05:56:14 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov 13 05:56:14 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov 13 05:56:14 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov 13 05:56:14 node-1 kernel: [    0.000000]   2 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000]   3 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000]   4 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000]   5 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000]   6 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000]   7 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000]   8 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000]   9 disabled
Nov 13 05:56:14 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 13 05:56:14 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov 13 05:56:14 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov 13 05:56:14 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov 13 05:56:14 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov 13 05:56:14 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov 13 05:56:14 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov 13 05:56:14 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov 13 05:56:14 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov 13 05:56:14 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov 13 05:56:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov 13 05:56:14 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov 13 05:56:14 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov 13 05:56:14 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov 13 05:56:14 node-1 kernel: [    0.000000] Zone ranges:
Nov 13 05:56:14 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] Movable zone start for each node
Nov 13 05:56:14 node-1 kernel: [    0.000000] Early memory node ranges
Nov 13 05:56:14 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Nov 13 05:56:14 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov 13 05:56:14 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov 13 05:56:14 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov 13 05:56:14 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Nov 13 05:56:14 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Nov 13 05:56:14 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov 13 05:56:14 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov 13 05:56:14 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov 13 05:56:14 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov 13 05:56:14 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov 13 05:56:14 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov 13 05:56:14 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov 13 05:56:14 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov 13 05:56:14 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov 13 05:56:14 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov 13 05:56:14 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov 13 05:56:14 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov 13 05:56:14 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov 13 05:56:14 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov 13 05:56:14 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov 13 05:56:14 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov 13 05:56:14 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov 13 05:56:14 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 05:56:14 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Nov 13 05:56:14 node-1 kernel: [    0.000000] Policy zone: Normal
Nov 13 05:56:14 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=4d578815-1f78-4432-819f-fb58b21aa868 nomdmonddf nomdmonisw
Nov 13 05:56:14 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov 13 05:56:14 node-1 kernel: [    0.000000] Checking aperture...
Nov 13 05:56:14 node-1 kernel: [    0.000000] No AGP bridge found
Nov 13 05:56:14 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov 13 05:56:14 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov 13 05:56:14 node-1 kernel: [    0.000000] Memory: 32653312K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Nov 13 05:56:14 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov 13 05:56:14 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov 13 05:56:14 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov 13 05:56:14 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov 13 05:56:14 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov 13 05:56:14 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov 13 05:56:14 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov 13 05:56:14 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov 13 05:56:14 node-1 kernel: [    0.000000] console [tty0] enabled
Nov 13 05:56:14 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov 13 05:56:14 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 13 05:56:14 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov 13 05:56:14 node-1 kernel: [    0.000000] hpet clockevent registered
Nov 13 05:56:14 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov 13 05:56:14 node-1 kernel: [    0.004000] tsc: Detected 3492.212 MHz processor
Nov 13 05:56:14 node-1 kernel: [    0.000006] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.42 BogoMIPS (lpj=13968848)
Nov 13 05:56:14 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov 13 05:56:14 node-1 kernel: [    0.000045] Security Framework initialized
Nov 13 05:56:14 node-1 kernel: [    0.000064] AppArmor: AppArmor initialized
Nov 13 05:56:14 node-1 kernel: [    0.000065] Yama: becoming mindful.
Nov 13 05:56:14 node-1 kernel: [    0.001460] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.006334] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.008260] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.008288] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.008565] Initializing cgroup subsys memory
Nov 13 05:56:14 node-1 kernel: [    0.008573] Initializing cgroup subsys devices
Nov 13 05:56:14 node-1 kernel: [    0.008574] Initializing cgroup subsys freezer
Nov 13 05:56:14 node-1 kernel: [    0.008576] Initializing cgroup subsys blkio
Nov 13 05:56:14 node-1 kernel: [    0.008578] Initializing cgroup subsys perf_event
Nov 13 05:56:14 node-1 kernel: [    0.008580] Initializing cgroup subsys hugetlb
Nov 13 05:56:14 node-1 kernel: [    0.008599] CPU: Physical Processor ID: 0
Nov 13 05:56:14 node-1 kernel: [    0.008601] CPU: Processor Core ID: 0
Nov 13 05:56:14 node-1 kernel: [    0.008604] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov 13 05:56:14 node-1 kernel: [    0.008604] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov 13 05:56:14 node-1 kernel: [    0.009298] mce: CPU supports 22 MCE banks
Nov 13 05:56:14 node-1 kernel: [    0.009326] CPU0: Thermal monitoring enabled (TM1)
Nov 13 05:56:14 node-1 kernel: [    0.009346] process: using mwait in idle threads
Nov 13 05:56:14 node-1 kernel: [    0.009349] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov 13 05:56:14 node-1 kernel: [    0.009349] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov 13 05:56:14 node-1 kernel: [    0.009349] tlb_flushall_shift: 6
Nov 13 05:56:14 node-1 kernel: [    0.009439] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov 13 05:56:14 node-1 kernel: [    0.010164] ACPI: Core revision 20131115
Nov 13 05:56:14 node-1 kernel: [    0.022973] ACPI: All ACPI Tables successfully acquired
Nov 13 05:56:14 node-1 kernel: [    0.023131] ftrace: allocating 28622 entries in 112 pages
Nov 13 05:56:14 node-1 kernel: [    0.031893] dmar: Host address width 46
Nov 13 05:56:14 node-1 kernel: [    0.031895] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov 13 05:56:14 node-1 kernel: [    0.031902] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 05:56:14 node-1 kernel: [    0.031903] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov 13 05:56:14 node-1 kernel: [    0.031907] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 05:56:14 node-1 kernel: [    0.031909] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov 13 05:56:14 node-1 kernel: [    0.031910] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov 13 05:56:14 node-1 kernel: [    0.031911] dmar: ATSR flags: 0x0
Nov 13 05:56:14 node-1 kernel: [    0.031912] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov 13 05:56:14 node-1 kernel: [    0.031914] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov 13 05:56:14 node-1 kernel: [    0.032030] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov 13 05:56:14 node-1 kernel: [    0.032031] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 05:56:14 node-1 kernel: [    0.032032] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 05:56:14 node-1 kernel: [    0.032033] HPET id 0 under DRHD base 0xc7ffc000
Nov 13 05:56:14 node-1 kernel: [    0.032034] Your BIOS is broken and requested that x2apic be disabled.
Nov 13 05:56:14 node-1 kernel: [    0.032034] This will slightly decrease performance.
Nov 13 05:56:14 node-1 kernel: [    0.032034] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov 13 05:56:14 node-1 kernel: [    0.032467] Enabled IRQ remapping in xapic mode
Nov 13 05:56:14 node-1 kernel: [    0.032468] x2apic not enabled, IRQ remapping is in xapic mode
Nov 13 05:56:14 node-1 kernel: [    0.032472] Switched APIC routing to physical flat.
Nov 13 05:56:14 node-1 kernel: [    0.033076] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 13 05:56:14 node-1 kernel: [    0.072729] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov 13 05:56:14 node-1 kernel: [    0.072735] TSC deadline timer enabled
Nov 13 05:56:14 node-1 kernel: [    0.072743] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov 13 05:56:14 node-1 kernel: [    0.072749] ... version:                3
Nov 13 05:56:14 node-1 kernel: [    0.072750] ... bit width:              48
Nov 13 05:56:14 node-1 kernel: [    0.072751] ... generic registers:      4
Nov 13 05:56:14 node-1 kernel: [    0.072752] ... value mask:             0000ffffffffffff
Nov 13 05:56:14 node-1 kernel: [    0.072753] ... max period:             0000ffffffffffff
Nov 13 05:56:14 node-1 kernel: [    0.072754] ... fixed-purpose events:   3
Nov 13 05:56:14 node-1 kernel: [    0.072754] ... event mask:             000000070000000f
Nov 13 05:56:14 node-1 kernel: [    0.074187] x86: Booting SMP configuration:
Nov 13 05:56:14 node-1 kernel: [    0.088292] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 13 05:56:14 node-1 kernel: [    0.074189] .... node  #0, CPUs:        #1  #2  #3
Nov 13 05:56:14 node-1 kernel: [    0.116199] .... node  #1, CPUs:    #4  #5  #6  #7
Nov 13 05:56:14 node-1 kernel: [    0.270059] .... node  #0, CPUs:    #8  #9 #10 #11
Nov 13 05:56:14 node-1 kernel: [    0.325677] .... node  #1, CPUs:   #12 #13 #14 #15
Nov 13 05:56:14 node-1 kernel: [    0.382342] x86: Booted up 2 nodes, 16 CPUs
Nov 13 05:56:14 node-1 kernel: [    0.382345] smpboot: Total of 16 processors activated (111763.35 BogoMIPS)
Nov 13 05:56:14 node-1 kernel: [    0.406314] devtmpfs: initialized
Nov 13 05:56:14 node-1 kernel: [    0.408633] EVM: security.selinux
Nov 13 05:56:14 node-1 kernel: [    0.408634] EVM: security.SMACK64
Nov 13 05:56:14 node-1 kernel: [    0.408635] EVM: security.ima
Nov 13 05:56:14 node-1 kernel: [    0.408636] EVM: security.capability
Nov 13 05:56:14 node-1 kernel: [    0.408685] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.409358] pinctrl core: initialized pinctrl subsystem
Nov 13 05:56:14 node-1 kernel: [    0.409414] regulator-dummy: no parameters
Nov 13 05:56:14 node-1 kernel: [    0.409446] RTC time:  5:55:38, date: 11/13/16
Nov 13 05:56:14 node-1 kernel: [    0.409480] NET: Registered protocol family 16
Nov 13 05:56:14 node-1 kernel: [    0.409562] cpuidle: using governor ladder
Nov 13 05:56:14 node-1 kernel: [    0.409564] cpuidle: using governor menu
Nov 13 05:56:14 node-1 kernel: [    0.409597] ACPI: bus type PCI registered
Nov 13 05:56:14 node-1 kernel: [    0.409599] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 13 05:56:14 node-1 kernel: [    0.409645] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov 13 05:56:14 node-1 kernel: [    0.409647] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov 13 05:56:14 node-1 kernel: [    0.423392] PCI: Using configuration type 1 for base access
Nov 13 05:56:14 node-1 kernel: [    0.424389] bio: create slab <bio-0> at 0
Nov 13 05:56:14 node-1 kernel: [    0.424650] ACPI: Added _OSI(Module Device)
Nov 13 05:56:14 node-1 kernel: [    0.424652] ACPI: Added _OSI(Processor Device)
Nov 13 05:56:14 node-1 kernel: [    0.424653] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 13 05:56:14 node-1 kernel: [    0.424654] ACPI: Added _OSI(Processor Aggregator Device)
Nov 13 05:56:14 node-1 kernel: [    0.437283] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov 13 05:56:14 node-1 kernel: [    0.447927] ACPI: Interpreter enabled
Nov 13 05:56:14 node-1 kernel: [    0.447933] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov 13 05:56:14 node-1 kernel: [    0.447937] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov 13 05:56:14 node-1 kernel: [    0.447939] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov 13 05:56:14 node-1 kernel: [    0.447946] ACPI: (supports S0 S4 S5)
Nov 13 05:56:14 node-1 kernel: [    0.447948] ACPI: Using IOAPIC for interrupt routing
Nov 13 05:56:14 node-1 kernel: [    0.447989] HEST: Table parsing has been initialized.
Nov 13 05:56:14 node-1 kernel: [    0.447992] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 13 05:56:14 node-1 kernel: [    0.448562] ACPI: No dock devices found.
Nov 13 05:56:14 node-1 kernel: [    0.460528] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov 13 05:56:14 node-1 kernel: [    0.460533] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 05:56:14 node-1 kernel: [    0.460536] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 05:56:14 node-1 kernel: [    0.460564] PCI host bridge to bus 0000:ff
Nov 13 05:56:14 node-1 kernel: [    0.460566] pci_bus 0000:ff: root bus resource [bus ff]
Nov 13 05:56:14 node-1 kernel: [    0.460574] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460612] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.460642] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460676] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460705] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.460734] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.460764] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460792] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460822] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460849] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460875] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460900] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460928] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460953] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.460979] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461005] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461033] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461060] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461086] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.461114] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461139] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.461164] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461190] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461219] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.461252] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461282] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461311] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461341] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461371] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461401] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461431] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461460] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461490] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461521] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461553] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461583] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461614] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461643] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461670] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461702] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461734] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461772] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461807] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461840] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461870] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461898] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461928] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461956] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.461988] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462019] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462051] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462084] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462113] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462142] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462171] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462202] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462234] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462291] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov 13 05:56:14 node-1 kernel: [    0.462294] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 05:56:14 node-1 kernel: [    0.462297] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 05:56:14 node-1 kernel: [    0.462315] PCI host bridge to bus 0000:7f
Nov 13 05:56:14 node-1 kernel: [    0.462317] pci_bus 0000:7f: root bus resource [bus 7f]
Nov 13 05:56:14 node-1 kernel: [    0.462322] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462349] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.462376] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462406] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462427] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.462452] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.462479] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462505] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462528] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462551] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462573] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462596] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462620] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462642] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462667] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462693] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462715] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462738] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462761] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.462784] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462806] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.462828] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462851] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462877] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 05:56:14 node-1 kernel: [    0.462910] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462937] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462964] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.462992] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463017] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463045] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463072] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463100] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463124] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463152] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463180] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463208] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463237] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463263] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463288] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463316] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463341] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463367] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463395] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463423] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463450] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463475] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463500] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463528] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463555] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463582] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463611] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463637] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463659] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463683] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463709] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463739] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.463765] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.465018] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov 13 05:56:14 node-1 kernel: [    0.465021] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 05:56:14 node-1 kernel: [    0.466144] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 05:56:14 node-1 kernel: [    0.466651] PCI host bridge to bus 0000:00
Nov 13 05:56:14 node-1 kernel: [    0.466654] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov 13 05:56:14 node-1 kernel: [    0.466655] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov 13 05:56:14 node-1 kernel: [    0.466657] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov 13 05:56:14 node-1 kernel: [    0.466658] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov 13 05:56:14 node-1 kernel: [    0.466659] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov 13 05:56:14 node-1 kernel: [    0.466661] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 13 05:56:14 node-1 kernel: [    0.466662] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov 13 05:56:14 node-1 kernel: [    0.466668] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov 13 05:56:14 node-1 kernel: [    0.466750] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.466781] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.466823] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov 13 05:56:14 node-1 kernel: [    0.466843] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.466872] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.466912] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov 13 05:56:14 node-1 kernel: [    0.466931] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.466961] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.467001] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov 13 05:56:14 node-1 kernel: [    0.467019] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.467087] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.467163] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.467237] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 05:56:14 node-1 kernel: [    0.467242] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov 13 05:56:14 node-1 kernel: [    0.467327] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov 13 05:56:14 node-1 kernel: [    0.467474] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov 13 05:56:14 node-1 kernel: [    0.467492] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov 13 05:56:14 node-1 kernel: [    0.467569] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.467624] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov 13 05:56:14 node-1 kernel: [    0.467645] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.467701] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.467747] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 13 05:56:14 node-1 kernel: [    0.467776] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.467833] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.467878] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov 13 05:56:14 node-1 kernel: [    0.467904] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov 13 05:56:14 node-1 kernel: [    0.467922] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov 13 05:56:14 node-1 kernel: [    0.468001] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.468053] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 13 05:56:14 node-1 kernel: [    0.468081] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov 13 05:56:14 node-1 kernel: [    0.468334] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov 13 05:56:14 node-1 kernel: [    0.468340] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov 13 05:56:14 node-1 kernel: [    0.468346] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.468353] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.468360] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov 13 05:56:14 node-1 kernel: [    0.468390] pci 0000:01:00.0: supports D1 D2
Nov 13 05:56:14 node-1 kernel: [    0.478079] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 05:56:14 node-1 kernel: [    0.478086] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 05:56:14 node-1 kernel: [    0.478090] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 05:56:14 node-1 kernel: [    0.478356] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.478416] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov 13 05:56:14 node-1 kernel: [    0.486077] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 05:56:14 node-1 kernel: [    0.486083] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.486087] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 05:56:14 node-1 kernel: [    0.486172] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.486245] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.486344] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.486430] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 05:56:14 node-1 kernel: [    0.486434] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.486436] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 05:56:14 node-1 kernel: [    0.486488] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.486610] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.486663] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 05:56:14 node-1 kernel: [    0.486666] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.486668] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.486717] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.486838] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.486875] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.486994] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.487030] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.487169] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.487205] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov 13 05:56:14 node-1 kernel: [    0.487327] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov 13 05:56:14 node-1 kernel: [    0.487367] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 05:56:14 node-1 kernel: [    0.487370] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.487372] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.487432] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov 13 05:56:14 node-1 kernel: [    0.487494] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.487546] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.487588] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov 13 05:56:14 node-1 kernel: [    0.487670] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov 13 05:56:14 node-1 kernel: [    0.487774] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 05:56:14 node-1 kernel: [    0.487777] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.487779] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.487837] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov 13 05:56:14 node-1 kernel: [    0.487890] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.487939] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.488168] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 05:56:14 node-1 kernel: [    0.488172] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 05:56:14 node-1 kernel: [    0.488234] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov 13 05:56:14 node-1 kernel: [    0.488290] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.488342] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.488551] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 05:56:14 node-1 kernel: [    0.488555] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 05:56:14 node-1 kernel: [    0.488614] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov 13 05:56:14 node-1 kernel: [    0.488673] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.488725] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov 13 05:56:14 node-1 kernel: [    0.488950] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 05:56:14 node-1 kernel: [    0.488954] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 05:56:14 node-1 kernel: [    0.489128] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 05:56:14 node-1 kernel: [    0.489166] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 05:56:14 node-1 kernel: [    0.489245] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov 13 05:56:14 node-1 kernel: [    0.489263] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov 13 05:56:14 node-1 kernel: [    0.489277] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov 13 05:56:14 node-1 kernel: [    0.489290] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov 13 05:56:14 node-1 kernel: [    0.489340] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov 13 05:56:14 node-1 kernel: [    0.494082] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 05:56:14 node-1 kernel: [    0.494086] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 05:56:14 node-1 kernel: [    0.494118] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov 13 05:56:14 node-1 kernel: [    0.494607] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov 13 05:56:14 node-1 kernel: [    0.494610] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 05:56:14 node-1 kernel: [    0.494730] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 05:56:14 node-1 kernel: [    0.494852] PCI host bridge to bus 0000:80
Nov 13 05:56:14 node-1 kernel: [    0.494854] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov 13 05:56:14 node-1 kernel: [    0.494856] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov 13 05:56:14 node-1 kernel: [    0.494857] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov 13 05:56:14 node-1 kernel: [    0.494866] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.494929] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.494997] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 05:56:14 node-1 kernel: [    0.495060] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 05:56:14 node-1 kernel: [    0.495065] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov 13 05:56:14 node-1 kernel: [    0.495138] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov 13 05:56:14 node-1 kernel: [    0.495435] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 13 05:56:14 node-1 kernel: [    0.495467] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 13 05:56:14 node-1 kernel: [    0.495496] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov 13 05:56:14 node-1 kernel: [    0.495525] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov 13 05:56:14 node-1 kernel: [    0.495555] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 05:56:14 node-1 kernel: [    0.495585] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 05:56:14 node-1 kernel: [    0.495614] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 05:56:14 node-1 kernel: [    0.495644] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 05:56:14 node-1 kernel: [    0.495729] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov 13 05:56:14 node-1 kernel: [    0.495733] ACPI: \_SB_.UNC1: notify handler is installed
Nov 13 05:56:14 node-1 kernel: [    0.495735] ACPI: \_SB_.UNC0: notify handler is installed
Nov 13 05:56:14 node-1 kernel: [    0.495750] ACPI: \_SB_.PCI0: notify handler is installed
Nov 13 05:56:14 node-1 kernel: [    0.495802] ACPI: \_SB_.PCI1: notify handler is installed
Nov 13 05:56:14 node-1 kernel: [    0.495882] Found 4 acpi root devices
Nov 13 05:56:14 node-1 kernel: [    0.496002] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov 13 05:56:14 node-1 kernel: [    0.496004] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov 13 05:56:14 node-1 kernel: [    0.496005] vgaarb: loaded
Nov 13 05:56:14 node-1 kernel: [    0.496007] vgaarb: bridge control possible 0000:0c:00.0
Nov 13 05:56:14 node-1 kernel: [    0.496130] SCSI subsystem initialized
Nov 13 05:56:14 node-1 kernel: [    0.496194] libata version 3.00 loaded.
Nov 13 05:56:14 node-1 kernel: [    0.496210] ACPI: bus type USB registered
Nov 13 05:56:14 node-1 kernel: [    0.496220] usbcore: registered new interface driver usbfs
Nov 13 05:56:14 node-1 kernel: [    0.496225] usbcore: registered new interface driver hub
Nov 13 05:56:14 node-1 kernel: [    0.496246] usbcore: registered new device driver usb
Nov 13 05:56:14 node-1 kernel: [    0.496410] PCI: Using ACPI for IRQ routing
Nov 13 05:56:14 node-1 kernel: [    0.500024] PCI: pci_cache_line_size set to 64 bytes
Nov 13 05:56:14 node-1 kernel: [    0.500246] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov 13 05:56:14 node-1 kernel: [    0.500247] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Nov 13 05:56:14 node-1 kernel: [    0.500248] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov 13 05:56:14 node-1 kernel: [    0.500313] NetLabel: Initializing
Nov 13 05:56:14 node-1 kernel: [    0.500314] NetLabel:  domain hash size = 128
Nov 13 05:56:14 node-1 kernel: [    0.500315] NetLabel:  protocols = UNLABELED CIPSOv4
Nov 13 05:56:14 node-1 kernel: [    0.500325] NetLabel:  unlabeled traffic allowed by default
Nov 13 05:56:14 node-1 kernel: [    0.500397] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov 13 05:56:14 node-1 kernel: [    0.500401] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov 13 05:56:14 node-1 kernel: [    0.502457] Switched to clocksource hpet
Nov 13 05:56:14 node-1 kernel: [    0.506355] AppArmor: AppArmor Filesystem Enabled
Nov 13 05:56:14 node-1 kernel: [    0.506372] pnp: PnP ACPI init
Nov 13 05:56:14 node-1 kernel: [    0.506379] ACPI: bus type PNP registered
Nov 13 05:56:14 node-1 kernel: [    0.506502] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506510] pnp 00:01: [dma 4]
Nov 13 05:56:14 node-1 kernel: [    0.506522] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506548] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506568] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506585] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506634] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506685] system 00:06: [io  0x0500-0x057f] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506687] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov 13 05:56:14 node-1 kernel: [    0.506689] system 00:06: [io  0x0580-0x059f] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506691] system 00:06: [io  0x0600-0x061f] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506692] system 00:06: [io  0x0880-0x0883] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506696] system 00:06: [io  0x0800-0x081f] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506698] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov 13 05:56:14 node-1 kernel: [    0.506700] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506701] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506703] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506704] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506706] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506707] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov 13 05:56:14 node-1 kernel: [    0.506709] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506792] pnp 00:07: [dma 0 disabled]
Nov 13 05:56:14 node-1 kernel: [    0.506820] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506894] pnp 00:08: [dma 0 disabled]
Nov 13 05:56:14 node-1 kernel: [    0.506925] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 05:56:14 node-1 kernel: [    0.506975] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov 13 05:56:14 node-1 kernel: [    0.507319] pnp: PnP ACPI: found 10 devices
Nov 13 05:56:14 node-1 kernel: [    0.507320] ACPI: bus type PNP unregistered
Nov 13 05:56:14 node-1 kernel: [    0.513422] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 05:56:14 node-1 kernel: [    0.513425] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 05:56:14 node-1 kernel: [    0.513428] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 05:56:14 node-1 kernel: [    0.513432] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 05:56:14 node-1 kernel: [    0.513434] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513449] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513478] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 05:56:14 node-1 kernel: [    0.513492] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513521] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 05:56:14 node-1 kernel: [    0.513536] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 05:56:14 node-1 kernel: [    0.513565] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 05:56:14 node-1 kernel: [    0.513579] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 05:56:14 node-1 kernel: [    0.513608] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 05:56:14 node-1 kernel: [    0.513610] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513625] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513656] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 05:56:14 node-1 kernel: [    0.513658] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513673] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513702] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 05:56:14 node-1 kernel: [    0.513703] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513706] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513710] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 05:56:14 node-1 kernel: [    0.513712] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513714] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513718] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 05:56:14 node-1 kernel: [    0.513723] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 05:56:14 node-1 kernel: [    0.513731] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 05:56:14 node-1 kernel: [    0.513734] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 05:56:14 node-1 kernel: [    0.513741] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov 13 05:56:14 node-1 kernel: [    0.513742] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov 13 05:56:14 node-1 kernel: [    0.513742] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov 13 05:56:14 node-1 kernel: [    0.513743] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov 13 05:56:14 node-1 kernel: [    0.513744] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov 13 05:56:14 node-1 kernel: [    0.513745] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov 13 05:56:14 node-1 kernel: [    0.513746] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov 13 05:56:14 node-1 kernel: [    0.513747] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov 13 05:56:14 node-1 kernel: [    0.513748] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513749] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513750] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513750] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513751] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513752] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513753] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513754] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513755] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov 13 05:56:14 node-1 kernel: [    0.513756] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513757] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov 13 05:56:14 node-1 kernel: [    0.513758] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov 13 05:56:14 node-1 kernel: [    0.513759] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov 13 05:56:14 node-1 kernel: [    0.513760] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov 13 05:56:14 node-1 kernel: [    0.513762] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov 13 05:56:14 node-1 kernel: [    0.513763] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov 13 05:56:14 node-1 kernel: [    0.513804] NET: Registered protocol family 2
Nov 13 05:56:14 node-1 kernel: [    0.514053] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.514379] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.514537] TCP: Hash tables configured (established 262144 bind 65536)
Nov 13 05:56:14 node-1 kernel: [    0.514580] TCP: reno registered
Nov 13 05:56:14 node-1 kernel: [    0.514609] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.514705] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.514850] NET: Registered protocol family 1
Nov 13 05:56:14 node-1 kernel: [    0.554536] pci 0000:0c:00.0: Video device with shadowed ROM
Nov 13 05:56:14 node-1 kernel: [    0.554543] PCI: CLS 64 bytes, default 64
Nov 13 05:56:14 node-1 kernel: [    0.554584] Trying to unpack rootfs image as initramfs...
Nov 13 05:56:14 node-1 kernel: [    0.774066] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Nov 13 05:56:14 node-1 kernel: [    0.774101] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov 13 05:56:14 node-1 kernel: [    0.774104] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Nov 13 05:56:14 node-1 kernel: [    0.774531] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774538] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774543] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774548] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774558] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774569] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774577] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774587] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774594] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774604] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774610] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774616] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774623] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774631] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774639] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774646] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 05:56:14 node-1 kernel: [    0.774724] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 13 05:56:14 node-1 kernel: [    0.774727] Scanning for low memory corruption every 60 seconds
Nov 13 05:56:14 node-1 kernel: [    0.775101] Initialise system trusted keyring
Nov 13 05:56:14 node-1 kernel: [    0.775153] audit: initializing netlink socket (disabled)
Nov 13 05:56:14 node-1 kernel: [    0.775174] type=2000 audit(1479016538.720:1): initialized
Nov 13 05:56:14 node-1 kernel: [    0.792944] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 13 05:56:14 node-1 kernel: [    0.794463] zbud: loaded
Nov 13 05:56:14 node-1 kernel: [    0.794590] VFS: Disk quotas dquot_6.5.2
Nov 13 05:56:14 node-1 kernel: [    0.794621] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 13 05:56:14 node-1 kernel: [    0.794996] fuse init (API version 7.22)
Nov 13 05:56:14 node-1 kernel: [    0.795059] msgmni has been set to 32768
Nov 13 05:56:14 node-1 kernel: [    0.795109] Key type big_key registered
Nov 13 05:56:14 node-1 kernel: [    0.795674] Key type asymmetric registered
Nov 13 05:56:14 node-1 kernel: [    0.795675] Asymmetric key parser 'x509' registered
Nov 13 05:56:14 node-1 kernel: [    0.795697] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 13 05:56:14 node-1 kernel: [    0.795767] io scheduler noop registered
Nov 13 05:56:14 node-1 kernel: [    0.795768] io scheduler deadline registered (default)
Nov 13 05:56:14 node-1 kernel: [    0.795790] io scheduler cfq registered
Nov 13 05:56:14 node-1 kernel: [    0.796301] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    0.796441] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    0.796554] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    0.796659] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    0.796795] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    0.796888] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    0.797281] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov 13 05:56:14 node-1 kernel: [    0.797315] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov 13 05:56:14 node-1 kernel: [    0.797332] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov 13 05:56:14 node-1 kernel: [    0.797341] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797343] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797346] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov 13 05:56:14 node-1 kernel: [    0.797351] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797353] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797354] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797356] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797357] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797358] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797360] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797361] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797363] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797364] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797365] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797367] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797369] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov 13 05:56:14 node-1 kernel: [    0.797374] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797377] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov 13 05:56:14 node-1 kernel: [    0.797391] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797395] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov 13 05:56:14 node-1 kernel: [    0.797405] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797407] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov 13 05:56:14 node-1 kernel: [    0.797410] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov 13 05:56:14 node-1 kernel: [    0.797447] ioapic: probe of 0000:00:05.4 failed with error -22
Nov 13 05:56:14 node-1 kernel: [    0.797453] ioapic: probe of 0000:80:05.4 failed with error -22
Nov 13 05:56:14 node-1 kernel: [    0.797457] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 13 05:56:14 node-1 kernel: [    0.797466] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 13 05:56:14 node-1 kernel: [    0.797507] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov 13 05:56:14 node-1 kernel: [    0.797508] vesafb: scrolling: redraw
Nov 13 05:56:14 node-1 kernel: [    0.797510] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 13 05:56:14 node-1 kernel: [    0.818170] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov 13 05:56:14 node-1 kernel: [    0.826671] Console: switching to colour frame buffer device 80x30
Nov 13 05:56:14 node-1 kernel: [    0.835342] fb0: VESA VGA frame buffer device
Nov 13 05:56:14 node-1 kernel: [    0.835539] intel_idle: MWAIT substates: 0x2120
Nov 13 05:56:14 node-1 kernel: [    0.835540] intel_idle: v0.4 model 0x3F
Nov 13 05:56:14 node-1 kernel: [    0.835540] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov 13 05:56:14 node-1 kernel: [    0.835769] ipmi message handler version 39.2
Nov 13 05:56:14 node-1 kernel: [    0.836042] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov 13 05:56:14 node-1 kernel: [    0.836476] ACPI: AC Adapter [P111] (on-line)
Nov 13 05:56:14 node-1 kernel: [    0.841716] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov 13 05:56:14 node-1 kernel: [    0.852708] ACPI: Power Button [PWRB]
Nov 13 05:56:14 node-1 kernel: [    0.858457] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov 13 05:56:14 node-1 kernel: [    0.870069] ACPI: Power Button [PWRF]
Nov 13 05:56:14 node-1 kernel: [    0.896009] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov 13 05:56:14 node-1 kernel: [    0.907628] pstore: Registered erst as persistent store backend
Nov 13 05:56:14 node-1 kernel: [    0.913811] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov 13 05:56:14 node-1 kernel: [    0.925720] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 13 05:56:14 node-1 kernel: [    0.952453] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov 13 05:56:14 node-1 kernel: [    0.985700] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov 13 05:56:14 node-1 kernel: [    0.999779] Linux agpgart interface v0.103
Nov 13 05:56:14 node-1 kernel: [    1.007413] brd: module loaded
Nov 13 05:56:14 node-1 kernel: [    1.014482] loop: module loaded
Nov 13 05:56:14 node-1 kernel: [    1.021185] libphy: Fixed MDIO Bus: probed
Nov 13 05:56:14 node-1 kernel: [    1.027649] tun: Universal TUN/TAP device driver, 1.6
Nov 13 05:56:14 node-1 kernel: [    1.034110] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 13 05:56:14 node-1 kernel: [    1.040621] PPP generic driver version 2.4.2
Nov 13 05:56:14 node-1 kernel: [    1.046996] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 13 05:56:14 node-1 kernel: [    1.053432] ehci-pci: EHCI PCI platform driver
Nov 13 05:56:14 node-1 kernel: [    1.059947] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov 13 05:56:14 node-1 kernel: [    1.066352] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov 13 05:56:14 node-1 kernel: [    1.078872] ehci-pci 0000:00:1a.0: debug port 2
Nov 13 05:56:14 node-1 kernel: [    1.089048] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov 13 05:56:14 node-1 kernel: [    1.089068] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov 13 05:56:14 node-1 kernel: [    1.105952] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov 13 05:56:14 node-1 kernel: [    1.112028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 05:56:14 node-1 kernel: [    1.118236] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 05:56:14 node-1 kernel: [    1.130214] usb usb1: Product: EHCI Host Controller
Nov 13 05:56:14 node-1 kernel: [    1.136283] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 05:56:14 node-1 kernel: [    1.142364] usb usb1: SerialNumber: 0000:00:1a.0
Nov 13 05:56:14 node-1 kernel: [    1.148355] hub 1-0:1.0: USB hub found
Nov 13 05:56:14 node-1 kernel: [    1.154165] hub 1-0:1.0: 2 ports detected
Nov 13 05:56:14 node-1 kernel: [    1.160001] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov 13 05:56:14 node-1 kernel: [    1.165664] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov 13 05:56:14 node-1 kernel: [    1.176715] ehci-pci 0000:00:1d.0: debug port 2
Nov 13 05:56:14 node-1 kernel: [    1.186100] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov 13 05:56:14 node-1 kernel: [    1.186103] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov 13 05:56:14 node-1 kernel: [    1.201869] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov 13 05:56:14 node-1 kernel: [    1.207099] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 05:56:14 node-1 kernel: [    1.212451] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 05:56:14 node-1 kernel: [    1.223076] usb usb2: Product: EHCI Host Controller
Nov 13 05:56:14 node-1 kernel: [    1.228551] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 05:56:14 node-1 kernel: [    1.234105] usb usb2: SerialNumber: 0000:00:1d.0
Nov 13 05:56:14 node-1 kernel: [    1.239631] hub 2-0:1.0: USB hub found
Nov 13 05:56:14 node-1 kernel: [    1.244983] hub 2-0:1.0: 2 ports detected
Nov 13 05:56:14 node-1 kernel: [    1.250291] ehci-platform: EHCI generic platform driver
Nov 13 05:56:14 node-1 kernel: [    1.255535] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 13 05:56:14 node-1 kernel: [    1.260862] ohci-pci: OHCI PCI platform driver
Nov 13 05:56:14 node-1 kernel: [    1.266181] ohci-platform: OHCI generic platform driver
Nov 13 05:56:14 node-1 kernel: [    1.271430] uhci_hcd: USB Universal Host Controller Interface driver
Nov 13 05:56:14 node-1 kernel: [    1.276839] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov 13 05:56:14 node-1 kernel: [    1.469650] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov 13 05:56:14 node-1 kernel: [    1.769448] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov 13 05:56:14 node-1 kernel: [    1.785714] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov 13 05:56:14 node-1 kernel: [    1.791327] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 05:56:14 node-1 kernel: [    1.797106] hub 1-1:1.0: USB hub found
Nov 13 05:56:14 node-1 kernel: [    1.802702] hub 1-1:1.0: 6 ports detected
Nov 13 05:56:14 node-1 kernel: [    1.917261] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov 13 05:56:14 node-1 kernel: [    2.315778] i8042: No controller found
Nov 13 05:56:14 node-1 kernel: [    2.321343] mousedev: PS/2 mouse device common for all mice
Nov 13 05:56:14 node-1 kernel: [    2.327097] rtc_cmos 00:02: RTC can wake from S4
Nov 13 05:56:14 node-1 kernel: [    2.329697] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov 13 05:56:14 node-1 kernel: [    2.329698] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 05:56:14 node-1 kernel: [    2.330209] hub 2-1:1.0: USB hub found
Nov 13 05:56:14 node-1 kernel: [    2.330445] hub 2-1:1.0: 8 ports detected
Nov 13 05:56:14 node-1 kernel: [    2.355726] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov 13 05:56:14 node-1 kernel: [    2.361571] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 13 05:56:14 node-1 kernel: [    2.372956] device-mapper: uevent: version 1.0.3
Nov 13 05:56:14 node-1 kernel: [    2.378680] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov 13 05:56:14 node-1 kernel: [    2.390082] ledtrig-cpu: registered to indicate activity on CPUs
Nov 13 05:56:14 node-1 kernel: [    2.396063] TCP: cubic registered
Nov 13 05:56:14 node-1 kernel: [    2.401934] NET: Registered protocol family 10
Nov 13 05:56:14 node-1 kernel: [    2.408002] NET: Registered protocol family 17
Nov 13 05:56:14 node-1 kernel: [    2.413782] Key type dns_resolver registered
Nov 13 05:56:14 node-1 kernel: [    2.419824] Loading compiled-in X.509 certificates
Nov 13 05:56:14 node-1 kernel: [    2.426037] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov 13 05:56:14 node-1 kernel: [    2.437665] registered taskstats version 1
Nov 13 05:56:14 node-1 kernel: [    2.445801] Key type trusted registered
Nov 13 05:56:14 node-1 kernel: [    2.453430] Key type encrypted registered
Nov 13 05:56:14 node-1 kernel: [    2.458944] AppArmor: AppArmor sha1 policy hashing enabled
Nov 13 05:56:14 node-1 kernel: [    2.464459] IMA: No TPM chip found, activating TPM-bypass!
Nov 13 05:56:14 node-1 kernel: [    2.470556] regulator-dummy: disabling
Nov 13 05:56:14 node-1 kernel: [    2.476055]   Magic number: 8:426:921
Nov 13 05:56:14 node-1 kernel: [    2.481536] clockevents clockevent14: hash matches
Nov 13 05:56:14 node-1 kernel: [    2.487036] acpi device:ef: hash matches
Nov 13 05:56:14 node-1 kernel: [    2.492606] rtc_cmos 00:02: setting system clock to 2016-11-13 05:55:40 UTC (1479016540)
Nov 13 05:56:14 node-1 kernel: [    2.504972] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov 13 05:56:14 node-1 kernel: [    2.510541] EDD information not available.
Nov 13 05:56:14 node-1 kernel: [    2.516099] PM: Hibernation image not present or could not be loaded.
Nov 13 05:56:14 node-1 kernel: [    2.516966] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov 13 05:56:14 node-1 kernel: [    2.528254] Write protecting the kernel read-only data: 12288k
Nov 13 05:56:14 node-1 kernel: [    2.534561] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov 13 05:56:14 node-1 kernel: [    2.547273] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov 13 05:56:14 node-1 kernel: [    2.579383] device-mapper: multipath: version 1.6.0 loaded
Nov 13 05:56:14 node-1 kernel: [    2.587134] systemd-udevd[215]: starting version 204
Nov 13 05:56:14 node-1 kernel: [    2.608691] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov 13 05:56:14 node-1 kernel: [    2.616803] md: linear personality registered for level -1
Nov 13 05:56:14 node-1 kernel: [    2.631905] md: multipath personality registered for level -4
Nov 13 05:56:14 node-1 kernel: [    2.640083] md: raid0 personality registered for level 0
Nov 13 05:56:14 node-1 kernel: [    2.648653] md: raid1 personality registered for level 1
Nov 13 05:56:14 node-1 kernel: [    2.656465] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov 13 05:56:14 node-1 kernel: [    2.662688] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov 13 05:56:14 node-1 kernel: [    2.668969] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov 13 05:56:14 node-1 kernel: [    2.670096] megasas: FW now in Ready state
Nov 13 05:56:14 node-1 kernel: [    2.670404] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.670492] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.670606] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.670765] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.670857] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.670984] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.671134] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.671259] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.671387] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.671533] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.671695] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.671779] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.671977] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.672127] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.672283] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.672389] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.673804] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov 13 05:56:14 node-1 kernel: [    2.702789] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Nov 13 05:56:14 node-1 kernel: [    2.716004] 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 05:56:14 node-1 kernel: [    2.729812] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 05:56:14 node-1 kernel: [    2.736732] raid6: sse2x1   11723 MB/s
Nov 13 05:56:14 node-1 kernel: [    2.736866] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.736882] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.736917] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.736970] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.737053] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.749041] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Nov 13 05:56:14 node-1 kernel: [    2.749043] 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 05:56:14 node-1 kernel: [    2.749045] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov 13 05:56:14 node-1 kernel: [    2.749121] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.749160] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.749191] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.749232] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.749276] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.749319] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.749699] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.763069] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Nov 13 05:56:14 node-1 kernel: [    2.763073] 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 05:56:14 node-1 kernel: [    2.763075] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 05:56:14 node-1 kernel: [    2.763270] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.763315] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.763365] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.763416] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.763596] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 05:56:14 node-1 kernel: [    2.764921] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov 13 05:56:14 node-1 kernel: [    2.764922] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 05:56:14 node-1 kernel: [    2.764922] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov 13 05:56:14 node-1 kernel: [    2.764923] usb 2-1.4: Manufacturer: Avocent
Nov 13 05:56:14 node-1 kernel: [    2.764924] usb 2-1.4: SerialNumber: 20111102-00000001
Nov 13 05:56:14 node-1 kernel: [    2.775774] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Nov 13 05:56:14 node-1 kernel: [    2.775776] 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 05:56:14 node-1 kernel: [    2.775778] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 05:56:14 node-1 kernel: [    2.996367] raid6: sse2x2    9786 MB/s
Nov 13 05:56:14 node-1 kernel: [    3.068294] raid6: sse2x4   10140 MB/s
Nov 13 05:56:14 node-1 kernel: [    3.140238] raid6: avx2x1   14947 MB/s
Nov 13 05:56:14 node-1 kernel: [    3.212174] raid6: avx2x2   18912 MB/s
Nov 13 05:56:14 node-1 kernel: [    3.284115] raid6: avx2x4   21343 MB/s
Nov 13 05:56:14 node-1 kernel: [    3.290201] raid6: using algorithm avx2x4 (21343 MB/s)
Nov 13 05:56:14 node-1 kernel: [    3.296234] raid6: using avx2x2 recovery algorithm
Nov 13 05:56:14 node-1 kernel: [    3.302099] Switched to clocksource tsc
Nov 13 05:56:14 node-1 kernel: [    3.302102] megasas:IOC Init cmd success
Nov 13 05:56:14 node-1 kernel: [    3.302157] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    3.302200] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    3.302244] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    3.302259] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov 13 05:56:14 node-1 kernel: [    3.302371] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 05:56:14 node-1 kernel: [    3.324386] megasas: INIT adapter done
Nov 13 05:56:14 node-1 kernel: [    3.330576] hidraw: raw HID events driver (C) Jiri Kosina
Nov 13 05:56:14 node-1 kernel: [    3.336235] xor: automatically using best checksumming function:
Nov 13 05:56:14 node-1 kernel: [    3.343571] usbcore: registered new interface driver usbhid
Nov 13 05:56:14 node-1 kernel: [    3.349077] usbhid: USB HID core driver
Nov 13 05:56:14 node-1 kernel: [    3.355428] 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 05:56:14 node-1 kernel: [    3.366828] 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 05:56:14 node-1 kernel: [    3.378549] 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 05:56:14 node-1 kernel: [    3.380071]    avx       : 35291.000 MB/sec
Nov 13 05:56:14 node-1 kernel: [    3.396128] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov 13 05:56:14 node-1 kernel: [    3.397575] scsi0 : LSI SAS based MegaRAID driver
Nov 13 05:56:14 node-1 kernel: [    3.405287] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 05:56:14 node-1 kernel: [    3.419824] 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 05:56:14 node-1 kernel: [    3.431796] 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 05:56:14 node-1 kernel: [    3.431798] async_tx: api initialized (async)
Nov 13 05:56:14 node-1 kernel: [    3.450244] 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 05:56:14 node-1 kernel: [    3.457264] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 05:56:14 node-1 kernel: [    3.461984] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov 13 05:56:14 node-1 kernel: [    3.462083] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov 13 05:56:14 node-1 kernel: [    3.462401] sd 0:2:0:0: [sda] Write Protect is off
Nov 13 05:56:14 node-1 kernel: [    3.462402] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov 13 05:56:14 node-1 kernel: [    3.462471] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov 13 05:56:14 node-1 kernel: [    3.487827]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Nov 13 05:56:14 node-1 kernel: [    3.488421] sd 0:2:0:0: [sda] Attached SCSI disk
Nov 13 05:56:14 node-1 kernel: [    3.536673] md: raid6 personality registered for level 6
Nov 13 05:56:14 node-1 kernel: [    3.543772] md: raid5 personality registered for level 5
Nov 13 05:56:14 node-1 kernel: [    3.550663] md: raid4 personality registered for level 4
Nov 13 05:56:14 node-1 kernel: [    3.560413] md: raid10 personality registered for level 10
Nov 13 05:56:14 node-1 kernel: [    3.613444] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Nov 13 05:56:14 node-1 kernel: [    3.668534] random: lvm urandom read with 32 bits of entropy available
Nov 13 05:56:14 node-1 kernel: [    3.779815] bio: create slab <bio-1> at 1
Nov 13 05:56:14 node-1 kernel: [    4.547711] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 05:56:14 node-1 kernel: [    5.056389] init: plymouth-upstart-bridge main process (552) terminated with status 1
Nov 13 05:56:14 node-1 kernel: [    5.068538] init: plymouth-upstart-bridge main process ended, respawning
Nov 13 05:56:14 node-1 kernel: [    5.076982] init: plymouth-upstart-bridge main process (563) terminated with status 1
Nov 13 05:56:14 node-1 kernel: [    5.089132] init: plymouth-upstart-bridge main process ended, respawning
Nov 13 05:56:14 node-1 kernel: [    5.214554] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov 13 05:56:14 node-1 kernel: [    5.240054] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov 13 05:56:14 node-1 kernel: [    5.302490] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov 13 05:56:14 node-1 kernel: [    5.332503] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov 13 05:56:14 node-1 kernel: [    5.431027] random: nonblocking pool is initialized
Nov 13 05:56:14 node-1 kernel: [    5.450528] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 05:56:14 node-1 kernel: [    5.592744] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov 13 05:56:14 node-1 kernel: [    5.651484] XFS (dm-0): Mounting Filesystem
Nov 13 05:56:14 node-1 kernel: [    5.862444] XFS (dm-0): Ending clean mount
Nov 13 05:56:14 node-1 kernel: [    5.915441] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 05:56:14 node-1 kernel: [    5.953689] XFS (dm-1): Mounting Filesystem
Nov 13 05:56:14 node-1 kernel: [    6.211859] XFS (dm-1): Ending clean mount
Nov 13 05:56:14 node-1 kernel: [    8.023524] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov 13 05:56:14 node-1 kernel: [    8.037814] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov 13 05:56:14 node-1 kernel: [    8.244084] systemd-udevd[780]: starting version 204
Nov 13 05:56:14 node-1 kernel: [    8.465369] power_meter ACPI000D:00: Found ACPI power meter.
Nov 13 05:56:14 node-1 kernel: [    8.465377] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov 13 05:56:14 node-1 kernel: [    8.473144] wmi: Mapper loaded
Nov 13 05:56:14 node-1 kernel: [    8.479047] IPMI System Interface driver.
Nov 13 05:56:14 node-1 kernel: [    8.479087] ipmi_si: probing via ACPI
Nov 13 05:56:14 node-1 kernel: [    8.479097] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov 13 05:56:14 node-1 kernel: [    8.479098] ipmi_si: Adding ACPI-specified kcs state machine
Nov 13 05:56:14 node-1 kernel: [    8.479105] ipmi_si: probing via SMBIOS
Nov 13 05:56:14 node-1 kernel: [    8.479106] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 05:56:14 node-1 kernel: [    8.479107] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov 13 05:56:14 node-1 kernel: [    8.479108] ipmi_si: probing via SPMI
Nov 13 05:56:14 node-1 kernel: [    8.479109] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 05:56:14 node-1 kernel: [    8.479110] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov 13 05:56:14 node-1 kernel: [    8.479111] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov 13 05:56:14 node-1 kernel: [    8.510806] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov 13 05:56:14 node-1 kernel: [    8.510811] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 05:56:14 node-1 kernel: [    8.510813] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov 13 05:56:14 node-1 kernel: [    8.510815] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 05:56:14 node-1 kernel: [    8.510856] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 13 05:56:14 node-1 kernel: [    8.520799] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov 13 05:56:14 node-1 kernel: [    8.588120] systemd-udevd[798]: renamed network interface eth0 to enp6s0
Nov 13 05:56:14 node-1 kernel: [    8.619973] systemd-udevd[826]: renamed network interface eth1 to enp7s0
Nov 13 05:56:14 node-1 kernel: [    8.625249] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov 13 05:56:14 node-1 kernel: [    8.625254] ipmi_si 00:09: IPMI kcs interface initialized
Nov 13 05:56:14 node-1 kernel: [    8.661746] systemd-udevd[801]: renamed network interface eth2 to enp8s0
Nov 13 05:56:14 node-1 kernel: [    8.671930] systemd-udevd[797]: renamed network interface eth3 to enp9s0
Nov 13 05:56:14 node-1 kernel: [    8.959689] type=1400 audit(1479016546.970:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.959846] type=1400 audit(1479016546.970:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.959976] type=1400 audit(1479016546.970:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.962853] type=1400 audit(1479016546.970:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1058 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.962991] type=1400 audit(1479016546.970:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1058 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.963106] type=1400 audit(1479016546.970:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1058 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.966873] type=1400 audit(1479016546.974:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.967024] type=1400 audit(1479016546.974:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.967146] type=1400 audit(1479016546.974:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    8.980028] type=1400 audit(1479016546.990:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Nov 13 05:56:14 node-1 kernel: [    9.503447] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov 13 05:56:14 node-1 kernel: [    9.515691] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov 13 05:56:14 node-1 kernel: [    9.682912] enic 0000:06:00.0 enp6s0: Link UP
Nov 13 05:56:14 node-1 kernel: [    9.683368] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov 13 05:56:14 node-1 kernel: [    9.683375] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov 13 05:56:14 node-1 kernel: [   18.953325] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov 13 05:56:14 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 05:56:15 node-1 failsafe: Failsafe of 120 seconds reached.
Nov 13 05:56:15 node-1 kernel: [   37.072626] init: failsafe main process (8419) killed by TERM signal
Nov 13 05:56:15 node-1 dbus[8441]: [system] AppArmor D-Bus mediation is enabled
Nov 13 05:56:16 node-1 kernel: [   37.303506] audit_printk_skb: 30 callbacks suppressed
Nov 13 05:56:16 node-1 kernel: [   37.303508] type=1400 audit(1479016576.084:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8544 comm="apparmor_parser"
Nov 13 05:56:16 node-1 kernel: [   37.303513] type=1400 audit(1479016576.084:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Nov 13 05:56:16 node-1 kernel: [   37.303516] type=1400 audit(1479016576.084:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Nov 13 05:56:16 node-1 kernel: [   37.303733] type=1400 audit(1479016576.084:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Nov 13 05:56:16 node-1 kernel: [   37.303735] type=1400 audit(1479016576.084:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Nov 13 05:56:16 node-1 kernel: [   37.303847] type=1400 audit(1479016576.084:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Nov 13 05:56:16 node-1 kernel: [   37.305199] type=1400 audit(1479016576.084:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8545 comm="apparmor_parser"
Nov 13 05:56:16 node-1 kernel: [   37.415257] type=1400 audit(1479016576.196:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8547 comm="apparmor_parser"
Nov 13 05:56:16 node-1 cron[8578]: (CRON) INFO (pidfile fd = 3)
Nov 13 05:56:16 node-1 anacron[8614]: Anacron 2.3 started on 2016-11-13
Nov 13 05:56:16 node-1 cron[8615]: (CRON) STARTUP (fork ok)
Nov 13 05:56:16 node-1 anacron[8614]: Will run job `cron.daily' in 5 min.
Nov 13 05:56:16 node-1 anacron[8614]: Will run job `cron.weekly' in 10 min.
Nov 13 05:56:16 node-1 anacron[8614]: Will run job `cron.monthly' in 15 min.
Nov 13 05:56:16 node-1 anacron[8614]: Jobs will be executed sequentially
Nov 13 05:56:16 node-1 cron[8615]: (CRON) INFO (Running @reboot jobs)
Nov 13 05:56:16 node-1 multipathd: path checkers start up
Nov 13 05:56:16 node-1 postfix/master[8756]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov 13 05:56:19 node-1 puppet-agent[8941]: Reopening log files
Nov 13 05:56:20 node-1 puppet-agent[8941]: Could not request certificate: Connection refused - connect(2)
Nov 13 05:56:35 node-1 puppet-user[9149]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov 13 05:56:35 node-1 puppet-user[9149]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov 13 05:56:37 node-1 puppet-user[9149]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov 13 05:56:37 node-1 puppet-user[9149]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov 13 05:56:37 node-1 puppet-user[9149]: Finished catalog run in 1.71 seconds
Nov 13 05:56:38 node-1 multipathd: uevent trigger error
Nov 13 05:56:38 node-1 puppet-user[9761]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 05:56:38 node-1 puppet-user[9761]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Nov 13 05:56:38 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov 13 05:56:38 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov 13 05:56:38 node-1 puppet-user[9761]: (/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 05:56:38 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov 13 05:56:38 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov 13 05:56:38 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov 13 05:56:38 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov 13 05:56:38 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov 13 05:56:38 node-1 puppet-user[9761]: Finished catalog run in 0.06 seconds
Nov 13 05:56:40 node-1 puppet-user[10236]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov 13 05:56:40 node-1 puppet-user[10236]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov 13 05:56:40 node-1 puppet-user[10236]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov 13 05:56:40 node-1 puppet-user[10236]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov 13 05:56:40 node-1 puppet-user[10236]: Finished catalog run in 0.03 seconds
Nov 13 05:56:41 node-1 puppet-user[10694]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov 13 05:56:41 node-1 puppet-user[10694]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov 13 05:56:41 node-1 puppet-user[10694]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov 13 05:56:41 node-1 puppet-user[10694]: Finished catalog run in 0.03 seconds
Nov 13 05:56:43 node-1 puppet-user[11136]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov 13 05:56:43 node-1 puppet-user[11136]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Nov 13 05:56:43 node-1 puppet-user[11136]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov 13 05:56:45 node-1 puppet-user[11136]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Nov 13 05:56:45 node-1 puppet-user[11136]: Finished catalog run in 2.42 seconds
Nov 13 05:56:47 node-1 puppet-user[11676]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov 13 05:56:47 node-1 puppet-user[11676]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Nov 13 05:56:47 node-1 puppet-user[11676]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov 13 05:56:47 node-1 puppet-user[11676]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Nov 13 05:56:47 node-1 puppet-user[11676]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov 13 05:56:47 node-1 puppet-user[11676]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov 13 05:56:47 node-1 puppet-user[11676]: Finished catalog run in 0.22 seconds
Nov 13 05:56:49 node-1 puppet-user[12150]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov 13 05:56:49 node-1 puppet-user[12150]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Nov 13 05:56:49 node-1 puppet-user[12150]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov 13 05:56:49 node-1 kernel: [   70.509991] nr_pdflush_threads exported in /proc is scheduled for removal
Nov 13 05:56:49 node-1 kernel: [   70.510040] 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 05:56:49 node-1 puppet-user[12150]: (/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 05:56:49 node-1 puppet-user[12150]: Finished catalog run in 0.05 seconds
Nov 13 05:56:49 node-1 kernel: [   71.012172] init: plymouth-upstart-bridge main process ended, respawning
Nov 13 05:56:50 node-1 puppet-agent[8941]: Could not run: SIGTERM
Nov 13 05:56:50 node-1 kernel: [   71.279486] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 13 05:56:50 node-1 ec2: 
Nov 13 05:56:50 node-1 ec2: #############################################################
Nov 13 05:56:50 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov 13 05:56:50 node-1 ec2: 1024 6f:e5:63:91:d0:90:fd:b8:da:55:e5:f9:50:56:cb:16  root@node-1.domain.tld (DSA)
Nov 13 05:56:50 node-1 ec2: 256 18:6e:97:13:11:52:f8:03:de:48:df:a9:4a:8c:64:ae  root@node-1.domain.tld (ECDSA)
Nov 13 05:56:50 node-1 ec2: 256 94:c2:38:9a:37:c2:d9:43:c9:ee:32:05:11:18:e6:6a  root@node-1.domain.tld (ED25519)
Nov 13 05:56:50 node-1 ec2: 2048 00:85:31:ba:d1:51:f8:5c:a0:e9:8c:37:4b:a4:5c:42  root@node-1.domain.tld (RSA)
Nov 13 05:56:50 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov 13 05:56:50 node-1 ec2: #############################################################
Nov 13 05:56:51 node-1 puppet-user[12756]: (Scope(Class[main])) MODULAR: sync_time
Nov 13 05:56:51 node-1 puppet-user[12756]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov 13 05:56:51 node-1 ntpdate[13183]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov 13 05:56:57 node-1 ntpdate[13183]: adjust time server 10.20.0.2 offset -0.369590 sec
Nov 13 05:56:57 node-1 puppet-user[12756]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov 13 05:56:57 node-1 puppet-user[12756]: Finished catalog run in 6.18 seconds
Nov 13 05:57:01 node-1 CRON[13339]: (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 05:57:03 node-1 puppet-user[13396]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 05:57:03 node-1 puppet-user[13396]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Nov 13 05:57:04 node-1 puppet-user[13396]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov 13 05:57:04 node-1 puppet-user[13396]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Nov 13 05:57:04 node-1 puppet-user[13396]: Finished catalog run in 0.07 seconds
Nov 13 05:57:05 node-1 puppet-user[13854]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov 13 05:57:05 node-1 puppet-user[13854]: Compiled catalog for node-1.domain.tld in environment production in 0.48 seconds
Nov 13 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/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 05:57:06 node-1 puppet-user[13854]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov 13 05:57:06 node-1 puppet-user[13854]: Finished catalog run in 0.81 seconds
Nov 13 05:57:08 node-1 puppet-user[14359]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov 13 05:57:08 node-1 puppet-user[14359]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Nov 13 05:57:12 node-1 puppet-user[14359]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov 13 05:57:30 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 05:57:30 node-1 nailgun-agent: I, [2016-11-13T05:57:30.629483 #13342]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov 13 05:57:39 node-1 puppet-user[14359]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov 13 05:57:39 node-1 puppet-user[14359]: Finished catalog run in 30.65 seconds
Nov 13 05:57:41 node-1 puppet-user[16880]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov 13 05:57:42 node-1 puppet-user[16880]: Compiled catalog for node-1.domain.tld in environment production in 0.56 seconds
Nov 13 05:57:42 node-1 puppet-user[16880]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov 13 05:57:42 node-1 puppet-user[16880]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov 13 05:57:42 node-1 puppet-user[16880]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov 13 05:57:42 node-1 puppet-user[16880]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov 13 05:57:42 node-1 puppet-user[16880]: Finished catalog run in 0.09 seconds
Nov 13 05:57:43 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 05:57:43 node-1 nailgun-agent: I, [2016-11-13T05:57:43.738506 #13342]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Nov 13 05:57:44 node-1 puppet-user[17334]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov 13 05:57:45 node-1 puppet-user[17334]: Compiled catalog for node-1.domain.tld in environment production in 1.00 seconds
Nov 13 05:57:45 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov 13 05:57:45 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov 13 05:57:45 node-1 crontab[17953]: (root) LIST (root)
Nov 13 05:57:45 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov 13 05:57:45 node-1 crontab[17954]: (root) REPLACE (root)
Nov 13 05:57:46 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/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 05:57:47 node-1 puppet-user[17334]: (/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 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/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 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov 13 05:57:47 node-1 puppet-user[17334]: (/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 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov 13 05:57:47 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov 13 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov 13 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov 13 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov 13 05:57:48 node-1 puppet-user[17334]: (/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 05:57:48 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8392" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 05:57:48 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov 13 05:57:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:57:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:57:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:57:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:57:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:03 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:03 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:03 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:03 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:03 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:49 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:50 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:52 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:52 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:52 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:52 node-1 multipathd: uevent trigger error
<27>Nov 13 05:58:52 node-1 multipathd: uevent trigger error
<27>Nov 13 05:59:32 node-1 ntpdate[1236]: no servers can be used, exiting
<27>Nov 13 05:59:32 node-1 ntpdate[1404]: no servers can be used, exiting
<27>Nov 13 06:00:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:07 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:07 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:07 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:07 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:07 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:00:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:24 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:24 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:24 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:24 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:24 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 06:01:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 06:01:32 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 06:01:32 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 06:01:38 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 06:01:43 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 06:01:43 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 06:01:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:01:51 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:13 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:15 node-1 haproxy[23032]: 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 06:02:16 node-1 haproxy[23036]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:17 node-1 haproxy[23036]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:17 node-1 haproxy[23036]: proxy mysqld has no server available!
<27>Nov 13 06:02:19 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:19 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:19 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:19 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:19 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:19 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:22 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:25 node-1 haproxy[25743]: 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 06:02:25 node-1 haproxy[25743]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:25 node-1 haproxy[25743]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:25 node-1 haproxy[25743]: proxy mysqld has no server available!
<129>Nov 13 06:02:26 node-1 haproxy[25747]: 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 06:02:26 node-1 haproxy[25747]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:26 node-1 haproxy[25747]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:26 node-1 haproxy[25747]: proxy object-storage has no server available!
<27>Nov 13 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:28 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:30 node-1 haproxy[27047]: 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 06:02:30 node-1 haproxy[27047]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:30 node-1 haproxy[27047]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:30 node-1 haproxy[27047]: proxy neutron has no server available!
<129>Nov 13 06:02:30 node-1 haproxy[27047]: 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 06:02:31 node-1 haproxy[27051]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:31 node-1 haproxy[27051]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:31 node-1 haproxy[27051]: proxy mysqld has no server available!
<129>Nov 13 06:02:31 node-1 haproxy[27051]: 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 06:02:31 node-1 haproxy[27051]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:32 node-1 haproxy[27051]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:32 node-1 haproxy[27051]: proxy object-storage has no server available!
<27>Nov 13 06:02:33 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:33 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:33 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:33 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:33 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:35 node-1 haproxy[28612]: 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 06:02:36 node-1 haproxy[28616]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:36 node-1 haproxy[28616]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:36 node-1 haproxy[28616]: proxy keystone-1 has no server available!
<129>Nov 13 06:02:36 node-1 haproxy[28616]: 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 06:02:36 node-1 haproxy[28616]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:36 node-1 haproxy[28616]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:36 node-1 haproxy[28616]: proxy keystone-2 has no server available!
<129>Nov 13 06:02:36 node-1 haproxy[28616]: 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 06:02:36 node-1 haproxy[28616]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:37 node-1 haproxy[28616]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:37 node-1 haproxy[28616]: proxy neutron has no server available!
<129>Nov 13 06:02:37 node-1 haproxy[28616]: 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 06:02:37 node-1 haproxy[28616]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:37 node-1 haproxy[28616]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:37 node-1 haproxy[28616]: proxy mysqld has no server available!
<129>Nov 13 06:02:37 node-1 haproxy[28616]: 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 06:02:37 node-1 haproxy[28616]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:37 node-1 haproxy[28616]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:37 node-1 haproxy[28616]: proxy object-storage has no server available!
<27>Nov 13 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:39 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:41 node-1 haproxy[29990]: 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 06:02:41 node-1 haproxy[29990]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:41 node-1 haproxy[29990]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:41 node-1 haproxy[29990]: proxy keystone-1 has no server available!
<129>Nov 13 06:02:41 node-1 haproxy[29990]: 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 06:02:41 node-1 haproxy[29990]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:41 node-1 haproxy[29990]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:41 node-1 haproxy[29990]: proxy keystone-2 has no server available!
<129>Nov 13 06:02:42 node-1 haproxy[29994]: 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 06:02:42 node-1 haproxy[29994]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:42 node-1 haproxy[29994]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:42 node-1 haproxy[29994]: proxy neutron has no server available!
<129>Nov 13 06:02:42 node-1 haproxy[29994]: 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 06:02:42 node-1 haproxy[29994]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:42 node-1 haproxy[29994]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:42 node-1 haproxy[29994]: proxy mysqld has no server available!
<129>Nov 13 06:02:42 node-1 haproxy[29994]: 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 06:02:42 node-1 haproxy[29994]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:42 node-1 haproxy[29994]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:42 node-1 haproxy[29994]: proxy object-storage has no server available!
<129>Nov 13 06:02:43 node-1 haproxy[29994]: 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 06:02:43 node-1 haproxy[29994]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:43 node-1 haproxy[29994]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:43 node-1 haproxy[29994]: proxy aodh has no server available!
<27>Nov 13 06:02:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:44 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:46 node-1 haproxy[31306]: 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 06:02:47 node-1 haproxy[31310]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:47 node-1 haproxy[31310]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:47 node-1 haproxy[31310]: proxy keystone-1 has no server available!
<129>Nov 13 06:02:47 node-1 haproxy[31310]: 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 06:02:47 node-1 haproxy[31310]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:47 node-1 haproxy[31310]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:47 node-1 haproxy[31310]: proxy keystone-2 has no server available!
<129>Nov 13 06:02:47 node-1 haproxy[31310]: 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 06:02:47 node-1 haproxy[31310]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:47 node-1 haproxy[31310]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:47 node-1 haproxy[31310]: proxy neutron has no server available!
<129>Nov 13 06:02:47 node-1 haproxy[31310]: 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 06:02:47 node-1 haproxy[31310]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:47 node-1 haproxy[31310]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:47 node-1 haproxy[31310]: proxy mysqld has no server available!
<129>Nov 13 06:02:48 node-1 haproxy[31310]: 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 06:02:48 node-1 haproxy[31310]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:48 node-1 haproxy[31310]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:48 node-1 haproxy[31310]: proxy object-storage has no server available!
<129>Nov 13 06:02:48 node-1 haproxy[31310]: 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 06:02:48 node-1 haproxy[31310]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:48 node-1 haproxy[31310]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:48 node-1 haproxy[31310]: proxy aodh has no server available!
<129>Nov 13 06:02:48 node-1 haproxy[31310]: 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 06:02:48 node-1 haproxy[31310]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:48 node-1 haproxy[31310]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:48 node-1 haproxy[31310]: proxy ceilometer has no server available!
<27>Nov 13 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:50 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:52 node-1 haproxy[32653]: 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 06:02:52 node-1 haproxy[32653]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:52 node-1 haproxy[32653]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:52 node-1 haproxy[32653]: proxy keystone-1 has no server available!
<129>Nov 13 06:02:52 node-1 haproxy[32653]: 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 06:02:52 node-1 haproxy[32653]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:52 node-1 haproxy[32653]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:52 node-1 haproxy[32653]: proxy keystone-2 has no server available!
<129>Nov 13 06:02:52 node-1 haproxy[32653]: 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 06:02:52 node-1 haproxy[32653]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:53 node-1 haproxy[32657]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:53 node-1 haproxy[32657]: proxy neutron has no server available!
<129>Nov 13 06:02:53 node-1 haproxy[32657]: 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 06:02:53 node-1 haproxy[32657]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:53 node-1 haproxy[32657]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:53 node-1 haproxy[32657]: proxy mysqld has no server available!
<129>Nov 13 06:02:53 node-1 haproxy[32657]: 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 06:02:53 node-1 haproxy[32657]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:53 node-1 haproxy[32657]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:53 node-1 haproxy[32657]: proxy object-storage has no server available!
<129>Nov 13 06:02:53 node-1 haproxy[32657]: 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 06:02:53 node-1 haproxy[32657]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:53 node-1 haproxy[32657]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:53 node-1 haproxy[32657]: proxy aodh has no server available!
<129>Nov 13 06:02:54 node-1 haproxy[32657]: 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 06:02:54 node-1 haproxy[32657]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:54 node-1 haproxy[32657]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:54 node-1 haproxy[32657]: proxy ceilometer has no server available!
<27>Nov 13 06:02:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:02:55 node-1 multipathd: uevent trigger error
<129>Nov 13 06:02:57 node-1 haproxy[1564]: 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 06:02:57 node-1 haproxy[1564]: 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 06:02:57 node-1 haproxy[1564]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:58 node-1 haproxy[1570]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:58 node-1 haproxy[1570]: proxy keystone-1 has no server available!
<129>Nov 13 06:02:58 node-1 haproxy[1570]: 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 06:02:58 node-1 haproxy[1570]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:58 node-1 haproxy[1570]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:58 node-1 haproxy[1570]: proxy keystone-2 has no server available!
<129>Nov 13 06:02:58 node-1 haproxy[1570]: 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 06:02:58 node-1 haproxy[1570]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:58 node-1 haproxy[1570]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:58 node-1 haproxy[1570]: proxy neutron has no server available!
<129>Nov 13 06:02:58 node-1 haproxy[1570]: 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 06:02:58 node-1 haproxy[1570]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:58 node-1 haproxy[1570]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:58 node-1 haproxy[1570]: proxy mysqld has no server available!
<129>Nov 13 06:02:58 node-1 haproxy[1570]: 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 06:02:58 node-1 haproxy[1570]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:59 node-1 haproxy[1570]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:59 node-1 haproxy[1570]: proxy object-storage has no server available!
<129>Nov 13 06:02:59 node-1 haproxy[1570]: 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 06:02:59 node-1 haproxy[1570]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:59 node-1 haproxy[1570]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:59 node-1 haproxy[1570]: proxy aodh has no server available!
<129>Nov 13 06:02:59 node-1 haproxy[1570]: 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 06:02:59 node-1 haproxy[1570]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:02:59 node-1 haproxy[1570]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:02:59 node-1 haproxy[1570]: proxy ceilometer has no server available!
<27>Nov 13 06:03:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:00 node-1 multipathd: uevent trigger error
<129>Nov 13 06:03:03 node-1 haproxy[2961]: 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 06:03:03 node-1 haproxy[2961]: 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 06:03:03 node-1 haproxy[2961]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:03 node-1 haproxy[2961]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:03 node-1 haproxy[2961]: proxy keystone-1 has no server available!
<129>Nov 13 06:03:04 node-1 haproxy[2965]: 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 06:03:04 node-1 haproxy[2965]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:04 node-1 haproxy[2965]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:04 node-1 haproxy[2965]: proxy keystone-2 has no server available!
<129>Nov 13 06:03:04 node-1 haproxy[2965]: 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 06:03:04 node-1 haproxy[2965]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:04 node-1 haproxy[2965]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:04 node-1 haproxy[2965]: proxy glance-api has no server available!
<129>Nov 13 06:03:04 node-1 haproxy[2965]: 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 06:03:04 node-1 haproxy[2965]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:04 node-1 haproxy[2965]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:04 node-1 haproxy[2965]: proxy glance-glare has no server available!
<129>Nov 13 06:03:04 node-1 haproxy[2965]: 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 06:03:04 node-1 haproxy[2965]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:04 node-1 haproxy[2965]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:04 node-1 haproxy[2965]: proxy neutron has no server available!
<129>Nov 13 06:03:04 node-1 haproxy[2965]: 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 06:03:04 node-1 haproxy[2965]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:04 node-1 haproxy[2965]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:04 node-1 haproxy[2965]: proxy glance-registry has no server available!
<129>Nov 13 06:03:04 node-1 haproxy[2965]: 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 06:03:05 node-1 haproxy[2965]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:05 node-1 haproxy[2965]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:05 node-1 haproxy[2965]: proxy mysqld has no server available!
<129>Nov 13 06:03:05 node-1 haproxy[2965]: 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 06:03:05 node-1 haproxy[2965]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:05 node-1 haproxy[2965]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:05 node-1 haproxy[2965]: proxy object-storage has no server available!
<129>Nov 13 06:03:05 node-1 haproxy[2965]: 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 06:03:05 node-1 haproxy[2965]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:05 node-1 haproxy[2965]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:05 node-1 haproxy[2965]: proxy aodh has no server available!
<129>Nov 13 06:03:05 node-1 haproxy[2965]: 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 06:03:05 node-1 haproxy[2965]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:05 node-1 haproxy[2965]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:05 node-1 haproxy[2965]: proxy ceilometer has no server available!
<27>Nov 13 06:03:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:06 node-1 multipathd: uevent trigger error
<129>Nov 13 06:03:09 node-1 haproxy[4371]: 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 06:03:09 node-1 haproxy[4371]: 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 06:03:09 node-1 haproxy[4371]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:09 node-1 haproxy[4371]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:09 node-1 haproxy[4371]: proxy keystone-1 has no server available!
<129>Nov 13 06:03:09 node-1 haproxy[4371]: 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 06:03:09 node-1 haproxy[4371]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:09 node-1 haproxy[4371]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:09 node-1 haproxy[4371]: proxy keystone-2 has no server available!
<129>Nov 13 06:03:09 node-1 haproxy[4371]: 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 06:03:09 node-1 haproxy[4371]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:10 node-1 haproxy[4375]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:10 node-1 haproxy[4375]: proxy nova-api has no server available!
<129>Nov 13 06:03:10 node-1 haproxy[4375]: 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 06:03:10 node-1 haproxy[4375]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:10 node-1 haproxy[4375]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:10 node-1 haproxy[4375]: proxy nova-metadata-api has no server available!
<129>Nov 13 06:03:10 node-1 haproxy[4375]: 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 06:03:10 node-1 haproxy[4375]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:10 node-1 haproxy[4375]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:10 node-1 haproxy[4375]: proxy glance-api has no server available!
<129>Nov 13 06:03:10 node-1 haproxy[4375]: 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 06:03:10 node-1 haproxy[4375]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:10 node-1 haproxy[4375]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:10 node-1 haproxy[4375]: proxy glance-glare has no server available!
<129>Nov 13 06:03:10 node-1 haproxy[4375]: 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 06:03:10 node-1 haproxy[4375]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:10 node-1 haproxy[4375]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:10 node-1 haproxy[4375]: proxy neutron has no server available!
<129>Nov 13 06:03:10 node-1 haproxy[4375]: 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 06:03:10 node-1 haproxy[4375]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:10 node-1 haproxy[4375]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:10 node-1 haproxy[4375]: proxy glance-registry has no server available!
<129>Nov 13 06:03:10 node-1 haproxy[4375]: 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 06:03:10 node-1 haproxy[4375]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:10 node-1 haproxy[4375]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:10 node-1 haproxy[4375]: proxy mysqld has no server available!
<129>Nov 13 06:03:10 node-1 haproxy[4375]: 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 06:03:10 node-1 haproxy[4375]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:11 node-1 haproxy[4375]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:11 node-1 haproxy[4375]: proxy object-storage has no server available!
<129>Nov 13 06:03:11 node-1 haproxy[4375]: 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 06:03:11 node-1 haproxy[4375]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:11 node-1 haproxy[4375]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:11 node-1 haproxy[4375]: proxy aodh has no server available!
<129>Nov 13 06:03:11 node-1 haproxy[4375]: 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 06:03:11 node-1 haproxy[4375]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:11 node-1 haproxy[4375]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:11 node-1 haproxy[4375]: proxy ceilometer has no server available!
<129>Nov 13 06:03:11 node-1 haproxy[4375]: 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 06:03:11 node-1 haproxy[4375]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:11 node-1 haproxy[4375]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:11 node-1 haproxy[4375]: proxy nova-novncproxy has no server available!
<27>Nov 13 06:03:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:12 node-1 multipathd: uevent trigger error
<129>Nov 13 06:03:14 node-1 haproxy[5701]: 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 06:03:15 node-1 haproxy[5707]: 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 06:03:15 node-1 haproxy[5707]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:15 node-1 haproxy[5707]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:15 node-1 haproxy[5707]: proxy keystone-1 has no server available!
<129>Nov 13 06:03:15 node-1 haproxy[5707]: 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 06:03:15 node-1 haproxy[5707]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:15 node-1 haproxy[5707]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:15 node-1 haproxy[5707]: proxy keystone-2 has no server available!
<129>Nov 13 06:03:15 node-1 haproxy[5707]: 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 06:03:15 node-1 haproxy[5707]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:15 node-1 haproxy[5707]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:15 node-1 haproxy[5707]: proxy nova-api has no server available!
<129>Nov 13 06:03:15 node-1 haproxy[5707]: 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 06:03:15 node-1 haproxy[5707]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:15 node-1 haproxy[5707]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:15 node-1 haproxy[5707]: proxy nova-metadata-api has no server available!
<129>Nov 13 06:03:15 node-1 haproxy[5707]: 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 06:03:15 node-1 haproxy[5707]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:15 node-1 haproxy[5707]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:15 node-1 haproxy[5707]: proxy cinder-api has no server available!
<129>Nov 13 06:03:15 node-1 haproxy[5707]: 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 06:03:15 node-1 haproxy[5707]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:15 node-1 haproxy[5707]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:15 node-1 haproxy[5707]: proxy glance-api has no server available!
<129>Nov 13 06:03:15 node-1 haproxy[5707]: 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 06:03:15 node-1 haproxy[5707]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:15 node-1 haproxy[5707]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:15 node-1 haproxy[5707]: proxy glance-glare has no server available!
<129>Nov 13 06:03:15 node-1 haproxy[5707]: 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 06:03:16 node-1 haproxy[5707]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:16 node-1 haproxy[5707]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:16 node-1 haproxy[5707]: proxy neutron has no server available!
<129>Nov 13 06:03:16 node-1 haproxy[5707]: 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 06:03:16 node-1 haproxy[5707]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:16 node-1 haproxy[5707]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:16 node-1 haproxy[5707]: proxy glance-registry has no server available!
<129>Nov 13 06:03:16 node-1 haproxy[5707]: 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 06:03:16 node-1 haproxy[5707]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:16 node-1 haproxy[5707]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:16 node-1 haproxy[5707]: proxy mysqld has no server available!
<129>Nov 13 06:03:16 node-1 haproxy[5707]: 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 06:03:16 node-1 haproxy[5707]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:16 node-1 haproxy[5707]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:16 node-1 haproxy[5707]: proxy object-storage has no server available!
<129>Nov 13 06:03:16 node-1 haproxy[5707]: 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 06:03:16 node-1 haproxy[5707]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:16 node-1 haproxy[5707]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:16 node-1 haproxy[5707]: proxy aodh has no server available!
<129>Nov 13 06:03:16 node-1 haproxy[5707]: 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 06:03:16 node-1 haproxy[5707]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:16 node-1 haproxy[5707]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:16 node-1 haproxy[5707]: proxy ceilometer has no server available!
<129>Nov 13 06:03:16 node-1 haproxy[5707]: 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 06:03:16 node-1 haproxy[5707]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:16 node-1 haproxy[5707]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:16 node-1 haproxy[5707]: proxy nova-novncproxy has no server available!
<27>Nov 13 06:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:18 node-1 multipathd: uevent trigger error
<129>Nov 13 06:03:20 node-1 haproxy[7212]: 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 06:03:20 node-1 haproxy[7212]: 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 06:03:20 node-1 haproxy[7212]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:20 node-1 haproxy[7212]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:20 node-1 haproxy[7212]: proxy keystone-1 has no server available!
<129>Nov 13 06:03:20 node-1 haproxy[7212]: 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 06:03:20 node-1 haproxy[7212]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy keystone-2 has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy nova-api has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy nova-metadata-api has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy cinder-api has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy glance-api has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy glance-glare has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy neutron has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy glance-registry has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:21 node-1 haproxy[7216]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:21 node-1 haproxy[7216]: proxy mysqld has no server available!
<129>Nov 13 06:03:21 node-1 haproxy[7216]: 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 06:03:21 node-1 haproxy[7216]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:22 node-1 haproxy[7216]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:22 node-1 haproxy[7216]: proxy object-storage has no server available!
<129>Nov 13 06:03:22 node-1 haproxy[7216]: 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 06:03:22 node-1 haproxy[7216]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:22 node-1 haproxy[7216]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:22 node-1 haproxy[7216]: proxy aodh has no server available!
<129>Nov 13 06:03:22 node-1 haproxy[7216]: 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 06:03:22 node-1 haproxy[7216]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:22 node-1 haproxy[7216]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:22 node-1 haproxy[7216]: proxy ceilometer has no server available!
<129>Nov 13 06:03:22 node-1 haproxy[7216]: 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 06:03:22 node-1 haproxy[7216]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:22 node-1 haproxy[7216]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:22 node-1 haproxy[7216]: proxy heat-api has no server available!
<129>Nov 13 06:03:22 node-1 haproxy[7216]: 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 06:03:22 node-1 haproxy[7216]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:22 node-1 haproxy[7216]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:22 node-1 haproxy[7216]: proxy heat-api-cfn has no server available!
<129>Nov 13 06:03:22 node-1 haproxy[7216]: 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 06:03:22 node-1 haproxy[7216]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:22 node-1 haproxy[7216]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:22 node-1 haproxy[7216]: proxy heat-api-cloudwatch has no server available!
<129>Nov 13 06:03:22 node-1 haproxy[7216]: 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 06:03:22 node-1 haproxy[7216]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 06:03:22 node-1 haproxy[7216]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 06:03:22 node-1 haproxy[7216]: proxy nova-novncproxy has no server available!
<27>Nov 13 06:03:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:03:34 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov 13 06:03:53 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:03:58 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Nov 13 06:04:00 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov 13 06:04:24 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 06:04:52 node-1 multipathd: uevent trigger error
<27>Nov 13 06:04:52 node-1 multipathd: uevent trigger error
<27>Nov 13 06:04:52 node-1 multipathd: uevent trigger error
<27>Nov 13 06:04:52 node-1 multipathd: uevent trigger error
<27>Nov 13 06:04:52 node-1 multipathd: uevent trigger error
<27>Nov 13 06:06:56 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:07:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:22 node-1 multipathd: uevent trigger error
<43>Nov 13 06:07:39 node-1 apache2_error [Sun Nov 13 06:07:32.793250 2016] [mpm_event:notice] [pid 18369:tid 140222724962176] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 06:07:39 node-1 apache2_error [Sun Nov 13 06:07:32.793417 2016] [core:notice] [pid 18369:tid 140222724962176] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 06:07:39 node-1 apache2_error [Sun Nov 13 06:07:35.656572 2016] [mpm_event:notice] [pid 18369:tid 140222724962176] AH00491: caught SIGTERM, shutting down
<43>Nov 13 06:07:39 node-1 apache2_error [Sun Nov 13 06:07:36.735232 2016] [mpm_worker:notice] [pid 18730:tid 140563467601792] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 06:07:39 node-1 apache2_error [Sun Nov 13 06:07:36.735270 2016] [core:notice] [pid 18730:tid 140563467601792] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 06:07:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:07:44 node-1 multipathd: uevent trigger error
<43>Nov 13 06:08:49 node-1 apache2_error [Sun Nov 13 06:08:47.304990 2016] [mpm_worker:notice] [pid 18730:tid 140563467601792] AH00295: caught SIGTERM, shutting down
<43>Nov 13 06:08:49 node-1 apache2_error [Sun Nov 13 06:08:48.058616 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 06:08:49 node-1 apache2_error [Sun Nov 13 06:08:48.058662 2016] [core:notice] [pid 30785:tid 140578967902080] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 06:09:39 node-1 apache2_error [Sun Nov 13 06:09:32.250908 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 06:09:39 node-1 apache2_error [Sun Nov 13 06:09:32.443404 2016] [mpm_worker:warn] [pid 30785:tid 140578967902080] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 06:09:39 node-1 apache2_error [Sun Nov 13 06:09:32.445901 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 06:09:39 node-1 apache2_error [Sun Nov 13 06:09:32.445920 2016] [core:notice] [pid 30785:tid 140578967902080] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 06:10:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:10:16 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:16 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:16 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:16 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:16 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:20 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:20 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:20 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:20 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:20 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:36 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:36 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:36 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:36 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:36 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 06:10:58 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:03 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:11:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:12:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:12:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:12:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:12:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:13:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:13:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:13:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:13:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:13:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:13:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:08 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:08 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:08 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:08 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:08 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:08 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:14:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:16:06 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:16:53 node-1 multipathd: uevent trigger error
<27>Nov 13 06:16:53 node-1 multipathd: uevent trigger error
<27>Nov 13 06:16:54 node-1 multipathd: uevent trigger error
<27>Nov 13 06:16:54 node-1 multipathd: uevent trigger error
<27>Nov 13 06:16:54 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:13 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:17:28 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:18:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:19:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:18 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:25 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Nov 13 06:19:25 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Nov 13 06:19:25 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Nov 13 06:19:26 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Nov 13 06:19:26 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Nov 13 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 06:20:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:20:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:20:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:20:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:20:12 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:54 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:54 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:54 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:54 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 06:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:23 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:27 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:31 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:31 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:32 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:32 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:43 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:43 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:43 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:43 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:43 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:49 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:49 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:49 node-1 multipathd: uevent trigger error
<27>Nov 13 06:23:50 node-1 multipathd: uevent trigger error
<27>Nov 13 06:24:32 node-1 multipathd: uevent trigger error
<27>Nov 13 06:24:32 node-1 multipathd: uevent trigger error
<27>Nov 13 06:24:32 node-1 multipathd: uevent trigger error
<27>Nov 13 06:24:32 node-1 multipathd: uevent trigger error
<27>Nov 13 06:24:32 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:25:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:41 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:25:57 node-1 multipathd: uevent trigger error
<11>Nov 13 06:26:10 node-1 liberasurecode[6672]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:10 node-1 liberasurecode[6672]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:10 node-1 liberasurecode[6672]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:10 node-1 liberasurecode[6672]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:10 node-1 liberasurecode[6696]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:10 node-1 liberasurecode[6696]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:10 node-1 liberasurecode[6696]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:10 node-1 liberasurecode[6696]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:12 node-1 liberasurecode[7113]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:12 node-1 liberasurecode[7113]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:12 node-1 liberasurecode[7113]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:12 node-1 liberasurecode[7113]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7791]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7791]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7791]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7791]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7832]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7832]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7832]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:16 node-1 liberasurecode[7832]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7871]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7871]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7871]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7871]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7931]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7931]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7949]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7949]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7949]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7949]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7961]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7961]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7975]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:17 node-1 liberasurecode[7975]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:26 node-1 liberasurecode[9962]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:26 node-1 liberasurecode[9962]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:26 node-1 liberasurecode[9962]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:26:26 node-1 liberasurecode[9962]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 06:26:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:26:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:26:35 node-1 multipathd: uevent trigger error
<27>Nov 13 06:26:35 node-1 multipathd: uevent trigger error
<43>Nov 13 06:27:30 node-1 apache2_error [Sun Nov 13 06:27:21.159720 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 06:27:30 node-1 apache2_error [Sun Nov 13 06:27:21.542492 2016] [mpm_worker:warn] [pid 30785:tid 140578967902080] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 06:27:30 node-1 apache2_error [Sun Nov 13 06:27:21.545983 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 06:27:30 node-1 apache2_error [Sun Nov 13 06:27:21.546001 2016] [core:notice] [pid 30785:tid 140578967902080] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 06:28:00 node-1 apache2_error [Sun Nov 13 06:27:58.456699 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 06:28:00 node-1 apache2_error [Sun Nov 13 06:27:58.650807 2016] [mpm_worker:warn] [pid 30785:tid 140578967902080] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 06:28:00 node-1 apache2_error [Sun Nov 13 06:27:58.654913 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 06:28:00 node-1 apache2_error [Sun Nov 13 06:27:58.654939 2016] [core:notice] [pid 30785:tid 140578967902080] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 06:28:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 06:28:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:15 node-1 multipathd: uevent trigger error
<43>Nov 13 06:28:50 node-1 apache2_error [Sun Nov 13 06:28:49.527927 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 06:28:50 node-1 apache2_error [Sun Nov 13 06:28:49.722480 2016] [mpm_worker:warn] [pid 30785:tid 140578967902080] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 06:28:50 node-1 apache2_error [Sun Nov 13 06:28:49.727020 2016] [mpm_worker:notice] [pid 30785:tid 140578967902080] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 06:28:50 node-1 apache2_error [Sun Nov 13 06:28:49.727040 2016] [core:notice] [pid 30785:tid 140578967902080] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 06:28:53 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:53 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:53 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:53 node-1 multipathd: uevent trigger error
<27>Nov 13 06:28:53 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:00 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:05 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:05 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:06 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:15 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:29 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:49 node-1 multipathd: uevent trigger error
<27>Nov 13 06:29:55 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<11>Nov 13 06:30:01 node-1 liberasurecode[23618]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:30:01 node-1 liberasurecode[23618]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:30:01 node-1 liberasurecode[23618]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:30:01 node-1 liberasurecode[23618]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 06:30:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:04 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:30:09 node-1 multipathd: uevent trigger error
<27>Nov 13 06:32:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:32:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:32:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:32:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:32:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:11 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:11 node-1 multipathd: uevent trigger error
<129>Nov 13 06:33:21 node-1 haproxy[24049]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 06:33:22 node-1 haproxy[24049]: 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.
<27>Nov 13 06:33:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:22 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:38 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:38 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:38 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:38 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:44 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:14 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:25 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:25 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:25 node-1 multipathd: uevent trigger error
<27>Nov 13 06:34:25 node-1 multipathd: uevent trigger error
<129>Nov 13 06:34:31 node-1 haproxy[24049]: 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.
<11>Nov 13 06:35:02 node-1 liberasurecode[21121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:35:02 node-1 liberasurecode[21121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:35:02 node-1 liberasurecode[21121]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 06:35:02 node-1 liberasurecode[21121]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 06:35:16 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:17 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:21 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:26 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:26 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:26 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:26 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:26 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:30 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:30 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:30 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:30 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:30 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:30 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:34 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:34 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:34 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:34 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov 13 06:35:39 node-1 multipathd: uevent trigger error
