Sep 18 11:19:02 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8421" x-info="http://www.rsyslog.com"] start
Sep 18 11:19:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 18 11:19:02 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep 18 11:19:02 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep 18 11:19:02 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 18 11:19:02 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 18 11:19:02 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 18 11:19:02 node-2 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 18 11:19:02 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=8464d10e-19b0-4bd4-aa70-a1e3fc658b0b nomdmonddf nomdmonisw
Sep 18 11:19:02 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep 18 11:19:02 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep 18 11:19:02 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep 18 11:19:02 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep 18 11:19:02 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 18 11:19:02 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 18 11:19:02 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 18 11:19:02 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Sep 18 11:19:02 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 18 11:19:02 node-2 kernel: [    0.000000] No AGP bridge found
Sep 18 11:19:02 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 18 11:19:02 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep 18 11:19:02 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 18 11:19:02 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep 18 11:19:02 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 18 11:19:02 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 18 11:19:02 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 18 11:19:02 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 18 11:19:02 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 18 11:19:02 node-2 kernel: [    0.000000]   2 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000]   3 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000]   4 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000]   5 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000]   6 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000]   7 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000]   8 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000]   9 disabled
Sep 18 11:19:02 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 18 11:19:02 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 18 11:19:02 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 18 11:19:02 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 18 11:19:02 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 18 11:19:02 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 18 11:19:02 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 18 11:19:02 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 18 11:19:02 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 18 11:19:02 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 18 11:19:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 18 11:19:02 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 18 11:19:02 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 18 11:19:02 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 18 11:19:02 node-2 kernel: [    0.000000] Zone ranges:
Sep 18 11:19:02 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] Movable zone start for each node
Sep 18 11:19:02 node-2 kernel: [    0.000000] Early memory node ranges
Sep 18 11:19:02 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 18 11:19:02 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 18 11:19:02 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 18 11:19:02 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 18 11:19:02 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 18 11:19:02 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 18 11:19:02 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 18 11:19:02 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 18 11:19:02 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 18 11:19:02 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 18 11:19:02 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 18 11:19:02 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 18 11:19:02 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 18 11:19:02 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 18 11:19:02 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 18 11:19:02 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 18 11:19:02 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 18 11:19:02 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 18 11:19:02 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 18 11:19:02 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 18 11:19:02 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 18 11:19:02 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 18 11:19:02 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 18 11:19:02 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Sep 18 11:19:02 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 18 11:19:02 node-2 kernel: [    0.000000] Policy zone: Normal
Sep 18 11:19:02 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=8464d10e-19b0-4bd4-aa70-a1e3fc658b0b nomdmonddf nomdmonisw
Sep 18 11:19:02 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 18 11:19:02 node-2 kernel: [    0.000000] Checking aperture...
Sep 18 11:19:02 node-2 kernel: [    0.000000] No AGP bridge found
Sep 18 11:19:02 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 18 11:19:02 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 18 11:19:02 node-2 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep 18 11:19:02 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 18 11:19:02 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 18 11:19:02 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 18 11:19:02 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 18 11:19:02 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 18 11:19:02 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 18 11:19:02 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 18 11:19:02 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 18 11:19:02 node-2 kernel: [    0.000000] console [tty0] enabled
Sep 18 11:19:02 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 18 11:19:02 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 18 11:19:02 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 18 11:19:02 node-2 kernel: [    0.000000] hpet clockevent registered
Sep 18 11:19:02 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 18 11:19:02 node-2 kernel: [    0.004000] tsc: Detected 3491.781 MHz processor
Sep 18 11:19:02 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.56 BogoMIPS (lpj=13967124)
Sep 18 11:19:02 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 18 11:19:02 node-2 kernel: [    0.000043] Security Framework initialized
Sep 18 11:19:02 node-2 kernel: [    0.000063] AppArmor: AppArmor initialized
Sep 18 11:19:02 node-2 kernel: [    0.000064] Yama: becoming mindful.
Sep 18 11:19:02 node-2 kernel: [    0.001464] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.006450] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.008380] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.008408] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.008697] Initializing cgroup subsys memory
Sep 18 11:19:02 node-2 kernel: [    0.008706] Initializing cgroup subsys devices
Sep 18 11:19:02 node-2 kernel: [    0.008707] Initializing cgroup subsys freezer
Sep 18 11:19:02 node-2 kernel: [    0.008709] Initializing cgroup subsys blkio
Sep 18 11:19:02 node-2 kernel: [    0.008711] Initializing cgroup subsys perf_event
Sep 18 11:19:02 node-2 kernel: [    0.008713] Initializing cgroup subsys hugetlb
Sep 18 11:19:02 node-2 kernel: [    0.008733] CPU: Physical Processor ID: 0
Sep 18 11:19:02 node-2 kernel: [    0.008734] CPU: Processor Core ID: 0
Sep 18 11:19:02 node-2 kernel: [    0.008738] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 18 11:19:02 node-2 kernel: [    0.008738] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 18 11:19:02 node-2 kernel: [    0.009431] mce: CPU supports 22 MCE banks
Sep 18 11:19:02 node-2 kernel: [    0.009459] CPU0: Thermal monitoring enabled (TM1)
Sep 18 11:19:02 node-2 kernel: [    0.009479] process: using mwait in idle threads
Sep 18 11:19:02 node-2 kernel: [    0.009482] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 18 11:19:02 node-2 kernel: [    0.009482] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 18 11:19:02 node-2 kernel: [    0.009482] tlb_flushall_shift: 6
Sep 18 11:19:02 node-2 kernel: [    0.009571] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 18 11:19:02 node-2 kernel: [    0.010295] ACPI: Core revision 20131115
Sep 18 11:19:02 node-2 kernel: [    0.022969] ACPI: All ACPI Tables successfully acquired
Sep 18 11:19:02 node-2 kernel: [    0.023132] ftrace: allocating 28617 entries in 112 pages
Sep 18 11:19:02 node-2 kernel: [    0.032106] dmar: Host address width 46
Sep 18 11:19:02 node-2 kernel: [    0.032108] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 18 11:19:02 node-2 kernel: [    0.032114] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 18 11:19:02 node-2 kernel: [    0.032115] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 18 11:19:02 node-2 kernel: [    0.032119] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 18 11:19:02 node-2 kernel: [    0.032121] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 18 11:19:02 node-2 kernel: [    0.032122] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 18 11:19:02 node-2 kernel: [    0.032123] dmar: ATSR flags: 0x0
Sep 18 11:19:02 node-2 kernel: [    0.032124] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 18 11:19:02 node-2 kernel: [    0.032126] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 18 11:19:02 node-2 kernel: [    0.032241] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 18 11:19:02 node-2 kernel: [    0.032243] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 18 11:19:02 node-2 kernel: [    0.032244] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 18 11:19:02 node-2 kernel: [    0.032245] HPET id 0 under DRHD base 0xc7ffc000
Sep 18 11:19:02 node-2 kernel: [    0.032246] Your BIOS is broken and requested that x2apic be disabled.
Sep 18 11:19:02 node-2 kernel: [    0.032246] This will slightly decrease performance.
Sep 18 11:19:02 node-2 kernel: [    0.032246] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 18 11:19:02 node-2 kernel: [    0.032679] Enabled IRQ remapping in xapic mode
Sep 18 11:19:02 node-2 kernel: [    0.032680] x2apic not enabled, IRQ remapping is in xapic mode
Sep 18 11:19:02 node-2 kernel: [    0.032684] Switched APIC routing to physical flat.
Sep 18 11:19:02 node-2 kernel: [    0.033308] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 18 11:19:02 node-2 kernel: [    0.072956] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 18 11:19:02 node-2 kernel: [    0.072962] TSC deadline timer enabled
Sep 18 11:19:02 node-2 kernel: [    0.072969] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 18 11:19:02 node-2 kernel: [    0.072976] ... version:                3
Sep 18 11:19:02 node-2 kernel: [    0.072977] ... bit width:              48
Sep 18 11:19:02 node-2 kernel: [    0.072978] ... generic registers:      4
Sep 18 11:19:02 node-2 kernel: [    0.072979] ... value mask:             0000ffffffffffff
Sep 18 11:19:02 node-2 kernel: [    0.072980] ... max period:             0000ffffffffffff
Sep 18 11:19:02 node-2 kernel: [    0.072981] ... fixed-purpose events:   3
Sep 18 11:19:02 node-2 kernel: [    0.072981] ... event mask:             000000070000000f
Sep 18 11:19:02 node-2 kernel: [    0.074363] x86: Booting SMP configuration:
Sep 18 11:19:02 node-2 kernel: [    0.088465] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 18 11:19:02 node-2 kernel: [    0.074365] .... node  #0, CPUs:        #1  #2  #3
Sep 18 11:19:02 node-2 kernel: [    0.116373] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 18 11:19:02 node-2 kernel: [    0.270301] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 18 11:19:02 node-2 kernel: [    0.325912] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 18 11:19:02 node-2 kernel: [    0.382762] x86: Booted up 2 nodes, 16 CPUs
Sep 18 11:19:02 node-2 kernel: [    0.382765] smpboot: Total of 16 processors activated (111749.17 BogoMIPS)
Sep 18 11:19:02 node-2 kernel: [    0.406798] devtmpfs: initialized
Sep 18 11:19:02 node-2 kernel: [    0.409916] EVM: security.selinux
Sep 18 11:19:02 node-2 kernel: [    0.409917] EVM: security.SMACK64
Sep 18 11:19:02 node-2 kernel: [    0.409918] EVM: security.ima
Sep 18 11:19:02 node-2 kernel: [    0.409919] EVM: security.capability
Sep 18 11:19:02 node-2 kernel: [    0.409969] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.410654] pinctrl core: initialized pinctrl subsystem
Sep 18 11:19:02 node-2 kernel: [    0.410718] regulator-dummy: no parameters
Sep 18 11:19:02 node-2 kernel: [    0.410750] RTC time: 11:18:23, date: 09/18/16
Sep 18 11:19:02 node-2 kernel: [    0.410785] NET: Registered protocol family 16
Sep 18 11:19:02 node-2 kernel: [    0.410869] cpuidle: using governor ladder
Sep 18 11:19:02 node-2 kernel: [    0.410870] cpuidle: using governor menu
Sep 18 11:19:02 node-2 kernel: [    0.410904] ACPI: bus type PCI registered
Sep 18 11:19:02 node-2 kernel: [    0.410906] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 18 11:19:02 node-2 kernel: [    0.410951] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 18 11:19:02 node-2 kernel: [    0.410954] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 18 11:19:02 node-2 kernel: [    0.424686] PCI: Using configuration type 1 for base access
Sep 18 11:19:02 node-2 kernel: [    0.425691] bio: create slab <bio-0> at 0
Sep 18 11:19:02 node-2 kernel: [    0.425975] ACPI: Added _OSI(Module Device)
Sep 18 11:19:02 node-2 kernel: [    0.425976] ACPI: Added _OSI(Processor Device)
Sep 18 11:19:02 node-2 kernel: [    0.425978] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 18 11:19:02 node-2 kernel: [    0.425979] ACPI: Added _OSI(Processor Aggregator Device)
Sep 18 11:19:02 node-2 kernel: [    0.438570] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 18 11:19:02 node-2 kernel: [    0.450164] ACPI: Interpreter enabled
Sep 18 11:19:02 node-2 kernel: [    0.450169] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 18 11:19:02 node-2 kernel: [    0.450173] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 18 11:19:02 node-2 kernel: [    0.450176] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 18 11:19:02 node-2 kernel: [    0.450183] ACPI: (supports S0 S4 S5)
Sep 18 11:19:02 node-2 kernel: [    0.450184] ACPI: Using IOAPIC for interrupt routing
Sep 18 11:19:02 node-2 kernel: [    0.450230] HEST: Table parsing has been initialized.
Sep 18 11:19:02 node-2 kernel: [    0.450233] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 18 11:19:02 node-2 kernel: [    0.450786] ACPI: No dock devices found.
Sep 18 11:19:02 node-2 kernel: [    0.462459] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 18 11:19:02 node-2 kernel: [    0.462463] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:02 node-2 kernel: [    0.462467] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 18 11:19:02 node-2 kernel: [    0.462493] PCI host bridge to bus 0000:ff
Sep 18 11:19:02 node-2 kernel: [    0.462495] pci_bus 0000:ff: root bus resource [bus ff]
Sep 18 11:19:02 node-2 kernel: [    0.462504] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462542] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.462572] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462607] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462636] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.462665] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.462696] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462725] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462754] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462782] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462809] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462835] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462864] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462893] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462919] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462948] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.462979] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463007] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463034] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.463062] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463088] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.463114] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463140] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463170] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.463207] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463238] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463268] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463302] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463335] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463369] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463402] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463432] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463462] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463495] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463528] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463560] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463593] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463625] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463652] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463684] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463716] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463755] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463790] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463824] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463855] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463884] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463914] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463946] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.463979] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464011] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464043] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464074] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464104] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464134] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464164] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464196] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464231] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464289] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 18 11:19:02 node-2 kernel: [    0.464292] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:02 node-2 kernel: [    0.464295] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 18 11:19:02 node-2 kernel: [    0.464313] PCI host bridge to bus 0000:7f
Sep 18 11:19:02 node-2 kernel: [    0.464314] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 18 11:19:02 node-2 kernel: [    0.464319] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464347] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.464374] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464407] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464429] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.464455] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.464481] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464508] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464531] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464554] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464576] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464599] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464623] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464645] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464669] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464695] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464717] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464740] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464763] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.464787] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464809] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.464831] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464854] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464880] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 18 11:19:02 node-2 kernel: [    0.464913] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464939] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464967] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.464995] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465020] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465046] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465072] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465099] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465124] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465151] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465179] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465207] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465235] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465260] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465284] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465312] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465337] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465364] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465393] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465420] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465446] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465472] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465500] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465530] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465557] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465584] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465614] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465640] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465663] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465688] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465714] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465743] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.465769] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.467009] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 18 11:19:02 node-2 kernel: [    0.467013] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:02 node-2 kernel: [    0.468130] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 18 11:19:02 node-2 kernel: [    0.468638] PCI host bridge to bus 0000:00
Sep 18 11:19:02 node-2 kernel: [    0.468641] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 18 11:19:02 node-2 kernel: [    0.468643] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 18 11:19:02 node-2 kernel: [    0.468644] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 18 11:19:02 node-2 kernel: [    0.468645] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 18 11:19:02 node-2 kernel: [    0.468647] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 18 11:19:02 node-2 kernel: [    0.468648] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 18 11:19:02 node-2 kernel: [    0.468649] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 18 11:19:02 node-2 kernel: [    0.468655] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 18 11:19:02 node-2 kernel: [    0.468738] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.468769] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.468810] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 18 11:19:02 node-2 kernel: [    0.468829] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.468859] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.468899] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 18 11:19:02 node-2 kernel: [    0.468917] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.468947] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.468989] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 18 11:19:02 node-2 kernel: [    0.469006] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.469076] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.469153] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.469227] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 18 11:19:02 node-2 kernel: [    0.469232] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 18 11:19:02 node-2 kernel: [    0.469317] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 18 11:19:02 node-2 kernel: [    0.469464] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 18 11:19:02 node-2 kernel: [    0.469481] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 18 11:19:02 node-2 kernel: [    0.469559] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.469613] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 18 11:19:02 node-2 kernel: [    0.469634] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.469690] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.469733] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 18 11:19:02 node-2 kernel: [    0.469760] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.469816] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.469860] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 18 11:19:02 node-2 kernel: [    0.469883] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 18 11:19:02 node-2 kernel: [    0.469901] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 18 11:19:02 node-2 kernel: [    0.469978] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.470027] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 18 11:19:02 node-2 kernel: [    0.470056] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 18 11:19:02 node-2 kernel: [    0.470303] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 18 11:19:02 node-2 kernel: [    0.470309] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 18 11:19:02 node-2 kernel: [    0.470314] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.470320] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.470327] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 18 11:19:02 node-2 kernel: [    0.470358] pci 0000:01:00.0: supports D1 D2
Sep 18 11:19:02 node-2 kernel: [    0.476398] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 18 11:19:02 node-2 kernel: [    0.476401] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 18 11:19:02 node-2 kernel: [    0.476403] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 18 11:19:02 node-2 kernel: [    0.476509] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.476543] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 18 11:19:02 node-2 kernel: [    0.484403] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 18 11:19:02 node-2 kernel: [    0.484410] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.484414] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:02 node-2 kernel: [    0.484499] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.484567] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.484646] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.484691] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 18 11:19:02 node-2 kernel: [    0.484694] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.484696] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:02 node-2 kernel: [    0.484748] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.484870] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.484929] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 18 11:19:02 node-2 kernel: [    0.484931] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.484933] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.484983] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.485103] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.485145] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.485264] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.485300] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.485420] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.485458] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:02 node-2 kernel: [    0.485579] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:02 node-2 kernel: [    0.485621] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 18 11:19:02 node-2 kernel: [    0.485624] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.485626] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.485685] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:02 node-2 kernel: [    0.485748] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.485800] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.485842] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 18 11:19:02 node-2 kernel: [    0.485949] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 18 11:19:02 node-2 kernel: [    0.486055] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 18 11:19:02 node-2 kernel: [    0.486058] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.486060] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.486116] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:02 node-2 kernel: [    0.486173] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.486221] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.486431] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 18 11:19:02 node-2 kernel: [    0.486435] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 18 11:19:02 node-2 kernel: [    0.486496] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:02 node-2 kernel: [    0.486549] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.486597] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.486808] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 18 11:19:02 node-2 kernel: [    0.486812] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 18 11:19:02 node-2 kernel: [    0.486870] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:02 node-2 kernel: [    0.486954] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.487006] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 18 11:19:02 node-2 kernel: [    0.487226] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 18 11:19:02 node-2 kernel: [    0.487230] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 18 11:19:02 node-2 kernel: [    0.487403] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 18 11:19:02 node-2 kernel: [    0.487441] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 18 11:19:02 node-2 kernel: [    0.487515] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 18 11:19:02 node-2 kernel: [    0.487534] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 18 11:19:02 node-2 kernel: [    0.487547] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 18 11:19:02 node-2 kernel: [    0.487560] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 18 11:19:02 node-2 kernel: [    0.487611] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 18 11:19:02 node-2 kernel: [    0.492417] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 18 11:19:02 node-2 kernel: [    0.492422] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 18 11:19:02 node-2 kernel: [    0.492454] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 18 11:19:02 node-2 kernel: [    0.492945] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 18 11:19:02 node-2 kernel: [    0.492948] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:02 node-2 kernel: [    0.493070] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 18 11:19:02 node-2 kernel: [    0.493176] PCI host bridge to bus 0000:80
Sep 18 11:19:02 node-2 kernel: [    0.493178] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 18 11:19:02 node-2 kernel: [    0.493179] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 18 11:19:02 node-2 kernel: [    0.493181] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 18 11:19:02 node-2 kernel: [    0.493188] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.493251] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.493321] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 18 11:19:02 node-2 kernel: [    0.493382] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 18 11:19:02 node-2 kernel: [    0.493387] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 18 11:19:02 node-2 kernel: [    0.493459] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 18 11:19:02 node-2 kernel: [    0.493759] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 18 11:19:02 node-2 kernel: [    0.493791] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 18 11:19:02 node-2 kernel: [    0.493821] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 18 11:19:02 node-2 kernel: [    0.493850] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 18 11:19:02 node-2 kernel: [    0.493880] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:02 node-2 kernel: [    0.493910] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:02 node-2 kernel: [    0.493939] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:02 node-2 kernel: [    0.493969] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:02 node-2 kernel: [    0.494054] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 18 11:19:02 node-2 kernel: [    0.494059] ACPI: \_SB_.UNC1: notify handler is installed
Sep 18 11:19:02 node-2 kernel: [    0.494060] ACPI: \_SB_.UNC0: notify handler is installed
Sep 18 11:19:02 node-2 kernel: [    0.494075] ACPI: \_SB_.PCI0: notify handler is installed
Sep 18 11:19:02 node-2 kernel: [    0.494128] ACPI: \_SB_.PCI1: notify handler is installed
Sep 18 11:19:02 node-2 kernel: [    0.494207] Found 4 acpi root devices
Sep 18 11:19:02 node-2 kernel: [    0.494312] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 18 11:19:02 node-2 kernel: [    0.494314] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 18 11:19:02 node-2 kernel: [    0.494316] vgaarb: loaded
Sep 18 11:19:02 node-2 kernel: [    0.494317] vgaarb: bridge control possible 0000:0c:00.0
Sep 18 11:19:02 node-2 kernel: [    0.494436] SCSI subsystem initialized
Sep 18 11:19:02 node-2 kernel: [    0.494501] libata version 3.00 loaded.
Sep 18 11:19:02 node-2 kernel: [    0.494516] ACPI: bus type USB registered
Sep 18 11:19:02 node-2 kernel: [    0.494527] usbcore: registered new interface driver usbfs
Sep 18 11:19:02 node-2 kernel: [    0.494532] usbcore: registered new interface driver hub
Sep 18 11:19:02 node-2 kernel: [    0.494556] usbcore: registered new device driver usb
Sep 18 11:19:02 node-2 kernel: [    0.494722] PCI: Using ACPI for IRQ routing
Sep 18 11:19:02 node-2 kernel: [    0.498319] PCI: pci_cache_line_size set to 64 bytes
Sep 18 11:19:02 node-2 kernel: [    0.498520] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 18 11:19:02 node-2 kernel: [    0.498521] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 18 11:19:02 node-2 kernel: [    0.498522] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 18 11:19:02 node-2 kernel: [    0.498588] NetLabel: Initializing
Sep 18 11:19:02 node-2 kernel: [    0.498589] NetLabel:  domain hash size = 128
Sep 18 11:19:02 node-2 kernel: [    0.498590] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 18 11:19:02 node-2 kernel: [    0.498600] NetLabel:  unlabeled traffic allowed by default
Sep 18 11:19:02 node-2 kernel: [    0.498668] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 18 11:19:02 node-2 kernel: [    0.498672] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 18 11:19:02 node-2 kernel: [    0.500728] Switched to clocksource hpet
Sep 18 11:19:02 node-2 kernel: [    0.504728] AppArmor: AppArmor Filesystem Enabled
Sep 18 11:19:02 node-2 kernel: [    0.504741] pnp: PnP ACPI init
Sep 18 11:19:02 node-2 kernel: [    0.504748] ACPI: bus type PNP registered
Sep 18 11:19:02 node-2 kernel: [    0.504857] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 18 11:19:02 node-2 kernel: [    0.504865] pnp 00:01: [dma 4]
Sep 18 11:19:02 node-2 kernel: [    0.504877] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 18 11:19:02 node-2 kernel: [    0.504904] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 18 11:19:02 node-2 kernel: [    0.504923] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 18 11:19:02 node-2 kernel: [    0.504941] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 18 11:19:02 node-2 kernel: [    0.504974] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 18 11:19:02 node-2 kernel: [    0.505027] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505029] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 18 11:19:02 node-2 kernel: [    0.505031] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505033] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505034] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505039] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505041] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 18 11:19:02 node-2 kernel: [    0.505043] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505044] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505046] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505047] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505049] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505050] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 18 11:19:02 node-2 kernel: [    0.505052] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 18 11:19:02 node-2 kernel: [    0.505135] pnp 00:07: [dma 0 disabled]
Sep 18 11:19:02 node-2 kernel: [    0.505164] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 18 11:19:02 node-2 kernel: [    0.505238] pnp 00:08: [dma 0 disabled]
Sep 18 11:19:02 node-2 kernel: [    0.505274] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 18 11:19:02 node-2 kernel: [    0.505326] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 18 11:19:02 node-2 kernel: [    0.505675] pnp: PnP ACPI: found 10 devices
Sep 18 11:19:02 node-2 kernel: [    0.505677] ACPI: bus type PNP unregistered
Sep 18 11:19:02 node-2 kernel: [    0.512080] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 18 11:19:02 node-2 kernel: [    0.512083] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 18 11:19:02 node-2 kernel: [    0.512086] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 18 11:19:02 node-2 kernel: [    0.512090] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 18 11:19:02 node-2 kernel: [    0.512092] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512107] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512136] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 18 11:19:02 node-2 kernel: [    0.512150] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512179] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 18 11:19:02 node-2 kernel: [    0.512194] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 18 11:19:02 node-2 kernel: [    0.512222] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 18 11:19:02 node-2 kernel: [    0.512237] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 18 11:19:02 node-2 kernel: [    0.512266] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 18 11:19:02 node-2 kernel: [    0.512267] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512282] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512311] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 18 11:19:02 node-2 kernel: [    0.512313] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512328] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512359] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 18 11:19:02 node-2 kernel: [    0.512361] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512364] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512368] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 18 11:19:02 node-2 kernel: [    0.512370] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512372] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512376] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 18 11:19:02 node-2 kernel: [    0.512381] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 18 11:19:02 node-2 kernel: [    0.512389] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 18 11:19:02 node-2 kernel: [    0.512392] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 18 11:19:02 node-2 kernel: [    0.512398] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 18 11:19:02 node-2 kernel: [    0.512399] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 18 11:19:02 node-2 kernel: [    0.512400] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 18 11:19:02 node-2 kernel: [    0.512401] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 18 11:19:02 node-2 kernel: [    0.512402] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 18 11:19:02 node-2 kernel: [    0.512403] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 18 11:19:02 node-2 kernel: [    0.512404] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 18 11:19:02 node-2 kernel: [    0.512405] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 18 11:19:02 node-2 kernel: [    0.512406] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512407] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512407] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512408] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512409] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512410] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512411] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512412] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512413] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:02 node-2 kernel: [    0.512414] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512415] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 18 11:19:02 node-2 kernel: [    0.512416] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 18 11:19:02 node-2 kernel: [    0.512417] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 18 11:19:02 node-2 kernel: [    0.512418] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 18 11:19:02 node-2 kernel: [    0.512420] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 18 11:19:02 node-2 kernel: [    0.512421] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 18 11:19:02 node-2 kernel: [    0.512462] NET: Registered protocol family 2
Sep 18 11:19:02 node-2 kernel: [    0.512719] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.513050] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.513194] TCP: Hash tables configured (established 262144 bind 65536)
Sep 18 11:19:02 node-2 kernel: [    0.513230] TCP: reno registered
Sep 18 11:19:02 node-2 kernel: [    0.513260] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.513354] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.513500] NET: Registered protocol family 1
Sep 18 11:19:02 node-2 kernel: [    0.548832] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 18 11:19:02 node-2 kernel: [    0.548847] PCI: CLS 64 bytes, default 64
Sep 18 11:19:02 node-2 kernel: [    0.548911] Trying to unpack rootfs image as initramfs...
Sep 18 11:19:02 node-2 kernel: [    0.769002] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep 18 11:19:02 node-2 kernel: [    0.769056] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 18 11:19:02 node-2 kernel: [    0.769058] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 18 11:19:02 node-2 kernel: [    0.769457] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769463] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769468] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769474] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769486] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769502] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769518] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769533] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769555] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769564] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769570] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769576] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769583] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769591] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769599] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769606] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:02 node-2 kernel: [    0.769647] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 18 11:19:02 node-2 kernel: [    0.769651] Scanning for low memory corruption every 60 seconds
Sep 18 11:19:02 node-2 kernel: [    0.769941] Initialise system trusted keyring
Sep 18 11:19:02 node-2 kernel: [    0.769986] audit: initializing netlink socket (disabled)
Sep 18 11:19:02 node-2 kernel: [    0.769995] type=2000 audit(1474197503.720:1): initialized
Sep 18 11:19:02 node-2 kernel: [    0.787792] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 18 11:19:02 node-2 kernel: [    0.789264] zbud: loaded
Sep 18 11:19:02 node-2 kernel: [    0.789375] VFS: Disk quotas dquot_6.5.2
Sep 18 11:19:02 node-2 kernel: [    0.789413] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 18 11:19:02 node-2 kernel: [    0.789782] fuse init (API version 7.22)
Sep 18 11:19:02 node-2 kernel: [    0.789839] msgmni has been set to 32768
Sep 18 11:19:02 node-2 kernel: [    0.789885] Key type big_key registered
Sep 18 11:19:02 node-2 kernel: [    0.790420] Key type asymmetric registered
Sep 18 11:19:02 node-2 kernel: [    0.790421] Asymmetric key parser 'x509' registered
Sep 18 11:19:02 node-2 kernel: [    0.790445] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 18 11:19:02 node-2 kernel: [    0.790504] io scheduler noop registered
Sep 18 11:19:02 node-2 kernel: [    0.790506] io scheduler deadline registered (default)
Sep 18 11:19:02 node-2 kernel: [    0.790524] io scheduler cfq registered
Sep 18 11:19:02 node-2 kernel: [    0.790807] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    0.790898] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    0.790984] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    0.791070] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    0.791164] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    0.791231] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    0.791488] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 18 11:19:02 node-2 kernel: [    0.791506] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 18 11:19:02 node-2 kernel: [    0.791519] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 18 11:19:02 node-2 kernel: [    0.791528] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791530] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791532] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:02 node-2 kernel: [    0.791536] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791537] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791538] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791539] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791541] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791542] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791544] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791545] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791546] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791548] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791549] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791550] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791552] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:02 node-2 kernel: [    0.791556] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791558] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:02 node-2 kernel: [    0.791567] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791569] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:02 node-2 kernel: [    0.791578] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791579] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:02 node-2 kernel: [    0.791582] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 18 11:19:02 node-2 kernel: [    0.791595] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 18 11:19:02 node-2 kernel: [    0.791682] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 18 11:19:02 node-2 kernel: [    0.791686] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 18 11:19:02 node-2 kernel: [    0.791694] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 18 11:19:02 node-2 kernel: [    0.791729] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 18 11:19:02 node-2 kernel: [    0.791730] vesafb: scrolling: redraw
Sep 18 11:19:02 node-2 kernel: [    0.791732] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 18 11:19:02 node-2 kernel: [    0.812545] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 18 11:19:02 node-2 kernel: [    0.821097] Console: switching to colour frame buffer device 80x30
Sep 18 11:19:02 node-2 kernel: [    0.829776] fb0: VESA VGA frame buffer device
Sep 18 11:19:02 node-2 kernel: [    0.829974] intel_idle: MWAIT substates: 0x2120
Sep 18 11:19:02 node-2 kernel: [    0.829975] intel_idle: v0.4 model 0x3F
Sep 18 11:19:02 node-2 kernel: [    0.829976] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 18 11:19:02 node-2 kernel: [    0.830217] ipmi message handler version 39.2
Sep 18 11:19:02 node-2 kernel: [    0.830481] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 18 11:19:02 node-2 kernel: [    0.830914] ACPI: AC Adapter [P111] (on-line)
Sep 18 11:19:02 node-2 kernel: [    0.836151] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 18 11:19:02 node-2 kernel: [    0.847310] ACPI: Power Button [PWRB]
Sep 18 11:19:02 node-2 kernel: [    0.853155] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 18 11:19:02 node-2 kernel: [    0.864816] ACPI: Power Button [PWRF]
Sep 18 11:19:02 node-2 kernel: [    0.890354] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 18 11:19:02 node-2 kernel: [    0.902036] pstore: Registered erst as persistent store backend
Sep 18 11:19:02 node-2 kernel: [    0.908254] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 18 11:19:02 node-2 kernel: [    0.920228] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 18 11:19:02 node-2 kernel: [    0.947015] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 18 11:19:02 node-2 kernel: [    0.980324] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 18 11:19:02 node-2 kernel: [    0.994433] Linux agpgart interface v0.103
Sep 18 11:19:02 node-2 kernel: [    1.002117] brd: module loaded
Sep 18 11:19:02 node-2 kernel: [    1.009168] loop: module loaded
Sep 18 11:19:02 node-2 kernel: [    1.015887] libphy: Fixed MDIO Bus: probed
Sep 18 11:19:02 node-2 kernel: [    1.022352] tun: Universal TUN/TAP device driver, 1.6
Sep 18 11:19:02 node-2 kernel: [    1.028831] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 18 11:19:02 node-2 kernel: [    1.035366] PPP generic driver version 2.4.2
Sep 18 11:19:02 node-2 kernel: [    1.041754] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 18 11:19:02 node-2 kernel: [    1.048197] ehci-pci: EHCI PCI platform driver
Sep 18 11:19:02 node-2 kernel: [    1.054787] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 18 11:19:02 node-2 kernel: [    1.061181] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 18 11:19:02 node-2 kernel: [    1.073714] ehci-pci 0000:00:1a.0: debug port 2
Sep 18 11:19:02 node-2 kernel: [    1.083900] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 18 11:19:02 node-2 kernel: [    1.083917] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 18 11:19:02 node-2 kernel: [    1.100222] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 18 11:19:02 node-2 kernel: [    1.106352] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 18 11:19:02 node-2 kernel: [    1.112551] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 18 11:19:02 node-2 kernel: [    1.124526] usb usb1: Product: EHCI Host Controller
Sep 18 11:19:02 node-2 kernel: [    1.130597] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 18 11:19:02 node-2 kernel: [    1.136655] usb usb1: SerialNumber: 0000:00:1a.0
Sep 18 11:19:02 node-2 kernel: [    1.142632] hub 1-0:1.0: USB hub found
Sep 18 11:19:02 node-2 kernel: [    1.148427] hub 1-0:1.0: 2 ports detected
Sep 18 11:19:02 node-2 kernel: [    1.154263] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 18 11:19:02 node-2 kernel: [    1.159897] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 18 11:19:02 node-2 kernel: [    1.170948] ehci-pci 0000:00:1d.0: debug port 2
Sep 18 11:19:02 node-2 kernel: [    1.180309] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 18 11:19:02 node-2 kernel: [    1.180312] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 18 11:19:02 node-2 kernel: [    1.196141] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 18 11:19:02 node-2 kernel: [    1.201430] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 18 11:19:02 node-2 kernel: [    1.206732] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 18 11:19:02 node-2 kernel: [    1.217284] usb usb2: Product: EHCI Host Controller
Sep 18 11:19:02 node-2 kernel: [    1.222743] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 18 11:19:02 node-2 kernel: [    1.228281] usb usb2: SerialNumber: 0000:00:1d.0
Sep 18 11:19:02 node-2 kernel: [    1.233791] hub 2-0:1.0: USB hub found
Sep 18 11:19:02 node-2 kernel: [    1.239120] hub 2-0:1.0: 2 ports detected
Sep 18 11:19:02 node-2 kernel: [    1.244407] ehci-platform: EHCI generic platform driver
Sep 18 11:19:02 node-2 kernel: [    1.249629] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 18 11:19:02 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 18 11:19:02 node-2 kernel: [    1.254938] ohci-pci: OHCI PCI platform driver
Sep 18 11:19:02 node-2 kernel: [    1.260220] ohci-platform: OHCI generic platform driver
Sep 18 11:19:02 node-2 kernel: [    1.265408] uhci_hcd: USB Universal Host Controller Interface driver
Sep 18 11:19:02 node-2 kernel: [    1.270740] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 18 11:19:02 node-2 kernel: [    1.471904] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 18 11:19:02 node-2 kernel: [    1.628087] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 18 11:19:02 node-2 kernel: [    1.633602] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 18 11:19:02 node-2 kernel: [    1.639350] hub 1-1:1.0: USB hub found
Sep 18 11:19:02 node-2 kernel: [    1.644823] hub 1-1:1.0: 6 ports detected
Sep 18 11:19:02 node-2 kernel: [    1.759661] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 18 11:19:02 node-2 kernel: [    1.767663] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 18 11:19:02 node-2 kernel: [    2.027749] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 18 11:19:02 node-2 kernel: [    2.033299] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 18 11:19:02 node-2 kernel: [    2.039141] hub 2-1:1.0: USB hub found
Sep 18 11:19:02 node-2 kernel: [    2.044736] hub 2-1:1.0: 8 ports detected
Sep 18 11:19:02 node-2 kernel: [    2.312184] i8042: No controller found
Sep 18 11:19:02 node-2 kernel: [    2.317660] mousedev: PS/2 mouse device common for all mice
Sep 18 11:19:02 node-2 kernel: [    2.323211] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 18 11:19:02 node-2 kernel: [    2.323456] rtc_cmos 00:02: RTC can wake from S4
Sep 18 11:19:02 node-2 kernel: [    2.324171] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 18 11:19:02 node-2 kernel: [    2.324373] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 18 11:19:02 node-2 kernel: [    2.324428] device-mapper: uevent: version 1.0.3
Sep 18 11:19:02 node-2 kernel: [    2.324693] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 18 11:19:02 node-2 kernel: [    2.324701] ledtrig-cpu: registered to indicate activity on CPUs
Sep 18 11:19:02 node-2 kernel: [    2.324813] TCP: cubic registered
Sep 18 11:19:02 node-2 kernel: [    2.324885] NET: Registered protocol family 10
Sep 18 11:19:02 node-2 kernel: [    2.325029] NET: Registered protocol family 17
Sep 18 11:19:02 node-2 kernel: [    2.325037] Key type dns_resolver registered
Sep 18 11:19:02 node-2 kernel: [    2.325718] Loading compiled-in X.509 certificates
Sep 18 11:19:02 node-2 kernel: [    2.326238] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 18 11:19:02 node-2 kernel: [    2.326248] registered taskstats version 1
Sep 18 11:19:02 node-2 kernel: [    2.332680] Key type trusted registered
Sep 18 11:19:02 node-2 kernel: [    2.339727] Key type encrypted registered
Sep 18 11:19:02 node-2 kernel: [    2.339729] AppArmor: AppArmor sha1 policy hashing enabled
Sep 18 11:19:02 node-2 kernel: [    2.339731] IMA: No TPM chip found, activating TPM-bypass!
Sep 18 11:19:02 node-2 kernel: [    2.340833] regulator-dummy: disabling
Sep 18 11:19:02 node-2 kernel: [    2.341173]   Magic number: 0:807:327
Sep 18 11:19:02 node-2 kernel: [    2.451656] rtc_cmos 00:02: setting system clock to 2016-09-18 11:18:25 UTC (1474197505)
Sep 18 11:19:02 node-2 kernel: [    2.463847] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 18 11:19:02 node-2 kernel: [    2.469369] EDD information not available.
Sep 18 11:19:02 node-2 kernel: [    2.474970] PM: Hibernation image not present or could not be loaded.
Sep 18 11:19:02 node-2 kernel: [    2.475753] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 18 11:19:02 node-2 kernel: [    2.487174] Write protecting the kernel read-only data: 12288k
Sep 18 11:19:02 node-2 kernel: [    2.493430] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 18 11:19:02 node-2 kernel: [    2.506143] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 18 11:19:02 node-2 kernel: [    2.538636] device-mapper: multipath: version 1.6.0 loaded
Sep 18 11:19:02 node-2 kernel: [    2.546481] systemd-udevd[218]: starting version 204
Sep 18 11:19:02 node-2 kernel: [    2.564967] md: linear personality registered for level -1
Sep 18 11:19:02 node-2 kernel: [    2.579214] md: multipath personality registered for level -4
Sep 18 11:19:02 node-2 kernel: [    2.585531] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 18 11:19:02 node-2 kernel: [    2.591941] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 18 11:19:02 node-2 kernel: [    2.604648] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 18 11:19:02 node-2 kernel: [    2.611121] usb 2-1.4: Manufacturer: Avocent
Sep 18 11:19:02 node-2 kernel: [    2.611193] md: raid0 personality registered for level 0
Sep 18 11:19:02 node-2 kernel: [    2.623719] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 18 11:19:02 node-2 kernel: [    2.630185] md: raid1 personality registered for level 1
Sep 18 11:19:02 node-2 kernel: [    2.641628] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 18 11:19:02 node-2 kernel: [    2.648237] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 18 11:19:02 node-2 kernel: [    2.648726] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 18 11:19:02 node-2 kernel: [    2.661414] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 18 11:19:02 node-2 kernel: [    2.661422] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 11:19:02 node-2 kernel: [    2.661425] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 11:19:02 node-2 kernel: [    2.669685] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.671702] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.671907] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.672060] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.672474] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.688988] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 18 11:19:02 node-2 kernel: [    2.689048] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 11:19:02 node-2 kernel: [    2.689060] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 18 11:19:02 node-2 kernel: [    2.689391] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.689497] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.689581] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.689739] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.689852] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.689973] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.690471] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.707469] raid6: sse2x1     270 MB/s
Sep 18 11:19:02 node-2 kernel: [    2.710215] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 18 11:19:02 node-2 kernel: [    2.710222] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 11:19:02 node-2 kernel: [    2.710241] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 11:19:02 node-2 kernel: [    2.710720] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.711138] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.711246] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.711375] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.711682] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.728747] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 18 11:19:02 node-2 kernel: [    2.728814] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 11:19:02 node-2 kernel: [    2.728832] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 11:19:02 node-2 kernel: [    2.729173] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.729350] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.729485] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.729581] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.730048] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 11:19:02 node-2 kernel: [    2.775129] raid6: sse2x2     478 MB/s
Sep 18 11:19:02 node-2 kernel: [    2.842985] raid6: sse2x4    1333 MB/s
Sep 18 11:19:02 node-2 kernel: [    2.910693] raid6: avx2x1   10071 MB/s
Sep 18 11:19:02 node-2 kernel: [    2.982636] raid6: avx2x2   18845 MB/s
Sep 18 11:19:02 node-2 kernel: [    3.054579] raid6: avx2x4   21360 MB/s
Sep 18 11:19:02 node-2 kernel: [    3.060479] raid6: using algorithm avx2x4 (21360 MB/s)
Sep 18 11:19:02 node-2 kernel: [    3.066509] raid6: using avx2x2 recovery algorithm
Sep 18 11:19:02 node-2 kernel: [    3.072408] Switched to clocksource tsc
Sep 18 11:19:02 node-2 kernel: [    3.073061] megasas: FW now in Ready state
Sep 18 11:19:02 node-2 kernel: [    3.073438] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.073564] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.073665] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.073780] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.073878] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074019] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074145] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074286] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074382] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074489] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074705] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074841] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.074973] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.075087] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.075263] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.075324] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Sep 18 11:19:02 node-2 kernel: [    3.075774] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 18 11:19:02 node-2 kernel: [    3.095638] xor: automatically using best checksumming function:
Sep 18 11:19:02 node-2 kernel: [    3.110668] hidraw: raw HID events driver (C) Jiri Kosina
Sep 18 11:19:02 node-2 kernel: [    3.119114] usbcore: registered new interface driver usbhid
Sep 18 11:19:02 node-2 kernel: [    3.124794] usbhid: USB HID core driver
Sep 18 11:19:02 node-2 kernel: [    3.131316] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 18 11:19:02 node-2 kernel: [    3.138597]    avx       : 35780.000 MB/sec
Sep 18 11:19:02 node-2 kernel: [    3.148500] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 18 11:19:02 node-2 kernel: [    3.159959] async_tx: api initialized (async)
Sep 18 11:19:02 node-2 kernel: [    3.160113] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 18 11:19:02 node-2 kernel: [    3.160889] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 18 11:19:02 node-2 kernel: [    3.161868] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 18 11:19:02 node-2 kernel: [    3.162403] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 18 11:19:02 node-2 kernel: [    3.217609] md: raid6 personality registered for level 6
Sep 18 11:19:02 node-2 kernel: [    3.223964] md: raid5 personality registered for level 5
Sep 18 11:19:02 node-2 kernel: [    3.230266] md: raid4 personality registered for level 4
Sep 18 11:19:02 node-2 kernel: [    3.239601] md: raid10 personality registered for level 10
Sep 18 11:19:02 node-2 kernel: [    3.295044] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Sep 18 11:19:02 node-2 kernel: [    3.434280] megasas:IOC Init cmd success
Sep 18 11:19:02 node-2 kernel: [    3.486251] megasas: INIT adapter done
Sep 18 11:19:02 node-2 kernel: [    3.562179] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 18 11:19:02 node-2 kernel: [    3.569089] scsi0 : LSI SAS based MegaRAID driver
Sep 18 11:19:02 node-2 kernel: [    3.576768] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 18 11:19:02 node-2 kernel: [    3.595937] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 18 11:19:02 node-2 kernel: [    3.611399] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 18 11:19:02 node-2 kernel: [    3.618032] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 18 11:19:02 node-2 kernel: [    3.631190] sd 0:2:0:0: [sda] Write Protect is off
Sep 18 11:19:02 node-2 kernel: [    3.637564] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 18 11:19:02 node-2 kernel: [    3.637584] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 18 11:19:02 node-2 kernel: [    3.677135]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 18 11:19:02 node-2 kernel: [    3.683841] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 18 11:19:02 node-2 kernel: [    3.803885] random: lvm urandom read with 27 bits of entropy available
Sep 18 11:19:02 node-2 kernel: [    3.938346] bio: create slab <bio-1> at 1
Sep 18 11:19:02 node-2 kernel: [    4.813571] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 11:19:02 node-2 kernel: [    5.587813] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 18 11:19:02 node-2 kernel: [    5.634016] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 18 11:19:02 node-2 kernel: [    5.781567] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 18 11:19:02 node-2 kernel: [    5.829425] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 18 11:19:02 node-2 kernel: [    5.844746] random: nonblocking pool is initialized
Sep 18 11:19:02 node-2 kernel: [    5.922957] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 11:19:02 node-2 kernel: [    6.091903] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 18 11:19:02 node-2 kernel: [    6.127732] XFS (dm-1): Mounting Filesystem
Sep 18 11:19:02 node-2 kernel: [    6.331626] XFS (dm-1): Ending clean mount
Sep 18 11:19:02 node-2 kernel: [    6.420050] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 11:19:02 node-2 kernel: [    6.449224] XFS (dm-2): Mounting Filesystem
Sep 18 11:19:02 node-2 kernel: [    6.656542] XFS (dm-2): Ending clean mount
Sep 18 11:19:02 node-2 kernel: [    6.800562] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 11:19:02 node-2 kernel: [    8.965124] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 18 11:19:02 node-2 kernel: [    8.993906] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 18 11:19:02 node-2 kernel: [    9.126609] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 18 11:19:02 node-2 kernel: [    9.126614] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 18 11:19:02 node-2 kernel: [    9.126618] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 18 11:19:02 node-2 kernel: [    9.126622] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 18 11:19:02 node-2 kernel: [    9.181757] systemd-udevd[802]: starting version 204
Sep 18 11:19:02 node-2 kernel: [    9.365745] power_meter ACPI000D:00: Found ACPI power meter.
Sep 18 11:19:02 node-2 kernel: [    9.365762] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 18 11:19:02 node-2 kernel: [    9.374471] IPMI System Interface driver.
Sep 18 11:19:02 node-2 kernel: [    9.374529] ipmi_si: probing via ACPI
Sep 18 11:19:02 node-2 kernel: [    9.374551] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 18 11:19:02 node-2 kernel: [    9.374552] ipmi_si: Adding ACPI-specified kcs state machine
Sep 18 11:19:02 node-2 kernel: [    9.374568] ipmi_si: probing via SMBIOS
Sep 18 11:19:02 node-2 kernel: [    9.374569] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 18 11:19:02 node-2 kernel: [    9.374569] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 18 11:19:02 node-2 kernel: [    9.374571] ipmi_si: probing via SPMI
Sep 18 11:19:02 node-2 kernel: [    9.374572] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 18 11:19:02 node-2 kernel: [    9.374573] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 18 11:19:02 node-2 kernel: [    9.374574] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 18 11:19:02 node-2 kernel: [    9.405998] wmi: Mapper loaded
Sep 18 11:19:02 node-2 kernel: [    9.407421] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 18 11:19:02 node-2 kernel: [    9.410358] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 18 11:19:02 node-2 kernel: [    9.410362] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 18 11:19:02 node-2 kernel: [    9.410364] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 18 11:19:02 node-2 kernel: [    9.410366] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 18 11:19:02 node-2 kernel: [    9.410378] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 18 11:19:02 node-2 kernel: [    9.469606] systemd-udevd[821]: renamed network interface eth1 to enp7s0
Sep 18 11:19:02 node-2 kernel: [    9.493482] systemd-udevd[820]: renamed network interface eth0 to enp6s0
Sep 18 11:19:02 node-2 kernel: [    9.521465] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 18 11:19:02 node-2 kernel: [    9.521470] ipmi_si 00:09: IPMI kcs interface initialized
Sep 18 11:19:02 node-2 kernel: [    9.521479] systemd-udevd[826]: renamed network interface eth2 to enp8s0
Sep 18 11:19:02 node-2 kernel: [    9.565514] systemd-udevd[858]: renamed network interface eth3 to enp9s0
Sep 18 11:19:02 node-2 kernel: [    9.853220] type=1400 audit(1474197513.016:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1084 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.853336] type=1400 audit(1474197513.016:3): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1086 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.853380] type=1400 audit(1474197513.016:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1084 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.853503] type=1400 audit(1474197513.016:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1086 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.853532] type=1400 audit(1474197513.016:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1084 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.853623] type=1400 audit(1474197513.016:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1086 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.865450] type=1400 audit(1474197513.028:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1087 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.865588] type=1400 audit(1474197513.028:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1087 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.865708] type=1400 audit(1474197513.028:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1087 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [    9.876503] type=1400 audit(1474197513.036:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1085 comm="apparmor_parser"
Sep 18 11:19:02 node-2 kernel: [   10.422177] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 18 11:19:02 node-2 kernel: [   10.423281] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 18 11:19:02 node-2 kernel: [   10.654981] enic 0000:06:00.0 enp6s0: Link UP
Sep 18 11:19:02 node-2 kernel: [   10.655428] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 18 11:19:02 node-2 kernel: [   10.655439] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 18 11:19:02 node-2 kernel: [   22.050407] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 18 11:19:03 node-2 failsafe: Failsafe of 120 seconds reached.
Sep 18 11:19:04 node-2 kernel: [   40.590162] init: failsafe main process (8449) killed by TERM signal
Sep 18 11:19:04 node-2 dbus[8497]: [system] AppArmor D-Bus mediation is enabled
Sep 18 11:19:04 node-2 kernel: [   40.798296] audit_printk_skb: 30 callbacks suppressed
Sep 18 11:19:04 node-2 kernel: [   40.798297] type=1400 audit(1474197544.259:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8575 comm="apparmor_parser"
Sep 18 11:19:04 node-2 kernel: [   40.802213] type=1400 audit(1474197544.263:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8574 comm="apparmor_parser"
Sep 18 11:19:04 node-2 kernel: [   40.802218] type=1400 audit(1474197544.263:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8574 comm="apparmor_parser"
Sep 18 11:19:04 node-2 kernel: [   40.802221] type=1400 audit(1474197544.263:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Sep 18 11:19:04 node-2 kernel: [   40.802454] type=1400 audit(1474197544.263:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8574 comm="apparmor_parser"
Sep 18 11:19:04 node-2 kernel: [   40.802456] type=1400 audit(1474197544.263:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Sep 18 11:19:04 node-2 kernel: [   40.802581] type=1400 audit(1474197544.263:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Sep 18 11:19:04 node-2 kernel: [   40.909013] type=1400 audit(1474197544.367:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8577 comm="apparmor_parser"
Sep 18 11:19:04 node-2 anacron[8656]: Anacron 2.3 started on 2016-09-18
Sep 18 11:19:04 node-2 multipathd: path checkers start up
Sep 18 11:19:04 node-2 cron[8607]: (CRON) INFO (pidfile fd = 3)
Sep 18 11:19:04 node-2 anacron[8656]: Will run job `cron.daily' in 5 min.
Sep 18 11:19:04 node-2 anacron[8656]: Will run job `cron.weekly' in 10 min.
Sep 18 11:19:04 node-2 anacron[8656]: Will run job `cron.monthly' in 15 min.
Sep 18 11:19:04 node-2 anacron[8656]: Jobs will be executed sequentially
Sep 18 11:19:04 node-2 cron[8680]: (CRON) STARTUP (fork ok)
Sep 18 11:19:04 node-2 cron[8680]: (CRON) INFO (Running @reboot jobs)
Sep 18 11:19:04 node-2 postfix/master[8786]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 18 11:19:08 node-2 puppet-agent[8970]: Reopening log files
Sep 18 11:19:10 node-2 puppet-agent[8970]: Could not request certificate: Connection refused - connect(2)
Sep 18 11:19:21 node-2 puppet-user[9178]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 18 11:19:21 node-2 puppet-user[9178]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 18 11:19:21 node-2 puppet-user[9178]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 18 11:19:21 node-2 puppet-user[9178]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 18 11:19:22 node-2 puppet-user[9178]: Finished catalog run in 0.46 seconds
Sep 18 11:19:23 node-2 multipathd: uevent trigger error
Sep 18 11:19:23 node-2 puppet-user[9598]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 18 11:19:23 node-2 puppet-user[9598]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 18 11:19:23 node-2 puppet-user[9598]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 18 11:19:23 node-2 puppet-user[9598]: Finished catalog run in 0.06 seconds
Sep 18 11:19:25 node-2 puppet-user[10065]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 18 11:19:25 node-2 puppet-user[10065]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep 18 11:19:25 node-2 puppet-user[10065]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 18 11:19:25 node-2 puppet-user[10065]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 18 11:19:25 node-2 puppet-user[10065]: Finished catalog run in 0.03 seconds
Sep 18 11:19:27 node-2 puppet-user[10534]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 18 11:19:27 node-2 puppet-user[10534]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 18 11:19:27 node-2 puppet-user[10534]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 18 11:19:27 node-2 puppet-user[10534]: Finished catalog run in 0.04 seconds
Sep 18 11:19:28 node-2 puppet-user[10998]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 18 11:19:28 node-2 puppet-user[10998]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Sep 18 11:19:28 node-2 puppet-user[10998]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 18 11:19:29 node-2 puppet-user[10998]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep 18 11:19:29 node-2 puppet-user[10998]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 18 11:19:30 node-2 puppet-user[10998]: (/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
Sep 18 11:19:30 node-2 puppet-user[10998]: Finished catalog run in 1.19 seconds
Sep 18 11:19:31 node-2 puppet-user[11697]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 18 11:19:31 node-2 puppet-user[11697]: Compiled catalog for node-2.domain.tld in environment production in 0.21 seconds
Sep 18 11:19:31 node-2 puppet-user[11697]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep 18 11:19:31 node-2 puppet-user[11697]: (/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
Sep 18 11:19:31 node-2 puppet-user[11697]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 18 11:19:31 node-2 puppet-user[11697]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 18 11:19:31 node-2 puppet-user[11697]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 18 11:19:32 node-2 puppet-user[11697]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 18 11:19:32 node-2 puppet-user[11697]: Finished catalog run in 0.41 seconds
Sep 18 11:19:33 node-2 puppet-user[12181]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 18 11:19:33 node-2 puppet-user[12181]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Sep 18 11:19:33 node-2 puppet-user[12181]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 18 11:19:33 node-2 kernel: [   70.362241] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 18 11:19:33 node-2 kernel: [   70.362289] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 18 11:19:33 node-2 puppet-user[12181]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 18 11:19:33 node-2 puppet-user[12181]: Finished catalog run in 0.06 seconds
Sep 18 11:19:35 node-2 puppet-user[12640]: (Scope(Class[main])) MODULAR: sync_time
Sep 18 11:19:35 node-2 puppet-user[12640]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 18 11:19:36 node-2 ntpdate[13063]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 18 11:19:40 node-2 kernel: [   76.777341] init: plymouth-upstart-bridge main process ended, respawning
Sep 18 11:19:40 node-2 puppet-agent[8970]: Could not run: SIGTERM
Sep 18 11:19:40 node-2 kernel: [   77.067415] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 18 11:19:40 node-2 ec2: 
Sep 18 11:19:40 node-2 ec2: #############################################################
Sep 18 11:19:40 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 18 11:19:40 node-2 ec2: 1024 8a:c2:d4:9c:9a:bf:e7:e4:93:3c:63:5f:f4:d8:fb:ad  root@node-2.domain.tld (DSA)
Sep 18 11:19:40 node-2 ec2: 256 e5:f3:a6:35:d0:0a:90:c5:cf:6f:32:a1:c4:83:b7:8a  root@node-2.domain.tld (ECDSA)
Sep 18 11:19:40 node-2 ec2: 256 49:a3:97:6b:9c:a8:1f:04:25:c1:e5:75:34:0c:a0:43  root@node-2.domain.tld (ED25519)
Sep 18 11:19:40 node-2 ec2: 2048 eb:da:1b:45:fb:9f:e8:61:6f:02:35:cb:3b:01:c1:ab  root@node-2.domain.tld (RSA)
Sep 18 11:19:40 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 18 11:19:40 node-2 ec2: #############################################################
Sep 18 11:19:42 node-2 ntpdate[13063]: adjust time server 10.20.0.2 offset 0.000367 sec
Sep 18 11:19:42 node-2 puppet-user[12640]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 18 11:19:42 node-2 puppet-user[12640]: Finished catalog run in 6.17 seconds
Sep 18 11:19:46 node-2 puppet-user[13421]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 18 11:19:46 node-2 puppet-user[13421]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep 18 11:19:46 node-2 puppet-user[13421]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 18 11:19:46 node-2 puppet-user[13421]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep 18 11:19:46 node-2 puppet-user[13421]: Finished catalog run in 0.08 seconds
Sep 18 11:19:47 node-2 puppet-user[13881]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 18 11:19:48 node-2 puppet-user[13881]: Compiled catalog for node-2.domain.tld in environment production in 0.51 seconds
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 18 11:19:48 node-2 puppet-user[13881]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 18 11:19:49 node-2 puppet-user[13881]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 18 11:19:49 node-2 puppet-user[13881]: Finished catalog run in 0.95 seconds
Sep 18 11:19:51 node-2 puppet-user[14394]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 18 11:19:51 node-2 puppet-user[14394]: Compiled catalog for node-2.domain.tld in environment production in 0.11 seconds
Sep 18 11:19:54 node-2 puppet-user[14394]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 18 11:20:01 node-2 CRON[15754]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 18 11:20:18 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 18 11:20:18 node-2 nailgun-agent: I, [2016-09-18T11:20:18.774698 #15757]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 18 11:20:24 node-2 puppet-user[14394]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 18 11:20:24 node-2 puppet-user[14394]: Finished catalog run in 32.96 seconds
Sep 18 11:20:25 node-2 puppet-user[17019]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 18 11:20:26 node-2 puppet-user[17019]: Compiled catalog for node-2.domain.tld in environment production in 0.56 seconds
Sep 18 11:20:26 node-2 puppet-user[17019]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 18 11:20:26 node-2 puppet-user[17019]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 18 11:20:26 node-2 puppet-user[17019]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 18 11:20:26 node-2 puppet-user[17019]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 18 11:20:26 node-2 puppet-user[17019]: Finished catalog run in 0.11 seconds
Sep 18 11:20:28 node-2 puppet-user[17489]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 18 11:20:29 node-2 puppet-user[17489]: Compiled catalog for node-2.domain.tld in environment production in 0.86 seconds
Sep 18 11:20:29 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 18 11:20:29 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 18 11:20:29 node-2 crontab[17932]: (root) LIST (root)
Sep 18 11:20:29 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 18 11:20:29 node-2 crontab[17933]: (root) REPLACE (root)
Sep 18 11:20:30 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 18 11:20:31 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 18 11:20:31 node-2 nailgun-agent: I, [2016-09-18T11:20:31.813031 #15757]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 18 11:20:31 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 18 11:20:32 node-2 puppet-user[17489]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 18 11:20:32 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8421" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:32 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 18 11:20:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:20:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:21:46 node-2 ntpdate[27945]: no servers can be used, exiting
<27>Sep 18 11:21:46 node-2 ntpdate[28165]: no servers can be used, exiting
<27>Sep 18 11:22:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:22:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:31 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:23:42 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 11:23:42 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 11:23:48 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 11:23:48 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 11:23:54 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 11:24:00 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 11:24:00 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 11:24:06 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:06 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:06 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:06 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:19 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:19 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:19 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:19 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:19 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:19 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:25 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:25 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:25 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:25 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:25 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:25 node-2 multipathd: uevent trigger error
<129>Sep 18 11:24:27 node-2 haproxy[15927]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:27 node-2 haproxy[15927]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:28 node-2 haproxy[15931]: 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>Sep 18 11:24:28 node-2 haproxy[15931]: proxy mysqld has no server available!
<27>Sep 18 11:24:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:33 node-2 multipathd: uevent trigger error
<129>Sep 18 11:24:36 node-2 haproxy[18346]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:36 node-2 haproxy[18346]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:36 node-2 haproxy[18346]: 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>Sep 18 11:24:36 node-2 haproxy[18346]: proxy mysqld has no server available!
<129>Sep 18 11:24:37 node-2 haproxy[18350]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:37 node-2 haproxy[18350]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:37 node-2 haproxy[18350]: 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>Sep 18 11:24:37 node-2 haproxy[18350]: proxy object-storage has no server available!
<27>Sep 18 11:24:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:39 node-2 multipathd: uevent trigger error
<129>Sep 18 11:24:41 node-2 haproxy[19803]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:41 node-2 haproxy[19803]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:41 node-2 haproxy[19803]: 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>Sep 18 11:24:41 node-2 haproxy[19803]: proxy neutron has no server available!
<129>Sep 18 11:24:42 node-2 haproxy[19807]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:42 node-2 haproxy[19807]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:42 node-2 haproxy[19807]: 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>Sep 18 11:24:42 node-2 haproxy[19807]: proxy mysqld has no server available!
<129>Sep 18 11:24:42 node-2 haproxy[19807]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:42 node-2 haproxy[19807]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:42 node-2 haproxy[19807]: 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>Sep 18 11:24:42 node-2 haproxy[19807]: proxy object-storage has no server available!
<27>Sep 18 11:24:44 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:44 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:44 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:44 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:44 node-2 multipathd: uevent trigger error
<129>Sep 18 11:24:46 node-2 haproxy[21059]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:47 node-2 haproxy[21063]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:47 node-2 haproxy[21063]: 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>Sep 18 11:24:47 node-2 haproxy[21063]: proxy keystone-1 has no server available!
<129>Sep 18 11:24:47 node-2 haproxy[21063]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:47 node-2 haproxy[21063]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:47 node-2 haproxy[21063]: 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>Sep 18 11:24:47 node-2 haproxy[21063]: proxy keystone-2 has no server available!
<129>Sep 18 11:24:47 node-2 haproxy[21063]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:47 node-2 haproxy[21063]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:47 node-2 haproxy[21063]: 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>Sep 18 11:24:47 node-2 haproxy[21063]: proxy neutron has no server available!
<129>Sep 18 11:24:47 node-2 haproxy[21063]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:48 node-2 haproxy[21063]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:48 node-2 haproxy[21063]: 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>Sep 18 11:24:48 node-2 haproxy[21063]: proxy mysqld has no server available!
<129>Sep 18 11:24:48 node-2 haproxy[21063]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:48 node-2 haproxy[21063]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:48 node-2 haproxy[21063]: 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>Sep 18 11:24:48 node-2 haproxy[21063]: proxy object-storage has no server available!
<27>Sep 18 11:24:49 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:49 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:49 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:49 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:49 node-2 multipathd: uevent trigger error
<129>Sep 18 11:24:51 node-2 haproxy[22283]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:52 node-2 haproxy[22287]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:52 node-2 haproxy[22287]: 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>Sep 18 11:24:52 node-2 haproxy[22287]: proxy keystone-1 has no server available!
<129>Sep 18 11:24:52 node-2 haproxy[22287]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:52 node-2 haproxy[22287]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:52 node-2 haproxy[22287]: 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>Sep 18 11:24:52 node-2 haproxy[22287]: proxy keystone-2 has no server available!
<129>Sep 18 11:24:52 node-2 haproxy[22287]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:52 node-2 haproxy[22287]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:52 node-2 haproxy[22287]: 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>Sep 18 11:24:52 node-2 haproxy[22287]: proxy neutron has no server available!
<129>Sep 18 11:24:52 node-2 haproxy[22287]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:52 node-2 haproxy[22287]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:53 node-2 haproxy[22287]: 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>Sep 18 11:24:53 node-2 haproxy[22287]: proxy mysqld has no server available!
<129>Sep 18 11:24:53 node-2 haproxy[22287]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:53 node-2 haproxy[22287]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:53 node-2 haproxy[22287]: 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>Sep 18 11:24:53 node-2 haproxy[22287]: proxy object-storage has no server available!
<129>Sep 18 11:24:53 node-2 haproxy[22287]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:53 node-2 haproxy[22287]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:53 node-2 haproxy[22287]: 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>Sep 18 11:24:53 node-2 haproxy[22287]: proxy aodh has no server available!
<27>Sep 18 11:24:55 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-2 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-2 multipathd: uevent trigger error
<129>Sep 18 11:24:57 node-2 haproxy[23505]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:57 node-2 haproxy[23505]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:57 node-2 haproxy[23505]: 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>Sep 18 11:24:57 node-2 haproxy[23505]: proxy keystone-1 has no server available!
<129>Sep 18 11:24:57 node-2 haproxy[23505]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:57 node-2 haproxy[23505]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:57 node-2 haproxy[23505]: 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>Sep 18 11:24:57 node-2 haproxy[23505]: proxy keystone-2 has no server available!
<129>Sep 18 11:24:57 node-2 haproxy[23505]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:57 node-2 haproxy[23505]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:57 node-2 haproxy[23505]: 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>Sep 18 11:24:57 node-2 haproxy[23505]: proxy neutron has no server available!
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: 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>Sep 18 11:24:58 node-2 haproxy[23509]: proxy mysqld has no server available!
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: 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>Sep 18 11:24:58 node-2 haproxy[23509]: proxy object-storage has no server available!
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: 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>Sep 18 11:24:58 node-2 haproxy[23509]: proxy aodh has no server available!
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:24:58 node-2 haproxy[23509]: 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>Sep 18 11:24:58 node-2 haproxy[23509]: proxy ceilometer has no server available!
<27>Sep 18 11:25:00 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:00 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:00 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:00 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:00 node-2 multipathd: uevent trigger error
<129>Sep 18 11:25:02 node-2 haproxy[24736]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:02 node-2 haproxy[24736]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:02 node-2 haproxy[24736]: 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>Sep 18 11:25:02 node-2 haproxy[24736]: proxy keystone-1 has no server available!
<129>Sep 18 11:25:02 node-2 haproxy[24736]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:02 node-2 haproxy[24736]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:02 node-2 haproxy[24736]: 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>Sep 18 11:25:02 node-2 haproxy[24736]: proxy keystone-2 has no server available!
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: 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>Sep 18 11:25:03 node-2 haproxy[24745]: proxy neutron has no server available!
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: 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>Sep 18 11:25:03 node-2 haproxy[24745]: proxy mysqld has no server available!
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: 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>Sep 18 11:25:03 node-2 haproxy[24745]: proxy object-storage has no server available!
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:03 node-2 haproxy[24745]: 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>Sep 18 11:25:03 node-2 haproxy[24745]: proxy aodh has no server available!
<129>Sep 18 11:25:04 node-2 haproxy[24745]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:04 node-2 haproxy[24745]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:04 node-2 haproxy[24745]: 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>Sep 18 11:25:04 node-2 haproxy[24745]: proxy ceilometer has no server available!
<27>Sep 18 11:25:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:05 node-2 multipathd: uevent trigger error
<129>Sep 18 11:25:07 node-2 haproxy[25998]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:07 node-2 haproxy[25998]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:07 node-2 haproxy[25998]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: 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>Sep 18 11:25:08 node-2 haproxy[26002]: proxy keystone-1 has no server available!
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: 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>Sep 18 11:25:08 node-2 haproxy[26002]: proxy keystone-2 has no server available!
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: 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>Sep 18 11:25:08 node-2 haproxy[26002]: proxy neutron has no server available!
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: 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>Sep 18 11:25:08 node-2 haproxy[26002]: proxy mysqld has no server available!
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:08 node-2 haproxy[26002]: 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>Sep 18 11:25:08 node-2 haproxy[26002]: proxy object-storage has no server available!
<129>Sep 18 11:25:09 node-2 haproxy[26002]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:09 node-2 haproxy[26002]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:09 node-2 haproxy[26002]: 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>Sep 18 11:25:09 node-2 haproxy[26002]: proxy aodh has no server available!
<129>Sep 18 11:25:09 node-2 haproxy[26002]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:09 node-2 haproxy[26002]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:09 node-2 haproxy[26002]: 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>Sep 18 11:25:09 node-2 haproxy[26002]: proxy ceilometer has no server available!
<27>Sep 18 11:25:10 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:10 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:10 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:10 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:10 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:10 node-2 multipathd: uevent trigger error
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: 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>Sep 18 11:25:13 node-2 haproxy[27297]: proxy keystone-1 has no server available!
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: 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>Sep 18 11:25:13 node-2 haproxy[27297]: proxy keystone-2 has no server available!
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: 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>Sep 18 11:25:13 node-2 haproxy[27297]: proxy glance-api has no server available!
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:13 node-2 haproxy[27297]: 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>Sep 18 11:25:13 node-2 haproxy[27297]: proxy glance-glare has no server available!
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: 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>Sep 18 11:25:14 node-2 haproxy[27301]: proxy neutron has no server available!
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: 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>Sep 18 11:25:14 node-2 haproxy[27301]: proxy glance-registry has no server available!
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: 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>Sep 18 11:25:14 node-2 haproxy[27301]: proxy mysqld has no server available!
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: 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>Sep 18 11:25:14 node-2 haproxy[27301]: proxy object-storage has no server available!
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: 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>Sep 18 11:25:14 node-2 haproxy[27301]: proxy aodh has no server available!
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:14 node-2 haproxy[27301]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:15 node-2 haproxy[27301]: 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>Sep 18 11:25:15 node-2 haproxy[27301]: proxy ceilometer has no server available!
<27>Sep 18 11:25:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:16 node-2 multipathd: uevent trigger error
<129>Sep 18 11:25:18 node-2 haproxy[28548]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:18 node-2 haproxy[28548]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: 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>Sep 18 11:25:19 node-2 haproxy[28552]: proxy keystone-1 has no server available!
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: 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>Sep 18 11:25:19 node-2 haproxy[28552]: proxy keystone-2 has no server available!
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: 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>Sep 18 11:25:19 node-2 haproxy[28552]: proxy nova-api has no server available!
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: 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>Sep 18 11:25:19 node-2 haproxy[28552]: proxy nova-metadata-api has no server available!
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: 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>Sep 18 11:25:19 node-2 haproxy[28552]: proxy glance-api has no server available!
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: 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>Sep 18 11:25:19 node-2 haproxy[28552]: proxy glance-glare has no server available!
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: 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>Sep 18 11:25:19 node-2 haproxy[28552]: proxy neutron has no server available!
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-2 haproxy[28552]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: 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>Sep 18 11:25:20 node-2 haproxy[28552]: proxy glance-registry has no server available!
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: 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>Sep 18 11:25:20 node-2 haproxy[28552]: proxy mysqld has no server available!
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: 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>Sep 18 11:25:20 node-2 haproxy[28552]: proxy object-storage has no server available!
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: 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>Sep 18 11:25:20 node-2 haproxy[28552]: proxy aodh has no server available!
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: 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>Sep 18 11:25:20 node-2 haproxy[28552]: proxy ceilometer has no server available!
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:20 node-2 haproxy[28552]: 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>Sep 18 11:25:20 node-2 haproxy[28552]: proxy nova-novncproxy has no server available!
<27>Sep 18 11:25:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:22 node-2 multipathd: uevent trigger error
<129>Sep 18 11:25:24 node-2 haproxy[29768]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:24 node-2 haproxy[29768]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:24 node-2 haproxy[29768]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:24 node-2 haproxy[29768]: 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>Sep 18 11:25:24 node-2 haproxy[29768]: proxy keystone-1 has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: 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>Sep 18 11:25:25 node-2 haproxy[29772]: proxy keystone-2 has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: 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>Sep 18 11:25:25 node-2 haproxy[29772]: proxy nova-api has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: 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>Sep 18 11:25:25 node-2 haproxy[29772]: proxy nova-metadata-api has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: 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>Sep 18 11:25:25 node-2 haproxy[29772]: proxy cinder-api has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: 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>Sep 18 11:25:25 node-2 haproxy[29772]: proxy glance-api has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: 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>Sep 18 11:25:25 node-2 haproxy[29772]: proxy glance-glare has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: 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>Sep 18 11:25:25 node-2 haproxy[29772]: proxy neutron has no server available!
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:25 node-2 haproxy[29772]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: 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>Sep 18 11:25:26 node-2 haproxy[29772]: proxy glance-registry has no server available!
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: 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>Sep 18 11:25:26 node-2 haproxy[29772]: proxy mysqld has no server available!
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: 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>Sep 18 11:25:26 node-2 haproxy[29772]: proxy object-storage has no server available!
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: 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>Sep 18 11:25:26 node-2 haproxy[29772]: proxy aodh has no server available!
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: 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>Sep 18 11:25:26 node-2 haproxy[29772]: proxy ceilometer has no server available!
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:26 node-2 haproxy[29772]: 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>Sep 18 11:25:26 node-2 haproxy[29772]: proxy nova-novncproxy has no server available!
<27>Sep 18 11:25:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:27 node-2 multipathd: uevent trigger error
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: 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>Sep 18 11:25:30 node-2 haproxy[31176]: proxy keystone-1 has no server available!
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: 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>Sep 18 11:25:30 node-2 haproxy[31176]: proxy keystone-2 has no server available!
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: 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>Sep 18 11:25:30 node-2 haproxy[31176]: proxy nova-api has no server available!
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: 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>Sep 18 11:25:30 node-2 haproxy[31176]: proxy nova-metadata-api has no server available!
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-2 haproxy[31176]: 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>Sep 18 11:25:30 node-2 haproxy[31176]: proxy cinder-api has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy glance-api has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy glance-glare has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy neutron has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy glance-registry has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy mysqld has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy object-storage has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy aodh has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy ceilometer has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:31 node-2 haproxy[31180]: 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>Sep 18 11:25:31 node-2 haproxy[31180]: proxy heat-api has no server available!
<129>Sep 18 11:25:31 node-2 haproxy[31180]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:32 node-2 haproxy[31180]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:32 node-2 haproxy[31180]: 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>Sep 18 11:25:32 node-2 haproxy[31180]: proxy heat-api-cfn has no server available!
<129>Sep 18 11:25:32 node-2 haproxy[31180]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:32 node-2 haproxy[31180]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:32 node-2 haproxy[31180]: 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>Sep 18 11:25:32 node-2 haproxy[31180]: proxy heat-api-cloudwatch has no server available!
<129>Sep 18 11:25:32 node-2 haproxy[31180]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:32 node-2 haproxy[31180]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:32 node-2 haproxy[31180]: 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>Sep 18 11:25:32 node-2 haproxy[31180]: proxy nova-novncproxy has no server available!
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:25:43 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 18 11:26:08 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Sep 18 11:26:10 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 18 11:26:40 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:26:43 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 11:27:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:22 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:42 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:29:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:42 node-2 multipathd: uevent trigger error
<43>Sep 18 11:29:43 node-2 apache2_error [Sun Sep 18 11:29:34.280719 2016] [mpm_event:notice] [pid 7049:tid 140454786799488] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 18 11:29:43 node-2 apache2_error [Sun Sep 18 11:29:34.280794 2016] [core:notice] [pid 7049:tid 140454786799488] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 18 11:29:43 node-2 apache2_error [Sun Sep 18 11:29:37.408133 2016] [mpm_event:notice] [pid 7049:tid 140454786799488] AH00491: caught SIGTERM, shutting down
<43>Sep 18 11:29:43 node-2 apache2_error [Sun Sep 18 11:29:38.503039 2016] [mpm_worker:notice] [pid 8669:tid 140027689940864] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 18 11:29:43 node-2 apache2_error [Sun Sep 18 11:29:38.503088 2016] [core:notice] [pid 8669:tid 140027689940864] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:29:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:29:50 node-2 multipathd: uevent trigger error
<43>Sep 18 11:31:03 node-2 apache2_error [Sun Sep 18 11:30:59.766754 2016] [mpm_worker:notice] [pid 8669:tid 140027689940864] AH00295: caught SIGTERM, shutting down
<43>Sep 18 11:31:03 node-2 apache2_error [Sun Sep 18 11:31:00.526167 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:31:03 node-2 apache2_error [Sun Sep 18 11:31:00.526226 2016] [core:notice] [pid 22645:tid 140312751986560] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 18 11:31:53 node-2 apache2_error [Sun Sep 18 11:31:46.018780 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:31:53 node-2 apache2_error [Sun Sep 18 11:31:46.215597 2016] [mpm_worker:warn] [pid 22645:tid 140312751986560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:31:53 node-2 apache2_error [Sun Sep 18 11:31:46.220026 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:31:53 node-2 apache2_error [Sun Sep 18 11:31:46.220045 2016] [core:notice] [pid 22645:tid 140312751986560] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:32:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:38 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:38 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:38 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:43 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:32:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:32:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:33:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:34:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:35:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:35:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:35:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:35:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:35:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:35:45 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:36:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:36:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:36:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:36:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:36:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:18 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:18 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:18 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:18 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:18 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:18 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:18 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:40 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:37:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:38:47 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:40:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:17 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:37 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:37 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:37 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:37 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:37 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:40:42 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:04 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:04 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:04 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:04 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:04 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:41:48 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:42:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:39 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:42:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:43:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:43:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:43:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:43:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:43:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:43:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:44:50 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:45:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:45:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:45:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:45:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:45:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:45:32 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:46:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:09 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:09 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:09 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:09 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:09 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:13 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:13 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:13 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:13 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:30 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:47:51 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 18 11:48:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:48:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:48:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:48:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:48:05 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:07 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:23 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:23 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:23 node-2 multipathd: uevent trigger error
<27>Sep 18 11:49:23 node-2 multipathd: uevent trigger error
<11>Sep 18 11:49:36 node-2 liberasurecode[8435]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:36 node-2 liberasurecode[8435]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:36 node-2 liberasurecode[8435]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:36 node-2 liberasurecode[8435]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:36 node-2 liberasurecode[8535]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:36 node-2 liberasurecode[8535]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:36 node-2 liberasurecode[8535]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:36 node-2 liberasurecode[8535]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:38 node-2 liberasurecode[9567]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:38 node-2 liberasurecode[9567]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:38 node-2 liberasurecode[9567]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:38 node-2 liberasurecode[9567]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10813]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10813]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10813]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:42 node-2 liberasurecode[10813]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10856]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10856]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10920]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10920]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10920]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10920]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10932]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10932]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10932]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10932]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10946]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10946]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10946]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10946]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10958]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:49:43 node-2 liberasurecode[10958]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:00 node-2 liberasurecode[11780]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:00 node-2 liberasurecode[11780]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:00 node-2 liberasurecode[11780]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:00 node-2 liberasurecode[11780]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:02 node-2 liberasurecode[11871]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:02 node-2 liberasurecode[11871]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:02 node-2 liberasurecode[11871]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:02 node-2 liberasurecode[11871]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 18 11:50:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:50:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:50:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:50:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:50:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:50:53 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 18 11:50:55 node-2 apache2_error [Sun Sep 18 11:50:54.817678 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:50:55 node-2 apache2_error [Sun Sep 18 11:50:55.199832 2016] [mpm_worker:warn] [pid 22645:tid 140312751986560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:50:55 node-2 apache2_error [Sun Sep 18 11:50:55.204532 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:50:55 node-2 apache2_error [Sun Sep 18 11:50:55.204554 2016] [core:notice] [pid 22645:tid 140312751986560] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 18 11:51:35 node-2 apache2_error [Sun Sep 18 11:51:31.848851 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:51:35 node-2 apache2_error [Sun Sep 18 11:51:32.233634 2016] [mpm_worker:warn] [pid 22645:tid 140312751986560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:51:35 node-2 apache2_error [Sun Sep 18 11:51:32.240402 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:51:35 node-2 apache2_error [Sun Sep 18 11:51:32.240428 2016] [core:notice] [pid 22645:tid 140312751986560] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:51:35 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:35 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:35 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:35 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:35 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:43 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:43 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:43 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:43 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:43 node-2 multipathd: uevent trigger error
<27>Sep 18 11:51:43 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:21 node-2 multipathd: uevent trigger error
<43>Sep 18 11:52:25 node-2 apache2_error [Sun Sep 18 11:52:17.446030 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:52:25 node-2 apache2_error [Sun Sep 18 11:52:17.831731 2016] [mpm_worker:warn] [pid 22645:tid 140312751986560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:52:25 node-2 apache2_error [Sun Sep 18 11:52:17.841011 2016] [mpm_worker:notice] [pid 22645:tid 140312751986560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:52:25 node-2 apache2_error [Sun Sep 18 11:52:17.841041 2016] [core:notice] [pid 22645:tid 140312751986560] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:52:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:27 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:33 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:52 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:52 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:52 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:52 node-2 multipathd: uevent trigger error
<27>Sep 18 11:52:52 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:15 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:21 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:27 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 18 11:53:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:36 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:51 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:51 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:51 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:51 node-2 multipathd: uevent trigger error
<27>Sep 18 11:53:51 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:03 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:03 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 11:54:29 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:29 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:29 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:29 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:29 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:34 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:47 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:54 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:59 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:59 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:59 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:59 node-2 multipathd: uevent trigger error
<27>Sep 18 11:54:59 node-2 multipathd: uevent trigger error
<11>Sep 18 11:55:01 node-2 liberasurecode[14644]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:55:01 node-2 liberasurecode[14644]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:55:01 node-2 liberasurecode[14644]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:55:01 node-2 liberasurecode[14644]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 18 11:55:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:11 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:41 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:45 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:46 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:46 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:50 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:58 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:58 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:58 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:58 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:58 node-2 multipathd: uevent trigger error
<27>Sep 18 11:55:58 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:02 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:08 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:12 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:16 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:20 node-2 multipathd: uevent trigger error
<27>Sep 18 11:56:20 node-2 multipathd: uevent trigger error
