Jul 31 00:16:03 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8414" x-info="http://www.rsyslog.com"] start
Jul 31 00:16:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 31 00:16:03 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 31 00:16:03 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 31 00:16:03 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 00:16:03 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 31 00:16:03 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 31 00:16:03 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 31 00:16:03 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=69b270f3-b4c4-47b8-8641-5ced645b037d nomdmonddf nomdmonisw
Jul 31 00:16:03 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 31 00:16:03 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 31 00:16:03 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 31 00:16:03 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 31 00:16:03 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 31 00:16:03 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 31 00:16:03 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 31 00:16:03 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
Jul 31 00:16:03 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 31 00:16:03 node-1 kernel: [    0.000000] No AGP bridge found
Jul 31 00:16:03 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 31 00:16:03 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 31 00:16:03 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 31 00:16:03 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 31 00:16:03 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 31 00:16:03 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 31 00:16:03 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 31 00:16:03 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 31 00:16:03 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 31 00:16:03 node-1 kernel: [    0.000000]   2 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000]   3 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000]   4 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000]   5 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000]   6 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000]   7 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000]   8 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000]   9 disabled
Jul 31 00:16:03 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 31 00:16:03 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 31 00:16:03 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 31 00:16:03 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 31 00:16:03 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 31 00:16:03 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 31 00:16:03 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 31 00:16:03 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 31 00:16:03 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 31 00:16:03 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 31 00:16:03 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 31 00:16:03 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 31 00:16:03 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 31 00:16:03 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 31 00:16:03 node-1 kernel: [    0.000000] Zone ranges:
Jul 31 00:16:03 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 31 00:16:03 node-1 kernel: [    0.000000] Early memory node ranges
Jul 31 00:16:03 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 31 00:16:03 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 31 00:16:03 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 31 00:16:03 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 31 00:16:03 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 31 00:16:03 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 31 00:16:03 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 31 00:16:03 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 31 00:16:03 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 31 00:16:03 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 31 00:16:03 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 31 00:16:03 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 31 00:16:03 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 31 00:16:03 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 31 00:16:03 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 31 00:16:03 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 31 00:16:03 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 31 00:16:03 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 31 00:16:03 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 31 00:16:03 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 31 00:16:03 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 31 00:16:03 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 31 00:16:03 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 31 00:16:03 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 
Jul 31 00:16:03 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 31 00:16:03 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 31 00:16:03 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=69b270f3-b4c4-47b8-8641-5ced645b037d nomdmonddf nomdmonisw
Jul 31 00:16:03 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 31 00:16:03 node-1 kernel: [    0.000000] Checking aperture...
Jul 31 00:16:03 node-1 kernel: [    0.000000] No AGP bridge found
Jul 31 00:16:03 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 31 00:16:03 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 31 00:16:03 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 31 00:16:03 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 31 00:16:03 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 31 00:16:03 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 31 00:16:03 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 31 00:16:03 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 31 00:16:03 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 31 00:16:03 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 31 00:16:03 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 31 00:16:03 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 31 00:16:03 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 31 00:16:03 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 31 00:16:03 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 31 00:16:03 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 31 00:16:03 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 31 00:16:03 node-1 kernel: [    0.004000] tsc: Detected 3492.034 MHz processor
Jul 31 00:16:03 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.06 BogoMIPS (lpj=13968136)
Jul 31 00:16:03 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 31 00:16:03 node-1 kernel: [    0.000042] Security Framework initialized
Jul 31 00:16:03 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 31 00:16:03 node-1 kernel: [    0.000063] Yama: becoming mindful.
Jul 31 00:16:03 node-1 kernel: [    0.001450] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.006277] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.008204] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.008233] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.008525] Initializing cgroup subsys memory
Jul 31 00:16:03 node-1 kernel: [    0.008533] Initializing cgroup subsys devices
Jul 31 00:16:03 node-1 kernel: [    0.008535] Initializing cgroup subsys freezer
Jul 31 00:16:03 node-1 kernel: [    0.008537] Initializing cgroup subsys blkio
Jul 31 00:16:03 node-1 kernel: [    0.008539] Initializing cgroup subsys perf_event
Jul 31 00:16:03 node-1 kernel: [    0.008541] Initializing cgroup subsys hugetlb
Jul 31 00:16:03 node-1 kernel: [    0.008561] CPU: Physical Processor ID: 0
Jul 31 00:16:03 node-1 kernel: [    0.008562] CPU: Processor Core ID: 0
Jul 31 00:16:03 node-1 kernel: [    0.008566] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 31 00:16:03 node-1 kernel: [    0.008566] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 31 00:16:03 node-1 kernel: [    0.009259] mce: CPU supports 22 MCE banks
Jul 31 00:16:03 node-1 kernel: [    0.009286] CPU0: Thermal monitoring enabled (TM1)
Jul 31 00:16:03 node-1 kernel: [    0.009307] process: using mwait in idle threads
Jul 31 00:16:03 node-1 kernel: [    0.009310] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 31 00:16:03 node-1 kernel: [    0.009310] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 31 00:16:03 node-1 kernel: [    0.009310] tlb_flushall_shift: 6
Jul 31 00:16:03 node-1 kernel: [    0.009399] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 31 00:16:03 node-1 kernel: [    0.010124] ACPI: Core revision 20131115
Jul 31 00:16:03 node-1 kernel: [    0.022823] ACPI: All ACPI Tables successfully acquired
Jul 31 00:16:03 node-1 kernel: [    0.022983] ftrace: allocating 28617 entries in 112 pages
Jul 31 00:16:03 node-1 kernel: [    0.031799] dmar: Host address width 46
Jul 31 00:16:03 node-1 kernel: [    0.031801] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 31 00:16:03 node-1 kernel: [    0.031807] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 00:16:03 node-1 kernel: [    0.031809] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 31 00:16:03 node-1 kernel: [    0.031813] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 00:16:03 node-1 kernel: [    0.031814] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 31 00:16:03 node-1 kernel: [    0.031816] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 31 00:16:03 node-1 kernel: [    0.031817] dmar: ATSR flags: 0x0
Jul 31 00:16:03 node-1 kernel: [    0.031818] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 31 00:16:03 node-1 kernel: [    0.031819] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 31 00:16:03 node-1 kernel: [    0.031934] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 31 00:16:03 node-1 kernel: [    0.031935] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 00:16:03 node-1 kernel: [    0.031936] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 00:16:03 node-1 kernel: [    0.031937] HPET id 0 under DRHD base 0xc7ffc000
Jul 31 00:16:03 node-1 kernel: [    0.031939] Your BIOS is broken and requested that x2apic be disabled.
Jul 31 00:16:03 node-1 kernel: [    0.031939] This will slightly decrease performance.
Jul 31 00:16:03 node-1 kernel: [    0.031939] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 31 00:16:03 node-1 kernel: [    0.032372] Enabled IRQ remapping in xapic mode
Jul 31 00:16:03 node-1 kernel: [    0.032373] x2apic not enabled, IRQ remapping is in xapic mode
Jul 31 00:16:03 node-1 kernel: [    0.032377] Switched APIC routing to physical flat.
Jul 31 00:16:03 node-1 kernel: [    0.033002] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 31 00:16:03 node-1 kernel: [    0.072654] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 31 00:16:03 node-1 kernel: [    0.072660] TSC deadline timer enabled
Jul 31 00:16:03 node-1 kernel: [    0.072667] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 31 00:16:03 node-1 kernel: [    0.072673] ... version:                3
Jul 31 00:16:03 node-1 kernel: [    0.072674] ... bit width:              48
Jul 31 00:16:03 node-1 kernel: [    0.072675] ... generic registers:      4
Jul 31 00:16:03 node-1 kernel: [    0.072676] ... value mask:             0000ffffffffffff
Jul 31 00:16:03 node-1 kernel: [    0.072677] ... max period:             0000ffffffffffff
Jul 31 00:16:03 node-1 kernel: [    0.072678] ... fixed-purpose events:   3
Jul 31 00:16:03 node-1 kernel: [    0.072678] ... event mask:             000000070000000f
Jul 31 00:16:03 node-1 kernel: [    0.074104] x86: Booting SMP configuration:
Jul 31 00:16:03 node-1 kernel: [    0.088209] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 31 00:16:03 node-1 kernel: [    0.074106] .... node  #0, CPUs:        #1  #2  #3
Jul 31 00:16:03 node-1 kernel: [    0.116116] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 31 00:16:03 node-1 kernel: [    0.270071] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 31 00:16:03 node-1 kernel: [    0.325686] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 31 00:16:03 node-1 kernel: [    0.382546] x86: Booted up 2 nodes, 16 CPUs
Jul 31 00:16:03 node-1 kernel: [    0.382550] smpboot: Total of 16 processors activated (111757.76 BogoMIPS)
Jul 31 00:16:03 node-1 kernel: [    0.406125] devtmpfs: initialized
Jul 31 00:16:03 node-1 kernel: [    0.409193] EVM: security.selinux
Jul 31 00:16:03 node-1 kernel: [    0.409195] EVM: security.SMACK64
Jul 31 00:16:03 node-1 kernel: [    0.409195] EVM: security.ima
Jul 31 00:16:03 node-1 kernel: [    0.409196] EVM: security.capability
Jul 31 00:16:03 node-1 kernel: [    0.409247] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.409920] pinctrl core: initialized pinctrl subsystem
Jul 31 00:16:03 node-1 kernel: [    0.409982] regulator-dummy: no parameters
Jul 31 00:16:03 node-1 kernel: [    0.410014] RTC time:  0:15:27, date: 07/31/16
Jul 31 00:16:03 node-1 kernel: [    0.410049] NET: Registered protocol family 16
Jul 31 00:16:03 node-1 kernel: [    0.410134] cpuidle: using governor ladder
Jul 31 00:16:03 node-1 kernel: [    0.410135] cpuidle: using governor menu
Jul 31 00:16:03 node-1 kernel: [    0.410169] ACPI: bus type PCI registered
Jul 31 00:16:03 node-1 kernel: [    0.410170] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 31 00:16:03 node-1 kernel: [    0.410217] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 31 00:16:03 node-1 kernel: [    0.410219] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 31 00:16:03 node-1 kernel: [    0.423948] PCI: Using configuration type 1 for base access
Jul 31 00:16:03 node-1 kernel: [    0.424944] bio: create slab <bio-0> at 0
Jul 31 00:16:03 node-1 kernel: [    0.425252] ACPI: Added _OSI(Module Device)
Jul 31 00:16:03 node-1 kernel: [    0.425253] ACPI: Added _OSI(Processor Device)
Jul 31 00:16:03 node-1 kernel: [    0.425255] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 31 00:16:03 node-1 kernel: [    0.425256] ACPI: Added _OSI(Processor Aggregator Device)
Jul 31 00:16:03 node-1 kernel: [    0.437931] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 31 00:16:03 node-1 kernel: [    0.449709] ACPI: Interpreter enabled
Jul 31 00:16:03 node-1 kernel: [    0.449715] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 31 00:16:03 node-1 kernel: [    0.449719] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 31 00:16:03 node-1 kernel: [    0.449721] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 31 00:16:03 node-1 kernel: [    0.449728] ACPI: (supports S0 S4 S5)
Jul 31 00:16:03 node-1 kernel: [    0.449729] ACPI: Using IOAPIC for interrupt routing
Jul 31 00:16:03 node-1 kernel: [    0.449771] HEST: Table parsing has been initialized.
Jul 31 00:16:03 node-1 kernel: [    0.449774] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 31 00:16:03 node-1 kernel: [    0.450327] ACPI: No dock devices found.
Jul 31 00:16:03 node-1 kernel: [    0.461880] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 31 00:16:03 node-1 kernel: [    0.461885] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:03 node-1 kernel: [    0.461888] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 00:16:03 node-1 kernel: [    0.461914] PCI host bridge to bus 0000:ff
Jul 31 00:16:03 node-1 kernel: [    0.461916] pci_bus 0000:ff: root bus resource [bus ff]
Jul 31 00:16:03 node-1 kernel: [    0.461924] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.461962] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.461992] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462026] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462055] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.462084] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.462114] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462141] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462170] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462199] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462225] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462252] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462280] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462306] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462332] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462359] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462387] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462414] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462441] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.462469] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462495] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.462520] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462546] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462576] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.462611] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462642] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462672] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462702] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462733] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462764] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462797] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462829] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462860] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462891] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462921] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462952] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.462984] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463012] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463039] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463072] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463105] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463143] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463179] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463211] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463241] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463272] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463303] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463333] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463364] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463397] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463428] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463458] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463488] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463517] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463547] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463578] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463612] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463669] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 31 00:16:03 node-1 kernel: [    0.463672] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:03 node-1 kernel: [    0.463675] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 00:16:03 node-1 kernel: [    0.463693] PCI host bridge to bus 0000:7f
Jul 31 00:16:03 node-1 kernel: [    0.463694] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 31 00:16:03 node-1 kernel: [    0.463699] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463727] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.463755] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463789] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463810] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.463835] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.463862] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463888] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463911] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463934] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463956] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.463979] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464003] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464025] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464049] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464075] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464096] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464119] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464141] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.464165] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464187] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.464209] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464231] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464258] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 00:16:03 node-1 kernel: [    0.464293] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464319] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464345] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464371] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464396] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464424] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464452] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464481] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464506] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464533] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464560] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464589] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464617] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464642] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464667] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464695] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464720] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464746] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464775] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464803] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464830] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464855] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464883] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464912] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464940] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464967] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.464997] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.465023] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.465045] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.465071] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.465097] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.465127] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.465153] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.466398] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 31 00:16:03 node-1 kernel: [    0.466402] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:03 node-1 kernel: [    0.467529] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 00:16:03 node-1 kernel: [    0.468043] PCI host bridge to bus 0000:00
Jul 31 00:16:03 node-1 kernel: [    0.468045] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 31 00:16:03 node-1 kernel: [    0.468047] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 31 00:16:03 node-1 kernel: [    0.468048] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 31 00:16:03 node-1 kernel: [    0.468049] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 31 00:16:03 node-1 kernel: [    0.468051] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 31 00:16:03 node-1 kernel: [    0.468052] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 31 00:16:03 node-1 kernel: [    0.468053] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 31 00:16:03 node-1 kernel: [    0.468059] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 31 00:16:03 node-1 kernel: [    0.468142] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.468172] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.468213] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 31 00:16:03 node-1 kernel: [    0.468236] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.468265] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.468305] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 31 00:16:03 node-1 kernel: [    0.468325] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.468354] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.468397] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 31 00:16:03 node-1 kernel: [    0.468415] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.468486] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.468562] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.468639] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 00:16:03 node-1 kernel: [    0.468644] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 31 00:16:03 node-1 kernel: [    0.468729] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 31 00:16:03 node-1 kernel: [    0.468878] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 31 00:16:03 node-1 kernel: [    0.468895] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 31 00:16:03 node-1 kernel: [    0.468973] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.469026] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 31 00:16:03 node-1 kernel: [    0.469048] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.469103] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.469146] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 31 00:16:03 node-1 kernel: [    0.469173] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.469229] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.469272] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 31 00:16:03 node-1 kernel: [    0.469296] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 31 00:16:03 node-1 kernel: [    0.469314] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 31 00:16:03 node-1 kernel: [    0.469391] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.469441] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 31 00:16:03 node-1 kernel: [    0.469466] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 31 00:16:03 node-1 kernel: [    0.469712] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 31 00:16:03 node-1 kernel: [    0.469718] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 31 00:16:03 node-1 kernel: [    0.469724] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.469730] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.469737] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 31 00:16:03 node-1 kernel: [    0.469767] pci 0000:01:00.0: supports D1 D2
Jul 31 00:16:03 node-1 kernel: [    0.479788] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 00:16:03 node-1 kernel: [    0.479791] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 00:16:03 node-1 kernel: [    0.479792] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 00:16:03 node-1 kernel: [    0.479899] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.479932] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 31 00:16:03 node-1 kernel: [    0.487777] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 00:16:03 node-1 kernel: [    0.487783] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.487787] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:03 node-1 kernel: [    0.487870] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.487953] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.488029] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.488073] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 00:16:03 node-1 kernel: [    0.488077] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.488078] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:03 node-1 kernel: [    0.488131] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.488253] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.488306] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 00:16:03 node-1 kernel: [    0.488309] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.488311] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.488360] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.488479] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.488518] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.488674] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.488710] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.488831] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.488869] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:03 node-1 kernel: [    0.488990] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:03 node-1 kernel: [    0.489032] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 00:16:03 node-1 kernel: [    0.489035] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.489037] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.489106] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:03 node-1 kernel: [    0.489170] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.489221] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.489262] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 31 00:16:03 node-1 kernel: [    0.489342] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 31 00:16:03 node-1 kernel: [    0.489463] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 00:16:03 node-1 kernel: [    0.489466] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.489468] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.489525] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:03 node-1 kernel: [    0.489607] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.489660] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.489872] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 00:16:03 node-1 kernel: [    0.489876] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 00:16:03 node-1 kernel: [    0.489940] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:03 node-1 kernel: [    0.489994] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.490042] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.490253] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 00:16:03 node-1 kernel: [    0.490257] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 00:16:03 node-1 kernel: [    0.490315] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:03 node-1 kernel: [    0.490375] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.490428] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 31 00:16:03 node-1 kernel: [    0.490670] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 00:16:03 node-1 kernel: [    0.490674] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 00:16:03 node-1 kernel: [    0.490851] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 00:16:03 node-1 kernel: [    0.490889] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 00:16:03 node-1 kernel: [    0.490964] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 31 00:16:03 node-1 kernel: [    0.490983] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 31 00:16:03 node-1 kernel: [    0.490996] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 31 00:16:03 node-1 kernel: [    0.491009] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 31 00:16:03 node-1 kernel: [    0.491059] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 31 00:16:03 node-1 kernel: [    0.495784] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 00:16:03 node-1 kernel: [    0.495793] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 00:16:03 node-1 kernel: [    0.495845] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 31 00:16:03 node-1 kernel: [    0.496363] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 31 00:16:03 node-1 kernel: [    0.496366] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:03 node-1 kernel: [    0.496491] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 00:16:03 node-1 kernel: [    0.496598] PCI host bridge to bus 0000:80
Jul 31 00:16:03 node-1 kernel: [    0.496600] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 31 00:16:03 node-1 kernel: [    0.496601] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 31 00:16:03 node-1 kernel: [    0.496603] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 31 00:16:03 node-1 kernel: [    0.496611] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.496674] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.496742] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 00:16:03 node-1 kernel: [    0.496805] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 00:16:03 node-1 kernel: [    0.496810] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 31 00:16:03 node-1 kernel: [    0.496883] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 31 00:16:03 node-1 kernel: [    0.497182] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 31 00:16:03 node-1 kernel: [    0.497214] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 31 00:16:03 node-1 kernel: [    0.497243] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 31 00:16:03 node-1 kernel: [    0.497272] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 31 00:16:03 node-1 kernel: [    0.497301] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:03 node-1 kernel: [    0.497331] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:03 node-1 kernel: [    0.497360] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:03 node-1 kernel: [    0.497390] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:03 node-1 kernel: [    0.497475] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 31 00:16:03 node-1 kernel: [    0.497479] ACPI: \_SB_.UNC1: notify handler is installed
Jul 31 00:16:03 node-1 kernel: [    0.497480] ACPI: \_SB_.UNC0: notify handler is installed
Jul 31 00:16:03 node-1 kernel: [    0.497495] ACPI: \_SB_.PCI0: notify handler is installed
Jul 31 00:16:03 node-1 kernel: [    0.497548] ACPI: \_SB_.PCI1: notify handler is installed
Jul 31 00:16:03 node-1 kernel: [    0.497628] Found 4 acpi root devices
Jul 31 00:16:03 node-1 kernel: [    0.497735] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 31 00:16:03 node-1 kernel: [    0.497737] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 31 00:16:03 node-1 kernel: [    0.497739] vgaarb: loaded
Jul 31 00:16:03 node-1 kernel: [    0.497740] vgaarb: bridge control possible 0000:0c:00.0
Jul 31 00:16:03 node-1 kernel: [    0.497857] SCSI subsystem initialized
Jul 31 00:16:03 node-1 kernel: [    0.497921] libata version 3.00 loaded.
Jul 31 00:16:03 node-1 kernel: [    0.497936] ACPI: bus type USB registered
Jul 31 00:16:03 node-1 kernel: [    0.497951] usbcore: registered new interface driver usbfs
Jul 31 00:16:03 node-1 kernel: [    0.497956] usbcore: registered new interface driver hub
Jul 31 00:16:03 node-1 kernel: [    0.497991] usbcore: registered new device driver usb
Jul 31 00:16:03 node-1 kernel: [    0.498152] PCI: Using ACPI for IRQ routing
Jul 31 00:16:03 node-1 kernel: [    0.501773] PCI: pci_cache_line_size set to 64 bytes
Jul 31 00:16:03 node-1 kernel: [    0.501980] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 31 00:16:03 node-1 kernel: [    0.501981] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 31 00:16:03 node-1 kernel: [    0.501982] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 31 00:16:03 node-1 kernel: [    0.502047] NetLabel: Initializing
Jul 31 00:16:03 node-1 kernel: [    0.502048] NetLabel:  domain hash size = 128
Jul 31 00:16:03 node-1 kernel: [    0.502049] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 31 00:16:03 node-1 kernel: [    0.502059] NetLabel:  unlabeled traffic allowed by default
Jul 31 00:16:03 node-1 kernel: [    0.502114] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 31 00:16:03 node-1 kernel: [    0.502119] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 31 00:16:03 node-1 kernel: [    0.504190] Switched to clocksource hpet
Jul 31 00:16:03 node-1 kernel: [    0.508164] AppArmor: AppArmor Filesystem Enabled
Jul 31 00:16:03 node-1 kernel: [    0.508183] pnp: PnP ACPI init
Jul 31 00:16:03 node-1 kernel: [    0.508190] ACPI: bus type PNP registered
Jul 31 00:16:03 node-1 kernel: [    0.508299] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508307] pnp 00:01: [dma 4]
Jul 31 00:16:03 node-1 kernel: [    0.508318] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508344] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508364] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508380] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508413] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508464] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508466] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 31 00:16:03 node-1 kernel: [    0.508468] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508470] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508471] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508475] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508478] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 31 00:16:03 node-1 kernel: [    0.508479] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508481] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508482] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508484] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508485] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508487] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 31 00:16:03 node-1 kernel: [    0.508489] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508572] pnp 00:07: [dma 0 disabled]
Jul 31 00:16:03 node-1 kernel: [    0.508601] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508675] pnp 00:08: [dma 0 disabled]
Jul 31 00:16:03 node-1 kernel: [    0.508706] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 00:16:03 node-1 kernel: [    0.508756] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 31 00:16:03 node-1 kernel: [    0.509100] pnp: PnP ACPI: found 10 devices
Jul 31 00:16:03 node-1 kernel: [    0.509102] ACPI: bus type PNP unregistered
Jul 31 00:16:03 node-1 kernel: [    0.515499] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 00:16:03 node-1 kernel: [    0.515503] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 00:16:03 node-1 kernel: [    0.515505] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 00:16:03 node-1 kernel: [    0.515510] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 00:16:03 node-1 kernel: [    0.515511] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515526] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515555] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 00:16:03 node-1 kernel: [    0.515585] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515613] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 00:16:03 node-1 kernel: [    0.515628] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 00:16:03 node-1 kernel: [    0.515657] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 00:16:03 node-1 kernel: [    0.515671] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 00:16:03 node-1 kernel: [    0.515700] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 00:16:03 node-1 kernel: [    0.515702] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515717] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515745] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 00:16:03 node-1 kernel: [    0.515747] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515762] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515791] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 00:16:03 node-1 kernel: [    0.515792] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515795] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515799] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 00:16:03 node-1 kernel: [    0.515801] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515803] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515807] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 00:16:03 node-1 kernel: [    0.515812] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 00:16:03 node-1 kernel: [    0.515820] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 00:16:03 node-1 kernel: [    0.515823] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 00:16:03 node-1 kernel: [    0.515830] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 31 00:16:03 node-1 kernel: [    0.515830] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 31 00:16:03 node-1 kernel: [    0.515831] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 31 00:16:03 node-1 kernel: [    0.515832] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 31 00:16:03 node-1 kernel: [    0.515833] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 31 00:16:03 node-1 kernel: [    0.515834] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 31 00:16:03 node-1 kernel: [    0.515835] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 31 00:16:03 node-1 kernel: [    0.515836] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 31 00:16:03 node-1 kernel: [    0.515837] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515837] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515838] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515839] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515840] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515841] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515842] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515843] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515844] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:03 node-1 kernel: [    0.515844] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515845] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 31 00:16:03 node-1 kernel: [    0.515847] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 31 00:16:03 node-1 kernel: [    0.515847] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 31 00:16:03 node-1 kernel: [    0.515848] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 31 00:16:03 node-1 kernel: [    0.515850] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 31 00:16:03 node-1 kernel: [    0.515851] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 31 00:16:03 node-1 kernel: [    0.515892] NET: Registered protocol family 2
Jul 31 00:16:03 node-1 kernel: [    0.516164] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.516497] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.516642] TCP: Hash tables configured (established 262144 bind 65536)
Jul 31 00:16:03 node-1 kernel: [    0.516685] TCP: reno registered
Jul 31 00:16:03 node-1 kernel: [    0.516712] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.516810] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.516960] NET: Registered protocol family 1
Jul 31 00:16:03 node-1 kernel: [    0.552283] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 31 00:16:03 node-1 kernel: [    0.552297] PCI: CLS 64 bytes, default 64
Jul 31 00:16:03 node-1 kernel: [    0.552372] Trying to unpack rootfs image as initramfs...
Jul 31 00:16:03 node-1 kernel: [    0.771537] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 31 00:16:03 node-1 kernel: [    0.771580] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 31 00:16:03 node-1 kernel: [    0.771583] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 31 00:16:03 node-1 kernel: [    0.772000] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772007] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772011] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772017] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772029] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772046] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772071] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772080] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772088] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772097] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772103] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772110] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772116] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772124] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772131] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772138] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:03 node-1 kernel: [    0.772210] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 31 00:16:03 node-1 kernel: [    0.772213] Scanning for low memory corruption every 60 seconds
Jul 31 00:16:03 node-1 kernel: [    0.772552] Initialise system trusted keyring
Jul 31 00:16:03 node-1 kernel: [    0.772600] audit: initializing netlink socket (disabled)
Jul 31 00:16:03 node-1 kernel: [    0.772614] type=2000 audit(1469924127.728:1): initialized
Jul 31 00:16:03 node-1 kernel: [    0.790464] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 31 00:16:03 node-1 kernel: [    0.791945] zbud: loaded
Jul 31 00:16:03 node-1 kernel: [    0.792101] VFS: Disk quotas dquot_6.5.2
Jul 31 00:16:03 node-1 kernel: [    0.792136] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 31 00:16:03 node-1 kernel: [    0.792529] fuse init (API version 7.22)
Jul 31 00:16:03 node-1 kernel: [    0.792587] msgmni has been set to 32768
Jul 31 00:16:03 node-1 kernel: [    0.792632] Key type big_key registered
Jul 31 00:16:03 node-1 kernel: [    0.793117] Key type asymmetric registered
Jul 31 00:16:03 node-1 kernel: [    0.793119] Asymmetric key parser 'x509' registered
Jul 31 00:16:03 node-1 kernel: [    0.793140] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 31 00:16:03 node-1 kernel: [    0.793201] io scheduler noop registered
Jul 31 00:16:03 node-1 kernel: [    0.793203] io scheduler deadline registered (default)
Jul 31 00:16:03 node-1 kernel: [    0.793221] io scheduler cfq registered
Jul 31 00:16:03 node-1 kernel: [    0.793706] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    0.793867] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    0.793978] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    0.794079] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    0.794191] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    0.794278] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    0.794672] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 31 00:16:03 node-1 kernel: [    0.794696] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 31 00:16:03 node-1 kernel: [    0.794712] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 31 00:16:03 node-1 kernel: [    0.794720] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794722] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794725] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:03 node-1 kernel: [    0.794730] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794732] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794733] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794734] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794736] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794738] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794739] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794740] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794742] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794743] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794745] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794746] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794748] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:03 node-1 kernel: [    0.794753] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794755] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:03 node-1 kernel: [    0.794776] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794779] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:03 node-1 kernel: [    0.794789] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794791] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:03 node-1 kernel: [    0.794794] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 31 00:16:03 node-1 kernel: [    0.794829] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 31 00:16:03 node-1 kernel: [    0.794835] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 31 00:16:03 node-1 kernel: [    0.794839] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 31 00:16:03 node-1 kernel: [    0.794848] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 31 00:16:03 node-1 kernel: [    0.794886] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 31 00:16:03 node-1 kernel: [    0.794888] vesafb: scrolling: redraw
Jul 31 00:16:03 node-1 kernel: [    0.794889] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 31 00:16:03 node-1 kernel: [    0.814216] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 31 00:16:03 node-1 kernel: [    0.822723] Console: switching to colour frame buffer device 80x30
Jul 31 00:16:03 node-1 kernel: [    0.831474] fb0: VESA VGA frame buffer device
Jul 31 00:16:03 node-1 kernel: [    0.831669] intel_idle: MWAIT substates: 0x2120
Jul 31 00:16:03 node-1 kernel: [    0.831670] intel_idle: v0.4 model 0x3F
Jul 31 00:16:03 node-1 kernel: [    0.831671] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 31 00:16:03 node-1 kernel: [    0.831909] ipmi message handler version 39.2
Jul 31 00:16:03 node-1 kernel: [    0.832179] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 31 00:16:03 node-1 kernel: [    0.832609] ACPI: AC Adapter [P111] (on-line)
Jul 31 00:16:03 node-1 kernel: [    0.837848] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 31 00:16:03 node-1 kernel: [    0.848904] ACPI: Power Button [PWRB]
Jul 31 00:16:03 node-1 kernel: [    0.854685] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 31 00:16:03 node-1 kernel: [    0.866358] ACPI: Power Button [PWRF]
Jul 31 00:16:03 node-1 kernel: [    0.893737] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 31 00:16:03 node-1 kernel: [    0.905458] pstore: Registered erst as persistent store backend
Jul 31 00:16:03 node-1 kernel: [    0.911696] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 31 00:16:03 node-1 kernel: [    0.923684] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 31 00:16:03 node-1 kernel: [    0.950453] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 31 00:16:03 node-1 kernel: [    0.983869] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 31 00:16:03 node-1 kernel: [    0.997941] Linux agpgart interface v0.103
Jul 31 00:16:03 node-1 kernel: [    1.005601] brd: module loaded
Jul 31 00:16:03 node-1 kernel: [    1.012657] loop: module loaded
Jul 31 00:16:03 node-1 kernel: [    1.019365] libphy: Fixed MDIO Bus: probed
Jul 31 00:16:03 node-1 kernel: [    1.025831] tun: Universal TUN/TAP device driver, 1.6
Jul 31 00:16:03 node-1 kernel: [    1.032309] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 31 00:16:03 node-1 kernel: [    1.038828] PPP generic driver version 2.4.2
Jul 31 00:16:03 node-1 kernel: [    1.045215] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 31 00:16:03 node-1 kernel: [    1.051653] ehci-pci: EHCI PCI platform driver
Jul 31 00:16:03 node-1 kernel: [    1.058172] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 31 00:16:03 node-1 kernel: [    1.064580] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 31 00:16:03 node-1 kernel: [    1.077216] ehci-pci 0000:00:1a.0: debug port 2
Jul 31 00:16:03 node-1 kernel: [    1.087451] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 31 00:16:03 node-1 kernel: [    1.087470] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 31 00:16:03 node-1 kernel: [    1.103681] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 31 00:16:03 node-1 kernel: [    1.109761] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 00:16:03 node-1 kernel: [    1.115927] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 00:16:03 node-1 kernel: [    1.127827] usb usb1: Product: EHCI Host Controller
Jul 31 00:16:03 node-1 kernel: [    1.133853] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 00:16:03 node-1 kernel: [    1.139895] usb usb1: SerialNumber: 0000:00:1a.0
Jul 31 00:16:03 node-1 kernel: [    1.145843] hub 1-0:1.0: USB hub found
Jul 31 00:16:03 node-1 kernel: [    1.151612] hub 1-0:1.0: 2 ports detected
Jul 31 00:16:03 node-1 kernel: [    1.157389] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 31 00:16:03 node-1 kernel: [    1.163054] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 31 00:16:03 node-1 kernel: [    1.173965] ehci-pci 0000:00:1d.0: debug port 2
Jul 31 00:16:03 node-1 kernel: [    1.183274] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 31 00:16:03 node-1 kernel: [    1.183277] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 31 00:16:03 node-1 kernel: [    1.199599] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 31 00:16:03 node-1 kernel: [    1.204787] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 00:16:03 node-1 kernel: [    1.210107] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 00:16:03 node-1 kernel: [    1.220868] usb usb2: Product: EHCI Host Controller
Jul 31 00:16:03 node-1 kernel: [    1.226460] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 00:16:03 node-1 kernel: [    1.232066] usb usb2: SerialNumber: 0000:00:1d.0
Jul 31 00:16:03 node-1 kernel: [    1.237638] hub 2-0:1.0: USB hub found
Jul 31 00:16:03 node-1 kernel: [    1.243040] hub 2-0:1.0: 2 ports detected
Jul 31 00:16:03 node-1 kernel: [    1.248454] ehci-platform: EHCI generic platform driver
Jul 31 00:16:03 node-1 kernel: [    1.253781] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 31 00:16:03 node-1 kernel: [    1.259171] ohci-pci: OHCI PCI platform driver
Jul 31 00:16:03 node-1 kernel: [    1.264534] ohci-platform: OHCI generic platform driver
Jul 31 00:16:03 node-1 kernel: [    1.269787] uhci_hcd: USB Universal Host Controller Interface driver
Jul 31 00:16:03 node-1 kernel: [    1.275188] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 31 00:16:03 node-1 kernel: [    1.467377] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 31 00:16:03 node-1 kernel: [    1.767148] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 31 00:16:03 node-1 kernel: [    1.783500] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 31 00:16:03 node-1 kernel: [    1.789099] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 00:16:03 node-1 kernel: [    1.794767] hub 1-1:1.0: USB hub found
Jul 31 00:16:03 node-1 kernel: [    1.800236] hub 1-1:1.0: 6 ports detected
Jul 31 00:16:03 node-1 kernel: [    1.915017] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 31 00:16:03 node-1 kernel: [    2.314170] i8042: No controller found
Jul 31 00:16:03 node-1 kernel: [    2.319713] mousedev: PS/2 mouse device common for all mice
Jul 31 00:16:03 node-1 kernel: [    2.325422] rtc_cmos 00:02: RTC can wake from S4
Jul 31 00:16:03 node-1 kernel: [    2.327476] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 31 00:16:03 node-1 kernel: [    2.327477] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 00:16:03 node-1 kernel: [    2.328002] hub 2-1:1.0: USB hub found
Jul 31 00:16:03 node-1 kernel: [    2.328231] hub 2-1:1.0: 8 ports detected
Jul 31 00:16:03 node-1 kernel: [    2.353678] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 31 00:16:03 node-1 kernel: [    2.359427] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 31 00:16:03 node-1 kernel: [    2.370722] device-mapper: uevent: version 1.0.3
Jul 31 00:16:03 node-1 kernel: [    2.376434] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 31 00:16:03 node-1 kernel: [    2.387794] ledtrig-cpu: registered to indicate activity on CPUs
Jul 31 00:16:03 node-1 kernel: [    2.393766] TCP: cubic registered
Jul 31 00:16:03 node-1 kernel: [    2.399650] NET: Registered protocol family 10
Jul 31 00:16:03 node-1 kernel: [    2.405706] NET: Registered protocol family 17
Jul 31 00:16:03 node-1 kernel: [    2.411497] Key type dns_resolver registered
Jul 31 00:16:03 node-1 kernel: [    2.417553] Loading compiled-in X.509 certificates
Jul 31 00:16:03 node-1 kernel: [    2.423778] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 31 00:16:03 node-1 kernel: [    2.435422] registered taskstats version 1
Jul 31 00:16:03 node-1 kernel: [    2.443598] Key type trusted registered
Jul 31 00:16:03 node-1 kernel: [    2.451355] Key type encrypted registered
Jul 31 00:16:03 node-1 kernel: [    2.456859] AppArmor: AppArmor sha1 policy hashing enabled
Jul 31 00:16:03 node-1 kernel: [    2.462379] IMA: No TPM chip found, activating TPM-bypass!
Jul 31 00:16:03 node-1 kernel: [    2.468449] regulator-dummy: disabling
Jul 31 00:16:03 node-1 kernel: [    2.473956]   Magic number: 8:53:255
Jul 31 00:16:03 node-1 kernel: [    2.479504] acpi device:94: hash matches
Jul 31 00:16:03 node-1 kernel: [    2.484994] memory memory129: hash matches
Jul 31 00:16:03 node-1 kernel: [    2.490369] rtc_cmos 00:02: setting system clock to 2016-07-31 00:15:29 UTC (1469924129)
Jul 31 00:16:03 node-1 kernel: [    2.502631] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 31 00:16:03 node-1 kernel: [    2.508143] EDD information not available.
Jul 31 00:16:03 node-1 kernel: [    2.513647] PM: Hibernation image not present or could not be loaded.
Jul 31 00:16:03 node-1 kernel: [    2.514505] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 31 00:16:03 node-1 kernel: [    2.525693] Write protecting the kernel read-only data: 12288k
Jul 31 00:16:03 node-1 kernel: [    2.531954] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 31 00:16:03 node-1 kernel: [    2.544564] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 31 00:16:03 node-1 kernel: [    2.577170] device-mapper: multipath: version 1.6.0 loaded
Jul 31 00:16:03 node-1 kernel: [    2.584919] systemd-udevd[217]: starting version 204
Jul 31 00:16:03 node-1 kernel: [    2.606124] md: linear personality registered for level -1
Jul 31 00:16:03 node-1 kernel: [    2.610477] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 31 00:16:03 node-1 kernel: [    2.626555] md: multipath personality registered for level -4
Jul 31 00:16:03 node-1 kernel: [    2.634627] md: raid0 personality registered for level 0
Jul 31 00:16:03 node-1 kernel: [    2.642816] md: raid1 personality registered for level 1
Jul 31 00:16:03 node-1 kernel: [    2.652712] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 31 00:16:03 node-1 kernel: [    2.658933] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 31 00:16:03 node-1 kernel: [    2.665152] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 31 00:16:03 node-1 kernel: [    2.671664] megasas: FW now in Ready state
Jul 31 00:16:03 node-1 kernel: [    2.678053] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678059] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678065] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678070] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678076] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678084] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678089] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678094] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678100] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678105] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678110] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678115] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678120] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678125] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678129] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678135] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.678178] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 31 00:16:03 node-1 kernel: [    2.683497] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 31 00:16:03 node-1 kernel: [    2.683498] 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
Jul 31 00:16:03 node-1 kernel: [    2.683499] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:03 node-1 kernel: [    2.684199] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.684295] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.684490] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.684654] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.685046] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.704383] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 31 00:16:03 node-1 kernel: [    2.704384] 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
Jul 31 00:16:03 node-1 kernel: [    2.704411] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:03 node-1 kernel: [    2.704678] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.704799] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.704919] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.705044] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.705319] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.718397] raid6: sse2x1    6708 MB/s
Jul 31 00:16:03 node-1 kernel: [    2.721666] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 31 00:16:03 node-1 kernel: [    2.721682] 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
Jul 31 00:16:03 node-1 kernel: [    2.721683] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:03 node-1 kernel: [    2.722004] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.722118] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.722254] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.722651] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.723054] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.737193] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 31 00:16:03 node-1 kernel: [    2.737212] 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
Jul 31 00:16:03 node-1 kernel: [    2.737251] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:03 node-1 kernel: [    2.737615] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.737707] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.737858] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.737977] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.738190] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:03 node-1 kernel: [    2.786502] raid6: sse2x2   10928 MB/s
Jul 31 00:16:03 node-1 kernel: [    2.854480] raid6: sse2x4    9564 MB/s
Jul 31 00:16:03 node-1 kernel: [    2.922152] raid6: avx2x1   14351 MB/s
Jul 31 00:16:03 node-1 kernel: [    2.994094] raid6: avx2x2   18873 MB/s
Jul 31 00:16:03 node-1 kernel: [    3.066032] raid6: avx2x4   21322 MB/s
Jul 31 00:16:03 node-1 kernel: [    3.071929] raid6: using algorithm avx2x4 (21322 MB/s)
Jul 31 00:16:03 node-1 kernel: [    3.077978] raid6: using avx2x2 recovery algorithm
Jul 31 00:16:03 node-1 kernel: [    3.083907] Switched to clocksource tsc
Jul 31 00:16:03 node-1 kernel: [    3.090444] xor: automatically using best checksumming function:
Jul 31 00:16:03 node-1 kernel: [    3.133968]    avx       : 36459.000 MB/sec
Jul 31 00:16:03 node-1 kernel: [    3.140234] async_tx: api initialized (async)
Jul 31 00:16:03 node-1 kernel: [    3.141754] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 31 00:16:03 node-1 kernel: [    3.141755] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 31 00:16:03 node-1 kernel: [    3.141756] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 31 00:16:03 node-1 kernel: [    3.141756] usb 2-1.4: Manufacturer: Avocent
Jul 31 00:16:03 node-1 kernel: [    3.141757] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 31 00:16:03 node-1 kernel: [    3.179518] hidraw: raw HID events driver (C) Jiri Kosina
Jul 31 00:16:03 node-1 kernel: [    3.187853] usbcore: registered new interface driver usbhid
Jul 31 00:16:03 node-1 kernel: [    3.193215] usbhid: USB HID core driver
Jul 31 00:16:03 node-1 kernel: [    3.198547] md: raid6 personality registered for level 6
Jul 31 00:16:03 node-1 kernel: [    3.203920] md: raid5 personality registered for level 5
Jul 31 00:16:03 node-1 kernel: [    3.209099] md: raid4 personality registered for level 4
Jul 31 00:16:03 node-1 kernel: [    3.214169] 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
Jul 31 00:16:03 node-1 kernel: [    3.224068] 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
Jul 31 00:16:03 node-1 kernel: [    3.234049] 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
Jul 31 00:16:03 node-1 kernel: [    3.244459] md: raid10 personality registered for level 10
Jul 31 00:16:03 node-1 kernel: [    3.244768] 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
Jul 31 00:16:03 node-1 kernel: [    3.246135] 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
Jul 31 00:16:03 node-1 kernel: [    3.246872] 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
Jul 31 00:16:03 node-1 kernel: [    3.333919] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Jul 31 00:16:03 node-1 kernel: [    3.429763] megasas:IOC Init cmd success
Jul 31 00:16:03 node-1 kernel: [    3.481716] megasas: INIT adapter done
Jul 31 00:16:03 node-1 kernel: [    3.557648] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 31 00:16:03 node-1 kernel: [    3.564535] scsi0 : LSI SAS based MegaRAID driver
Jul 31 00:16:03 node-1 kernel: [    3.571964] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 00:16:03 node-1 kernel: [    3.597713] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 00:16:03 node-1 kernel: [    3.614335] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 31 00:16:03 node-1 kernel: [    3.621365] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 31 00:16:03 node-1 kernel: [    3.635202] sd 0:2:0:0: [sda] Write Protect is off
Jul 31 00:16:03 node-1 kernel: [    3.641920] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 31 00:16:03 node-1 kernel: [    3.641942] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 31 00:16:03 node-1 kernel: [    3.683398]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 31 00:16:03 node-1 kernel: [    3.690578] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 31 00:16:03 node-1 kernel: [    3.815134] random: lvm urandom read with 30 bits of entropy available
Jul 31 00:16:03 node-1 kernel: [    3.944725] bio: create slab <bio-1> at 1
Jul 31 00:16:03 node-1 kernel: [    4.816200] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 00:16:03 node-1 kernel: [    5.357468] init: plymouth-upstart-bridge main process (575) terminated with status 1
Jul 31 00:16:03 node-1 kernel: [    5.369835] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 00:16:03 node-1 kernel: [    5.465783] random: nonblocking pool is initialized
Jul 31 00:16:03 node-1 kernel: [    5.496073] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 31 00:16:03 node-1 kernel: [    5.535100] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 31 00:16:03 node-1 kernel: [    5.707789] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 31 00:16:03 node-1 kernel: [    5.755692] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 31 00:16:03 node-1 kernel: [    5.825326] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 00:16:03 node-1 kernel: [    6.043427] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 31 00:16:03 node-1 kernel: [    6.086093] XFS (dm-1): Mounting Filesystem
Jul 31 00:16:03 node-1 kernel: [    6.263930] XFS (dm-1): Ending clean mount
Jul 31 00:16:03 node-1 kernel: [    6.322405] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 00:16:03 node-1 kernel: [    6.371724] XFS (dm-2): Mounting Filesystem
Jul 31 00:16:03 node-1 kernel: [    6.570934] XFS (dm-2): Ending clean mount
Jul 31 00:16:03 node-1 kernel: [    6.702819] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 00:16:03 node-1 kernel: [    8.295372] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 31 00:16:03 node-1 kernel: [    8.321920] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 31 00:16:03 node-1 kernel: [    8.469148] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 31 00:16:03 node-1 kernel: [    8.469153] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 31 00:16:03 node-1 kernel: [    8.469156] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 31 00:16:03 node-1 kernel: [    8.469160] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 31 00:16:03 node-1 kernel: [    8.515820] systemd-udevd[807]: starting version 204
Jul 31 00:16:03 node-1 kernel: [    8.718561] power_meter ACPI000D:00: Found ACPI power meter.
Jul 31 00:16:03 node-1 kernel: [    8.718582] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 31 00:16:03 node-1 kernel: [    8.738427] IPMI System Interface driver.
Jul 31 00:16:03 node-1 kernel: [    8.738518] ipmi_si: probing via ACPI
Jul 31 00:16:03 node-1 kernel: [    8.738534] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 31 00:16:03 node-1 kernel: [    8.738536] ipmi_si: Adding ACPI-specified kcs state machine
Jul 31 00:16:03 node-1 kernel: [    8.738555] ipmi_si: probing via SMBIOS
Jul 31 00:16:03 node-1 kernel: [    8.738557] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 00:16:03 node-1 kernel: [    8.738558] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 31 00:16:03 node-1 kernel: [    8.738560] ipmi_si: probing via SPMI
Jul 31 00:16:03 node-1 kernel: [    8.738561] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 00:16:03 node-1 kernel: [    8.738562] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 31 00:16:03 node-1 kernel: [    8.738564] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 31 00:16:03 node-1 kernel: [    8.761450] wmi: Mapper loaded
Jul 31 00:16:03 node-1 kernel: [    8.768684] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 31 00:16:03 node-1 kernel: [    8.773729] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 31 00:16:03 node-1 kernel: [    8.773734] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 00:16:03 node-1 kernel: [    8.773736] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 31 00:16:03 node-1 kernel: [    8.773738] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 00:16:03 node-1 kernel: [    8.773751] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 31 00:16:03 node-1 kernel: [    8.869613] systemd-udevd[826]: renamed network interface eth0 to enp6s0
Jul 31 00:16:03 node-1 kernel: [    8.878752] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 31 00:16:03 node-1 kernel: [    8.878761] ipmi_si 00:09: IPMI kcs interface initialized
Jul 31 00:16:03 node-1 kernel: [    8.893436] systemd-udevd[835]: renamed network interface eth1 to enp7s0
Jul 31 00:16:03 node-1 kernel: [    8.926118] systemd-udevd[861]: renamed network interface eth2 to enp8s0
Jul 31 00:16:03 node-1 kernel: [    8.941461] systemd-udevd[824]: renamed network interface eth3 to enp9s0
Jul 31 00:16:03 node-1 kernel: [    9.187067] type=1400 audit(1469924136.196:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1095 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.187211] type=1400 audit(1469924136.196:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1095 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.187339] type=1400 audit(1469924136.196:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1095 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.200796] type=1400 audit(1469924136.208:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1090 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.200953] type=1400 audit(1469924136.212:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1090 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.201080] type=1400 audit(1469924136.212:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1090 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.216056] type=1400 audit(1469924136.224:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1098 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.216196] type=1400 audit(1469924136.224:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1098 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.216316] type=1400 audit(1469924136.224:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1098 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.218520] type=1400 audit(1469924136.228:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Jul 31 00:16:03 node-1 kernel: [    9.718973] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 31 00:16:03 node-1 kernel: [    9.719670] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 31 00:16:03 node-1 kernel: [    9.904052] enic 0000:06:00.0 enp6s0: Link UP
Jul 31 00:16:03 node-1 kernel: [    9.905273] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 31 00:16:03 node-1 kernel: [    9.905279] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 31 00:16:03 node-1 kernel: [   19.282147] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 31 00:16:03 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 31 00:16:04 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 31 00:16:05 node-1 kernel: [   37.582771] init: failsafe main process (8441) killed by TERM signal
Jul 31 00:16:05 node-1 dbus[8512]: [system] AppArmor D-Bus mediation is enabled
Jul 31 00:16:05 node-1 kernel: [   37.820039] audit_printk_skb: 30 callbacks suppressed
Jul 31 00:16:05 node-1 kernel: [   37.820040] type=1400 audit(1469924165.330:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8560 comm="apparmor_parser"
Jul 31 00:16:05 node-1 kernel: [   37.820044] type=1400 audit(1469924165.330:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8560 comm="apparmor_parser"
Jul 31 00:16:05 node-1 kernel: [   37.820047] type=1400 audit(1469924165.330:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8560 comm="apparmor_parser"
Jul 31 00:16:05 node-1 kernel: [   37.820280] type=1400 audit(1469924165.330:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8560 comm="apparmor_parser"
Jul 31 00:16:05 node-1 kernel: [   37.820282] type=1400 audit(1469924165.330:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8560 comm="apparmor_parser"
Jul 31 00:16:05 node-1 kernel: [   37.820395] type=1400 audit(1469924165.330:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8560 comm="apparmor_parser"
Jul 31 00:16:05 node-1 kernel: [   37.822984] type=1400 audit(1469924165.330:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8561 comm="apparmor_parser"
Jul 31 00:16:05 node-1 kernel: [   37.896191] type=1400 audit(1469924165.406:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8563 comm="apparmor_parser"
Jul 31 00:16:05 node-1 anacron[8633]: Anacron 2.3 started on 2016-07-31
Jul 31 00:16:05 node-1 cron[8599]: (CRON) INFO (pidfile fd = 3)
Jul 31 00:16:05 node-1 cron[8641]: (CRON) STARTUP (fork ok)
Jul 31 00:16:05 node-1 anacron[8633]: Will run job `cron.daily' in 5 min.
Jul 31 00:16:05 node-1 anacron[8633]: Will run job `cron.weekly' in 10 min.
Jul 31 00:16:05 node-1 anacron[8633]: Will run job `cron.monthly' in 15 min.
Jul 31 00:16:05 node-1 anacron[8633]: Jobs will be executed sequentially
Jul 31 00:16:05 node-1 multipathd: path checkers start up
Jul 31 00:16:05 node-1 cron[8641]: (CRON) INFO (Running @reboot jobs)
Jul 31 00:16:05 node-1 postfix/master[8778]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 31 00:16:09 node-1 puppet-agent[8962]: Reopening log files
Jul 31 00:16:09 node-1 puppet-agent[8962]: Could not request certificate: Connection refused - connect(2)
Jul 31 00:16:23 node-1 puppet-user[9041]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 31 00:16:23 node-1 puppet-user[9041]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 31 00:16:24 node-1 puppet-user[9041]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 31 00:16:24 node-1 puppet-user[9041]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 31 00:16:24 node-1 puppet-user[9041]: Finished catalog run in 0.91 seconds
Jul 31 00:16:25 node-1 multipathd: uevent trigger error
Jul 31 00:16:25 node-1 puppet-user[9461]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 00:16:25 node-1 puppet-user[9461]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 31 00:16:26 node-1 puppet-user[9461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 31 00:16:26 node-1 puppet-user[9461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 31 00:16:26 node-1 puppet-user[9461]: (/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"]'
Jul 31 00:16:26 node-1 puppet-user[9461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 31 00:16:26 node-1 puppet-user[9461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 31 00:16:26 node-1 puppet-user[9461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 31 00:16:26 node-1 puppet-user[9461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 31 00:16:26 node-1 puppet-user[9461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 31 00:16:26 node-1 puppet-user[9461]: Finished catalog run in 0.06 seconds
Jul 31 00:16:27 node-1 puppet-user[10058]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 31 00:16:27 node-1 puppet-user[10058]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 31 00:16:27 node-1 puppet-user[10058]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 31 00:16:27 node-1 puppet-user[10058]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 31 00:16:27 node-1 puppet-user[10058]: Finished catalog run in 0.04 seconds
Jul 31 00:16:28 node-1 puppet-user[10518]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 31 00:16:28 node-1 puppet-user[10518]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 31 00:16:28 node-1 puppet-user[10518]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 31 00:16:29 node-1 puppet-user[10518]: Finished catalog run in 0.03 seconds
Jul 31 00:16:30 node-1 puppet-user[10967]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 31 00:16:30 node-1 puppet-user[10967]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Jul 31 00:16:30 node-1 puppet-user[10967]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 31 00:16:30 node-1 puppet-user[10967]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 31 00:16:31 node-1 puppet-user[10967]: (/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
Jul 31 00:16:31 node-1 puppet-user[10967]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Jul 31 00:16:31 node-1 puppet-user[10967]: Finished catalog run in 1.18 seconds
Jul 31 00:16:32 node-1 puppet-user[11517]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 31 00:16:33 node-1 puppet-user[11517]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Jul 31 00:16:33 node-1 puppet-user[11517]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 31 00:16:33 node-1 puppet-user[11517]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Jul 31 00:16:33 node-1 puppet-user[11517]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 31 00:16:33 node-1 puppet-user[11517]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 31 00:16:33 node-1 puppet-user[11517]: (/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
Jul 31 00:16:33 node-1 puppet-user[11517]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 31 00:16:33 node-1 puppet-user[11517]: Finished catalog run in 0.37 seconds
Jul 31 00:16:34 node-1 puppet-user[11997]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 31 00:16:34 node-1 puppet-user[11997]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Jul 31 00:16:35 node-1 puppet-user[11997]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 31 00:16:35 node-1 kernel: [   67.566287] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 31 00:16:35 node-1 kernel: [   67.566358] 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.
Jul 31 00:16:35 node-1 puppet-user[11997]: (/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'
Jul 31 00:16:35 node-1 puppet-user[11997]: Finished catalog run in 0.05 seconds
Jul 31 00:16:36 node-1 puppet-user[12461]: (Scope(Class[main])) MODULAR: sync_time
Jul 31 00:16:36 node-1 puppet-user[12461]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 31 00:16:37 node-1 ntpdate[12874]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 31 00:16:43 node-1 ntpdate[12874]: adjust time server 10.20.0.2 offset 0.001124 sec
Jul 31 00:16:43 node-1 puppet-user[12461]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 31 00:16:43 node-1 puppet-user[12461]: Finished catalog run in 6.16 seconds
Jul 31 00:16:50 node-1 kernel: [   82.952211] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 00:16:50 node-1 puppet-agent[8962]: Could not run: SIGTERM
Jul 31 00:16:50 node-1 kernel: [   83.213940] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 31 00:16:50 node-1 ec2: 
Jul 31 00:16:50 node-1 ec2: #############################################################
Jul 31 00:16:50 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 31 00:16:50 node-1 ec2: 1024 f5:92:a2:33:26:94:2a:e4:fa:01:e3:77:87:fc:57:66  root@node-1.domain.tld (DSA)
Jul 31 00:16:50 node-1 ec2: 256 fb:65:cd:c7:4f:a2:17:78:5f:ca:d9:aa:9b:8e:71:cf  root@node-1.domain.tld (ECDSA)
Jul 31 00:16:50 node-1 ec2: 256 cd:eb:ae:24:17:d3:f6:15:55:05:3d:76:f5:7f:a2:cb  root@node-1.domain.tld (ED25519)
Jul 31 00:16:50 node-1 ec2: 2048 bb:05:a1:ce:72:30:05:0f:a2:8a:b9:17:a9:ec:f8:47  root@node-1.domain.tld (RSA)
Jul 31 00:16:50 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 31 00:16:50 node-1 ec2: #############################################################
Jul 31 00:17:01 node-1 CRON[13426]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 31 00:17:01 node-1 CRON[13427]: (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")
Jul 31 00:17:24 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:17:24 node-1 nailgun-agent: I, [2016-07-31T00:17:24.829268 #13431]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 00:17:33 node-1 puppet-user[13588]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 00:17:33 node-1 puppet-user[13588]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Jul 31 00:17:33 node-1 puppet-user[13588]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 31 00:17:33 node-1 puppet-user[13588]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 31 00:17:33 node-1 puppet-user[13588]: Finished catalog run in 0.07 seconds
Jul 31 00:17:35 node-1 puppet-user[14038]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 31 00:17:36 node-1 puppet-user[14038]: Compiled catalog for node-1.domain.tld in environment production in 1.20 seconds
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:36 node-1 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 31 00:17:36 node-1 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 31 00:17:36 node-1 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:36 node-1 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 31 00:17:36 node-1 puppet-user[14038]: (/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
Jul 31 00:17:37 node-1 puppet-user[14038]: (/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
Jul 31 00:17:37 node-1 puppet-user[14038]: (/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
Jul 31 00:17:37 node-1 puppet-user[14038]: (/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
Jul 31 00:17:37 node-1 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 31 00:17:37 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:17:37 node-1 nailgun-agent: I, [2016-07-31T00:17:37.829137 #13431]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 31 00:17:54 node-1 puppet-user[14038]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 31 00:17:54 node-1 puppet-user[14038]: Finished catalog run in 18.19 seconds
Jul 31 00:17:57 node-1 puppet-user[15126]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 31 00:17:57 node-1 puppet-user[15126]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 31 00:18:01 node-1 CRON[16059]: (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")
Jul 31 00:18:02 node-1 puppet-user[15126]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 31 00:18:13 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:18:13 node-1 nailgun-agent: I, [2016-07-31T00:18:13.006603 #16062]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 00:18:25 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:18:26 node-1 nailgun-agent: I, [2016-07-31T00:18:26.153744 #16062]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 31 00:18:33 node-1 puppet-user[15126]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 31 00:18:33 node-1 puppet-user[15126]: Finished catalog run in 35.90 seconds
Jul 31 00:18:35 node-1 puppet-user[17901]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 31 00:18:35 node-1 puppet-user[17901]: Compiled catalog for node-1.domain.tld in environment production in 0.60 seconds
Jul 31 00:18:35 node-1 puppet-user[17901]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 31 00:18:35 node-1 puppet-user[17901]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 31 00:18:35 node-1 puppet-user[17901]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 31 00:18:35 node-1 puppet-user[17901]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 31 00:18:36 node-1 puppet-user[17901]: Finished catalog run in 0.13 seconds
Jul 31 00:18:37 node-1 puppet-user[18361]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 31 00:18:38 node-1 puppet-user[18361]: Compiled catalog for node-1.domain.tld in environment production in 0.97 seconds
Jul 31 00:18:39 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 31 00:18:39 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 31 00:18:39 node-1 crontab[18806]: (root) LIST (root)
Jul 31 00:18:39 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 31 00:18:39 node-1 crontab[18809]: (root) REPLACE (root)
Jul 31 00:18:41 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/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
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 31 00:18:43 node-1 puppet-user[18361]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 31 00:18:43 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8414" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 31 00:18:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:18:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:18:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:18:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:18:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:19:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:06 node-1 ntpdate[28811]: no servers can be used, exiting
<27>Jul 31 00:20:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:07 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 00:22:07 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 00:22:13 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 00:22:13 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 00:22:18 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 00:22:24 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 00:22:24 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 00:22:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:44 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:44 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:44 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:44 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:44 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:49 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:49 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:49 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:50 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:50 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:50 node-1 multipathd: uevent trigger error
<129>Jul 31 00:22:52 node-1 haproxy[16580]: 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>Jul 31 00:22:52 node-1 haproxy[16580]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:22:53 node-1 haproxy[16587]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:22:53 node-1 haproxy[16587]: proxy mysqld has no server available!
<27>Jul 31 00:22:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:22:58 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:01 node-1 haproxy[18900]: 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>Jul 31 00:23:01 node-1 haproxy[18900]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:01 node-1 haproxy[18900]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:01 node-1 haproxy[18900]: proxy mysqld has no server available!
<129>Jul 31 00:23:02 node-1 haproxy[18904]: 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>Jul 31 00:23:02 node-1 haproxy[18904]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:02 node-1 haproxy[18904]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:02 node-1 haproxy[18904]: proxy object-storage has no server available!
<27>Jul 31 00:23:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:04 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:04 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:06 node-1 haproxy[20187]: 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>Jul 31 00:23:06 node-1 haproxy[20187]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:07 node-1 haproxy[20191]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:07 node-1 haproxy[20191]: proxy neutron has no server available!
<129>Jul 31 00:23:07 node-1 haproxy[20191]: 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>Jul 31 00:23:07 node-1 haproxy[20191]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:07 node-1 haproxy[20191]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:07 node-1 haproxy[20191]: proxy mysqld has no server available!
<129>Jul 31 00:23:07 node-1 haproxy[20191]: 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>Jul 31 00:23:08 node-1 haproxy[20191]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:08 node-1 haproxy[20191]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:08 node-1 haproxy[20191]: proxy object-storage has no server available!
<27>Jul 31 00:23:09 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:09 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:09 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:09 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:09 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:09 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:12 node-1 haproxy[21472]: 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>Jul 31 00:23:12 node-1 haproxy[21472]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:12 node-1 haproxy[21472]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:12 node-1 haproxy[21472]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:12 node-1 haproxy[21472]: 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>Jul 31 00:23:12 node-1 haproxy[21472]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:12 node-1 haproxy[21472]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:12 node-1 haproxy[21472]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:12 node-1 haproxy[21472]: 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>Jul 31 00:23:13 node-1 haproxy[21489]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:13 node-1 haproxy[21489]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:13 node-1 haproxy[21489]: proxy neutron has no server available!
<129>Jul 31 00:23:13 node-1 haproxy[21489]: 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>Jul 31 00:23:13 node-1 haproxy[21489]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:13 node-1 haproxy[21489]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:13 node-1 haproxy[21489]: proxy mysqld has no server available!
<129>Jul 31 00:23:13 node-1 haproxy[21489]: 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>Jul 31 00:23:13 node-1 haproxy[21489]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:13 node-1 haproxy[21489]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:13 node-1 haproxy[21489]: proxy object-storage has no server available!
<27>Jul 31 00:23:15 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:15 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:15 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:15 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:15 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:17 node-1 haproxy[22759]: 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>Jul 31 00:23:17 node-1 haproxy[22759]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:17 node-1 haproxy[22759]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:17 node-1 haproxy[22759]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:17 node-1 haproxy[22759]: 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>Jul 31 00:23:17 node-1 haproxy[22759]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:17 node-1 haproxy[22759]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:17 node-1 haproxy[22759]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:18 node-1 haproxy[22763]: 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>Jul 31 00:23:18 node-1 haproxy[22763]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:18 node-1 haproxy[22763]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:18 node-1 haproxy[22763]: proxy neutron has no server available!
<129>Jul 31 00:23:18 node-1 haproxy[22763]: 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>Jul 31 00:23:18 node-1 haproxy[22763]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:18 node-1 haproxy[22763]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:18 node-1 haproxy[22763]: proxy mysqld has no server available!
<129>Jul 31 00:23:18 node-1 haproxy[22763]: 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>Jul 31 00:23:18 node-1 haproxy[22763]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:18 node-1 haproxy[22763]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:18 node-1 haproxy[22763]: proxy object-storage has no server available!
<129>Jul 31 00:23:18 node-1 haproxy[22763]: 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>Jul 31 00:23:19 node-1 haproxy[22763]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:19 node-1 haproxy[22763]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:19 node-1 haproxy[22763]: proxy aodh has no server available!
<27>Jul 31 00:23:20 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:22 node-1 haproxy[24046]: 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>Jul 31 00:23:22 node-1 haproxy[24046]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:23 node-1 haproxy[24050]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:23 node-1 haproxy[24050]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:23 node-1 haproxy[24050]: 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>Jul 31 00:23:23 node-1 haproxy[24050]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:23 node-1 haproxy[24050]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:23 node-1 haproxy[24050]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:23 node-1 haproxy[24050]: 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>Jul 31 00:23:23 node-1 haproxy[24050]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:23 node-1 haproxy[24050]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:23 node-1 haproxy[24050]: proxy neutron has no server available!
<129>Jul 31 00:23:23 node-1 haproxy[24050]: 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>Jul 31 00:23:23 node-1 haproxy[24050]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:23 node-1 haproxy[24050]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:23 node-1 haproxy[24050]: proxy mysqld has no server available!
<129>Jul 31 00:23:23 node-1 haproxy[24050]: 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>Jul 31 00:23:23 node-1 haproxy[24050]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:24 node-1 haproxy[24050]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:24 node-1 haproxy[24050]: proxy object-storage has no server available!
<129>Jul 31 00:23:24 node-1 haproxy[24050]: 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>Jul 31 00:23:24 node-1 haproxy[24050]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:24 node-1 haproxy[24050]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:24 node-1 haproxy[24050]: proxy aodh has no server available!
<129>Jul 31 00:23:24 node-1 haproxy[24050]: 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>Jul 31 00:23:24 node-1 haproxy[24050]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:24 node-1 haproxy[24050]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:24 node-1 haproxy[24050]: proxy ceilometer has no server available!
<27>Jul 31 00:23:25 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:25 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:25 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:25 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:25 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:28 node-1 haproxy[25372]: 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>Jul 31 00:23:28 node-1 haproxy[25372]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:28 node-1 haproxy[25372]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:28 node-1 haproxy[25372]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:28 node-1 haproxy[25372]: 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>Jul 31 00:23:28 node-1 haproxy[25372]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:28 node-1 haproxy[25372]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:28 node-1 haproxy[25372]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:28 node-1 haproxy[25372]: 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>Jul 31 00:23:28 node-1 haproxy[25372]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:28 node-1 haproxy[25372]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:28 node-1 haproxy[25372]: proxy neutron has no server available!
<129>Jul 31 00:23:28 node-1 haproxy[25372]: 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>Jul 31 00:23:28 node-1 haproxy[25372]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:28 node-1 haproxy[25372]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:28 node-1 haproxy[25372]: proxy mysqld has no server available!
<129>Jul 31 00:23:29 node-1 haproxy[25401]: 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>Jul 31 00:23:29 node-1 haproxy[25401]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:29 node-1 haproxy[25401]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:29 node-1 haproxy[25401]: proxy object-storage has no server available!
<129>Jul 31 00:23:29 node-1 haproxy[25401]: 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>Jul 31 00:23:29 node-1 haproxy[25401]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:29 node-1 haproxy[25401]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:29 node-1 haproxy[25401]: proxy aodh has no server available!
<129>Jul 31 00:23:29 node-1 haproxy[25401]: 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>Jul 31 00:23:29 node-1 haproxy[25401]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:29 node-1 haproxy[25401]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:29 node-1 haproxy[25401]: proxy ceilometer has no server available!
<27>Jul 31 00:23:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:31 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:33 node-1 haproxy[26739]: 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>Jul 31 00:23:33 node-1 haproxy[26739]: 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>Jul 31 00:23:33 node-1 haproxy[26739]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:33 node-1 haproxy[26739]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:33 node-1 haproxy[26739]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:33 node-1 haproxy[26739]: 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>Jul 31 00:23:33 node-1 haproxy[26739]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:33 node-1 haproxy[26739]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:33 node-1 haproxy[26739]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:33 node-1 haproxy[26739]: 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>Jul 31 00:23:33 node-1 haproxy[26739]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:33 node-1 haproxy[26739]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:33 node-1 haproxy[26739]: proxy neutron has no server available!
<129>Jul 31 00:23:33 node-1 haproxy[26739]: 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>Jul 31 00:23:34 node-1 haproxy[26743]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:34 node-1 haproxy[26743]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:34 node-1 haproxy[26743]: proxy mysqld has no server available!
<129>Jul 31 00:23:34 node-1 haproxy[26743]: 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>Jul 31 00:23:34 node-1 haproxy[26743]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:34 node-1 haproxy[26743]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:34 node-1 haproxy[26743]: proxy object-storage has no server available!
<129>Jul 31 00:23:34 node-1 haproxy[26743]: 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>Jul 31 00:23:34 node-1 haproxy[26743]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:34 node-1 haproxy[26743]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:34 node-1 haproxy[26743]: proxy aodh has no server available!
<129>Jul 31 00:23:34 node-1 haproxy[26743]: 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>Jul 31 00:23:34 node-1 haproxy[26743]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:34 node-1 haproxy[26743]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:34 node-1 haproxy[26743]: proxy ceilometer has no server available!
<27>Jul 31 00:23:35 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:35 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:36 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:36 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:36 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:38 node-1 haproxy[28081]: 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>Jul 31 00:23:38 node-1 haproxy[28081]: 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>Jul 31 00:23:38 node-1 haproxy[28081]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:38 node-1 haproxy[28081]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:38 node-1 haproxy[28081]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:38 node-1 haproxy[28081]: 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>Jul 31 00:23:38 node-1 haproxy[28081]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:39 node-1 haproxy[28085]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:39 node-1 haproxy[28085]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:39 node-1 haproxy[28085]: 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>Jul 31 00:23:39 node-1 haproxy[28085]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:39 node-1 haproxy[28085]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:39 node-1 haproxy[28085]: proxy glance-api has no server available!
<129>Jul 31 00:23:39 node-1 haproxy[28085]: 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>Jul 31 00:23:39 node-1 haproxy[28085]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:39 node-1 haproxy[28085]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:39 node-1 haproxy[28085]: proxy glance-glare has no server available!
<129>Jul 31 00:23:39 node-1 haproxy[28085]: 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>Jul 31 00:23:39 node-1 haproxy[28085]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:39 node-1 haproxy[28085]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:39 node-1 haproxy[28085]: proxy neutron has no server available!
<129>Jul 31 00:23:39 node-1 haproxy[28085]: 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>Jul 31 00:23:39 node-1 haproxy[28085]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:39 node-1 haproxy[28085]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:39 node-1 haproxy[28085]: proxy glance-registry has no server available!
<129>Jul 31 00:23:39 node-1 haproxy[28085]: 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>Jul 31 00:23:39 node-1 haproxy[28085]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:39 node-1 haproxy[28085]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:39 node-1 haproxy[28085]: proxy mysqld has no server available!
<129>Jul 31 00:23:39 node-1 haproxy[28085]: 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>Jul 31 00:23:39 node-1 haproxy[28085]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:40 node-1 haproxy[28085]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:40 node-1 haproxy[28085]: proxy object-storage has no server available!
<129>Jul 31 00:23:40 node-1 haproxy[28085]: 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>Jul 31 00:23:40 node-1 haproxy[28085]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:40 node-1 haproxy[28085]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:40 node-1 haproxy[28085]: proxy aodh has no server available!
<129>Jul 31 00:23:40 node-1 haproxy[28085]: 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>Jul 31 00:23:40 node-1 haproxy[28085]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:40 node-1 haproxy[28085]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:40 node-1 haproxy[28085]: proxy ceilometer has no server available!
<27>Jul 31 00:23:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:41 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:44 node-1 haproxy[29573]: 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>Jul 31 00:23:44 node-1 haproxy[29573]: 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>Jul 31 00:23:44 node-1 haproxy[29573]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:44 node-1 haproxy[29573]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:44 node-1 haproxy[29573]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:44 node-1 haproxy[29573]: 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>Jul 31 00:23:44 node-1 haproxy[29573]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:44 node-1 haproxy[29573]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:44 node-1 haproxy[29573]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:44 node-1 haproxy[29573]: 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>Jul 31 00:23:44 node-1 haproxy[29573]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:44 node-1 haproxy[29573]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:44 node-1 haproxy[29573]: proxy nova-api has no server available!
<129>Jul 31 00:23:44 node-1 haproxy[29573]: 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>Jul 31 00:23:44 node-1 haproxy[29573]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:44 node-1 haproxy[29573]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:44 node-1 haproxy[29573]: proxy nova-metadata-api has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:45 node-1 haproxy[29577]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:45 node-1 haproxy[29577]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:45 node-1 haproxy[29577]: proxy glance-api has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:45 node-1 haproxy[29577]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:45 node-1 haproxy[29577]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:45 node-1 haproxy[29577]: proxy glance-glare has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:45 node-1 haproxy[29577]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:45 node-1 haproxy[29577]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:45 node-1 haproxy[29577]: proxy neutron has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:45 node-1 haproxy[29577]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:45 node-1 haproxy[29577]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:45 node-1 haproxy[29577]: proxy glance-registry has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:45 node-1 haproxy[29577]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:45 node-1 haproxy[29577]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:45 node-1 haproxy[29577]: proxy mysqld has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:45 node-1 haproxy[29577]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:45 node-1 haproxy[29577]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:45 node-1 haproxy[29577]: proxy object-storage has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:45 node-1 haproxy[29577]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:45 node-1 haproxy[29577]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:45 node-1 haproxy[29577]: proxy aodh has no server available!
<129>Jul 31 00:23:45 node-1 haproxy[29577]: 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>Jul 31 00:23:46 node-1 haproxy[29577]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:46 node-1 haproxy[29577]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:46 node-1 haproxy[29577]: proxy ceilometer has no server available!
<129>Jul 31 00:23:46 node-1 haproxy[29577]: 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>Jul 31 00:23:46 node-1 haproxy[29577]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:46 node-1 haproxy[29577]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:46 node-1 haproxy[29577]: proxy nova-novncproxy has no server available!
<27>Jul 31 00:23:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:47 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:49 node-1 haproxy[30854]: 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>Jul 31 00:23:49 node-1 haproxy[30854]: 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>Jul 31 00:23:49 node-1 haproxy[30854]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:49 node-1 haproxy[30854]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:49 node-1 haproxy[30854]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:50 node-1 haproxy[30858]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:50 node-1 haproxy[30858]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:50 node-1 haproxy[30858]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:50 node-1 haproxy[30858]: proxy nova-api has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:50 node-1 haproxy[30858]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:50 node-1 haproxy[30858]: proxy nova-metadata-api has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:50 node-1 haproxy[30858]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:50 node-1 haproxy[30858]: proxy cinder-api has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:50 node-1 haproxy[30858]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:50 node-1 haproxy[30858]: proxy glance-api has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:50 node-1 haproxy[30858]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:50 node-1 haproxy[30858]: proxy glance-glare has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:50 node-1 haproxy[30858]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:50 node-1 haproxy[30858]: proxy neutron has no server available!
<129>Jul 31 00:23:50 node-1 haproxy[30858]: 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>Jul 31 00:23:50 node-1 haproxy[30858]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:51 node-1 haproxy[30858]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:51 node-1 haproxy[30858]: proxy glance-registry has no server available!
<129>Jul 31 00:23:51 node-1 haproxy[30858]: 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>Jul 31 00:23:51 node-1 haproxy[30858]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:51 node-1 haproxy[30858]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:51 node-1 haproxy[30858]: proxy mysqld has no server available!
<129>Jul 31 00:23:51 node-1 haproxy[30858]: 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>Jul 31 00:23:51 node-1 haproxy[30858]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:51 node-1 haproxy[30858]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:51 node-1 haproxy[30858]: proxy object-storage has no server available!
<129>Jul 31 00:23:51 node-1 haproxy[30858]: 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>Jul 31 00:23:51 node-1 haproxy[30858]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:51 node-1 haproxy[30858]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:51 node-1 haproxy[30858]: proxy aodh has no server available!
<129>Jul 31 00:23:51 node-1 haproxy[30858]: 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>Jul 31 00:23:51 node-1 haproxy[30858]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:51 node-1 haproxy[30858]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:51 node-1 haproxy[30858]: proxy ceilometer has no server available!
<129>Jul 31 00:23:51 node-1 haproxy[30858]: 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>Jul 31 00:23:51 node-1 haproxy[30858]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:51 node-1 haproxy[30858]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:51 node-1 haproxy[30858]: proxy nova-novncproxy has no server available!
<27>Jul 31 00:23:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:52 node-1 multipathd: uevent trigger error
<129>Jul 31 00:23:55 node-1 haproxy[32167]: 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>Jul 31 00:23:55 node-1 haproxy[32167]: 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>Jul 31 00:23:55 node-1 haproxy[32167]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:55 node-1 haproxy[32167]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:55 node-1 haproxy[32167]: proxy keystone-1 has no server available!
<129>Jul 31 00:23:55 node-1 haproxy[32167]: 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>Jul 31 00:23:55 node-1 haproxy[32167]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:55 node-1 haproxy[32167]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:55 node-1 haproxy[32167]: proxy keystone-2 has no server available!
<129>Jul 31 00:23:55 node-1 haproxy[32167]: 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>Jul 31 00:23:55 node-1 haproxy[32167]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:55 node-1 haproxy[32167]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:55 node-1 haproxy[32167]: proxy nova-api has no server available!
<129>Jul 31 00:23:55 node-1 haproxy[32167]: 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>Jul 31 00:23:55 node-1 haproxy[32167]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:55 node-1 haproxy[32167]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:55 node-1 haproxy[32167]: proxy nova-metadata-api has no server available!
<129>Jul 31 00:23:55 node-1 haproxy[32167]: 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>Jul 31 00:23:55 node-1 haproxy[32167]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy cinder-api has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy glance-api has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy glance-glare has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy neutron has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy glance-registry has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy mysqld has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy object-storage has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy aodh has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy ceilometer has no server available!
<129>Jul 31 00:23:56 node-1 haproxy[32171]: 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>Jul 31 00:23:56 node-1 haproxy[32171]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:56 node-1 haproxy[32171]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:56 node-1 haproxy[32171]: proxy heat-api has no server available!
<129>Jul 31 00:23:57 node-1 haproxy[32171]: 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>Jul 31 00:23:57 node-1 haproxy[32171]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:57 node-1 haproxy[32171]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:57 node-1 haproxy[32171]: proxy heat-api-cfn has no server available!
<129>Jul 31 00:23:57 node-1 haproxy[32171]: 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>Jul 31 00:23:57 node-1 haproxy[32171]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:57 node-1 haproxy[32171]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:57 node-1 haproxy[32171]: proxy heat-api-cloudwatch has no server available!
<129>Jul 31 00:23:57 node-1 haproxy[32171]: 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>Jul 31 00:23:57 node-1 haproxy[32171]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:57 node-1 haproxy[32171]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:23:57 node-1 haproxy[32171]: proxy nova-novncproxy has no server available!
<27>Jul 31 00:23:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:23:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-1 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-1 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-1 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-1 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-1 multipathd: uevent trigger error
<27>Jul 31 00:24:13 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 31 00:24:38 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>Jul 31 00:24:41 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 31 00:25:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:25:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 00:25:38 node-1 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-1 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-1 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-1 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-1 multipathd: uevent trigger error
<27>Jul 31 00:27:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:27:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:27:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:27:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:27:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:27:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 31 00:28:24 node-1 apache2_error [Sun Jul 31 00:28:17.568962 2016] [mpm_event:notice] [pid 10708:tid 139765697103744] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 00:28:24 node-1 apache2_error [Sun Jul 31 00:28:17.569036 2016] [core:notice] [pid 10708:tid 139765697103744] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 00:28:24 node-1 apache2_error [Sun Jul 31 00:28:20.727606 2016] [mpm_event:notice] [pid 10708:tid 139765697103744] AH00491: caught SIGTERM, shutting down
<43>Jul 31 00:28:24 node-1 apache2_error [Sun Jul 31 00:28:21.837797 2016] [mpm_worker:notice] [pid 11093:tid 140351302342528] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 00:28:24 node-1 apache2_error [Sun Jul 31 00:28:21.837920 2016] [core:notice] [pid 11093:tid 140351302342528] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:28:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:28:34 node-1 multipathd: uevent trigger error
<43>Jul 31 00:29:44 node-1 apache2_error [Sun Jul 31 00:29:43.421358 2016] [mpm_worker:notice] [pid 11093:tid 140351302342528] AH00295: caught SIGTERM, shutting down
<43>Jul 31 00:29:44 node-1 apache2_error [Sun Jul 31 00:29:44.178130 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:29:44 node-1 apache2_error [Sun Jul 31 00:29:44.178161 2016] [core:notice] [pid 26230:tid 140086027360128] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 00:30:35 node-1 apache2_error [Sun Jul 31 00:30:28.435214 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:30:35 node-1 apache2_error [Sun Jul 31 00:30:28.631741 2016] [mpm_worker:warn] [pid 26230:tid 140086027360128] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:30:35 node-1 apache2_error [Sun Jul 31 00:30:28.635349 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:30:35 node-1 apache2_error [Sun Jul 31 00:30:28.635367 2016] [core:notice] [pid 26230:tid 140086027360128] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:31:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:13 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:13 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:17 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:17 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:17 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:17 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:17 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:17 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:32 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:32 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:32 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:32 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:32 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:32 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:31:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:41 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:59 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:59 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:59 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:59 node-1 multipathd: uevent trigger error
<27>Jul 31 00:32:59 node-1 multipathd: uevent trigger error
<27>Jul 31 00:33:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:33:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:33:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:33:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:33:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:34:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:34:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:34:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:34:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:34:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:34:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:35:14 node-1 multipathd: uevent trigger error
<27>Jul 31 00:35:14 node-1 multipathd: uevent trigger error
<27>Jul 31 00:35:14 node-1 multipathd: uevent trigger error
<27>Jul 31 00:35:14 node-1 multipathd: uevent trigger error
<27>Jul 31 00:35:14 node-1 multipathd: uevent trigger error
<27>Jul 31 00:35:14 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:36:40 node-1 multipathd: uevent trigger error
<27>Jul 31 00:37:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:39:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:39:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:40:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:40:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:40:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:40:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:40:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:40:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:41:42 node-1 multipathd: uevent trigger error
<27>Jul 31 00:42:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:42:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:42:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:42:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:42:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:43:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:44:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:44:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:44:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:44:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:44:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:44:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:12 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:45:55 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:07 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:13 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:13 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:13 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:13 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:46:48 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:48 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:48 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:48 node-1 multipathd: uevent trigger error
<27>Jul 31 00:46:48 node-1 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:11 node-1 multipathd: uevent trigger error
<11>Jul 31 00:48:25 node-1 liberasurecode[12730]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:25 node-1 liberasurecode[12730]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:25 node-1 liberasurecode[12730]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:25 node-1 liberasurecode[12730]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:25 node-1 liberasurecode[12756]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:25 node-1 liberasurecode[12756]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:25 node-1 liberasurecode[12756]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:25 node-1 liberasurecode[12756]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:27 node-1 liberasurecode[13183]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:27 node-1 liberasurecode[13183]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:27 node-1 liberasurecode[13183]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:27 node-1 liberasurecode[13183]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14022]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14022]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14022]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14022]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14063]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14063]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14063]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:32 node-1 liberasurecode[14063]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14133]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14133]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14193]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14193]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14193]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14193]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14205]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14205]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14205]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14205]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14224]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14224]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14224]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14224]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14236]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14236]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14236]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:33 node-1 liberasurecode[14236]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:50 node-1 liberasurecode[16796]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:50 node-1 liberasurecode[16796]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:50 node-1 liberasurecode[16796]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:48:50 node-1 liberasurecode[16796]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 00:48:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:48:58 node-1 multipathd: uevent trigger error
<27>Jul 31 00:49:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 31 00:49:46 node-1 apache2_error [Sun Jul 31 00:49:45.214388 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:49:46 node-1 apache2_error [Sun Jul 31 00:49:45.594850 2016] [mpm_worker:warn] [pid 26230:tid 140086027360128] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:49:46 node-1 apache2_error [Sun Jul 31 00:49:45.598190 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:49:46 node-1 apache2_error [Sun Jul 31 00:49:45.598206 2016] [core:notice] [pid 26230:tid 140086027360128] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 31 00:50:01 node-1 liberasurecode[26521]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:50:01 node-1 liberasurecode[26521]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:50:01 node-1 liberasurecode[26521]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:50:01 node-1 liberasurecode[26521]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 00:50:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:26 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:26 node-1 multipathd: uevent trigger error
<43>Jul 31 00:50:26 node-1 apache2_error [Sun Jul 31 00:50:22.613707 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:50:26 node-1 apache2_error [Sun Jul 31 00:50:22.805849 2016] [mpm_worker:warn] [pid 26230:tid 140086027360128] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:50:26 node-1 apache2_error [Sun Jul 31 00:50:22.815014 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:50:26 node-1 apache2_error [Sun Jul 31 00:50:22.815042 2016] [core:notice] [pid 26230:tid 140086027360128] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:50:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:11 node-1 multipathd: uevent trigger error
<43>Jul 31 00:51:16 node-1 apache2_error [Sun Jul 31 00:51:07.740164 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:51:16 node-1 apache2_error [Sun Jul 31 00:51:07.936029 2016] [mpm_worker:warn] [pid 26230:tid 140086027360128] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:51:16 node-1 apache2_error [Sun Jul 31 00:51:07.945341 2016] [mpm_worker:notice] [pid 26230:tid 140086027360128] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:51:16 node-1 apache2_error [Sun Jul 31 00:51:07.945370 2016] [core:notice] [pid 26230:tid 140086027360128] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:51:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:18 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:22 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:37 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:51:51 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:14 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:22 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 31 00:52:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:31 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:56 node-1 multipathd: uevent trigger error
<27>Jul 31 00:52:57 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 00:53:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:28 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:36 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:36 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:36 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:36 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:53:47 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:00 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:29 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:29 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:29 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:29 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:29 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:30 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:34 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:39 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:43 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:52 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:54:57 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:02 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:02 node-1 multipathd: uevent trigger error
<11>Jul 31 00:55:02 node-1 liberasurecode[6588]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:55:02 node-1 liberasurecode[6588]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:55:02 node-1 liberasurecode[6588]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:55:02 node-1 liberasurecode[6588]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 00:55:06 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:06 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:06 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:06 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:06 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:06 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:11 node-1 multipathd: uevent trigger error
<27>Jul 31 00:55:11 node-1 multipathd: uevent trigger error
