Sep 13 02:28:07 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] start
Sep 13 02:28:07 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 13 02:28:07 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 13 02:28:07 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 13 02:28:07 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 13 02:28:07 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 13 02:28:07 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 13 02:28:07 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 13 02:28:07 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e76b488b-bb17-444e-85ed-a4331c84d8bf nomdmonddf nomdmonisw
Sep 13 02:28:07 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 13 02:28:07 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 13 02:28:07 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 13 02:28:07 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 13 02:28:07 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 13 02:28:07 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 13 02:28:07 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 13 02:28:07 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Sep 13 02:28:07 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 13 02:28:07 node-1 kernel: [    0.000000] No AGP bridge found
Sep 13 02:28:07 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 13 02:28:07 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 13 02:28:07 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 13 02:28:07 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 13 02:28:07 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 13 02:28:07 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 13 02:28:07 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 13 02:28:07 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 13 02:28:07 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 13 02:28:07 node-1 kernel: [    0.000000]   2 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000]   3 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000]   4 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000]   5 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000]   6 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000]   7 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000]   8 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000]   9 disabled
Sep 13 02:28:07 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 13 02:28:07 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 13 02:28:07 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 13 02:28:07 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 13 02:28:07 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 13 02:28:07 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 13 02:28:07 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 13 02:28:07 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 13 02:28:07 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 13 02:28:07 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 13 02:28:07 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 13 02:28:07 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 13 02:28:07 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 13 02:28:07 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 13 02:28:07 node-1 kernel: [    0.000000] Zone ranges:
Sep 13 02:28:07 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 13 02:28:07 node-1 kernel: [    0.000000] Early memory node ranges
Sep 13 02:28:07 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 13 02:28:07 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 13 02:28:07 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 13 02:28:07 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 13 02:28:07 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 13 02:28:07 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 13 02:28:07 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 13 02:28:07 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 13 02:28:07 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 13 02:28:07 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 13 02:28:07 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 13 02:28:07 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 13 02:28:07 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 13 02:28:07 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 13 02:28:07 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 13 02:28:07 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 13 02:28:07 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 13 02:28:07 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 13 02:28:07 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 13 02:28:07 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 13 02:28:07 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 13 02:28:07 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 13 02:28:07 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 13 02:28:07 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Sep 13 02:28:07 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 13 02:28:07 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 13 02:28:07 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e76b488b-bb17-444e-85ed-a4331c84d8bf nomdmonddf nomdmonisw
Sep 13 02:28:07 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 13 02:28:07 node-1 kernel: [    0.000000] Checking aperture...
Sep 13 02:28:07 node-1 kernel: [    0.000000] No AGP bridge found
Sep 13 02:28:07 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 13 02:28:07 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 13 02:28:07 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 13 02:28:07 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 13 02:28:07 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 13 02:28:07 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 13 02:28:07 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 13 02:28:07 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 13 02:28:07 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 13 02:28:07 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 13 02:28:07 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 13 02:28:07 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 13 02:28:07 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 13 02:28:07 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 13 02:28:07 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 13 02:28:07 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 13 02:28:07 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 13 02:28:07 node-1 kernel: [    0.004000] tsc: Detected 3491.907 MHz processor
Sep 13 02:28:07 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.81 BogoMIPS (lpj=13967628)
Sep 13 02:28:07 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 13 02:28:07 node-1 kernel: [    0.000041] Security Framework initialized
Sep 13 02:28:07 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Sep 13 02:28:07 node-1 kernel: [    0.000062] Yama: becoming mindful.
Sep 13 02:28:07 node-1 kernel: [    0.001457] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.006377] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.008303] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.008331] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.008621] Initializing cgroup subsys memory
Sep 13 02:28:07 node-1 kernel: [    0.008629] Initializing cgroup subsys devices
Sep 13 02:28:07 node-1 kernel: [    0.008631] Initializing cgroup subsys freezer
Sep 13 02:28:07 node-1 kernel: [    0.008633] Initializing cgroup subsys blkio
Sep 13 02:28:07 node-1 kernel: [    0.008634] Initializing cgroup subsys perf_event
Sep 13 02:28:07 node-1 kernel: [    0.008636] Initializing cgroup subsys hugetlb
Sep 13 02:28:07 node-1 kernel: [    0.008656] CPU: Physical Processor ID: 0
Sep 13 02:28:07 node-1 kernel: [    0.008657] CPU: Processor Core ID: 0
Sep 13 02:28:07 node-1 kernel: [    0.008661] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 13 02:28:07 node-1 kernel: [    0.008661] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 13 02:28:07 node-1 kernel: [    0.009354] mce: CPU supports 22 MCE banks
Sep 13 02:28:07 node-1 kernel: [    0.009382] CPU0: Thermal monitoring enabled (TM1)
Sep 13 02:28:07 node-1 kernel: [    0.009402] process: using mwait in idle threads
Sep 13 02:28:07 node-1 kernel: [    0.009405] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 13 02:28:07 node-1 kernel: [    0.009405] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 13 02:28:07 node-1 kernel: [    0.009405] tlb_flushall_shift: 6
Sep 13 02:28:07 node-1 kernel: [    0.009494] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 13 02:28:07 node-1 kernel: [    0.010216] ACPI: Core revision 20131115
Sep 13 02:28:07 node-1 kernel: [    0.022887] ACPI: All ACPI Tables successfully acquired
Sep 13 02:28:07 node-1 kernel: [    0.023037] ftrace: allocating 28617 entries in 112 pages
Sep 13 02:28:07 node-1 kernel: [    0.032019] dmar: Host address width 46
Sep 13 02:28:07 node-1 kernel: [    0.032021] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 13 02:28:07 node-1 kernel: [    0.032027] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 13 02:28:07 node-1 kernel: [    0.032028] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 13 02:28:07 node-1 kernel: [    0.032032] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 13 02:28:07 node-1 kernel: [    0.032034] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 13 02:28:07 node-1 kernel: [    0.032035] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 13 02:28:07 node-1 kernel: [    0.032036] dmar: ATSR flags: 0x0
Sep 13 02:28:07 node-1 kernel: [    0.032037] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 13 02:28:07 node-1 kernel: [    0.032038] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 13 02:28:07 node-1 kernel: [    0.032153] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 13 02:28:07 node-1 kernel: [    0.032155] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 13 02:28:07 node-1 kernel: [    0.032156] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 13 02:28:07 node-1 kernel: [    0.032157] HPET id 0 under DRHD base 0xc7ffc000
Sep 13 02:28:07 node-1 kernel: [    0.032158] Your BIOS is broken and requested that x2apic be disabled.
Sep 13 02:28:07 node-1 kernel: [    0.032158] This will slightly decrease performance.
Sep 13 02:28:07 node-1 kernel: [    0.032158] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 13 02:28:07 node-1 kernel: [    0.032588] Enabled IRQ remapping in xapic mode
Sep 13 02:28:07 node-1 kernel: [    0.032589] x2apic not enabled, IRQ remapping is in xapic mode
Sep 13 02:28:07 node-1 kernel: [    0.032593] Switched APIC routing to physical flat.
Sep 13 02:28:07 node-1 kernel: [    0.033210] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 13 02:28:07 node-1 kernel: [    0.072859] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 13 02:28:07 node-1 kernel: [    0.072864] TSC deadline timer enabled
Sep 13 02:28:07 node-1 kernel: [    0.072872] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 13 02:28:07 node-1 kernel: [    0.072878] ... version:                3
Sep 13 02:28:07 node-1 kernel: [    0.072879] ... bit width:              48
Sep 13 02:28:07 node-1 kernel: [    0.072879] ... generic registers:      4
Sep 13 02:28:07 node-1 kernel: [    0.072881] ... value mask:             0000ffffffffffff
Sep 13 02:28:07 node-1 kernel: [    0.072882] ... max period:             0000ffffffffffff
Sep 13 02:28:07 node-1 kernel: [    0.072883] ... fixed-purpose events:   3
Sep 13 02:28:07 node-1 kernel: [    0.072883] ... event mask:             000000070000000f
Sep 13 02:28:07 node-1 kernel: [    0.074278] x86: Booting SMP configuration:
Sep 13 02:28:07 node-1 kernel: [    0.088405] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 13 02:28:07 node-1 kernel: [    0.074280] .... node  #0, CPUs:        #1  #2  #3
Sep 13 02:28:07 node-1 kernel: [    0.116317] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 13 02:28:07 node-1 kernel: [    0.270263] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 13 02:28:07 node-1 kernel: [    0.325878] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 13 02:28:07 node-1 kernel: [    0.382730] x86: Booted up 2 nodes, 16 CPUs
Sep 13 02:28:07 node-1 kernel: [    0.382733] smpboot: Total of 16 processors activated (111753.22 BogoMIPS)
Sep 13 02:28:07 node-1 kernel: [    0.406382] devtmpfs: initialized
Sep 13 02:28:07 node-1 kernel: [    0.409516] EVM: security.selinux
Sep 13 02:28:07 node-1 kernel: [    0.409517] EVM: security.SMACK64
Sep 13 02:28:07 node-1 kernel: [    0.409518] EVM: security.ima
Sep 13 02:28:07 node-1 kernel: [    0.409519] EVM: security.capability
Sep 13 02:28:07 node-1 kernel: [    0.409571] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.410246] pinctrl core: initialized pinctrl subsystem
Sep 13 02:28:07 node-1 kernel: [    0.410308] regulator-dummy: no parameters
Sep 13 02:28:07 node-1 kernel: [    0.410340] RTC time:  2:27:31, date: 09/13/16
Sep 13 02:28:07 node-1 kernel: [    0.410375] NET: Registered protocol family 16
Sep 13 02:28:07 node-1 kernel: [    0.410460] cpuidle: using governor ladder
Sep 13 02:28:07 node-1 kernel: [    0.410461] cpuidle: using governor menu
Sep 13 02:28:07 node-1 kernel: [    0.410497] ACPI: bus type PCI registered
Sep 13 02:28:07 node-1 kernel: [    0.410499] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 13 02:28:07 node-1 kernel: [    0.410547] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 13 02:28:07 node-1 kernel: [    0.410549] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 13 02:28:07 node-1 kernel: [    0.424276] PCI: Using configuration type 1 for base access
Sep 13 02:28:07 node-1 kernel: [    0.425291] bio: create slab <bio-0> at 0
Sep 13 02:28:07 node-1 kernel: [    0.425569] ACPI: Added _OSI(Module Device)
Sep 13 02:28:07 node-1 kernel: [    0.425571] ACPI: Added _OSI(Processor Device)
Sep 13 02:28:07 node-1 kernel: [    0.425572] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 13 02:28:07 node-1 kernel: [    0.425573] ACPI: Added _OSI(Processor Aggregator Device)
Sep 13 02:28:07 node-1 kernel: [    0.438227] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 13 02:28:07 node-1 kernel: [    0.448715] ACPI: Interpreter enabled
Sep 13 02:28:07 node-1 kernel: [    0.448720] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 13 02:28:07 node-1 kernel: [    0.448724] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 13 02:28:07 node-1 kernel: [    0.448727] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 13 02:28:07 node-1 kernel: [    0.448733] ACPI: (supports S0 S4 S5)
Sep 13 02:28:07 node-1 kernel: [    0.448735] ACPI: Using IOAPIC for interrupt routing
Sep 13 02:28:07 node-1 kernel: [    0.448776] HEST: Table parsing has been initialized.
Sep 13 02:28:07 node-1 kernel: [    0.448779] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 13 02:28:07 node-1 kernel: [    0.449334] ACPI: No dock devices found.
Sep 13 02:28:07 node-1 kernel: [    0.461070] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 13 02:28:07 node-1 kernel: [    0.461074] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 02:28:07 node-1 kernel: [    0.461078] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 13 02:28:07 node-1 kernel: [    0.461104] PCI host bridge to bus 0000:ff
Sep 13 02:28:07 node-1 kernel: [    0.461106] pci_bus 0000:ff: root bus resource [bus ff]
Sep 13 02:28:07 node-1 kernel: [    0.461114] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461152] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.461183] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461218] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461247] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.461276] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.461306] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461335] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461364] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461392] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461419] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461445] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461473] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461499] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461525] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461552] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461580] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461607] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461634] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.461662] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461688] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.461714] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461740] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461770] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.461805] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461837] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461867] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461898] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461928] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461959] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.461992] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462024] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462054] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462086] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462116] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462147] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462180] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462210] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462238] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462269] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462301] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462337] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462372] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462403] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462432] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462461] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462493] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462523] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462556] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462586] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462618] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462647] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462677] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462706] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462735] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462767] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462798] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462856] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 13 02:28:07 node-1 kernel: [    0.462859] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 02:28:07 node-1 kernel: [    0.462862] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 13 02:28:07 node-1 kernel: [    0.462879] PCI host bridge to bus 0000:7f
Sep 13 02:28:07 node-1 kernel: [    0.462881] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 13 02:28:07 node-1 kernel: [    0.462886] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462915] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.462943] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462972] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.462994] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.463022] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.463048] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463074] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463096] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463119] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463143] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463167] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463193] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463216] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463241] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463268] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463290] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463312] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463335] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.463359] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463381] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.463405] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463429] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463457] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 13 02:28:07 node-1 kernel: [    0.463490] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463517] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463545] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463573] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463598] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463626] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463653] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463681] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463707] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463735] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463764] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463793] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463821] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463846] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463871] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463898] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463923] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463952] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.463983] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464012] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464039] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464064] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464090] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464117] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464145] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464172] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464203] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464229] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464252] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464278] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464304] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464334] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.464361] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.465618] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 13 02:28:07 node-1 kernel: [    0.465622] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 02:28:07 node-1 kernel: [    0.466746] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 13 02:28:07 node-1 kernel: [    0.467259] PCI host bridge to bus 0000:00
Sep 13 02:28:07 node-1 kernel: [    0.467262] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 13 02:28:07 node-1 kernel: [    0.467263] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 13 02:28:07 node-1 kernel: [    0.467265] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 13 02:28:07 node-1 kernel: [    0.467266] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 13 02:28:07 node-1 kernel: [    0.467267] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 13 02:28:07 node-1 kernel: [    0.467269] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 13 02:28:07 node-1 kernel: [    0.467270] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 13 02:28:07 node-1 kernel: [    0.467276] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 13 02:28:07 node-1 kernel: [    0.467360] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.467391] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.467432] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 13 02:28:07 node-1 kernel: [    0.467452] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.467481] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.467521] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 13 02:28:07 node-1 kernel: [    0.467544] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.467573] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.467613] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 13 02:28:07 node-1 kernel: [    0.467631] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.467702] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.467780] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.467857] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 13 02:28:07 node-1 kernel: [    0.467862] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 13 02:28:07 node-1 kernel: [    0.467947] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 13 02:28:07 node-1 kernel: [    0.468096] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 13 02:28:07 node-1 kernel: [    0.468113] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 13 02:28:07 node-1 kernel: [    0.468190] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.468245] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 13 02:28:07 node-1 kernel: [    0.468267] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.468323] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.468366] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 13 02:28:07 node-1 kernel: [    0.468394] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.468450] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.468493] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 13 02:28:07 node-1 kernel: [    0.468515] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 13 02:28:07 node-1 kernel: [    0.468533] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 13 02:28:07 node-1 kernel: [    0.468610] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.468660] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 13 02:28:07 node-1 kernel: [    0.468685] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 13 02:28:07 node-1 kernel: [    0.468932] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 13 02:28:07 node-1 kernel: [    0.468937] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 13 02:28:07 node-1 kernel: [    0.468944] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.468949] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.468957] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 13 02:28:07 node-1 kernel: [    0.468987] pci 0000:01:00.0: supports D1 D2
Sep 13 02:28:07 node-1 kernel: [    0.479015] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 13 02:28:07 node-1 kernel: [    0.479021] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 13 02:28:07 node-1 kernel: [    0.479025] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 13 02:28:07 node-1 kernel: [    0.479289] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.479350] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 13 02:28:07 node-1 kernel: [    0.487013] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 13 02:28:07 node-1 kernel: [    0.487019] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.487023] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 02:28:07 node-1 kernel: [    0.487116] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.487183] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.487260] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.487304] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 13 02:28:07 node-1 kernel: [    0.487307] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.487309] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 02:28:07 node-1 kernel: [    0.487361] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.487488] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.487541] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 13 02:28:07 node-1 kernel: [    0.487543] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.487545] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.487594] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.487713] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.487752] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.487871] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.487908] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.488047] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.488085] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 13 02:28:07 node-1 kernel: [    0.488203] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 13 02:28:07 node-1 kernel: [    0.488246] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 13 02:28:07 node-1 kernel: [    0.488249] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.488251] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.488309] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 13 02:28:07 node-1 kernel: [    0.488374] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.488426] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.488467] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 13 02:28:07 node-1 kernel: [    0.488549] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 13 02:28:07 node-1 kernel: [    0.488654] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 13 02:28:07 node-1 kernel: [    0.488657] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.488659] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.488715] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 13 02:28:07 node-1 kernel: [    0.488768] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.488817] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.489053] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 13 02:28:07 node-1 kernel: [    0.489057] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 13 02:28:07 node-1 kernel: [    0.489120] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 13 02:28:07 node-1 kernel: [    0.489176] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.489225] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.489433] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 13 02:28:07 node-1 kernel: [    0.489437] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 13 02:28:07 node-1 kernel: [    0.489495] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 13 02:28:07 node-1 kernel: [    0.489555] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.489608] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 13 02:28:07 node-1 kernel: [    0.489829] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 13 02:28:07 node-1 kernel: [    0.489833] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 13 02:28:07 node-1 kernel: [    0.490009] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 13 02:28:07 node-1 kernel: [    0.490047] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 13 02:28:07 node-1 kernel: [    0.490126] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 13 02:28:07 node-1 kernel: [    0.490144] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 13 02:28:07 node-1 kernel: [    0.490158] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 13 02:28:07 node-1 kernel: [    0.490171] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 13 02:28:07 node-1 kernel: [    0.490221] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 13 02:28:07 node-1 kernel: [    0.495025] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 13 02:28:07 node-1 kernel: [    0.495046] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 13 02:28:07 node-1 kernel: [    0.495078] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 13 02:28:07 node-1 kernel: [    0.495569] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 13 02:28:07 node-1 kernel: [    0.495572] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 02:28:07 node-1 kernel: [    0.495691] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 13 02:28:07 node-1 kernel: [    0.495798] PCI host bridge to bus 0000:80
Sep 13 02:28:07 node-1 kernel: [    0.495800] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 13 02:28:07 node-1 kernel: [    0.495801] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 13 02:28:07 node-1 kernel: [    0.495803] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 13 02:28:07 node-1 kernel: [    0.495811] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.495874] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.495941] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 13 02:28:07 node-1 kernel: [    0.496002] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 13 02:28:07 node-1 kernel: [    0.496007] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 13 02:28:07 node-1 kernel: [    0.496078] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 13 02:28:07 node-1 kernel: [    0.496376] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 13 02:28:07 node-1 kernel: [    0.496407] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 13 02:28:07 node-1 kernel: [    0.496437] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 13 02:28:07 node-1 kernel: [    0.496466] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 13 02:28:07 node-1 kernel: [    0.496496] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 02:28:07 node-1 kernel: [    0.496526] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 02:28:07 node-1 kernel: [    0.496556] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 02:28:07 node-1 kernel: [    0.496585] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 02:28:07 node-1 kernel: [    0.496670] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 13 02:28:07 node-1 kernel: [    0.496675] ACPI: \_SB_.UNC1: notify handler is installed
Sep 13 02:28:07 node-1 kernel: [    0.496676] ACPI: \_SB_.UNC0: notify handler is installed
Sep 13 02:28:07 node-1 kernel: [    0.496691] ACPI: \_SB_.PCI0: notify handler is installed
Sep 13 02:28:07 node-1 kernel: [    0.496744] ACPI: \_SB_.PCI1: notify handler is installed
Sep 13 02:28:07 node-1 kernel: [    0.496823] Found 4 acpi root devices
Sep 13 02:28:07 node-1 kernel: [    0.496931] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 13 02:28:07 node-1 kernel: [    0.496933] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 13 02:28:07 node-1 kernel: [    0.496935] vgaarb: loaded
Sep 13 02:28:07 node-1 kernel: [    0.496936] vgaarb: bridge control possible 0000:0c:00.0
Sep 13 02:28:07 node-1 kernel: [    0.497056] SCSI subsystem initialized
Sep 13 02:28:07 node-1 kernel: [    0.497121] libata version 3.00 loaded.
Sep 13 02:28:07 node-1 kernel: [    0.497136] ACPI: bus type USB registered
Sep 13 02:28:07 node-1 kernel: [    0.497147] usbcore: registered new interface driver usbfs
Sep 13 02:28:07 node-1 kernel: [    0.497152] usbcore: registered new interface driver hub
Sep 13 02:28:07 node-1 kernel: [    0.497176] usbcore: registered new device driver usb
Sep 13 02:28:07 node-1 kernel: [    0.497340] PCI: Using ACPI for IRQ routing
Sep 13 02:28:07 node-1 kernel: [    0.500924] PCI: pci_cache_line_size set to 64 bytes
Sep 13 02:28:07 node-1 kernel: [    0.501128] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 13 02:28:07 node-1 kernel: [    0.501129] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 13 02:28:07 node-1 kernel: [    0.501130] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 13 02:28:07 node-1 kernel: [    0.501195] NetLabel: Initializing
Sep 13 02:28:07 node-1 kernel: [    0.501196] NetLabel:  domain hash size = 128
Sep 13 02:28:07 node-1 kernel: [    0.501197] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 13 02:28:07 node-1 kernel: [    0.501207] NetLabel:  unlabeled traffic allowed by default
Sep 13 02:28:07 node-1 kernel: [    0.501263] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 13 02:28:07 node-1 kernel: [    0.501267] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 13 02:28:07 node-1 kernel: [    0.503324] Switched to clocksource hpet
Sep 13 02:28:07 node-1 kernel: [    0.507173] AppArmor: AppArmor Filesystem Enabled
Sep 13 02:28:07 node-1 kernel: [    0.507188] pnp: PnP ACPI init
Sep 13 02:28:07 node-1 kernel: [    0.507195] ACPI: bus type PNP registered
Sep 13 02:28:07 node-1 kernel: [    0.507312] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507326] pnp 00:01: [dma 4]
Sep 13 02:28:07 node-1 kernel: [    0.507338] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507364] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507384] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507401] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507434] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507488] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507490] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 13 02:28:07 node-1 kernel: [    0.507492] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507493] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507495] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507499] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507501] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 13 02:28:07 node-1 kernel: [    0.507503] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507504] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507506] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507507] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507509] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507510] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 13 02:28:07 node-1 kernel: [    0.507512] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507596] pnp 00:07: [dma 0 disabled]
Sep 13 02:28:07 node-1 kernel: [    0.507624] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507699] pnp 00:08: [dma 0 disabled]
Sep 13 02:28:07 node-1 kernel: [    0.507730] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 13 02:28:07 node-1 kernel: [    0.507781] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 13 02:28:07 node-1 kernel: [    0.508132] pnp: PnP ACPI: found 10 devices
Sep 13 02:28:07 node-1 kernel: [    0.508134] ACPI: bus type PNP unregistered
Sep 13 02:28:07 node-1 kernel: [    0.514444] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 13 02:28:07 node-1 kernel: [    0.514447] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 13 02:28:07 node-1 kernel: [    0.514450] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 13 02:28:07 node-1 kernel: [    0.514454] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 13 02:28:07 node-1 kernel: [    0.514456] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514471] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514503] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 13 02:28:07 node-1 kernel: [    0.514517] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514546] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 13 02:28:07 node-1 kernel: [    0.514561] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 13 02:28:07 node-1 kernel: [    0.514589] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 13 02:28:07 node-1 kernel: [    0.514604] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 13 02:28:07 node-1 kernel: [    0.514633] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 13 02:28:07 node-1 kernel: [    0.514634] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514649] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514678] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 13 02:28:07 node-1 kernel: [    0.514680] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514694] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514723] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 13 02:28:07 node-1 kernel: [    0.514724] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514727] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514731] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 13 02:28:07 node-1 kernel: [    0.514733] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514735] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514739] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 13 02:28:07 node-1 kernel: [    0.514744] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 13 02:28:07 node-1 kernel: [    0.514752] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 13 02:28:07 node-1 kernel: [    0.514755] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 13 02:28:07 node-1 kernel: [    0.514761] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 13 02:28:07 node-1 kernel: [    0.514762] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 13 02:28:07 node-1 kernel: [    0.514763] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 13 02:28:07 node-1 kernel: [    0.514764] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 13 02:28:07 node-1 kernel: [    0.514765] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 13 02:28:07 node-1 kernel: [    0.514766] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 13 02:28:07 node-1 kernel: [    0.514767] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 13 02:28:07 node-1 kernel: [    0.514768] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 13 02:28:07 node-1 kernel: [    0.514769] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514770] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514770] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514771] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514772] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514773] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514774] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514775] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514776] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 13 02:28:07 node-1 kernel: [    0.514777] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514778] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 13 02:28:07 node-1 kernel: [    0.514779] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 13 02:28:07 node-1 kernel: [    0.514779] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 13 02:28:07 node-1 kernel: [    0.514781] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 13 02:28:07 node-1 kernel: [    0.514782] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 13 02:28:07 node-1 kernel: [    0.514783] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 13 02:28:07 node-1 kernel: [    0.514819] NET: Registered protocol family 2
Sep 13 02:28:07 node-1 kernel: [    0.515076] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.515414] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.515559] TCP: Hash tables configured (established 262144 bind 65536)
Sep 13 02:28:07 node-1 kernel: [    0.515596] TCP: reno registered
Sep 13 02:28:07 node-1 kernel: [    0.515623] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.515719] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.515867] NET: Registered protocol family 1
Sep 13 02:28:07 node-1 kernel: [    0.551428] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 13 02:28:07 node-1 kernel: [    0.551443] PCI: CLS 64 bytes, default 64
Sep 13 02:28:07 node-1 kernel: [    0.551518] Trying to unpack rootfs image as initramfs...
Sep 13 02:28:07 node-1 kernel: [    0.771665] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 13 02:28:07 node-1 kernel: [    0.771710] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 13 02:28:07 node-1 kernel: [    0.771712] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 13 02:28:07 node-1 kernel: [    0.772107] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772113] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772118] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772123] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772133] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772143] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772152] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772161] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772169] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772178] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772184] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772190] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772197] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772204] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772212] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772219] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 02:28:07 node-1 kernel: [    0.772288] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 13 02:28:07 node-1 kernel: [    0.772292] Scanning for low memory corruption every 60 seconds
Sep 13 02:28:07 node-1 kernel: [    0.772583] Initialise system trusted keyring
Sep 13 02:28:07 node-1 kernel: [    0.772628] audit: initializing netlink socket (disabled)
Sep 13 02:28:07 node-1 kernel: [    0.772637] type=2000 audit(1473733650.728:1): initialized
Sep 13 02:28:07 node-1 kernel: [    0.790406] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 13 02:28:07 node-1 kernel: [    0.791903] zbud: loaded
Sep 13 02:28:07 node-1 kernel: [    0.792017] VFS: Disk quotas dquot_6.5.2
Sep 13 02:28:07 node-1 kernel: [    0.792057] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 13 02:28:07 node-1 kernel: [    0.792422] fuse init (API version 7.22)
Sep 13 02:28:07 node-1 kernel: [    0.792481] msgmni has been set to 32768
Sep 13 02:28:07 node-1 kernel: [    0.792524] Key type big_key registered
Sep 13 02:28:07 node-1 kernel: [    0.793035] Key type asymmetric registered
Sep 13 02:28:07 node-1 kernel: [    0.793037] Asymmetric key parser 'x509' registered
Sep 13 02:28:07 node-1 kernel: [    0.793066] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 13 02:28:07 node-1 kernel: [    0.793126] io scheduler noop registered
Sep 13 02:28:07 node-1 kernel: [    0.793128] io scheduler deadline registered (default)
Sep 13 02:28:07 node-1 kernel: [    0.793145] io scheduler cfq registered
Sep 13 02:28:07 node-1 kernel: [    0.793432] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    0.793523] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    0.793609] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    0.793696] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    0.793791] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    0.793857] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    0.794116] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 13 02:28:07 node-1 kernel: [    0.794134] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 13 02:28:07 node-1 kernel: [    0.794146] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 13 02:28:07 node-1 kernel: [    0.794155] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794157] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794160] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 13 02:28:07 node-1 kernel: [    0.794164] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794165] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794166] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794168] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794169] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794171] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794172] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794173] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794175] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794176] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794177] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794179] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794181] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 13 02:28:07 node-1 kernel: [    0.794184] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794186] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 13 02:28:07 node-1 kernel: [    0.794195] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794198] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 13 02:28:07 node-1 kernel: [    0.794206] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794208] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 13 02:28:07 node-1 kernel: [    0.794210] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 13 02:28:07 node-1 kernel: [    0.794223] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 13 02:28:07 node-1 kernel: [    0.794332] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 13 02:28:07 node-1 kernel: [    0.794336] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 13 02:28:07 node-1 kernel: [    0.794345] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 13 02:28:07 node-1 kernel: [    0.794379] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 13 02:28:07 node-1 kernel: [    0.794381] vesafb: scrolling: redraw
Sep 13 02:28:07 node-1 kernel: [    0.794382] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 13 02:28:07 node-1 kernel: [    0.815235] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 13 02:28:07 node-1 kernel: [    0.823731] Console: switching to colour frame buffer device 80x30
Sep 13 02:28:07 node-1 kernel: [    0.832402] fb0: VESA VGA frame buffer device
Sep 13 02:28:07 node-1 kernel: [    0.832604] intel_idle: MWAIT substates: 0x2120
Sep 13 02:28:07 node-1 kernel: [    0.832605] intel_idle: v0.4 model 0x3F
Sep 13 02:28:07 node-1 kernel: [    0.832606] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 13 02:28:07 node-1 kernel: [    0.832832] ipmi message handler version 39.2
Sep 13 02:28:07 node-1 kernel: [    0.833098] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 13 02:28:07 node-1 kernel: [    0.833530] ACPI: AC Adapter [P111] (on-line)
Sep 13 02:28:07 node-1 kernel: [    0.838751] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 13 02:28:07 node-1 kernel: [    0.849766] ACPI: Power Button [PWRB]
Sep 13 02:28:07 node-1 kernel: [    0.855549] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 13 02:28:07 node-1 kernel: [    0.867278] ACPI: Power Button [PWRF]
Sep 13 02:28:07 node-1 kernel: [    0.892973] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 13 02:28:07 node-1 kernel: [    0.904713] pstore: Registered erst as persistent store backend
Sep 13 02:28:07 node-1 kernel: [    0.910927] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 13 02:28:07 node-1 kernel: [    0.922913] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 13 02:28:07 node-1 kernel: [    0.949659] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 13 02:28:07 node-1 kernel: [    0.982958] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 13 02:28:07 node-1 kernel: [    0.997040] Linux agpgart interface v0.103
Sep 13 02:28:07 node-1 kernel: [    1.004719] brd: module loaded
Sep 13 02:28:07 node-1 kernel: [    1.011787] loop: module loaded
Sep 13 02:28:07 node-1 kernel: [    1.018527] libphy: Fixed MDIO Bus: probed
Sep 13 02:28:07 node-1 kernel: [    1.024991] tun: Universal TUN/TAP device driver, 1.6
Sep 13 02:28:07 node-1 kernel: [    1.031487] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 13 02:28:07 node-1 kernel: [    1.038001] PPP generic driver version 2.4.2
Sep 13 02:28:07 node-1 kernel: [    1.044379] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 13 02:28:07 node-1 kernel: [    1.050803] ehci-pci: EHCI PCI platform driver
Sep 13 02:28:07 node-1 kernel: [    1.057386] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 13 02:28:07 node-1 kernel: [    1.063797] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 13 02:28:07 node-1 kernel: [    1.076333] ehci-pci 0000:00:1a.0: debug port 2
Sep 13 02:28:07 node-1 kernel: [    1.086511] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 13 02:28:07 node-1 kernel: [    1.086529] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 13 02:28:07 node-1 kernel: [    1.102819] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 13 02:28:07 node-1 kernel: [    1.108899] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 13 02:28:07 node-1 kernel: [    1.115058] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 13 02:28:07 node-1 kernel: [    1.126930] usb usb1: Product: EHCI Host Controller
Sep 13 02:28:07 node-1 kernel: [    1.132947] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 13 02:28:07 node-1 kernel: [    1.138986] usb usb1: SerialNumber: 0000:00:1a.0
Sep 13 02:28:07 node-1 kernel: [    1.144920] hub 1-0:1.0: USB hub found
Sep 13 02:28:07 node-1 kernel: [    1.150682] hub 1-0:1.0: 2 ports detected
Sep 13 02:28:07 node-1 kernel: [    1.156470] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 13 02:28:07 node-1 kernel: [    1.162027] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 13 02:28:07 node-1 kernel: [    1.172917] ehci-pci 0000:00:1d.0: debug port 2
Sep 13 02:28:07 node-1 kernel: [    1.182223] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 13 02:28:07 node-1 kernel: [    1.182226] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 13 02:28:07 node-1 kernel: [    1.198737] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 13 02:28:07 node-1 kernel: [    1.203979] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 13 02:28:07 node-1 kernel: [    1.209283] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 13 02:28:07 node-1 kernel: [    1.219839] usb usb2: Product: EHCI Host Controller
Sep 13 02:28:07 node-1 kernel: [    1.225301] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 13 02:28:07 node-1 kernel: [    1.230849] usb usb2: SerialNumber: 0000:00:1d.0
Sep 13 02:28:07 node-1 kernel: [    1.236360] hub 2-0:1.0: USB hub found
Sep 13 02:28:07 node-1 kernel: [    1.241712] hub 2-0:1.0: 2 ports detected
Sep 13 02:28:07 node-1 kernel: [    1.247008] ehci-platform: EHCI generic platform driver
Sep 13 02:28:07 node-1 kernel: [    1.252244] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 13 02:28:07 node-1 kernel: [    1.257557] ohci-pci: OHCI PCI platform driver
Sep 13 02:28:07 node-1 kernel: [    1.262851] ohci-platform: OHCI generic platform driver
Sep 13 02:28:07 node-1 kernel: [    1.268051] uhci_hcd: USB Universal Host Controller Interface driver
Sep 13 02:28:07 node-1 kernel: [    1.273382] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 13 02:28:07 node-1 kernel: [    1.466519] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 13 02:28:07 node-1 kernel: [    1.630684] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 13 02:28:07 node-1 kernel: [    1.636213] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 13 02:28:07 node-1 kernel: [    1.641948] hub 1-1:1.0: USB hub found
Sep 13 02:28:07 node-1 kernel: [    1.647422] hub 1-1:1.0: 6 ports detected
Sep 13 02:28:07 node-1 kernel: [    1.762257] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 13 02:28:07 node-1 kernel: [    1.770276] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 13 02:28:07 node-1 kernel: [    2.030346] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 13 02:28:07 node-1 kernel: [    2.035902] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 13 02:28:07 node-1 kernel: [    2.041738] hub 2-1:1.0: USB hub found
Sep 13 02:28:07 node-1 kernel: [    2.047457] hub 2-1:1.0: 8 ports detected
Sep 13 02:28:07 node-1 kernel: [    2.314827] i8042: No controller found
Sep 13 02:28:07 node-1 kernel: [    2.320225] mousedev: PS/2 mouse device common for all mice
Sep 13 02:28:07 node-1 kernel: [    2.325729] rtc_cmos 00:02: RTC can wake from S4
Sep 13 02:28:07 node-1 kernel: [    2.325904] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 13 02:28:07 node-1 kernel: [    2.336939] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 13 02:28:07 node-1 kernel: [    2.342624] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 13 02:28:07 node-1 kernel: [    2.353907] device-mapper: uevent: version 1.0.3
Sep 13 02:28:07 node-1 kernel: [    2.359558] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 13 02:28:07 node-1 kernel: [    2.370833] ledtrig-cpu: registered to indicate activity on CPUs
Sep 13 02:28:07 node-1 kernel: [    2.376797] TCP: cubic registered
Sep 13 02:28:07 node-1 kernel: [    2.382696] NET: Registered protocol family 10
Sep 13 02:28:07 node-1 kernel: [    2.388697] NET: Registered protocol family 17
Sep 13 02:28:07 node-1 kernel: [    2.394390] Key type dns_resolver registered
Sep 13 02:28:07 node-1 kernel: [    2.400347] Loading compiled-in X.509 certificates
Sep 13 02:28:07 node-1 kernel: [    2.406623] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 13 02:28:07 node-1 kernel: [    2.418064] registered taskstats version 1
Sep 13 02:28:07 node-1 kernel: [    2.426069] Key type trusted registered
Sep 13 02:28:07 node-1 kernel: [    2.433626] Key type encrypted registered
Sep 13 02:28:07 node-1 kernel: [    2.439103] AppArmor: AppArmor sha1 policy hashing enabled
Sep 13 02:28:07 node-1 kernel: [    2.444599] IMA: No TPM chip found, activating TPM-bypass!
Sep 13 02:28:07 node-1 kernel: [    2.450778] regulator-dummy: disabling
Sep 13 02:28:07 node-1 kernel: [    2.456369]   Magic number: 0:131:460
Sep 13 02:28:07 node-1 kernel: [    2.462080] rtc_cmos 00:02: setting system clock to 2016-09-13 02:27:33 UTC (1473733653)
Sep 13 02:28:07 node-1 kernel: [    2.462179] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 13 02:28:07 node-1 kernel: [    2.462180] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 13 02:28:07 node-1 kernel: [    2.462181] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 13 02:28:07 node-1 kernel: [    2.462182] usb 2-1.4: Manufacturer: Avocent
Sep 13 02:28:07 node-1 kernel: [    2.462182] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 13 02:28:07 node-1 kernel: [    2.508901] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 13 02:28:07 node-1 kernel: [    2.514614] EDD information not available.
Sep 13 02:28:07 node-1 kernel: [    2.520292] PM: Hibernation image not present or could not be loaded.
Sep 13 02:28:07 node-1 kernel: [    2.521155] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 13 02:28:07 node-1 kernel: [    2.532484] Write protecting the kernel read-only data: 12288k
Sep 13 02:28:07 node-1 kernel: [    2.538809] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 13 02:28:07 node-1 kernel: [    2.551315] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 13 02:28:07 node-1 kernel: [    2.583913] device-mapper: multipath: version 1.6.0 loaded
Sep 13 02:28:07 node-1 kernel: [    2.591888] systemd-udevd[217]: starting version 204
Sep 13 02:28:07 node-1 kernel: [    2.616964] md: linear personality registered for level -1
Sep 13 02:28:07 node-1 kernel: [    2.630883] md: multipath personality registered for level -4
Sep 13 02:28:07 node-1 kernel: [    2.638871] md: raid0 personality registered for level 0
Sep 13 02:28:07 node-1 kernel: [    2.646996] md: raid1 personality registered for level 1
Sep 13 02:28:07 node-1 kernel: [    2.658586] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 13 02:28:07 node-1 kernel: [    2.664987] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 13 02:28:07 node-1 kernel: [    2.665323] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 13 02:28:07 node-1 kernel: [    2.676279] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 13 02:28:07 node-1 kernel: [    2.676307] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 13 02:28:07 node-1 kernel: [    2.676309] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 02:28:07 node-1 kernel: [    2.677017] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.677081] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.677160] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.677249] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.677891] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.691705] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 13 02:28:07 node-1 kernel: [    2.691718] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 13 02:28:07 node-1 kernel: [    2.691719] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 02:28:07 node-1 kernel: [    2.692003] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.692102] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.692192] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.692278] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.692617] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.705188] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 13 02:28:07 node-1 kernel: [    2.705201] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 13 02:28:07 node-1 kernel: [    2.705210] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 02:28:07 node-1 kernel: [    2.705640] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.705727] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.705799] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.705883] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.706131] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.720229] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 13 02:28:07 node-1 kernel: [    2.720231] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 13 02:28:07 node-1 kernel: [    2.720270] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 02:28:07 node-1 kernel: [    2.720529] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.720610] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.720683] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.720784] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.721401] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 02:28:07 node-1 kernel: [    2.721727] raid6: sse2x1     749 MB/s
Sep 13 02:28:07 node-1 kernel: [    2.789790] raid6: sse2x2     588 MB/s
Sep 13 02:28:07 node-1 kernel: [    2.857520] raid6: sse2x4    1304 MB/s
Sep 13 02:28:07 node-1 kernel: [    2.925286] raid6: avx2x1    9890 MB/s
Sep 13 02:28:07 node-1 kernel: [    2.997227] raid6: avx2x2   18875 MB/s
Sep 13 02:28:07 node-1 kernel: [    3.069164] raid6: avx2x4   21315 MB/s
Sep 13 02:28:07 node-1 kernel: [    3.074950] raid6: using algorithm avx2x4 (21315 MB/s)
Sep 13 02:28:07 node-1 kernel: [    3.080886] raid6: using avx2x2 recovery algorithm
Sep 13 02:28:07 node-1 kernel: [    3.086689] Switched to clocksource tsc
Sep 13 02:28:07 node-1 kernel: [    3.087239] megasas: FW now in Ready state
Sep 13 02:28:07 node-1 kernel: [    3.087755] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.087866] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.087951] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088074] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088170] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088217] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088386] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088426] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088546] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088652] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088747] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.088854] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.089039] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.089293] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.089396] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.089447] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Sep 13 02:28:07 node-1 kernel: [    3.090024] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 13 02:28:07 node-1 kernel: [    3.108919] xor: automatically using best checksumming function:
Sep 13 02:28:07 node-1 kernel: [    3.108920] hidraw: raw HID events driver (C) Jiri Kosina
Sep 13 02:28:07 node-1 kernel: [    3.122966] usbcore: registered new interface driver usbhid
Sep 13 02:28:07 node-1 kernel: [    3.128573] usbhid: USB HID core driver
Sep 13 02:28:07 node-1 kernel: [    3.139451] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 13 02:28:07 node-1 kernel: [    3.150618] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 13 02:28:07 node-1 kernel: [    3.157131]    avx       : 35565.000 MB/sec
Sep 13 02:28:07 node-1 kernel: [    3.167551] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 13 02:28:07 node-1 kernel: [    3.179116] async_tx: api initialized (async)
Sep 13 02:28:07 node-1 kernel: [    3.179144] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 13 02:28:07 node-1 kernel: [    3.179202] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 13 02:28:07 node-1 kernel: [    3.179240] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 13 02:28:07 node-1 kernel: [    3.223690] md: raid6 personality registered for level 6
Sep 13 02:28:07 node-1 kernel: [    3.229985] md: raid5 personality registered for level 5
Sep 13 02:28:07 node-1 kernel: [    3.236284] md: raid4 personality registered for level 4
Sep 13 02:28:07 node-1 kernel: [    3.245550] md: raid10 personality registered for level 10
Sep 13 02:28:07 node-1 kernel: [    3.300398] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Sep 13 02:28:07 node-1 kernel: [    3.424868] megasas:IOC Init cmd success
Sep 13 02:28:07 node-1 kernel: [    3.452894] megasas: INIT adapter done
Sep 13 02:28:07 node-1 kernel: [    3.552787] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 13 02:28:07 node-1 kernel: [    3.559685] scsi0 : LSI SAS based MegaRAID driver
Sep 13 02:28:07 node-1 kernel: [    3.567050] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 13 02:28:07 node-1 kernel: [    3.586173] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 13 02:28:07 node-1 kernel: [    3.601656] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 13 02:28:07 node-1 kernel: [    3.608190] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 13 02:28:07 node-1 kernel: [    3.621132] sd 0:2:0:0: [sda] Write Protect is off
Sep 13 02:28:07 node-1 kernel: [    3.627501] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 13 02:28:07 node-1 kernel: [    3.627520] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 13 02:28:07 node-1 kernel: [    3.668766]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 13 02:28:07 node-1 kernel: [    3.675418] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 13 02:28:07 node-1 kernel: [    3.834008] random: lvm urandom read with 26 bits of entropy available
Sep 13 02:28:07 node-1 kernel: [    3.946780] bio: create slab <bio-1> at 1
Sep 13 02:28:07 node-1 kernel: [    4.712483] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 02:28:07 node-1 kernel: [    5.228675] init: plymouth-upstart-bridge main process (552) terminated with status 1
Sep 13 02:28:07 node-1 kernel: [    5.241048] init: plymouth-upstart-bridge main process ended, respawning
Sep 13 02:28:07 node-1 kernel: [    5.419771] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 13 02:28:07 node-1 kernel: [    5.457113] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 13 02:28:07 node-1 kernel: [    5.567512] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 13 02:28:07 node-1 kernel: [    5.603449] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 13 02:28:07 node-1 kernel: [    5.613363] random: nonblocking pool is initialized
Sep 13 02:28:07 node-1 kernel: [    5.715500] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 02:28:07 node-1 kernel: [    5.912649] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 13 02:28:07 node-1 kernel: [    5.946111] XFS (dm-0): Mounting Filesystem
Sep 13 02:28:07 node-1 kernel: [    6.113124] XFS (dm-0): Ending clean mount
Sep 13 02:28:07 node-1 kernel: [    6.150705] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 02:28:07 node-1 kernel: [    6.224352] XFS (dm-1): Mounting Filesystem
Sep 13 02:28:07 node-1 kernel: [    6.309360] XFS (dm-1): Ending clean mount
Sep 13 02:28:07 node-1 kernel: [    8.223092] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 13 02:28:07 node-1 kernel: [    8.249062] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 13 02:28:07 node-1 kernel: [    8.410647] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 13 02:28:07 node-1 kernel: [    8.410653] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 13 02:28:07 node-1 kernel: [    8.410658] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 13 02:28:07 node-1 kernel: [    8.410662] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 13 02:28:07 node-1 kernel: [    8.451537] systemd-udevd[778]: starting version 204
Sep 13 02:28:07 node-1 kernel: [    8.680143] IPMI System Interface driver.
Sep 13 02:28:07 node-1 kernel: [    8.680214] ipmi_si: probing via ACPI
Sep 13 02:28:07 node-1 kernel: [    8.680231] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 13 02:28:07 node-1 kernel: [    8.680233] ipmi_si: Adding ACPI-specified kcs state machine
Sep 13 02:28:07 node-1 kernel: [    8.680243] ipmi_si: probing via SMBIOS
Sep 13 02:28:07 node-1 kernel: [    8.680244] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 13 02:28:07 node-1 kernel: [    8.680245] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 13 02:28:07 node-1 kernel: [    8.680247] ipmi_si: probing via SPMI
Sep 13 02:28:07 node-1 kernel: [    8.680247] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 13 02:28:07 node-1 kernel: [    8.680248] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 13 02:28:07 node-1 kernel: [    8.680249] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 13 02:28:07 node-1 kernel: [    8.710575] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 13 02:28:07 node-1 kernel: [    8.710580] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 13 02:28:07 node-1 kernel: [    8.710583] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 13 02:28:07 node-1 kernel: [    8.710584] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 13 02:28:07 node-1 kernel: [    8.710611] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 13 02:28:07 node-1 kernel: [    8.714605] power_meter ACPI000D:00: Found ACPI power meter.
Sep 13 02:28:07 node-1 kernel: [    8.714618] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 13 02:28:07 node-1 kernel: [    8.724717] wmi: Mapper loaded
Sep 13 02:28:07 node-1 kernel: [    8.747581] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 13 02:28:07 node-1 kernel: [    8.769648] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 13 02:28:07 node-1 kernel: [    8.769653] ipmi_si 00:09: IPMI kcs interface initialized
Sep 13 02:28:07 node-1 kernel: [    8.856719] systemd-udevd[806]: renamed network interface eth3 to enp9s0
Sep 13 02:28:07 node-1 kernel: [    8.876613] systemd-udevd[796]: renamed network interface eth1 to enp7s0
Sep 13 02:28:07 node-1 kernel: [    8.924573] systemd-udevd[800]: renamed network interface eth2 to enp8s0
Sep 13 02:28:07 node-1 kernel: [    8.948545] systemd-udevd[807]: renamed network interface eth0 to enp6s0
Sep 13 02:28:07 node-1 kernel: [    9.306142] type=1400 audit(1473733660.344:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1076 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.306308] type=1400 audit(1473733660.344:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1076 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.306440] type=1400 audit(1473733660.344:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1076 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.311363] type=1400 audit(1473733660.348:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1051 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.311513] type=1400 audit(1473733660.348:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1051 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.311691] type=1400 audit(1473733660.348:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1051 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.311715] type=1400 audit(1473733660.348:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.311873] type=1400 audit(1473733660.352:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.312008] type=1400 audit(1473733660.352:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.319424] type=1400 audit(1473733660.356:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Sep 13 02:28:07 node-1 kernel: [    9.830078] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 13 02:28:07 node-1 kernel: [    9.831034] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 13 02:28:07 node-1 kernel: [    9.981821] enic 0000:06:00.0 enp6s0: Link UP
Sep 13 02:28:07 node-1 kernel: [    9.984834] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 13 02:28:07 node-1 kernel: [    9.984843] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 13 02:28:07 node-1 kernel: [   19.435754] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 13 02:28:07 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 13 02:28:09 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 13 02:28:09 node-1 kernel: [   38.138041] init: failsafe main process (8418) killed by TERM signal
Sep 13 02:28:09 node-1 dbus[8467]: [system] AppArmor D-Bus mediation is enabled
Sep 13 02:28:09 node-1 kernel: [   38.340389] audit_printk_skb: 30 callbacks suppressed
Sep 13 02:28:09 node-1 kernel: [   38.340389] type=1400 audit(1473733689.319:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8536 comm="apparmor_parser"
Sep 13 02:28:09 node-1 kernel: [   38.340521] type=1400 audit(1473733689.319:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8535 comm="apparmor_parser"
Sep 13 02:28:09 node-1 kernel: [   38.340525] type=1400 audit(1473733689.319:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8535 comm="apparmor_parser"
Sep 13 02:28:09 node-1 kernel: [   38.340527] type=1400 audit(1473733689.319:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8535 comm="apparmor_parser"
Sep 13 02:28:09 node-1 kernel: [   38.340744] type=1400 audit(1473733689.319:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8535 comm="apparmor_parser"
Sep 13 02:28:09 node-1 kernel: [   38.340746] type=1400 audit(1473733689.319:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8535 comm="apparmor_parser"
Sep 13 02:28:09 node-1 kernel: [   38.340858] type=1400 audit(1473733689.319:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8535 comm="apparmor_parser"
Sep 13 02:28:09 node-1 kernel: [   38.415333] type=1400 audit(1473733689.395:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8538 comm="apparmor_parser"
Sep 13 02:28:09 node-1 cron[8575]: (CRON) INFO (pidfile fd = 3)
Sep 13 02:28:09 node-1 anacron[8609]: Anacron 2.3 started on 2016-09-13
Sep 13 02:28:09 node-1 cron[8611]: (CRON) STARTUP (fork ok)
Sep 13 02:28:09 node-1 anacron[8609]: Will run job `cron.daily' in 5 min.
Sep 13 02:28:09 node-1 anacron[8609]: Will run job `cron.weekly' in 10 min.
Sep 13 02:28:09 node-1 anacron[8609]: Will run job `cron.monthly' in 15 min.
Sep 13 02:28:09 node-1 anacron[8609]: Jobs will be executed sequentially
Sep 13 02:28:09 node-1 cron[8611]: (CRON) INFO (Running @reboot jobs)
Sep 13 02:28:09 node-1 multipathd: path checkers start up
Sep 13 02:28:10 node-1 postfix/master[8755]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 13 02:28:13 node-1 puppet-agent[8940]: Reopening log files
Sep 13 02:28:13 node-1 puppet-agent[8940]: Could not request certificate: Connection refused - connect(2)
Sep 13 02:28:28 node-1 puppet-user[9148]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 13 02:28:28 node-1 puppet-user[9148]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Sep 13 02:28:29 node-1 puppet-user[9148]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 13 02:28:29 node-1 puppet-user[9148]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 13 02:28:29 node-1 puppet-user[9148]: Finished catalog run in 1.00 seconds
Sep 13 02:28:30 node-1 multipathd: uevent trigger error
Sep 13 02:28:30 node-1 puppet-user[9578]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 13 02:28:30 node-1 puppet-user[9578]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 13 02:28:31 node-1 puppet-user[9578]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 13 02:28:31 node-1 puppet-user[9578]: Finished catalog run in 0.06 seconds
Sep 13 02:28:32 node-1 puppet-user[10034]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 13 02:28:32 node-1 puppet-user[10034]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 13 02:28:32 node-1 puppet-user[10034]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 13 02:28:32 node-1 puppet-user[10034]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 13 02:28:32 node-1 puppet-user[10034]: Finished catalog run in 0.02 seconds
Sep 13 02:28:33 node-1 puppet-user[10492]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 13 02:28:33 node-1 puppet-user[10492]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 13 02:28:33 node-1 puppet-user[10492]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 13 02:28:34 node-1 puppet-user[10492]: Finished catalog run in 0.03 seconds
Sep 13 02:28:35 node-1 puppet-user[10934]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 13 02:28:35 node-1 puppet-user[10934]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Sep 13 02:28:35 node-1 puppet-user[10934]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 13 02:28:35 node-1 puppet-user[10934]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 13 02:28:35 node-1 puppet-user[10934]: Finished catalog run in 0.47 seconds
Sep 13 02:28:37 node-1 puppet-user[11413]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 13 02:28:37 node-1 puppet-user[11413]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 13 02:28:37 node-1 puppet-user[11413]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 13 02:28:37 node-1 puppet-user[11413]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 13 02:28:37 node-1 puppet-user[11413]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 13 02:28:37 node-1 puppet-user[11413]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 13 02:28:37 node-1 puppet-user[11413]: Finished catalog run in 0.29 seconds
Sep 13 02:28:39 node-1 puppet-user[12075]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 13 02:28:39 node-1 puppet-user[12075]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep 13 02:28:39 node-1 puppet-user[12075]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 13 02:28:39 node-1 kernel: [   68.440880] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 13 02:28:39 node-1 kernel: [   68.440929] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 13 02:28:39 node-1 puppet-user[12075]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 13 02:28:39 node-1 puppet-user[12075]: Finished catalog run in 0.05 seconds
Sep 13 02:28:41 node-1 puppet-user[12532]: (Scope(Class[main])) MODULAR: sync_time
Sep 13 02:28:41 node-1 puppet-user[12532]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 13 02:28:41 node-1 ntpdate[12943]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 13 02:28:47 node-1 ntpdate[12943]: adjust time server 10.20.0.2 offset 0.042499 sec
Sep 13 02:28:47 node-1 puppet-user[12532]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 13 02:28:47 node-1 puppet-user[12532]: Finished catalog run in 6.18 seconds
Sep 13 02:28:50 node-1 kernel: [   79.440988] init: plymouth-upstart-bridge main process ended, respawning
Sep 13 02:28:50 node-1 puppet-agent[8940]: Could not run: SIGTERM
Sep 13 02:28:50 node-1 kernel: [   79.695927] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 13 02:28:50 node-1 ec2: 
Sep 13 02:28:50 node-1 ec2: #############################################################
Sep 13 02:28:50 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 13 02:28:50 node-1 ec2: 1024 ed:55:60:19:28:3a:b7:51:06:8c:ab:9a:36:bb:c7:b0  root@node-1.domain.tld (DSA)
Sep 13 02:28:50 node-1 ec2: 256 89:9d:98:1b:c3:e7:27:82:35:51:66:0b:42:47:87:71  root@node-1.domain.tld (ECDSA)
Sep 13 02:28:50 node-1 ec2: 256 af:c4:49:31:e5:16:14:8c:78:41:45:2f:00:e6:c9:b4  root@node-1.domain.tld (ED25519)
Sep 13 02:28:50 node-1 ec2: 2048 a9:7f:1a:96:62:9f:c3:e7:97:48:54:c7:7d:32:8d:df  root@node-1.domain.tld (RSA)
Sep 13 02:28:50 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 13 02:28:50 node-1 ec2: #############################################################
Sep 13 02:28:53 node-1 puppet-user[13311]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 13 02:28:53 node-1 puppet-user[13311]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 13 02:28:53 node-1 puppet-user[13311]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 13 02:28:53 node-1 puppet-user[13311]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Sep 13 02:28:53 node-1 puppet-user[13311]: Finished catalog run in 0.08 seconds
Sep 13 02:28:55 node-1 puppet-user[13768]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 13 02:28:56 node-1 puppet-user[13768]: Compiled catalog for node-1.domain.tld in environment production in 1.48 seconds
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 13 02:28:56 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Sep 13 02:28:57 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 13 02:28:57 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Sep 13 02:28:57 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Sep 13 02:28:57 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 13 02:28:57 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Sep 13 02:28:57 node-1 puppet-user[13768]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 13 02:29:01 node-1 CRON[14428]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 13 02:29:03 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 02:29:03 node-1 nailgun-agent: I, [2016-09-13T02:29:03.776734 #14431]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 13 02:29:07 node-1 puppet-user[13768]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep 13 02:29:07 node-1 puppet-user[13768]: Finished catalog run in 10.33 seconds
Sep 13 02:29:08 node-1 puppet-user[14780]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 13 02:29:08 node-1 puppet-user[14780]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Sep 13 02:29:13 node-1 puppet-user[14780]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 13 02:29:16 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 02:29:16 node-1 nailgun-agent: I, [2016-09-13T02:29:16.657555 #14431]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 13 02:29:52 node-1 puppet-user[14780]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 13 02:29:52 node-1 puppet-user[14780]: Finished catalog run in 44.07 seconds
Sep 13 02:29:54 node-1 puppet-user[17610]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 13 02:29:55 node-1 puppet-user[17610]: Compiled catalog for node-1.domain.tld in environment production in 0.58 seconds
Sep 13 02:29:55 node-1 puppet-user[17610]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 13 02:29:55 node-1 puppet-user[17610]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 13 02:29:55 node-1 puppet-user[17610]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 13 02:29:55 node-1 puppet-user[17610]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 13 02:29:55 node-1 puppet-user[17610]: Finished catalog run in 0.12 seconds
Sep 13 02:29:57 node-1 puppet-user[18054]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 13 02:29:57 node-1 puppet-user[18054]: Compiled catalog for node-1.domain.tld in environment production in 0.91 seconds
Sep 13 02:29:58 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 13 02:29:58 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 13 02:29:58 node-1 crontab[18490]: (root) LIST (root)
Sep 13 02:29:58 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 13 02:29:58 node-1 crontab[18491]: (root) REPLACE (root)
Sep 13 02:30:00 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 13 02:30:01 node-1 CRON[18637]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 13 02:30:01 node-1 CRON[18638]: (root) CMD (/usr/bin/fuel-logrotate)
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 13 02:30:02 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 13 02:30:03 node-1 puppet-user[18054]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 13 02:30:03 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 02:30:03 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 13 02:30:04 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:04 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:04 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:04 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:04 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:30:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:31:28 node-1 ntpdate[30816]: no servers can be used, exiting
<27>Sep 13 02:32:00 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:00 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:00 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:00 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:03 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:03 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:03 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:03 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:03 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:15 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:15 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:15 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:15 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:15 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:32:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 02:33:29 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 02:33:34 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 02:33:34 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 02:33:40 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 02:33:46 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 02:33:46 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 02:33:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:33:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:06 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:06 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:06 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:34:39 node-1 multipathd: uevent trigger error
<129>Sep 13 02:34:42 node-1 haproxy[25431]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 61ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:34:42 node-1 haproxy[25431]: proxy odl-neutron-endpoint has no server available!
<129>Sep 13 02:34:43 node-1 haproxy[25445]: Server odl-jetty/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:34:43 node-1 haproxy[25445]: proxy odl-jetty has no server available!
<27>Sep 13 02:35:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:05 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:07 node-1 haproxy[27768]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:07 node-1 haproxy[27768]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:08 node-1 haproxy[27772]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:08 node-1 haproxy[27772]: proxy mysqld has no server available!
<27>Sep 13 02:35:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:14 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:14 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:14 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:14 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:14 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:14 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:17 node-1 haproxy[30527]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:17 node-1 haproxy[30527]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:17 node-1 haproxy[30527]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:17 node-1 haproxy[30527]: proxy mysqld has no server available!
<129>Sep 13 02:35:17 node-1 haproxy[30527]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:18 node-1 haproxy[30531]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:18 node-1 haproxy[30531]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:18 node-1 haproxy[30531]: proxy object-storage has no server available!
<27>Sep 13 02:35:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:20 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:22 node-1 haproxy[31916]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:22 node-1 haproxy[31916]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:22 node-1 haproxy[31916]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:22 node-1 haproxy[31916]: proxy neutron has no server available!
<129>Sep 13 02:35:22 node-1 haproxy[31916]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:22 node-1 haproxy[31916]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:23 node-1 haproxy[31920]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:23 node-1 haproxy[31920]: proxy mysqld has no server available!
<129>Sep 13 02:35:23 node-1 haproxy[31920]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:23 node-1 haproxy[31920]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:23 node-1 haproxy[31920]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:23 node-1 haproxy[31920]: proxy object-storage has no server available!
<27>Sep 13 02:35:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:25 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:28 node-1 haproxy[1032]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:28 node-1 haproxy[1032]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:28 node-1 haproxy[1032]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:28 node-1 haproxy[1032]: proxy keystone-1 has no server available!
<129>Sep 13 02:35:28 node-1 haproxy[1032]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:29 node-1 haproxy[1046]: proxy keystone-2 has no server available!
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:29 node-1 haproxy[1046]: proxy neutron has no server available!
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:29 node-1 haproxy[1046]: proxy mysqld has no server available!
<129>Sep 13 02:35:29 node-1 haproxy[1046]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:30 node-1 haproxy[1046]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:30 node-1 haproxy[1046]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:30 node-1 haproxy[1046]: proxy object-storage has no server available!
<27>Sep 13 02:35:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:31 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:34 node-1 haproxy[2390]: proxy keystone-1 has no server available!
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:34 node-1 haproxy[2390]: proxy keystone-2 has no server available!
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:34 node-1 haproxy[2390]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:34 node-1 haproxy[2390]: proxy neutron has no server available!
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:35 node-1 haproxy[2396]: proxy mysqld has no server available!
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:35 node-1 haproxy[2396]: proxy object-storage has no server available!
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:35 node-1 haproxy[2396]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:35 node-1 haproxy[2396]: proxy aodh has no server available!
<27>Sep 13 02:35:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:37 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:39 node-1 haproxy[3756]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:39 node-1 haproxy[3756]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:39 node-1 haproxy[3756]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:39 node-1 haproxy[3756]: proxy keystone-1 has no server available!
<129>Sep 13 02:35:39 node-1 haproxy[3756]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:39 node-1 haproxy[3756]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:40 node-1 haproxy[3762]: proxy keystone-2 has no server available!
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:40 node-1 haproxy[3762]: proxy neutron has no server available!
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:40 node-1 haproxy[3762]: proxy mysqld has no server available!
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:40 node-1 haproxy[3762]: proxy object-storage has no server available!
<129>Sep 13 02:35:40 node-1 haproxy[3762]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:41 node-1 haproxy[3762]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:41 node-1 haproxy[3762]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:41 node-1 haproxy[3762]: proxy aodh has no server available!
<129>Sep 13 02:35:41 node-1 haproxy[3762]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:41 node-1 haproxy[3762]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:41 node-1 haproxy[3762]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:41 node-1 haproxy[3762]: proxy ceilometer has no server available!
<27>Sep 13 02:35:42 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:42 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:42 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:42 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:45 node-1 haproxy[5093]: proxy keystone-1 has no server available!
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:45 node-1 haproxy[5093]: proxy keystone-2 has no server available!
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:45 node-1 haproxy[5093]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:45 node-1 haproxy[5093]: proxy neutron has no server available!
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:46 node-1 haproxy[5097]: proxy mysqld has no server available!
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:46 node-1 haproxy[5097]: proxy object-storage has no server available!
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:46 node-1 haproxy[5097]: proxy aodh has no server available!
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:46 node-1 haproxy[5097]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:46 node-1 haproxy[5097]: proxy ceilometer has no server available!
<27>Sep 13 02:35:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:48 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:50 node-1 haproxy[6465]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:50 node-1 haproxy[6465]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:50 node-1 haproxy[6465]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:50 node-1 haproxy[6465]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:50 node-1 haproxy[6465]: proxy keystone-1 has no server available!
<129>Sep 13 02:35:50 node-1 haproxy[6465]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:51 node-1 haproxy[6469]: proxy keystone-2 has no server available!
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:51 node-1 haproxy[6469]: proxy neutron has no server available!
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:51 node-1 haproxy[6469]: proxy mysqld has no server available!
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:51 node-1 haproxy[6469]: proxy object-storage has no server available!
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:51 node-1 haproxy[6469]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:52 node-1 haproxy[6469]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:52 node-1 haproxy[6469]: proxy aodh has no server available!
<129>Sep 13 02:35:52 node-1 haproxy[6469]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:52 node-1 haproxy[6469]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:52 node-1 haproxy[6469]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:52 node-1 haproxy[6469]: proxy ceilometer has no server available!
<27>Sep 13 02:35:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:53 node-1 multipathd: uevent trigger error
<129>Sep 13 02:35:56 node-1 haproxy[7887]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:56 node-1 haproxy[7887]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:56 node-1 haproxy[7887]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:56 node-1 haproxy[7887]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:56 node-1 haproxy[7887]: proxy keystone-1 has no server available!
<129>Sep 13 02:35:56 node-1 haproxy[7887]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:56 node-1 haproxy[7887]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:56 node-1 haproxy[7887]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:56 node-1 haproxy[7887]: proxy keystone-2 has no server available!
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:57 node-1 haproxy[7891]: proxy glance-api has no server available!
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:57 node-1 haproxy[7891]: proxy glance-glare has no server available!
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:57 node-1 haproxy[7891]: proxy neutron has no server available!
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:57 node-1 haproxy[7891]: proxy glance-registry has no server available!
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:57 node-1 haproxy[7891]: proxy mysqld has no server available!
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:57 node-1 haproxy[7891]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:57 node-1 haproxy[7891]: proxy object-storage has no server available!
<129>Sep 13 02:35:58 node-1 haproxy[7891]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:58 node-1 haproxy[7891]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:58 node-1 haproxy[7891]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:58 node-1 haproxy[7891]: proxy aodh has no server available!
<129>Sep 13 02:35:58 node-1 haproxy[7891]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:58 node-1 haproxy[7891]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:35:58 node-1 haproxy[7891]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:35:58 node-1 haproxy[7891]: proxy ceilometer has no server available!
<27>Sep 13 02:35:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:35:59 node-1 multipathd: uevent trigger error
<129>Sep 13 02:36:02 node-1 haproxy[9481]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:02 node-1 haproxy[9481]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:02 node-1 haproxy[9481]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy keystone-1 has no server available!
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy keystone-2 has no server available!
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy nova-api has no server available!
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy nova-metadata-api has no server available!
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy glance-api has no server available!
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy glance-glare has no server available!
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy neutron has no server available!
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:03 node-1 haproxy[9487]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:03 node-1 haproxy[9487]: proxy glance-registry has no server available!
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:04 node-1 haproxy[9487]: proxy mysqld has no server available!
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:04 node-1 haproxy[9487]: proxy object-storage has no server available!
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:04 node-1 haproxy[9487]: proxy aodh has no server available!
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:04 node-1 haproxy[9487]: proxy ceilometer has no server available!
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:04 node-1 haproxy[9487]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:04 node-1 haproxy[9487]: proxy nova-novncproxy has no server available!
<27>Sep 13 02:36:06 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:06 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:06 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:06 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:06 node-1 multipathd: uevent trigger error
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:08 node-1 haproxy[10825]: proxy keystone-1 has no server available!
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:08 node-1 haproxy[10825]: proxy keystone-2 has no server available!
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:08 node-1 haproxy[10825]: proxy nova-api has no server available!
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:08 node-1 haproxy[10825]: proxy nova-metadata-api has no server available!
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:08 node-1 haproxy[10825]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy cinder-api has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy glance-api has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy glance-glare has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy neutron has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy glance-registry has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy mysqld has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy object-storage has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:09 node-1 haproxy[10829]: proxy aodh has no server available!
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:09 node-1 haproxy[10829]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:10 node-1 haproxy[10829]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:10 node-1 haproxy[10829]: proxy ceilometer has no server available!
<129>Sep 13 02:36:10 node-1 haproxy[10829]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:10 node-1 haproxy[10829]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:10 node-1 haproxy[10829]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:10 node-1 haproxy[10829]: proxy nova-novncproxy has no server available!
<27>Sep 13 02:36:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:11 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:11 node-1 multipathd: uevent trigger error
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:14 node-1 haproxy[12216]: proxy keystone-1 has no server available!
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:14 node-1 haproxy[12216]: proxy keystone-2 has no server available!
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:14 node-1 haproxy[12216]: proxy nova-api has no server available!
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:14 node-1 haproxy[12216]: proxy nova-metadata-api has no server available!
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:14 node-1 haproxy[12216]: proxy cinder-api has no server available!
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:14 node-1 haproxy[12216]: proxy glance-api has no server available!
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:14 node-1 haproxy[12216]: proxy glance-glare has no server available!
<129>Sep 13 02:36:14 node-1 haproxy[12216]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy neutron has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy glance-registry has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy mysqld has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy object-storage has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy aodh has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy ceilometer has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy heat-api has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy heat-api-cfn has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:15 node-1 haproxy[12220]: proxy heat-api-cloudwatch has no server available!
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:15 node-1 haproxy[12220]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 02:36:16 node-1 haproxy[12220]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 02:36:16 node-1 haproxy[12220]: proxy nova-novncproxy has no server available!
<27>Sep 13 02:36:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:17 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 13 02:36:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 02:36:28 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 02:36:37 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 13 02:37:02 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Sep 13 02:37:04 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 13 02:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 02:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 02:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 02:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 02:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 02:39:39 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 02:40:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:28 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:33 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:33 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:33 node-1 multipathd: uevent trigger error
<43>Sep 13 02:40:54 node-1 apache2_error [Tue Sep 13 02:40:46.927289 2016] [mpm_event:notice] [pid 26797:tid 140645019105152] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 13 02:40:54 node-1 apache2_error [Tue Sep 13 02:40:46.927433 2016] [core:notice] [pid 26797:tid 140645019105152] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 13 02:40:54 node-1 apache2_error [Tue Sep 13 02:40:50.226341 2016] [mpm_event:notice] [pid 26797:tid 140645019105152] AH00491: caught SIGTERM, shutting down
<43>Sep 13 02:40:54 node-1 apache2_error [Tue Sep 13 02:40:51.302159 2016] [mpm_worker:notice] [pid 27168:tid 140235867060096] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 13 02:40:54 node-1 apache2_error [Tue Sep 13 02:40:51.302210 2016] [core:notice] [pid 27168:tid 140235867060096] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 02:40:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:40:59 node-1 multipathd: uevent trigger error
<43>Sep 13 02:42:14 node-1 apache2_error [Tue Sep 13 02:42:07.944832 2016] [mpm_worker:notice] [pid 27168:tid 140235867060096] AH00295: caught SIGTERM, shutting down
<43>Sep 13 02:42:14 node-1 apache2_error [Tue Sep 13 02:42:08.700599 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 02:42:14 node-1 apache2_error [Tue Sep 13 02:42:08.700646 2016] [core:notice] [pid 8378:tid 139703261960064] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 02:42:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 13 02:42:54 node-1 apache2_error [Tue Sep 13 02:42:52.759325 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 02:42:54 node-1 apache2_error [Tue Sep 13 02:42:52.953776 2016] [mpm_worker:warn] [pid 8378:tid 139703261960064] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 02:42:54 node-1 apache2_error [Tue Sep 13 02:42:52.958779 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 02:42:54 node-1 apache2_error [Tue Sep 13 02:42:52.958806 2016] [core:notice] [pid 8378:tid 139703261960064] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 02:43:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:37 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:18 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:23 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:44:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:45:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:45:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:45:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:45:39 node-1 multipathd: uevent trigger error
<27>Sep 13 02:45:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 02:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:53 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:47:59 node-1 multipathd: uevent trigger error
<27>Sep 13 02:48:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:48:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:48:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:48:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:48:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:48:22 node-1 multipathd: uevent trigger error
<27>Sep 13 02:48:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 02:50:49 node-1 multipathd: uevent trigger error
<27>Sep 13 02:50:49 node-1 multipathd: uevent trigger error
<27>Sep 13 02:50:49 node-1 multipathd: uevent trigger error
<27>Sep 13 02:50:49 node-1 multipathd: uevent trigger error
<27>Sep 13 02:50:49 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:16 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:16 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:16 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:16 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:16 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:41 node-1 multipathd: uevent trigger error
<27>Sep 13 02:51:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 02:52:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:52:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:52:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:52:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:52:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:52:26 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:10 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:53:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:54:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 02:56:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:05 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:43 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:56:48 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:25 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:30 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:30 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:30 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:30 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:30 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:33 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:33 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:33 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:33 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:33 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:46 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:46 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:46 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:46 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:46 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:49 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 02:57:52 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:52 node-1 multipathd: uevent trigger error
<27>Sep 13 02:57:52 node-1 multipathd: uevent trigger error
<27>Sep 13 02:58:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:58:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:58:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:58:31 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:38 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:38 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:38 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:38 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:57 node-1 multipathd: uevent trigger error
<27>Sep 13 02:59:57 node-1 multipathd: uevent trigger error
<11>Sep 13 03:00:11 node-1 liberasurecode[24965]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:11 node-1 liberasurecode[24965]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:11 node-1 liberasurecode[24965]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:11 node-1 liberasurecode[24965]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:11 node-1 liberasurecode[24998]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:11 node-1 liberasurecode[24998]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:11 node-1 liberasurecode[24998]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:11 node-1 liberasurecode[24998]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:13 node-1 liberasurecode[25779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:13 node-1 liberasurecode[25779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:13 node-1 liberasurecode[25779]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:13 node-1 liberasurecode[25779]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26506]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26506]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26506]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26506]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26550]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26550]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26550]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:18 node-1 liberasurecode[26550]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26665]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26665]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26750]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26750]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26764]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26764]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26764]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26764]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26783]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26783]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26783]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26783]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26803]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26803]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26803]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:19 node-1 liberasurecode[26803]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:36 node-1 liberasurecode[27886]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:36 node-1 liberasurecode[27886]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:36 node-1 liberasurecode[27886]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:00:36 node-1 liberasurecode[27886]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 13 03:00:44 node-1 multipathd: uevent trigger error
<27>Sep 13 03:00:44 node-1 multipathd: uevent trigger error
<27>Sep 13 03:00:44 node-1 multipathd: uevent trigger error
<27>Sep 13 03:00:44 node-1 multipathd: uevent trigger error
<27>Sep 13 03:00:44 node-1 multipathd: uevent trigger error
<27>Sep 13 03:00:44 node-1 multipathd: uevent trigger error
<27>Sep 13 03:00:50 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 13 03:01:35 node-1 apache2_error [Tue Sep 13 03:01:33.850291 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 03:01:35 node-1 apache2_error [Tue Sep 13 03:01:34.231976 2016] [mpm_worker:warn] [pid 8378:tid 139703261960064] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 03:01:35 node-1 apache2_error [Tue Sep 13 03:01:34.236338 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 03:01:35 node-1 apache2_error [Tue Sep 13 03:01:34.236380 2016] [core:notice] [pid 8378:tid 139703261960064] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 03:02:15 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:15 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:15 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:15 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:15 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:15 node-1 multipathd: uevent trigger error
<43>Sep 13 03:02:15 node-1 apache2_error [Tue Sep 13 03:02:11.138609 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 03:02:15 node-1 apache2_error [Tue Sep 13 03:02:11.331101 2016] [mpm_worker:warn] [pid 8378:tid 139703261960064] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 03:02:15 node-1 apache2_error [Tue Sep 13 03:02:11.339689 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 03:02:15 node-1 apache2_error [Tue Sep 13 03:02:11.339716 2016] [core:notice] [pid 8378:tid 139703261960064] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 03:02:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:02:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:01 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:01 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:01 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:01 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:01 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:01 node-1 multipathd: uevent trigger error
<43>Sep 13 03:03:05 node-1 apache2_error [Tue Sep 13 03:02:57.068843 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 03:03:05 node-1 apache2_error [Tue Sep 13 03:02:57.262454 2016] [mpm_worker:warn] [pid 8378:tid 139703261960064] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 03:03:05 node-1 apache2_error [Tue Sep 13 03:02:57.269629 2016] [mpm_worker:notice] [pid 8378:tid 139703261960064] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 03:03:05 node-1 apache2_error [Tue Sep 13 03:02:57.269656 2016] [core:notice] [pid 8378:tid 139703261960064] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 03:03:08 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:08 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:08 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:08 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:08 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:14 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:14 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:14 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:14 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:14 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:23 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:23 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:23 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:23 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:23 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:39 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:39 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:39 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:39 node-1 multipathd: uevent trigger error
<27>Sep 13 03:03:52 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 03:04:00 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:08 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 13 03:04:16 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:16 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:16 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:16 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:16 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:21 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:21 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:21 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:21 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:27 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:38 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:38 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:38 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:38 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:54 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:54 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:54 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:54 node-1 multipathd: uevent trigger error
<27>Sep 13 03:04:55 node-1 multipathd: uevent trigger error
<11>Sep 13 03:05:01 node-1 liberasurecode[21798]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:05:01 node-1 liberasurecode[21798]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:05:01 node-1 liberasurecode[21798]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 03:05:01 node-1 liberasurecode[21798]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 13 03:05:02 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 03:05:10 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:10 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:10 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:10 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:10 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:24 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:24 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:24 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:24 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:24 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:31 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:31 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:31 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:31 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:36 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:36 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:36 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:36 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:48 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:48 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:48 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:48 node-1 multipathd: uevent trigger error
<27>Sep 13 03:05:48 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:17 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:17 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:17 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:17 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:17 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:22 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:26 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:30 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:30 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:30 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:30 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:30 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:30 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:35 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:35 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:35 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:35 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:40 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:40 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:40 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:40 node-1 multipathd: uevent trigger error
<27>Sep 13 03:06:40 node-1 multipathd: uevent trigger error
