Sep 21 10:02:48 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8397" x-info="http://www.rsyslog.com"] start
Sep 21 10:02:48 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 21 10:02:48 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep 21 10:02:48 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep 21 10:02:48 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 21 10:02:48 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 21 10:02:48 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 21 10:02:48 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 21 10:02:48 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=d4d3075f-6393-4f3e-86fd-b8e78855f6ea nomdmonddf nomdmonisw
Sep 21 10:02:48 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep 21 10:02:48 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep 21 10:02:48 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep 21 10:02:48 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep 21 10:02:48 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 21 10:02:48 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 21 10:02:48 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 21 10:02:48 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 21 10:02:48 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 21 10:02:48 node-2 kernel: [    0.000000] No AGP bridge found
Sep 21 10:02:48 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 21 10:02:48 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep 21 10:02:48 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 21 10:02:48 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep 21 10:02:48 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 21 10:02:48 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 21 10:02:48 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 21 10:02:48 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 21 10:02:48 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 21 10:02:48 node-2 kernel: [    0.000000]   2 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000]   3 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000]   4 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000]   5 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000]   6 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000]   7 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000]   8 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000]   9 disabled
Sep 21 10:02:48 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 21 10:02:48 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 21 10:02:48 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 21 10:02:48 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 21 10:02:48 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 21 10:02:48 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 21 10:02:48 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 21 10:02:48 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 21 10:02:48 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 21 10:02:48 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 21 10:02:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 21 10:02:48 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 21 10:02:48 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 21 10:02:48 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 21 10:02:48 node-2 kernel: [    0.000000] Zone ranges:
Sep 21 10:02:48 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] Movable zone start for each node
Sep 21 10:02:48 node-2 kernel: [    0.000000] Early memory node ranges
Sep 21 10:02:48 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 21 10:02:48 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 21 10:02:48 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 21 10:02:48 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 21 10:02:48 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 21 10:02:48 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 21 10:02:48 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 21 10:02:48 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 21 10:02:48 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 21 10:02:48 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 21 10:02:48 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 21 10:02:48 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 21 10:02:48 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 21 10:02:48 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 21 10:02:48 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 21 10:02:48 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 21 10:02:48 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 21 10:02:48 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 21 10:02:48 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 21 10:02:48 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 21 10:02:48 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 21 10:02:48 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 21 10:02:48 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 21 10:02:48 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 21 10:02:48 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 21 10:02:48 node-2 kernel: [    0.000000] Policy zone: Normal
Sep 21 10:02:48 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=d4d3075f-6393-4f3e-86fd-b8e78855f6ea nomdmonddf nomdmonisw
Sep 21 10:02:48 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 21 10:02:48 node-2 kernel: [    0.000000] Checking aperture...
Sep 21 10:02:48 node-2 kernel: [    0.000000] No AGP bridge found
Sep 21 10:02:48 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 21 10:02:48 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 21 10:02:48 node-2 kernel: [    0.000000] Memory: 32653312K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Sep 21 10:02:48 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 21 10:02:48 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 21 10:02:48 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 21 10:02:48 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 21 10:02:48 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 21 10:02:48 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 21 10:02:48 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 21 10:02:48 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 21 10:02:48 node-2 kernel: [    0.000000] console [tty0] enabled
Sep 21 10:02:48 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 21 10:02:48 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 21 10:02:48 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 21 10:02:48 node-2 kernel: [    0.000000] hpet clockevent registered
Sep 21 10:02:48 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 21 10:02:48 node-2 kernel: [    0.004000] tsc: Detected 3491.636 MHz processor
Sep 21 10:02:48 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.27 BogoMIPS (lpj=13966544)
Sep 21 10:02:48 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 21 10:02:48 node-2 kernel: [    0.000047] Security Framework initialized
Sep 21 10:02:48 node-2 kernel: [    0.000066] AppArmor: AppArmor initialized
Sep 21 10:02:48 node-2 kernel: [    0.000067] Yama: becoming mindful.
Sep 21 10:02:48 node-2 kernel: [    0.001462] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.006345] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.008273] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.008300] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.008588] Initializing cgroup subsys memory
Sep 21 10:02:48 node-2 kernel: [    0.008596] Initializing cgroup subsys devices
Sep 21 10:02:48 node-2 kernel: [    0.008598] Initializing cgroup subsys freezer
Sep 21 10:02:48 node-2 kernel: [    0.008600] Initializing cgroup subsys blkio
Sep 21 10:02:48 node-2 kernel: [    0.008601] Initializing cgroup subsys perf_event
Sep 21 10:02:48 node-2 kernel: [    0.008604] Initializing cgroup subsys hugetlb
Sep 21 10:02:48 node-2 kernel: [    0.008623] CPU: Physical Processor ID: 0
Sep 21 10:02:48 node-2 kernel: [    0.008624] CPU: Processor Core ID: 0
Sep 21 10:02:48 node-2 kernel: [    0.008628] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 21 10:02:48 node-2 kernel: [    0.008628] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 21 10:02:48 node-2 kernel: [    0.009322] mce: CPU supports 22 MCE banks
Sep 21 10:02:48 node-2 kernel: [    0.009350] CPU0: Thermal monitoring enabled (TM1)
Sep 21 10:02:48 node-2 kernel: [    0.009370] process: using mwait in idle threads
Sep 21 10:02:48 node-2 kernel: [    0.009373] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 21 10:02:48 node-2 kernel: [    0.009373] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 21 10:02:48 node-2 kernel: [    0.009373] tlb_flushall_shift: 6
Sep 21 10:02:48 node-2 kernel: [    0.009462] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 21 10:02:48 node-2 kernel: [    0.010185] ACPI: Core revision 20131115
Sep 21 10:02:48 node-2 kernel: [    0.022863] ACPI: All ACPI Tables successfully acquired
Sep 21 10:02:48 node-2 kernel: [    0.023027] ftrace: allocating 28617 entries in 112 pages
Sep 21 10:02:48 node-2 kernel: [    0.032000] dmar: Host address width 46
Sep 21 10:02:48 node-2 kernel: [    0.032002] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 21 10:02:48 node-2 kernel: [    0.032008] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 21 10:02:48 node-2 kernel: [    0.032009] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 21 10:02:48 node-2 kernel: [    0.032013] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 21 10:02:48 node-2 kernel: [    0.032015] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 21 10:02:48 node-2 kernel: [    0.032016] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 21 10:02:48 node-2 kernel: [    0.032017] dmar: ATSR flags: 0x0
Sep 21 10:02:48 node-2 kernel: [    0.032018] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 21 10:02:48 node-2 kernel: [    0.032019] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 21 10:02:48 node-2 kernel: [    0.032134] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 21 10:02:48 node-2 kernel: [    0.032136] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 21 10:02:48 node-2 kernel: [    0.032137] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 21 10:02:48 node-2 kernel: [    0.032138] HPET id 0 under DRHD base 0xc7ffc000
Sep 21 10:02:48 node-2 kernel: [    0.032139] Your BIOS is broken and requested that x2apic be disabled.
Sep 21 10:02:48 node-2 kernel: [    0.032139] This will slightly decrease performance.
Sep 21 10:02:48 node-2 kernel: [    0.032139] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 21 10:02:48 node-2 kernel: [    0.032571] Enabled IRQ remapping in xapic mode
Sep 21 10:02:48 node-2 kernel: [    0.032572] x2apic not enabled, IRQ remapping is in xapic mode
Sep 21 10:02:48 node-2 kernel: [    0.032576] Switched APIC routing to physical flat.
Sep 21 10:02:48 node-2 kernel: [    0.033195] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 21 10:02:48 node-2 kernel: [    0.072841] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 21 10:02:48 node-2 kernel: [    0.072847] TSC deadline timer enabled
Sep 21 10:02:48 node-2 kernel: [    0.072854] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 21 10:02:48 node-2 kernel: [    0.072860] ... version:                3
Sep 21 10:02:48 node-2 kernel: [    0.072861] ... bit width:              48
Sep 21 10:02:48 node-2 kernel: [    0.072862] ... generic registers:      4
Sep 21 10:02:48 node-2 kernel: [    0.072863] ... value mask:             0000ffffffffffff
Sep 21 10:02:48 node-2 kernel: [    0.072864] ... max period:             0000ffffffffffff
Sep 21 10:02:48 node-2 kernel: [    0.072865] ... fixed-purpose events:   3
Sep 21 10:02:48 node-2 kernel: [    0.072866] ... event mask:             000000070000000f
Sep 21 10:02:48 node-2 kernel: [    0.074248] x86: Booting SMP configuration:
Sep 21 10:02:48 node-2 kernel: [    0.088350] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 21 10:02:48 node-2 kernel: [    0.074250] .... node  #0, CPUs:        #1  #2  #3
Sep 21 10:02:48 node-2 kernel: [    0.116257] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 21 10:02:48 node-2 kernel: [    0.270206] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 21 10:02:48 node-2 kernel: [    0.325811] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 21 10:02:48 node-2 kernel: [    0.382459] x86: Booted up 2 nodes, 16 CPUs
Sep 21 10:02:48 node-2 kernel: [    0.382462] smpboot: Total of 16 processors activated (111744.33 BogoMIPS)
Sep 21 10:02:48 node-2 kernel: [    0.405757] devtmpfs: initialized
Sep 21 10:02:48 node-2 kernel: [    0.408868] EVM: security.selinux
Sep 21 10:02:48 node-2 kernel: [    0.408869] EVM: security.SMACK64
Sep 21 10:02:48 node-2 kernel: [    0.408870] EVM: security.ima
Sep 21 10:02:48 node-2 kernel: [    0.408871] EVM: security.capability
Sep 21 10:02:48 node-2 kernel: [    0.408922] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.409609] pinctrl core: initialized pinctrl subsystem
Sep 21 10:02:48 node-2 kernel: [    0.409672] regulator-dummy: no parameters
Sep 21 10:02:48 node-2 kernel: [    0.409704] RTC time: 10:02:12, date: 09/21/16
Sep 21 10:02:48 node-2 kernel: [    0.409738] NET: Registered protocol family 16
Sep 21 10:02:48 node-2 kernel: [    0.409823] cpuidle: using governor ladder
Sep 21 10:02:48 node-2 kernel: [    0.409824] cpuidle: using governor menu
Sep 21 10:02:48 node-2 kernel: [    0.409860] ACPI: bus type PCI registered
Sep 21 10:02:48 node-2 kernel: [    0.409862] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 21 10:02:48 node-2 kernel: [    0.409907] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 21 10:02:48 node-2 kernel: [    0.409910] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 21 10:02:48 node-2 kernel: [    0.423641] PCI: Using configuration type 1 for base access
Sep 21 10:02:48 node-2 kernel: [    0.424647] bio: create slab <bio-0> at 0
Sep 21 10:02:48 node-2 kernel: [    0.424926] ACPI: Added _OSI(Module Device)
Sep 21 10:02:48 node-2 kernel: [    0.424928] ACPI: Added _OSI(Processor Device)
Sep 21 10:02:48 node-2 kernel: [    0.424929] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 21 10:02:48 node-2 kernel: [    0.424930] ACPI: Added _OSI(Processor Aggregator Device)
Sep 21 10:02:48 node-2 kernel: [    0.437589] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 21 10:02:48 node-2 kernel: [    0.448256] ACPI: Interpreter enabled
Sep 21 10:02:48 node-2 kernel: [    0.448262] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 21 10:02:48 node-2 kernel: [    0.448266] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 21 10:02:48 node-2 kernel: [    0.448268] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 21 10:02:48 node-2 kernel: [    0.448275] ACPI: (supports S0 S4 S5)
Sep 21 10:02:48 node-2 kernel: [    0.448277] ACPI: Using IOAPIC for interrupt routing
Sep 21 10:02:48 node-2 kernel: [    0.448318] HEST: Table parsing has been initialized.
Sep 21 10:02:48 node-2 kernel: [    0.448321] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 21 10:02:48 node-2 kernel: [    0.448876] ACPI: No dock devices found.
Sep 21 10:02:48 node-2 kernel: [    0.460543] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 21 10:02:48 node-2 kernel: [    0.460548] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 10:02:48 node-2 kernel: [    0.460551] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 21 10:02:48 node-2 kernel: [    0.460576] PCI host bridge to bus 0000:ff
Sep 21 10:02:48 node-2 kernel: [    0.460579] pci_bus 0000:ff: root bus resource [bus ff]
Sep 21 10:02:48 node-2 kernel: [    0.460587] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 21 10:02:48 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 21 10:02:48 node-2 kernel: [    0.460625] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.460655] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460689] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460718] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.460747] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.460777] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460805] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460835] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460862] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460888] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460914] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460942] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460968] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.460994] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461020] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461048] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461075] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461101] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.461130] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461156] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.461181] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461207] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461236] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.461271] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461305] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461335] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461367] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461400] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461433] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461466] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461499] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461530] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461561] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461591] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461624] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461658] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461689] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461716] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461747] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461780] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461820] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461856] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461889] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461918] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461949] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.461982] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462013] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462044] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462074] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462106] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462136] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462166] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462196] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462226] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462258] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462290] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462348] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 21 10:02:48 node-2 kernel: [    0.462350] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 10:02:48 node-2 kernel: [    0.462353] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 21 10:02:48 node-2 kernel: [    0.462374] PCI host bridge to bus 0000:7f
Sep 21 10:02:48 node-2 kernel: [    0.462376] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 21 10:02:48 node-2 kernel: [    0.462381] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462411] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.462440] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462471] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462493] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.462518] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.462545] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462572] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462594] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462617] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462640] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462662] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462686] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462709] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462732] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462758] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462780] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462803] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462826] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.462850] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462872] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.462894] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462917] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.462943] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 21 10:02:48 node-2 kernel: [    0.462977] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463004] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463032] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463060] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463086] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463113] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463139] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463167] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463194] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463222] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463253] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463282] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463310] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463335] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463360] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463388] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463414] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463441] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463469] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463498] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463525] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463551] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463576] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463606] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463634] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463661] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463692] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463719] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463742] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463769] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463795] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463826] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.463852] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.465105] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 21 10:02:48 node-2 kernel: [    0.465108] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 10:02:48 node-2 kernel: [    0.466235] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 21 10:02:48 node-2 kernel: [    0.466746] PCI host bridge to bus 0000:00
Sep 21 10:02:48 node-2 kernel: [    0.466749] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 21 10:02:48 node-2 kernel: [    0.466750] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 21 10:02:48 node-2 kernel: [    0.466752] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 21 10:02:48 node-2 kernel: [    0.466753] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 21 10:02:48 node-2 kernel: [    0.466754] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 21 10:02:48 node-2 kernel: [    0.466756] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 21 10:02:48 node-2 kernel: [    0.466757] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 21 10:02:48 node-2 kernel: [    0.466763] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 21 10:02:48 node-2 kernel: [    0.466846] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.466877] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.466918] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 21 10:02:48 node-2 kernel: [    0.466937] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.466966] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.467007] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 21 10:02:48 node-2 kernel: [    0.467025] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.467055] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.467095] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 21 10:02:48 node-2 kernel: [    0.467111] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.467181] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.467258] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.467333] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 21 10:02:48 node-2 kernel: [    0.467338] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 21 10:02:48 node-2 kernel: [    0.467422] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 21 10:02:48 node-2 kernel: [    0.467571] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 21 10:02:48 node-2 kernel: [    0.467588] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 21 10:02:48 node-2 kernel: [    0.467666] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.467719] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 21 10:02:48 node-2 kernel: [    0.467741] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.467797] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.467840] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 21 10:02:48 node-2 kernel: [    0.467868] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.467924] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.467967] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 21 10:02:48 node-2 kernel: [    0.467992] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 21 10:02:48 node-2 kernel: [    0.468010] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 21 10:02:48 node-2 kernel: [    0.468087] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.468137] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 21 10:02:48 node-2 kernel: [    0.468164] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 21 10:02:48 node-2 kernel: [    0.468416] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 21 10:02:48 node-2 kernel: [    0.468422] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 21 10:02:48 node-2 kernel: [    0.468428] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.468434] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.468441] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 21 10:02:48 node-2 kernel: [    0.468471] pci 0000:01:00.0: supports D1 D2
Sep 21 10:02:48 node-2 kernel: [    0.474384] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 21 10:02:48 node-2 kernel: [    0.474390] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 21 10:02:48 node-2 kernel: [    0.474394] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 21 10:02:48 node-2 kernel: [    0.474591] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.474625] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 21 10:02:48 node-2 kernel: [    0.482379] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 21 10:02:48 node-2 kernel: [    0.482381] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.482383] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 10:02:48 node-2 kernel: [    0.482438] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.482505] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.482582] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.482627] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 21 10:02:48 node-2 kernel: [    0.482631] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.482632] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 10:02:48 node-2 kernel: [    0.482686] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.482808] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.482862] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 21 10:02:48 node-2 kernel: [    0.482864] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.482866] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.482916] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.483036] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.483078] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.483197] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.483234] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.483356] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.483392] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 21 10:02:48 node-2 kernel: [    0.483540] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 21 10:02:48 node-2 kernel: [    0.483582] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 21 10:02:48 node-2 kernel: [    0.483585] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.483587] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.483652] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 21 10:02:48 node-2 kernel: [    0.483717] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.483768] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.483809] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 21 10:02:48 node-2 kernel: [    0.483892] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 21 10:02:48 node-2 kernel: [    0.484004] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 21 10:02:48 node-2 kernel: [    0.484006] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.484008] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.484068] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 21 10:02:48 node-2 kernel: [    0.484124] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.484172] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.484393] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 21 10:02:48 node-2 kernel: [    0.484397] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 21 10:02:48 node-2 kernel: [    0.484479] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 21 10:02:48 node-2 kernel: [    0.484536] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.484584] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.484794] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 21 10:02:48 node-2 kernel: [    0.484797] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 21 10:02:48 node-2 kernel: [    0.484856] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 21 10:02:48 node-2 kernel: [    0.484916] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.484970] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 21 10:02:48 node-2 kernel: [    0.485190] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 21 10:02:48 node-2 kernel: [    0.485200] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 21 10:02:48 node-2 kernel: [    0.485375] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 21 10:02:48 node-2 kernel: [    0.485413] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 21 10:02:48 node-2 kernel: [    0.485492] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 21 10:02:48 node-2 kernel: [    0.485511] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 21 10:02:48 node-2 kernel: [    0.485524] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 21 10:02:48 node-2 kernel: [    0.485537] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 21 10:02:48 node-2 kernel: [    0.485587] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 21 10:02:48 node-2 kernel: [    0.490400] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 21 10:02:48 node-2 kernel: [    0.490405] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 21 10:02:48 node-2 kernel: [    0.490436] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 21 10:02:48 node-2 kernel: [    0.490929] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 21 10:02:48 node-2 kernel: [    0.490932] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 10:02:48 node-2 kernel: [    0.491051] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 21 10:02:48 node-2 kernel: [    0.491160] PCI host bridge to bus 0000:80
Sep 21 10:02:48 node-2 kernel: [    0.491162] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 21 10:02:48 node-2 kernel: [    0.491164] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 21 10:02:48 node-2 kernel: [    0.491165] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 21 10:02:48 node-2 kernel: [    0.491173] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.491238] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.491306] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 21 10:02:48 node-2 kernel: [    0.491368] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 21 10:02:48 node-2 kernel: [    0.491374] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 21 10:02:48 node-2 kernel: [    0.491448] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 21 10:02:48 node-2 kernel: [    0.491746] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 21 10:02:48 node-2 kernel: [    0.491778] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 21 10:02:48 node-2 kernel: [    0.491807] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 21 10:02:48 node-2 kernel: [    0.491837] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 10:02:48 node-2 kernel: [    0.491866] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 10:02:48 node-2 kernel: [    0.491897] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 10:02:48 node-2 kernel: [    0.491926] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 10:02:48 node-2 kernel: [    0.491956] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 10:02:48 node-2 kernel: [    0.492041] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 21 10:02:48 node-2 kernel: [    0.492046] ACPI: \_SB_.UNC1: notify handler is installed
Sep 21 10:02:48 node-2 kernel: [    0.492047] ACPI: \_SB_.UNC0: notify handler is installed
Sep 21 10:02:48 node-2 kernel: [    0.492062] ACPI: \_SB_.PCI0: notify handler is installed
Sep 21 10:02:48 node-2 kernel: [    0.492115] ACPI: \_SB_.PCI1: notify handler is installed
Sep 21 10:02:48 node-2 kernel: [    0.492194] Found 4 acpi root devices
Sep 21 10:02:48 node-2 kernel: [    0.492304] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 21 10:02:48 node-2 kernel: [    0.492306] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 21 10:02:48 node-2 kernel: [    0.492307] vgaarb: loaded
Sep 21 10:02:48 node-2 kernel: [    0.492308] vgaarb: bridge control possible 0000:0c:00.0
Sep 21 10:02:48 node-2 kernel: [    0.492426] SCSI subsystem initialized
Sep 21 10:02:48 node-2 kernel: [    0.492491] libata version 3.00 loaded.
Sep 21 10:02:48 node-2 kernel: [    0.492506] ACPI: bus type USB registered
Sep 21 10:02:48 node-2 kernel: [    0.492516] usbcore: registered new interface driver usbfs
Sep 21 10:02:48 node-2 kernel: [    0.492521] usbcore: registered new interface driver hub
Sep 21 10:02:48 node-2 kernel: [    0.492545] usbcore: registered new device driver usb
Sep 21 10:02:48 node-2 kernel: [    0.492716] PCI: Using ACPI for IRQ routing
Sep 21 10:02:48 node-2 kernel: [    0.496325] PCI: pci_cache_line_size set to 64 bytes
Sep 21 10:02:48 node-2 kernel: [    0.496543] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 21 10:02:48 node-2 kernel: [    0.496544] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 21 10:02:48 node-2 kernel: [    0.496545] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 21 10:02:48 node-2 kernel: [    0.496608] NetLabel: Initializing
Sep 21 10:02:48 node-2 kernel: [    0.496610] NetLabel:  domain hash size = 128
Sep 21 10:02:48 node-2 kernel: [    0.496611] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 21 10:02:48 node-2 kernel: [    0.496620] NetLabel:  unlabeled traffic allowed by default
Sep 21 10:02:48 node-2 kernel: [    0.496678] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 21 10:02:48 node-2 kernel: [    0.496682] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 21 10:02:48 node-2 kernel: [    0.498751] Switched to clocksource hpet
Sep 21 10:02:48 node-2 kernel: [    0.503202] AppArmor: AppArmor Filesystem Enabled
Sep 21 10:02:48 node-2 kernel: [    0.503240] pnp: PnP ACPI init
Sep 21 10:02:48 node-2 kernel: [    0.503252] ACPI: bus type PNP registered
Sep 21 10:02:48 node-2 kernel: [    0.503432] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503443] pnp 00:01: [dma 4]
Sep 21 10:02:48 node-2 kernel: [    0.503462] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503497] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503522] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503543] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503589] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503702] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503705] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 21 10:02:48 node-2 kernel: [    0.503706] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503708] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503709] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503711] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503714] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 21 10:02:48 node-2 kernel: [    0.503716] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503717] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503719] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503720] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503722] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503723] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 21 10:02:48 node-2 kernel: [    0.503726] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503826] pnp 00:07: [dma 0 disabled]
Sep 21 10:02:48 node-2 kernel: [    0.503859] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 21 10:02:48 node-2 kernel: [    0.503941] pnp 00:08: [dma 0 disabled]
Sep 21 10:02:48 node-2 kernel: [    0.503977] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 21 10:02:48 node-2 kernel: [    0.504036] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 21 10:02:48 node-2 kernel: [    0.504484] pnp: PnP ACPI: found 10 devices
Sep 21 10:02:48 node-2 kernel: [    0.504486] ACPI: bus type PNP unregistered
Sep 21 10:02:48 node-2 kernel: [    0.510490] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 21 10:02:48 node-2 kernel: [    0.510493] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 21 10:02:48 node-2 kernel: [    0.510496] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 21 10:02:48 node-2 kernel: [    0.510501] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 21 10:02:48 node-2 kernel: [    0.510503] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510518] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510547] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 21 10:02:48 node-2 kernel: [    0.510562] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510590] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 21 10:02:48 node-2 kernel: [    0.510605] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 21 10:02:48 node-2 kernel: [    0.510637] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 21 10:02:48 node-2 kernel: [    0.510651] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 21 10:02:48 node-2 kernel: [    0.510681] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 21 10:02:48 node-2 kernel: [    0.510683] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510697] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510731] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 21 10:02:48 node-2 kernel: [    0.510733] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510747] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510776] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 21 10:02:48 node-2 kernel: [    0.510778] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510781] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510786] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 21 10:02:48 node-2 kernel: [    0.510788] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510790] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510795] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 21 10:02:48 node-2 kernel: [    0.510801] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 21 10:02:48 node-2 kernel: [    0.510810] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 21 10:02:48 node-2 kernel: [    0.510813] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 21 10:02:48 node-2 kernel: [    0.510820] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 21 10:02:48 node-2 kernel: [    0.510821] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 21 10:02:48 node-2 kernel: [    0.510822] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 21 10:02:48 node-2 kernel: [    0.510823] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 21 10:02:48 node-2 kernel: [    0.510824] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 21 10:02:48 node-2 kernel: [    0.510825] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 21 10:02:48 node-2 kernel: [    0.510826] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 21 10:02:48 node-2 kernel: [    0.510827] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 21 10:02:48 node-2 kernel: [    0.510828] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510829] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510830] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510831] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510832] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510833] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510834] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510835] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510836] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 21 10:02:48 node-2 kernel: [    0.510837] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510838] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 21 10:02:48 node-2 kernel: [    0.510839] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 21 10:02:48 node-2 kernel: [    0.510841] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 21 10:02:48 node-2 kernel: [    0.510842] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 21 10:02:48 node-2 kernel: [    0.510844] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 21 10:02:48 node-2 kernel: [    0.510845] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 21 10:02:48 node-2 kernel: [    0.510885] NET: Registered protocol family 2
Sep 21 10:02:48 node-2 kernel: [    0.511185] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.511555] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.511722] TCP: Hash tables configured (established 262144 bind 65536)
Sep 21 10:02:48 node-2 kernel: [    0.511767] TCP: reno registered
Sep 21 10:02:48 node-2 kernel: [    0.511803] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.511909] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.512091] NET: Registered protocol family 1
Sep 21 10:02:48 node-2 kernel: [    0.546847] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 21 10:02:48 node-2 kernel: [    0.546863] PCI: CLS 64 bytes, default 64
Sep 21 10:02:48 node-2 kernel: [    0.546948] Trying to unpack rootfs image as initramfs...
Sep 21 10:02:48 node-2 kernel: [    0.769421] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Sep 21 10:02:48 node-2 kernel: [    0.769453] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 21 10:02:48 node-2 kernel: [    0.769456] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 21 10:02:48 node-2 kernel: [    0.769888] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769903] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769917] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769942] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769949] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769956] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769962] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769969] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769976] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769984] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.769994] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.770001] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.770009] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.770016] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.770022] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.770028] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 10:02:48 node-2 kernel: [    0.770075] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 21 10:02:48 node-2 kernel: [    0.770078] Scanning for low memory corruption every 60 seconds
Sep 21 10:02:48 node-2 kernel: [    0.770392] Initialise system trusted keyring
Sep 21 10:02:48 node-2 kernel: [    0.770439] audit: initializing netlink socket (disabled)
Sep 21 10:02:48 node-2 kernel: [    0.770449] type=2000 audit(1474452131.720:1): initialized
Sep 21 10:02:48 node-2 kernel: [    0.788324] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 21 10:02:48 node-2 kernel: [    0.789794] zbud: loaded
Sep 21 10:02:48 node-2 kernel: [    0.789915] VFS: Disk quotas dquot_6.5.2
Sep 21 10:02:48 node-2 kernel: [    0.789953] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 21 10:02:48 node-2 kernel: [    0.790306] fuse init (API version 7.22)
Sep 21 10:02:48 node-2 kernel: [    0.790361] msgmni has been set to 32768
Sep 21 10:02:48 node-2 kernel: [    0.790408] Key type big_key registered
Sep 21 10:02:48 node-2 kernel: [    0.790965] Key type asymmetric registered
Sep 21 10:02:48 node-2 kernel: [    0.790967] Asymmetric key parser 'x509' registered
Sep 21 10:02:48 node-2 kernel: [    0.790990] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 21 10:02:48 node-2 kernel: [    0.791053] io scheduler noop registered
Sep 21 10:02:48 node-2 kernel: [    0.791055] io scheduler deadline registered (default)
Sep 21 10:02:48 node-2 kernel: [    0.791074] io scheduler cfq registered
Sep 21 10:02:48 node-2 kernel: [    0.791555] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    0.791735] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    0.791858] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    0.791970] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    0.792105] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    0.792190] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    0.792642] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 21 10:02:48 node-2 kernel: [    0.792682] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 21 10:02:48 node-2 kernel: [    0.792708] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 21 10:02:48 node-2 kernel: [    0.792731] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792735] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792741] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 21 10:02:48 node-2 kernel: [    0.792752] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792755] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792759] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792763] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792779] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792780] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792781] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792783] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792784] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792786] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792787] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792788] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792791] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 21 10:02:48 node-2 kernel: [    0.792801] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792803] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 21 10:02:48 node-2 kernel: [    0.792814] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792818] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 21 10:02:48 node-2 kernel: [    0.792828] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792829] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 21 10:02:48 node-2 kernel: [    0.792832] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 21 10:02:48 node-2 kernel: [    0.792859] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 21 10:02:48 node-2 kernel: [    0.792864] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 21 10:02:48 node-2 kernel: [    0.792868] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 21 10:02:48 node-2 kernel: [    0.792877] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 21 10:02:48 node-2 kernel: [    0.792914] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 21 10:02:48 node-2 kernel: [    0.792916] vesafb: scrolling: redraw
Sep 21 10:02:48 node-2 kernel: [    0.792917] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 21 10:02:48 node-2 kernel: [    0.813208] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 21 10:02:48 node-2 kernel: [    0.821707] Console: switching to colour frame buffer device 80x30
Sep 21 10:02:48 node-2 kernel: [    0.830367] fb0: VESA VGA frame buffer device
Sep 21 10:02:48 node-2 kernel: [    0.830579] intel_idle: MWAIT substates: 0x2120
Sep 21 10:02:48 node-2 kernel: [    0.830580] intel_idle: v0.4 model 0x3F
Sep 21 10:02:48 node-2 kernel: [    0.830581] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 21 10:02:48 node-2 kernel: [    0.830813] ipmi message handler version 39.2
Sep 21 10:02:48 node-2 kernel: [    0.831089] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 21 10:02:48 node-2 kernel: [    0.831522] ACPI: AC Adapter [P111] (on-line)
Sep 21 10:02:48 node-2 kernel: [    0.836770] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 21 10:02:48 node-2 kernel: [    0.847794] ACPI: Power Button [PWRB]
Sep 21 10:02:48 node-2 kernel: [    0.853561] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 21 10:02:48 node-2 kernel: [    0.865180] ACPI: Power Button [PWRF]
Sep 21 10:02:48 node-2 kernel: [    0.884319] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 21 10:02:48 node-2 kernel: [    0.895982] pstore: Registered erst as persistent store backend
Sep 21 10:02:48 node-2 kernel: [    0.902176] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 21 10:02:48 node-2 kernel: [    0.914116] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 21 10:02:48 node-2 kernel: [    0.940870] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 21 10:02:48 node-2 kernel: [    0.974155] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 21 10:02:48 node-2 kernel: [    0.988226] Linux agpgart interface v0.103
Sep 21 10:02:48 node-2 kernel: [    0.995852] brd: module loaded
Sep 21 10:02:48 node-2 kernel: [    1.002889] loop: module loaded
Sep 21 10:02:48 node-2 kernel: [    1.009626] libphy: Fixed MDIO Bus: probed
Sep 21 10:02:48 node-2 kernel: [    1.016097] tun: Universal TUN/TAP device driver, 1.6
Sep 21 10:02:48 node-2 kernel: [    1.022581] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 21 10:02:48 node-2 kernel: [    1.029117] PPP generic driver version 2.4.2
Sep 21 10:02:48 node-2 kernel: [    1.035505] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 21 10:02:48 node-2 kernel: [    1.041949] ehci-pci: EHCI PCI platform driver
Sep 21 10:02:48 node-2 kernel: [    1.048494] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 21 10:02:48 node-2 kernel: [    1.054922] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 21 10:02:48 node-2 kernel: [    1.067481] ehci-pci 0000:00:1a.0: debug port 2
Sep 21 10:02:48 node-2 kernel: [    1.077719] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 21 10:02:48 node-2 kernel: [    1.077737] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 21 10:02:48 node-2 kernel: [    1.094237] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 21 10:02:48 node-2 kernel: [    1.100338] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 21 10:02:48 node-2 kernel: [    1.106522] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 21 10:02:48 node-2 kernel: [    1.118490] usb usb1: Product: EHCI Host Controller
Sep 21 10:02:48 node-2 kernel: [    1.124566] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 21 10:02:48 node-2 kernel: [    1.130679] usb usb1: SerialNumber: 0000:00:1a.0
Sep 21 10:02:48 node-2 kernel: [    1.136656] hub 1-0:1.0: USB hub found
Sep 21 10:02:48 node-2 kernel: [    1.142447] hub 1-0:1.0: 2 ports detected
Sep 21 10:02:48 node-2 kernel: [    1.148244] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 21 10:02:48 node-2 kernel: [    1.153847] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 21 10:02:48 node-2 kernel: [    1.164749] ehci-pci 0000:00:1d.0: debug port 2
Sep 21 10:02:48 node-2 kernel: [    1.174070] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 21 10:02:48 node-2 kernel: [    1.174073] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 21 10:02:48 node-2 kernel: [    1.190155] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 21 10:02:48 node-2 kernel: [    1.195362] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 21 10:02:48 node-2 kernel: [    1.200661] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 21 10:02:48 node-2 kernel: [    1.211236] usb usb2: Product: EHCI Host Controller
Sep 21 10:02:48 node-2 kernel: [    1.216702] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 21 10:02:48 node-2 kernel: [    1.222237] usb usb2: SerialNumber: 0000:00:1d.0
Sep 21 10:02:48 node-2 kernel: [    1.227779] hub 2-0:1.0: USB hub found
Sep 21 10:02:48 node-2 kernel: [    1.233128] hub 2-0:1.0: 2 ports detected
Sep 21 10:02:48 node-2 kernel: [    1.238428] ehci-platform: EHCI generic platform driver
Sep 21 10:02:48 node-2 kernel: [    1.243643] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 21 10:02:48 node-2 kernel: [    1.248949] ohci-pci: OHCI PCI platform driver
Sep 21 10:02:48 node-2 kernel: [    1.254232] ohci-platform: OHCI generic platform driver
Sep 21 10:02:48 node-2 kernel: [    1.259421] uhci_hcd: USB Universal Host Controller Interface driver
Sep 21 10:02:48 node-2 kernel: [    1.264746] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 21 10:02:48 node-2 kernel: [    1.461922] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 21 10:02:48 node-2 kernel: [    1.634148] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 21 10:02:48 node-2 kernel: [    1.639689] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 21 10:02:48 node-2 kernel: [    1.645546] hub 1-1:1.0: USB hub found
Sep 21 10:02:48 node-2 kernel: [    1.651007] hub 1-1:1.0: 6 ports detected
Sep 21 10:02:48 node-2 kernel: [    1.765667] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 21 10:02:48 node-2 kernel: [    1.765689] tsc: Refined TSC clocksource calibration: 3491.891 MHz
Sep 21 10:02:48 node-2 kernel: [    2.033808] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 21 10:02:48 node-2 kernel: [    2.039335] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 21 10:02:48 node-2 kernel: [    2.045202] hub 2-1:1.0: USB hub found
Sep 21 10:02:48 node-2 kernel: [    2.050919] hub 2-1:1.0: 8 ports detected
Sep 21 10:02:48 node-2 kernel: [    2.306168] i8042: No controller found
Sep 21 10:02:48 node-2 kernel: [    2.311574] mousedev: PS/2 mouse device common for all mice
Sep 21 10:02:48 node-2 kernel: [    2.317088] rtc_cmos 00:02: RTC can wake from S4
Sep 21 10:02:48 node-2 kernel: [    2.322670] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 21 10:02:48 node-2 kernel: [    2.328300] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 21 10:02:48 node-2 kernel: [    2.329253] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 21 10:02:48 node-2 kernel: [    2.344967] device-mapper: uevent: version 1.0.3
Sep 21 10:02:48 node-2 kernel: [    2.350631] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 21 10:02:48 node-2 kernel: [    2.361894] ledtrig-cpu: registered to indicate activity on CPUs
Sep 21 10:02:48 node-2 kernel: [    2.367834] TCP: cubic registered
Sep 21 10:02:48 node-2 kernel: [    2.373740] NET: Registered protocol family 10
Sep 21 10:02:48 node-2 kernel: [    2.379728] NET: Registered protocol family 17
Sep 21 10:02:48 node-2 kernel: [    2.385428] Key type dns_resolver registered
Sep 21 10:02:48 node-2 kernel: [    2.391424] Loading compiled-in X.509 certificates
Sep 21 10:02:48 node-2 kernel: [    2.397593] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 21 10:02:48 node-2 kernel: [    2.408977] registered taskstats version 1
Sep 21 10:02:48 node-2 kernel: [    2.416889] Key type trusted registered
Sep 21 10:02:48 node-2 kernel: [    2.424730] Key type encrypted registered
Sep 21 10:02:48 node-2 kernel: [    2.430183] AppArmor: AppArmor sha1 policy hashing enabled
Sep 21 10:02:48 node-2 kernel: [    2.435667] IMA: No TPM chip found, activating TPM-bypass!
Sep 21 10:02:48 node-2 kernel: [    2.441796] regulator-dummy: disabling
Sep 21 10:02:48 node-2 kernel: [    2.447356]   Magic number: 0:617:22
Sep 21 10:02:48 node-2 kernel: [    2.452785] pci 0000:ff:15.2: hash matches
Sep 21 10:02:48 node-2 kernel: [    2.458246] memory memory62: hash matches
Sep 21 10:02:48 node-2 kernel: [    2.463593] rtc_cmos 00:02: setting system clock to 2016-09-21 10:02:14 UTC (1474452134)
Sep 21 10:02:48 node-2 kernel: [    2.474179] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 21 10:02:48 node-2 kernel: [    2.474182] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 21 10:02:48 node-2 kernel: [    2.474183] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 21 10:02:48 node-2 kernel: [    2.474185] usb 2-1.4: Manufacturer: Avocent
Sep 21 10:02:48 node-2 kernel: [    2.474187] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 21 10:02:48 node-2 kernel: [    2.509990] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 21 10:02:48 node-2 kernel: [    2.515570] EDD information not available.
Sep 21 10:02:48 node-2 kernel: [    2.521061] PM: Hibernation image not present or could not be loaded.
Sep 21 10:02:48 node-2 kernel: [    2.521922] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 21 10:02:48 node-2 kernel: [    2.532953] Write protecting the kernel read-only data: 12288k
Sep 21 10:02:48 node-2 kernel: [    2.538993] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 21 10:02:48 node-2 kernel: [    2.551281] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 21 10:02:48 node-2 kernel: [    2.583789] device-mapper: multipath: version 1.6.0 loaded
Sep 21 10:02:48 node-2 kernel: [    2.591834] systemd-udevd[216]: starting version 204
Sep 21 10:02:48 node-2 kernel: [    2.612053] md: linear personality registered for level -1
Sep 21 10:02:48 node-2 kernel: [    2.626629] md: multipath personality registered for level -4
Sep 21 10:02:48 node-2 kernel: [    2.634566] md: raid0 personality registered for level 0
Sep 21 10:02:48 node-2 kernel: [    2.642740] md: raid1 personality registered for level 1
Sep 21 10:02:48 node-2 kernel: [    2.651183] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 21 10:02:48 node-2 kernel: [    2.657477] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 21 10:02:48 node-2 kernel: [    2.663849] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 21 10:02:48 node-2 kernel: [    2.663861] hidraw: raw HID events driver (C) Jiri Kosina
Sep 21 10:02:48 node-2 kernel: [    2.664313] megasas: FW now in Ready state
Sep 21 10:02:48 node-2 kernel: [    2.664371] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664408] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664441] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664478] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664510] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664549] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664582] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664616] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664651] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664689] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664723] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664760] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664793] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664829] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664864] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.664989] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.665161] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 21 10:02:48 node-2 kernel: [    2.698312] usbcore: registered new interface driver usbhid
Sep 21 10:02:48 node-2 kernel: [    2.704689] usbhid: USB HID core driver
Sep 21 10:02:48 node-2 kernel: [    2.705477] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 21 10:02:48 node-2 kernel: [    2.705486] 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 21 10:02:48 node-2 kernel: [    2.705494] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 21 10:02:48 node-2 kernel: [    2.706257] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.706387] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.706783] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.706923] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.707143] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.717638] raid6: sse2x1    6673 MB/s
Sep 21 10:02:48 node-2 kernel: [    2.727483] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 21 10:02:48 node-2 kernel: [    2.727519] 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 21 10:02:48 node-2 kernel: [    2.727536] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 21 10:02:48 node-2 kernel: [    2.727958] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.728101] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.728253] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.728445] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.728566] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.728696] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.729274] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.748631] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 21 10:02:48 node-2 kernel: [    2.748639] 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 21 10:02:48 node-2 kernel: [    2.748641] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 21 10:02:48 node-2 kernel: [    2.749318] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.749471] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.749598] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.749702] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.749987] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 21 10:02:48 node-2 kernel: [    2.785133] raid6: sse2x2     539 MB/s
Sep 21 10:02:48 node-2 kernel: [    2.852954] raid6: sse2x4    1437 MB/s
Sep 21 10:02:48 node-2 kernel: [    2.920702] raid6: avx2x1   12422 MB/s
Sep 21 10:02:48 node-2 kernel: [    2.992644] raid6: avx2x2   18908 MB/s
Sep 21 10:02:48 node-2 kernel: [    3.064578] raid6: avx2x4   20730 MB/s
Sep 21 10:02:48 node-2 kernel: [    3.070523] raid6: using algorithm avx2x4 (20730 MB/s)
Sep 21 10:02:48 node-2 kernel: [    3.076459] raid6: using avx2x2 recovery algorithm
Sep 21 10:02:48 node-2 kernel: [    3.082320] Switched to clocksource tsc
Sep 21 10:02:48 node-2 kernel: [    3.082321] megasas:IOC Init cmd success
Sep 21 10:02:48 node-2 kernel: [    3.091297] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 21 10:02:48 node-2 kernel: [    3.091298] 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 21 10:02:48 node-2 kernel: [    3.091299] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 21 10:02:48 node-2 kernel: [    3.091361] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    3.091407] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    3.091444] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    3.091480] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 21 10:02:48 node-2 kernel: [    3.091590] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 21 10:02:48 node-2 kernel: [    3.104558] megasas: INIT adapter done
Sep 21 10:02:48 node-2 kernel: [    3.139310] xor: automatically using best checksumming function:
Sep 21 10:02:48 node-2 kernel: [    3.145086] 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 21 10:02:48 node-2 kernel: [    3.156365] 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 21 10:02:48 node-2 kernel: [    3.168161] 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 21 10:02:48 node-2 kernel: [    3.176464] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 21 10:02:48 node-2 kernel: [    3.176831] scsi0 : LSI SAS based MegaRAID driver
Sep 21 10:02:48 node-2 kernel: [    3.184152] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 21 10:02:48 node-2 kernel: [    3.184454]    avx       : 35762.000 MB/sec
Sep 21 10:02:48 node-2 kernel: [    3.195056] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 21 10:02:48 node-2 kernel: [    3.199460] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 21 10:02:48 node-2 kernel: [    3.199575] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 21 10:02:48 node-2 kernel: [    3.199893] sd 0:2:0:0: [sda] Write Protect is off
Sep 21 10:02:48 node-2 kernel: [    3.199894] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 21 10:02:48 node-2 kernel: [    3.199958] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 21 10:02:48 node-2 kernel: [    3.225780]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 21 10:02:48 node-2 kernel: [    3.227409] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 21 10:02:48 node-2 kernel: [    3.272109] 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 21 10:02:48 node-2 kernel: [    3.285611] async_tx: api initialized (async)
Sep 21 10:02:48 node-2 kernel: [    3.285642] 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 21 10:02:48 node-2 kernel: [    3.285697] 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 21 10:02:48 node-2 kernel: [    3.323722] md: raid6 personality registered for level 6
Sep 21 10:02:48 node-2 kernel: [    3.330834] md: raid5 personality registered for level 5
Sep 21 10:02:48 node-2 kernel: [    3.337824] md: raid4 personality registered for level 4
Sep 21 10:02:48 node-2 kernel: [    3.347466] md: raid10 personality registered for level 10
Sep 21 10:02:48 node-2 kernel: [    3.401190] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Sep 21 10:02:48 node-2 kernel: [    3.432587] random: lvm urandom read with 30 bits of entropy available
Sep 21 10:02:48 node-2 kernel: [    3.604334] bio: create slab <bio-1> at 1
Sep 21 10:02:48 node-2 kernel: [    4.418428] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 21 10:02:48 node-2 kernel: [    4.957187] init: plymouth-upstart-bridge main process (553) terminated with status 1
Sep 21 10:02:48 node-2 kernel: [    4.970001] init: plymouth-upstart-bridge main process ended, respawning
Sep 21 10:02:48 node-2 kernel: [    5.090285] random: nonblocking pool is initialized
Sep 21 10:02:48 node-2 kernel: [    5.123769] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 21 10:02:48 node-2 kernel: [    5.148744] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 21 10:02:48 node-2 kernel: [    5.319321] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 21 10:02:48 node-2 kernel: [    5.373214] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 21 10:02:48 node-2 kernel: [    5.461360] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 21 10:02:48 node-2 kernel: [    5.698911] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 21 10:02:48 node-2 kernel: [    5.742419] XFS (dm-0): Mounting Filesystem
Sep 21 10:02:48 node-2 kernel: [    6.032436] XFS (dm-0): Ending clean mount
Sep 21 10:02:48 node-2 kernel: [    6.075892] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 21 10:02:48 node-2 kernel: [    6.110395] XFS (dm-1): Mounting Filesystem
Sep 21 10:02:48 node-2 kernel: [    6.244876] XFS (dm-1): Ending clean mount
Sep 21 10:02:48 node-2 kernel: [    7.954472] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 21 10:02:48 node-2 kernel: [    7.982971] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 21 10:02:48 node-2 kernel: [    8.159764] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 21 10:02:48 node-2 kernel: [    8.159776] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 21 10:02:48 node-2 kernel: [    8.159785] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 21 10:02:48 node-2 kernel: [    8.159803] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 21 10:02:48 node-2 kernel: [    8.188097] systemd-udevd[780]: starting version 204
Sep 21 10:02:48 node-2 kernel: [    8.353307] power_meter ACPI000D:00: Found ACPI power meter.
Sep 21 10:02:48 node-2 kernel: [    8.353317] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 21 10:02:48 node-2 kernel: [    8.383706] wmi: Mapper loaded
Sep 21 10:02:48 node-2 kernel: [    8.397223] IPMI System Interface driver.
Sep 21 10:02:48 node-2 kernel: [    8.397275] ipmi_si: probing via ACPI
Sep 21 10:02:48 node-2 kernel: [    8.397293] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 21 10:02:48 node-2 kernel: [    8.397294] ipmi_si: Adding ACPI-specified kcs state machine
Sep 21 10:02:48 node-2 kernel: [    8.397303] ipmi_si: probing via SMBIOS
Sep 21 10:02:48 node-2 kernel: [    8.397304] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 21 10:02:48 node-2 kernel: [    8.397305] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 21 10:02:48 node-2 kernel: [    8.397306] ipmi_si: probing via SPMI
Sep 21 10:02:48 node-2 kernel: [    8.397307] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 21 10:02:48 node-2 kernel: [    8.397307] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 21 10:02:48 node-2 kernel: [    8.397308] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 21 10:02:48 node-2 kernel: [    8.417371] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 21 10:02:48 node-2 kernel: [    8.435778] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 21 10:02:48 node-2 kernel: [    8.435784] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 21 10:02:48 node-2 kernel: [    8.435787] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 21 10:02:48 node-2 kernel: [    8.435790] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 21 10:02:48 node-2 kernel: [    8.435810] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 21 10:02:48 node-2 kernel: [    8.484412] systemd-udevd[825]: renamed network interface eth1 to enp7s0
Sep 21 10:02:48 node-2 kernel: [    8.508819] systemd-udevd[822]: renamed network interface eth3 to enp9s0
Sep 21 10:02:48 node-2 kernel: [    8.532266] systemd-udevd[798]: renamed network interface eth2 to enp8s0
Sep 21 10:02:48 node-2 kernel: [    8.536598] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 21 10:02:48 node-2 kernel: [    8.536606] ipmi_si 00:09: IPMI kcs interface initialized
Sep 21 10:02:48 node-2 kernel: [    8.556282] systemd-udevd[809]: renamed network interface eth0 to enp6s0
Sep 21 10:02:48 node-2 kernel: [    8.893124] type=1400 audit(1474452140.932:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1063 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.893246] type=1400 audit(1474452140.932:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1063 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.893360] type=1400 audit(1474452140.932:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1063 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.898613] type=1400 audit(1474452140.936:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1065 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.898760] type=1400 audit(1474452140.936:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1065 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.898904] type=1400 audit(1474452140.936:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1065 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.898971] type=1400 audit(1474452140.936:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.899112] type=1400 audit(1474452140.936:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.899234] type=1400 audit(1474452140.936:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    8.900748] type=1400 audit(1474452140.940:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Sep 21 10:02:48 node-2 kernel: [    9.374423] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 21 10:02:48 node-2 kernel: [    9.406895] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 21 10:02:48 node-2 kernel: [    9.640471] enic 0000:06:00.0 enp6s0: Link UP
Sep 21 10:02:48 node-2 kernel: [    9.641588] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 21 10:02:48 node-2 kernel: [    9.641597] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 21 10:02:48 node-2 kernel: [   18.922209] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 21 10:02:49 node-2 failsafe: Failsafe of 120 seconds reached.
Sep 21 10:02:49 node-2 kernel: [   38.174831] init: failsafe main process (8424) killed by TERM signal
Sep 21 10:02:49 node-2 dbus[8464]: [system] AppArmor D-Bus mediation is enabled
Sep 21 10:02:50 node-2 kernel: [   38.354113] audit_printk_skb: 30 callbacks suppressed
Sep 21 10:02:50 node-2 kernel: [   38.354114] type=1400 audit(1474452170.115:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8550 comm="apparmor_parser"
Sep 21 10:02:50 node-2 kernel: [   38.354315] type=1400 audit(1474452170.115:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8549 comm="apparmor_parser"
Sep 21 10:02:50 node-2 kernel: [   38.354320] type=1400 audit(1474452170.115:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8549 comm="apparmor_parser"
Sep 21 10:02:50 node-2 kernel: [   38.354323] type=1400 audit(1474452170.115:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8549 comm="apparmor_parser"
Sep 21 10:02:50 node-2 kernel: [   38.354544] type=1400 audit(1474452170.115:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8549 comm="apparmor_parser"
Sep 21 10:02:50 node-2 kernel: [   38.354546] type=1400 audit(1474452170.115:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8549 comm="apparmor_parser"
Sep 21 10:02:50 node-2 kernel: [   38.354671] type=1400 audit(1474452170.119:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8549 comm="apparmor_parser"
Sep 21 10:02:50 node-2 kernel: [   38.430233] type=1400 audit(1474452170.191:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8552 comm="apparmor_parser"
Sep 21 10:02:50 node-2 anacron[8616]: Anacron 2.3 started on 2016-09-21
Sep 21 10:02:50 node-2 cron[8582]: (CRON) INFO (pidfile fd = 3)
Sep 21 10:02:50 node-2 cron[8630]: (CRON) STARTUP (fork ok)
Sep 21 10:02:50 node-2 multipathd: path checkers start up
Sep 21 10:02:50 node-2 anacron[8616]: Will run job `cron.daily' in 5 min.
Sep 21 10:02:50 node-2 anacron[8616]: Will run job `cron.weekly' in 10 min.
Sep 21 10:02:50 node-2 anacron[8616]: Will run job `cron.monthly' in 15 min.
Sep 21 10:02:50 node-2 anacron[8616]: Jobs will be executed sequentially
Sep 21 10:02:50 node-2 cron[8630]: (CRON) INFO (Running @reboot jobs)
Sep 21 10:02:50 node-2 postfix/master[8761]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 21 10:02:54 node-2 puppet-agent[8945]: Reopening log files
Sep 21 10:02:54 node-2 puppet-agent[8945]: Could not request certificate: Connection refused - connect(2)
Sep 21 10:03:01 node-2 CRON[8976]: (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 21 10:03:09 node-2 puppet-user[9035]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 21 10:03:09 node-2 puppet-user[9035]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Sep 21 10:03:10 node-2 puppet-user[9035]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 21 10:03:10 node-2 puppet-user[9035]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 21 10:03:10 node-2 puppet-user[9035]: Finished catalog run in 0.77 seconds
Sep 21 10:03:11 node-2 multipathd: uevent trigger error
Sep 21 10:03:12 node-2 puppet-user[9460]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 21 10:03:12 node-2 puppet-user[9460]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep 21 10:03:12 node-2 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 21 10:03:12 node-2 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 21 10:03:12 node-2 puppet-user[9460]: (/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 21 10:03:12 node-2 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 21 10:03:12 node-2 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 21 10:03:12 node-2 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 21 10:03:12 node-2 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 21 10:03:12 node-2 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 21 10:03:12 node-2 puppet-user[9460]: Finished catalog run in 0.06 seconds
Sep 21 10:03:12 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 21 10:03:12 node-2 nailgun-agent: D, [2016-09-21T10:03:01.647348 #8979] DEBUG -- : Sleep for 11 seconds before sending request
Sep 21 10:03:12 node-2 nailgun-agent: I, [2016-09-21T10:03:12.672205 #8979]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 21 10:03:13 node-2 nailgun-agent: D, [2016-09-21T10:03:13.430339 #8979] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep 21 10:03:13 node-2 puppet-user[9922]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 21 10:03:13 node-2 puppet-user[9922]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Sep 21 10:03:13 node-2 puppet-user[9922]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 21 10:03:13 node-2 puppet-user[9922]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 21 10:03:13 node-2 puppet-user[9922]: Finished catalog run in 0.03 seconds
Sep 21 10:03:15 node-2 puppet-user[10514]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 21 10:03:15 node-2 puppet-user[10514]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 21 10:03:15 node-2 puppet-user[10514]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 21 10:03:15 node-2 puppet-user[10514]: Finished catalog run in 0.03 seconds
Sep 21 10:03:17 node-2 puppet-user[11098]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 21 10:03:17 node-2 puppet-user[11098]: Compiled catalog for node-2.domain.tld in environment production in 0.21 seconds
Sep 21 10:03:17 node-2 puppet-user[11098]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 21 10:03:17 node-2 kernel: [   65.836343] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 21 10:03:17 node-2 kernel: [   65.836396] 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 21 10:03:17 node-2 puppet-user[11098]: (/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 21 10:03:17 node-2 puppet-user[11098]: Finished catalog run in 0.08 seconds
Sep 21 10:03:19 node-2 puppet-user[11574]: (Scope(Class[main])) MODULAR: sync_time
Sep 21 10:03:19 node-2 puppet-user[11574]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 21 10:03:19 node-2 ntpdate[11998]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.449078 #8979] DEBUG -- : Trying to find block devices
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.449161 #8979] DEBUG -- : Found block device: sda
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.449230 #8979] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.449253 #8979] DEBUG -- : Trying to get list of physical devices
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.449428 #8979] DEBUG -- : Getting udev properties for device: sda
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.451373 #8979] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Sep 21 10:03:25 node-2 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83149", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.451401 #8979] DEBUG -- : Trying to find out if device sda is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.451446 #8979] DEBUG -- : Device sda removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.451461 #8979] DEBUG -- : Device sda seems to be appropriate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.451915 #8979] DEBUG -- : Getting udev properties for device: dm-0
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.453449 #8979] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-xKdz1LwPc1j0HN4m8bWPG8z4OhZNrcIvHdt34ntYiDUzCodOniVqPi95bxZte3kz /dev/disk/by-uuid/a4ab701b-203c-4877-b7ea-23c9072b08d0 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-xKdz1LwPc1j0HN4m8bWPG8z4OhZNrcIvHdt34ntYiDUzCodOniVqPi95bxZte3kz", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a4ab701b-203c-4877-b7ea-23c9072b08d0", "ID_FS_UUID_ENC"=>"a4ab701b-203c-4877-b7ea-23c9072b08d0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60236", "nomdmonddf"=>"1", "nomd
Sep 21 10:03:25 node-2 nailgun-agent: monisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.453477 #8979] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.453518 #8979] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.453532 #8979] DEBUG -- : Device dm-0 seems to be appropriate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.453548 #8979] DEBUG -- : Getting udev properties for device: dm-1
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.455167 #8979] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-EOlyAOEH94h2nqruycvO6w6rX2P3GO7x2UeWA5TnXacXKfjqpSyuNVtwyJ0rZ2hM /dev/disk/by-uuid/fbfc0079-2b1e-455a-a206-24dbe44c40dc /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-EOlyAOEH94h2nqruycvO6w6rX2P3GO7x2UeWA5TnXacXKfjqpSyuNVtwyJ0rZ2hM", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"fbfc0079-2b1e-455a-a206-24dbe44c40dc", "ID_FS_UUID_ENC"=>"fbfc0079-2b1e-455a-a206-24dbe44c40dc", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"25
Sep 21 10:03:25 node-2 nailgun-agent: 256", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.455216 #8979] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.455248 #8979] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.455262 #8979] DEBUG -- : Device dm-1 seems to be appropriate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.455277 #8979] DEBUG -- : Getting udev properties for device: dm-2
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.456818 #8979] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-dM4Y3SlkA7rYYAPe4lnOLxR3SmUJypkPC3KwF3qzl5bnXhBc8bZ7smisendeuS3L /dev/disk/by-uuid/35e5e016-3a0c-4f8e-9a36-828daba73c60 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-dM4Y3SlkA7rYYAPe4lnOLxR3SmUJypkPC3KwF3qzl5bnXhBc8bZ7smisendeuS3L", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"35e5e016-3a0c-4f8e-9a36-828daba73c60", "ID_FS_UUID_ENC"=>"35e5e016-3a0c-4f8e-9a36-828daba73c60", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33554", "nomdmond
Sep 21 10:03:25 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.456844 #8979] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.456891 #8979] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.456911 #8979] DEBUG -- : Device dm-2 seems to be appropriate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.456932 #8979] DEBUG -- : Getting udev properties for device: dm-3
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.458460 #8979] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-TILdEjdTu82RCztrThMijzv9PruEE6qtEpFgFxDwf93bld3xST5zCMFxHG8o012r /dev/disk/by-uuid/2cd04de0-2aca-44e9-a13d-e8fb87cccd90 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-TILdEjdTu82RCztrThMijzv9PruEE6qtEpFgFxDwf93bld3xST5zCMFxHG8o012r", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2cd04de0-2aca-44e9-a13d-e8fb87cccd90", "ID_FS_UUID_ENC"=>"2cd04de0-2aca-44e9-a13d-e8fb87cccd90", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35869", "nomdmonddf"=>"1", 
Sep 21 10:03:25 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.458486 #8979] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.458531 #8979] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.458546 #8979] DEBUG -- : Device dm-3 seems to be appropriate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.458560 #8979] DEBUG -- : Getting udev properties for device: dm-4
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.460077 #8979] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-WJB7HvjF5Mgvsir8OUxulOaF4scBDjXjuV8NXdMMgp6HfdI91IHQGuG8Uk0iUMmD /dev/disk/by-uuid/d4d3075f-6393-4f3e-86fd-b8e78855f6ea /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-WJB7HvjF5Mgvsir8OUxulOaF4scBDjXjuV8NXdMMgp6HfdI91IHQGuG8Uk0iUMmD", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d4d3075f-6393-4f3e-86fd-b8e78855f6ea", "ID_FS_UUID_ENC"=>"d4d3075f-6393-4f3e-86fd-b8e78855f6ea", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37008", "nomdmonddf"=>"1", "nomd
Sep 21 10:03:25 node-2 nailgun-agent: monisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.460103 #8979] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.460145 #8979] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.460162 #8979] DEBUG -- : Device dm-4 seems to be appropriate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.460192 #8979] DEBUG -- : Getting udev properties for device: dm-5
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.461728 #8979] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-WJB7HvjF5Mgvsir8OUxulOaF4scBDjXjqnseTYNSaCCGs85Aln3dArzhRrmqfwVD /dev/disk/by-uuid/19bb7d54-5d16-4c0a-a3a4-155f3cb0efe6 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-WJB7HvjF5Mgvsir8OUxulOaF4scBDjXjqnseTYNSaCCGs85Aln3dArzhRrmqfwVD", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"19bb7d54-5d16-4c0a-a3a4-155f3cb0efe6", "ID_FS_UUID_ENC"=>"19bb7d54-5d16-4c0a-a3a4-155f3cb0efe6", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37430", "nomdmonddf"=>"1", "nomdmonisw"
Sep 21 10:03:25 node-2 nailgun-agent: =>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.461769 #8979] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.461822 #8979] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.461837 #8979] DEBUG -- : Device dm-5 seems to be appropriate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.461852 #8979] DEBUG -- : Getting udev properties for device: ram0
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.463328 #8979] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86592", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.463354 #8979] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.463393 #8979] DEBUG -- : Device ram0 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.463414 #8979] DEBUG -- : Getting udev properties for device: ram1
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.464828 #8979] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86729", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.464853 #8979] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.464891 #8979] DEBUG -- : Device ram1 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.464911 #8979] DEBUG -- : Getting udev properties for device: ram2
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.466320 #8979] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87462", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.466373 #8979] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.466412 #8979] DEBUG -- : Device ram2 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.466433 #8979] DEBUG -- : Getting udev properties for device: ram3
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.467799 #8979] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87534", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.467837 #8979] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.467874 #8979] DEBUG -- : Device ram3 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.467895 #8979] DEBUG -- : Getting udev properties for device: ram4
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.469250 #8979] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87628", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.469276 #8979] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.469312 #8979] DEBUG -- : Device ram4 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.469347 #8979] DEBUG -- : Getting udev properties for device: ram5
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.470695 #8979] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87765", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.470721 #8979] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.470753 #8979] DEBUG -- : Device ram5 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.470786 #8979] DEBUG -- : Getting udev properties for device: ram6
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.472124 #8979] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87851", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.472150 #8979] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.472202 #8979] DEBUG -- : Device ram6 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.472222 #8979] DEBUG -- : Getting udev properties for device: ram7
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.473567 #8979] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88349", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.473592 #8979] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.473635 #8979] DEBUG -- : Device ram7 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.473659 #8979] DEBUG -- : Getting udev properties for device: ram8
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.474988 #8979] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88450", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.475014 #8979] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.475063 #8979] DEBUG -- : Device ram8 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.475083 #8979] DEBUG -- : Getting udev properties for device: ram9
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.476493 #8979] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88536", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.476520 #8979] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.476563 #8979] DEBUG -- : Device ram9 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.476593 #8979] DEBUG -- : Getting udev properties for device: loop0
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.477956 #8979] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85820", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.477981 #8979] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.478012 #8979] DEBUG -- : Device loop0 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.478042 #8979] DEBUG -- : Getting udev properties for device: loop1
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.479424 #8979] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85906", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.479451 #8979] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.479484 #8979] DEBUG -- : Device loop1 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.479515 #8979] DEBUG -- : Getting udev properties for device: loop2
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.480867 #8979] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85988", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.480914 #8979] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.480947 #8979] DEBUG -- : Device loop2 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.480968 #8979] DEBUG -- : Getting udev properties for device: loop3
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.482332 #8979] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86073", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.482366 #8979] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.482402 #8979] DEBUG -- : Device loop3 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.482434 #8979] DEBUG -- : Getting udev properties for device: loop4
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.483811 #8979] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86157", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.483836 #8979] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.483876 #8979] DEBUG -- : Device loop4 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.483908 #8979] DEBUG -- : Getting udev properties for device: loop5
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.485298 #8979] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86220", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.485335 #8979] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.485368 #8979] DEBUG -- : Device loop5 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.485399 #8979] DEBUG -- : Getting udev properties for device: loop6
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.486768 #8979] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86297", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.486792 #8979] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.486835 #8979] DEBUG -- : Device loop6 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.486856 #8979] DEBUG -- : Getting udev properties for device: loop7
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.488228 #8979] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86459", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.488265 #8979] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.488305 #8979] DEBUG -- : Device loop7 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.492563 #8979] DEBUG -- : Getting udev properties for device: ram10
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.494122 #8979] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86841", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.494147 #8979] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.494181 #8979] DEBUG -- : Device ram10 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.494201 #8979] DEBUG -- : Getting udev properties for device: ram11
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.495583 #8979] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86915", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.495608 #8979] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.495639 #8979] DEBUG -- : Device ram11 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.495659 #8979] DEBUG -- : Getting udev properties for device: ram12
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.497050 #8979] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87064", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.497074 #8979] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.497111 #8979] DEBUG -- : Device ram12 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.497130 #8979] DEBUG -- : Getting udev properties for device: ram13
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.498514 #8979] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87156", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.498539 #8979] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.498575 #8979] DEBUG -- : Device ram13 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.498594 #8979] DEBUG -- : Getting udev properties for device: ram14
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.499987 #8979] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87235", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.500012 #8979] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.500048 #8979] DEBUG -- : Device ram14 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.500067 #8979] DEBUG -- : Getting udev properties for device: ram15
Sep 21 10:03:25 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501411 #8979] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87339", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501475 #8979] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501511 #8979] DEBUG -- : Device ram15 removable parameter: "0"
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501545 #8979] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501559 #8979] DEBUG -- : Block device seems to be physical data storage: sda
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501608 #8979] DEBUG -- : Found block device: dm-0
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501622 #8979] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501634 #8979] DEBUG -- : Found block device: dm-1
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501645 #8979] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501655 #8979] DEBUG -- : Found block device: dm-2
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501665 #8979] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501709 #8979] DEBUG -- : Found block device: dm-3
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501719 #8979] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501728 #8979] DEBUG -- : Found block device: dm-4
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501738 #8979] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501746 #8979] DEBUG -- : Found block device: dm-5
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501755 #8979] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501764 #8979] DEBUG -- : Found block device: ram0
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501774 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501783 #8979] DEBUG -- : Found block device: ram1
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501793 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501832 #8979] DEBUG -- : Found block device: ram2
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501843 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501852 #8979] DEBUG -- : Found block device: ram3
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501862 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501870 #8979] DEBUG -- : Found block device: ram4
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501880 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501888 #8979] DEBUG -- : Found block device: ram5
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501899 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501908 #8979] DEBUG -- : Found block device: ram6
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501918 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501927 #8979] DEBUG -- : Found block device: ram7
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501967 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501976 #8979] DEBUG -- : Found block device: ram8
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501986 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.501994 #8979] DEBUG -- : Found block device: ram9
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502004 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502013 #8979] DEBUG -- : Found block device: loop0
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502023 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502031 #8979] DEBUG -- : Found block device: loop1
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502041 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502050 #8979] DEBUG -- : Found block device: loop2
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502097 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502106 #8979] DEBUG -- : Found block device: loop3
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502116 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502125 #8979] DEBUG -- : Found block device: loop4
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502137 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502145 #8979] DEBUG -- : Found block device: loop5
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502154 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502163 #8979] DEBUG -- : Found block device: loop6
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502173 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502217 #8979] DEBUG -- : Found block device: loop7
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502228 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502237 #8979] DEBUG -- : Found block device: ram10
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502246 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502255 #8979] DEBUG -- : Found block device: ram11
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502265 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502273 #8979] DEBUG -- : Found block device: ram12
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502282 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502291 #8979] DEBUG -- : Found block device: ram13
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502300 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502348 #8979] DEBUG -- : Found block device: ram14
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502359 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502368 #8979] DEBUG -- : Found block device: ram15
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502378 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.502407 #8979] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.596692 #8979] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep 21 10:03:25 node-2 nailgun-agent: D, [2016-09-21T10:03:25.596739 #8979] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 21 10:03:25 node-2 ntpdate[11998]: adjust time server 10.20.0.2 offset 0.150825 sec
Sep 21 10:03:25 node-2 puppet-user[11574]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 21 10:03:25 node-2 puppet-user[11574]: Finished catalog run in 6.21 seconds
Sep 21 10:03:31 node-2 puppet-user[12560]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 21 10:03:31 node-2 puppet-user[12560]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep 21 10:03:31 node-2 puppet-user[12560]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 21 10:03:31 node-2 puppet-user[12560]: Finished catalog run in 0.07 seconds
Sep 21 10:03:32 node-2 puppet-user[13013]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 21 10:03:33 node-2 puppet-user[13013]: Compiled catalog for node-2.domain.tld in environment production in 0.53 seconds
Sep 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:33 node-2 puppet-user[13013]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:33 node-2 puppet-user[13013]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:33 node-2 puppet-user[13013]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:33 node-2 puppet-user[13013]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 21 10:03:33 node-2 puppet-user[13013]: (/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 21 10:03:34 node-2 puppet-user[13013]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 21 10:03:34 node-2 puppet-user[13013]: Finished catalog run in 0.79 seconds
Sep 21 10:03:35 node-2 puppet-user[13526]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 21 10:03:36 node-2 puppet-user[13526]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Sep 21 10:03:37 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.540827 #8979] DEBUG -- : Trying to find block devices
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.540910 #8979] DEBUG -- : Found block device: sda
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.540937 #8979] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.540957 #8979] DEBUG -- : Block device seems to be physical data storage: sda
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.540977 #8979] DEBUG -- : Found block device: dm-0
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541009 #8979] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541022 #8979] DEBUG -- : Found block device: dm-1
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541033 #8979] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541042 #8979] DEBUG -- : Found block device: dm-2
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541053 #8979] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541062 #8979] DEBUG -- : Found block device: dm-3
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541071 #8979] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541080 #8979] DEBUG -- : Found block device: dm-4
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541090 #8979] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541099 #8979] DEBUG -- : Found block device: dm-5
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541138 #8979] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541148 #8979] DEBUG -- : Found block device: ram0
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541158 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541166 #8979] DEBUG -- : Found block device: ram1
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541175 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541185 #8979] DEBUG -- : Found block device: ram2
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541194 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541202 #8979] DEBUG -- : Found block device: ram3
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541211 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541219 #8979] DEBUG -- : Found block device: ram4
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541229 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541253 #8979] DEBUG -- : Found block device: ram5
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541262 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541271 #8979] DEBUG -- : Found block device: ram6
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541280 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541288 #8979] DEBUG -- : Found block device: ram7
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541297 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541320 #8979] DEBUG -- : Found block device: ram8
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541330 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541338 #8979] DEBUG -- : Found block device: ram9
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541347 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541356 #8979] DEBUG -- : Found block device: loop0
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541365 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541373 #8979] DEBUG -- : Found block device: loop1
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541398 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541407 #8979] DEBUG -- : Found block device: loop2
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541416 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541425 #8979] DEBUG -- : Found block device: loop3
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541434 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541442 #8979] DEBUG -- : Found block device: loop4
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541451 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541459 #8979] DEBUG -- : Found block device: loop5
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541478 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541487 #8979] DEBUG -- : Found block device: loop6
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541496 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541504 #8979] DEBUG -- : Found block device: loop7
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541525 #8979] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541535 #8979] DEBUG -- : Found block device: ram10
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541544 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541552 #8979] DEBUG -- : Found block device: ram11
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541561 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541583 #8979] DEBUG -- : Found block device: ram12
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541592 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541601 #8979] DEBUG -- : Found block device: ram13
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541621 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541631 #8979] DEBUG -- : Found block device: ram14
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541640 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541649 #8979] DEBUG -- : Found block device: ram15
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541672 #8979] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.541699 #8979] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Sep 21 10:03:37 node-2 nailgun-agent: D, [2016-09-21T10:03:37.698283 #8979] DEBUG -- : Response: status: 200 body: {"id": 2}
Sep 21 10:03:37 node-2 nailgun-agent: I, [2016-09-21T10:03:37.699249 #8979]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep 21 10:03:39 node-2 kernel: [   87.603869] init: plymouth-upstart-bridge main process ended, respawning
Sep 21 10:03:39 node-2 puppet-user[13526]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 21 10:03:39 node-2 puppet-agent[8945]: Could not run: SIGTERM
Sep 21 10:03:39 node-2 kernel: [   87.902264] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 21 10:03:39 node-2 ec2: 
Sep 21 10:03:39 node-2 ec2: #############################################################
Sep 21 10:03:39 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 21 10:03:39 node-2 ec2: 1024 a4:f7:19:af:70:00:b2:25:31:c0:05:84:0f:e6:e9:f5  root@node-2.domain.tld (DSA)
Sep 21 10:03:39 node-2 ec2: 256 c1:f4:75:65:0f:97:87:9d:b1:01:fe:d7:91:53:cf:60  root@node-2.domain.tld (ECDSA)
Sep 21 10:03:39 node-2 ec2: 256 d1:72:9c:44:c4:78:3d:1d:b3:d8:5e:34:56:98:b0:67  root@node-2.domain.tld (ED25519)
Sep 21 10:03:39 node-2 ec2: 2048 60:79:d1:b7:a1:9f:bb:e6:de:7c:cb:64:5a:64:9b:d5  root@node-2.domain.tld (RSA)
Sep 21 10:03:39 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 21 10:03:39 node-2 ec2: #############################################################
Sep 21 10:04:01 node-2 CRON[16376]: (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 21 10:04:06 node-2 puppet-user[13526]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 21 10:04:06 node-2 puppet-user[13526]: Finished catalog run in 30.10 seconds
Sep 21 10:04:08 node-2 puppet-user[16655]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 21 10:04:08 node-2 puppet-user[16655]: Compiled catalog for node-2.domain.tld in environment production in 0.61 seconds
Sep 21 10:04:09 node-2 puppet-user[16655]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 21 10:04:09 node-2 puppet-user[16655]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 21 10:04:09 node-2 puppet-user[16655]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 21 10:04:09 node-2 puppet-user[16655]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 21 10:04:09 node-2 puppet-user[16655]: Finished catalog run in 0.09 seconds
Sep 21 10:04:10 node-2 puppet-user[17113]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 21 10:04:11 node-2 puppet-user[17113]: Compiled catalog for node-2.domain.tld in environment production in 0.90 seconds
Sep 21 10:04:12 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 21 10:04:12 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 21 10:04:12 node-2 crontab[17550]: (root) LIST (root)
Sep 21 10:04:12 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 21 10:04:12 node-2 crontab[17551]: (root) REPLACE (root)
Sep 21 10:04:13 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 21 10:04:13 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 21 10:04:14 node-2 puppet-user[17113]: (/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 21 10:04:14 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8397" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 21 10:04:14 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 10:04:15 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 21 10:04:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:31 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:31 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:31 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:31 node-2 multipathd: uevent trigger error
<27>Sep 21 10:04:31 node-2 multipathd: uevent trigger error
<27>Sep 21 10:05:26 node-2 ntpdate[28760]: no servers can be used, exiting
<27>Sep 21 10:05:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:05:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:05:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:05:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:05:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:01 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:01 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:01 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:01 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:01 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:06:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:10 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:10 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:10 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:10 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:10 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:21 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 10:07:21 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 10:07:27 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 10:07:27 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 10:07:33 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 10:07:38 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 10:07:38 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 10:07:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:07:58 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:00 node-2 haproxy[16133]: 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 21 10:08:01 node-2 haproxy[16144]: 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 21 10:08:02 node-2 haproxy[16144]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:02 node-2 haproxy[16144]: proxy mysqld has no server available!
<27>Sep 21 10:08:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:07 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:10 node-2 haproxy[18886]: 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 21 10:08:10 node-2 haproxy[18886]: 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 21 10:08:11 node-2 haproxy[18897]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:11 node-2 haproxy[18897]: proxy mysqld has no server available!
<129>Sep 21 10:08:11 node-2 haproxy[18897]: 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 21 10:08:11 node-2 haproxy[18897]: 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 21 10:08:12 node-2 haproxy[18897]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:12 node-2 haproxy[18897]: proxy object-storage has no server available!
<27>Sep 21 10:08:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:13 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:15 node-2 haproxy[20268]: 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 21 10:08:15 node-2 haproxy[20268]: 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 21 10:08:15 node-2 haproxy[20268]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:15 node-2 haproxy[20268]: proxy neutron has no server available!
<129>Sep 21 10:08:16 node-2 haproxy[20272]: 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 21 10:08:16 node-2 haproxy[20272]: 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 21 10:08:16 node-2 haproxy[20272]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:16 node-2 haproxy[20272]: proxy mysqld has no server available!
<129>Sep 21 10:08:16 node-2 haproxy[20272]: 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 21 10:08:17 node-2 haproxy[20272]: 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 21 10:08:17 node-2 haproxy[20272]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:17 node-2 haproxy[20272]: proxy object-storage has no server available!
<27>Sep 21 10:08:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:18 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:20 node-2 haproxy[21637]: 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 21 10:08:20 node-2 haproxy[21637]: 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 21 10:08:21 node-2 haproxy[21644]: Server keystone-1/node-5 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 21 10:08:21 node-2 haproxy[21644]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:21 node-2 haproxy[21644]: 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 21 10:08:21 node-2 haproxy[21644]: 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 21 10:08:21 node-2 haproxy[21644]: Server keystone-2/node-5 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 21 10:08:21 node-2 haproxy[21644]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:21 node-2 haproxy[21644]: 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 21 10:08:21 node-2 haproxy[21644]: 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 21 10:08:21 node-2 haproxy[21644]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:21 node-2 haproxy[21644]: proxy neutron has no server available!
<129>Sep 21 10:08:22 node-2 haproxy[21644]: 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 21 10:08:22 node-2 haproxy[21644]: 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 21 10:08:22 node-2 haproxy[21644]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:22 node-2 haproxy[21644]: proxy mysqld has no server available!
<129>Sep 21 10:08:22 node-2 haproxy[21644]: 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 21 10:08:22 node-2 haproxy[21644]: 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 21 10:08:22 node-2 haproxy[21644]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:22 node-2 haproxy[21644]: proxy object-storage has no server available!
<27>Sep 21 10:08:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:24 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:26 node-2 haproxy[23134]: 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 21 10:08:26 node-2 haproxy[23134]: 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 21 10:08:26 node-2 haproxy[23134]: Server keystone-1/node-5 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 21 10:08:26 node-2 haproxy[23134]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:26 node-2 haproxy[23134]: 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 21 10:08:26 node-2 haproxy[23134]: 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 21 10:08:26 node-2 haproxy[23134]: Server keystone-2/node-5 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 21 10:08:26 node-2 haproxy[23134]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:26 node-2 haproxy[23134]: 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 21 10:08:27 node-2 haproxy[23138]: 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 21 10:08:27 node-2 haproxy[23138]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:27 node-2 haproxy[23138]: proxy neutron has no server available!
<129>Sep 21 10:08:27 node-2 haproxy[23138]: 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 21 10:08:27 node-2 haproxy[23138]: 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 21 10:08:27 node-2 haproxy[23138]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:27 node-2 haproxy[23138]: proxy mysqld has no server available!
<129>Sep 21 10:08:27 node-2 haproxy[23138]: 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 21 10:08:27 node-2 haproxy[23138]: 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 21 10:08:27 node-2 haproxy[23138]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:27 node-2 haproxy[23138]: proxy object-storage has no server available!
<129>Sep 21 10:08:27 node-2 haproxy[23138]: 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 21 10:08:28 node-2 haproxy[23138]: 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 21 10:08:28 node-2 haproxy[23138]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:28 node-2 haproxy[23138]: proxy aodh has no server available!
<27>Sep 21 10:08:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:29 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:31 node-2 haproxy[24513]: 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 21 10:08:31 node-2 haproxy[24513]: 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 21 10:08:31 node-2 haproxy[24513]: Server keystone-1/node-5 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 21 10:08:31 node-2 haproxy[24513]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:31 node-2 haproxy[24513]: 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 21 10:08:32 node-2 haproxy[24520]: 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 21 10:08:32 node-2 haproxy[24520]: Server keystone-2/node-5 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 21 10:08:32 node-2 haproxy[24520]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:32 node-2 haproxy[24520]: 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 21 10:08:32 node-2 haproxy[24520]: 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 21 10:08:32 node-2 haproxy[24520]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:32 node-2 haproxy[24520]: proxy neutron has no server available!
<129>Sep 21 10:08:32 node-2 haproxy[24520]: 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 21 10:08:32 node-2 haproxy[24520]: 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 21 10:08:32 node-2 haproxy[24520]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:32 node-2 haproxy[24520]: proxy mysqld has no server available!
<129>Sep 21 10:08:32 node-2 haproxy[24520]: 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 21 10:08:32 node-2 haproxy[24520]: 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 21 10:08:33 node-2 haproxy[24520]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:33 node-2 haproxy[24520]: proxy object-storage has no server available!
<129>Sep 21 10:08:33 node-2 haproxy[24520]: 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 21 10:08:33 node-2 haproxy[24520]: 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 21 10:08:33 node-2 haproxy[24520]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:33 node-2 haproxy[24520]: proxy aodh has no server available!
<129>Sep 21 10:08:33 node-2 haproxy[24520]: 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 21 10:08:33 node-2 haproxy[24520]: 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 21 10:08:33 node-2 haproxy[24520]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:33 node-2 haproxy[24520]: proxy ceilometer has no server available!
<27>Sep 21 10:08:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:35 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:37 node-2 haproxy[25889]: 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 21 10:08:37 node-2 haproxy[25889]: 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 21 10:08:37 node-2 haproxy[25889]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:37 node-2 haproxy[25889]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:37 node-2 haproxy[25889]: 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 21 10:08:37 node-2 haproxy[25889]: 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 21 10:08:37 node-2 haproxy[25889]: Server keystone-2/node-5 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 21 10:08:37 node-2 haproxy[25889]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:37 node-2 haproxy[25889]: 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 21 10:08:37 node-2 haproxy[25889]: 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 21 10:08:37 node-2 haproxy[25889]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:37 node-2 haproxy[25889]: proxy neutron has no server available!
<129>Sep 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:38 node-2 haproxy[25893]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:38 node-2 haproxy[25893]: proxy mysqld has no server available!
<129>Sep 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:38 node-2 haproxy[25893]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:38 node-2 haproxy[25893]: proxy object-storage has no server available!
<129>Sep 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:38 node-2 haproxy[25893]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:38 node-2 haproxy[25893]: proxy aodh has no server available!
<129>Sep 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:38 node-2 haproxy[25893]: 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 21 10:08:39 node-2 haproxy[25893]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:39 node-2 haproxy[25893]: proxy ceilometer has no server available!
<27>Sep 21 10:08:40 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:40 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:40 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:40 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:40 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:42 node-2 haproxy[27242]: 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 21 10:08:42 node-2 haproxy[27242]: 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 21 10:08:42 node-2 haproxy[27242]: 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 21 10:08:42 node-2 haproxy[27242]: Server keystone-1/node-5 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 21 10:08:42 node-2 haproxy[27242]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:42 node-2 haproxy[27242]: 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 21 10:08:42 node-2 haproxy[27242]: 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 21 10:08:43 node-2 haproxy[27246]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:43 node-2 haproxy[27246]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:43 node-2 haproxy[27246]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:43 node-2 haproxy[27246]: proxy neutron has no server available!
<129>Sep 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:43 node-2 haproxy[27246]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:43 node-2 haproxy[27246]: proxy mysqld has no server available!
<129>Sep 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:43 node-2 haproxy[27246]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:43 node-2 haproxy[27246]: proxy object-storage has no server available!
<129>Sep 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:43 node-2 haproxy[27246]: 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 21 10:08:44 node-2 haproxy[27246]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:44 node-2 haproxy[27246]: proxy aodh has no server available!
<129>Sep 21 10:08:44 node-2 haproxy[27246]: 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 21 10:08:44 node-2 haproxy[27246]: 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 21 10:08:44 node-2 haproxy[27246]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:44 node-2 haproxy[27246]: proxy ceilometer has no server available!
<27>Sep 21 10:08:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:45 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:48 node-2 haproxy[28633]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:48 node-2 haproxy[28633]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:48 node-2 haproxy[28633]: proxy glance-api has no server available!
<129>Sep 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:48 node-2 haproxy[28633]: 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 21 10:08:49 node-2 haproxy[28639]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:49 node-2 haproxy[28639]: proxy glance-glare has no server available!
<129>Sep 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:49 node-2 haproxy[28639]: proxy neutron has no server available!
<129>Sep 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:49 node-2 haproxy[28639]: proxy glance-registry has no server available!
<129>Sep 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:49 node-2 haproxy[28639]: proxy mysqld has no server available!
<129>Sep 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:49 node-2 haproxy[28639]: proxy object-storage has no server available!
<129>Sep 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:49 node-2 haproxy[28639]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:49 node-2 haproxy[28639]: proxy aodh has no server available!
<129>Sep 21 10:08:49 node-2 haproxy[28639]: 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 21 10:08:50 node-2 haproxy[28639]: 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 21 10:08:50 node-2 haproxy[28639]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:50 node-2 haproxy[28639]: proxy ceilometer has no server available!
<27>Sep 21 10:08:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:51 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:53 node-2 haproxy[30038]: 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 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:54 node-2 haproxy[30044]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:54 node-2 haproxy[30044]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:54 node-2 haproxy[30044]: proxy nova-api has no server available!
<129>Sep 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:54 node-2 haproxy[30044]: proxy nova-metadata-api has no server available!
<129>Sep 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:54 node-2 haproxy[30044]: proxy glance-api has no server available!
<129>Sep 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:54 node-2 haproxy[30044]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:54 node-2 haproxy[30044]: proxy glance-glare has no server available!
<129>Sep 21 10:08:54 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:55 node-2 haproxy[30044]: proxy neutron has no server available!
<129>Sep 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:55 node-2 haproxy[30044]: proxy glance-registry has no server available!
<129>Sep 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:55 node-2 haproxy[30044]: proxy mysqld has no server available!
<129>Sep 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:55 node-2 haproxy[30044]: proxy object-storage has no server available!
<129>Sep 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:55 node-2 haproxy[30044]: proxy aodh has no server available!
<129>Sep 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:55 node-2 haproxy[30044]: proxy ceilometer has no server available!
<129>Sep 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: 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 21 10:08:55 node-2 haproxy[30044]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:55 node-2 haproxy[30044]: proxy nova-novncproxy has no server available!
<27>Sep 21 10:08:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:08:57 node-2 multipathd: uevent trigger error
<129>Sep 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:59 node-2 haproxy[31374]: proxy keystone-1 has no server available!
<129>Sep 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:59 node-2 haproxy[31374]: proxy keystone-2 has no server available!
<129>Sep 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:59 node-2 haproxy[31374]: proxy nova-api has no server available!
<129>Sep 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:08:59 node-2 haproxy[31374]: proxy nova-metadata-api has no server available!
<129>Sep 21 10:08:59 node-2 haproxy[31374]: 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 21 10:08:59 node-2 haproxy[31374]: 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 21 10:09:00 node-2 haproxy[31378]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy cinder-api has no server available!
<129>Sep 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy glance-api has no server available!
<129>Sep 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy glance-glare has no server available!
<129>Sep 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy neutron has no server available!
<129>Sep 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy glance-registry has no server available!
<129>Sep 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy mysqld has no server available!
<129>Sep 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy object-storage has no server available!
<129>Sep 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: 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 21 10:09:00 node-2 haproxy[31378]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:00 node-2 haproxy[31378]: proxy aodh has no server available!
<129>Sep 21 10:09:01 node-2 haproxy[31378]: 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 21 10:09:01 node-2 haproxy[31378]: 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 21 10:09:01 node-2 haproxy[31378]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:01 node-2 haproxy[31378]: proxy ceilometer has no server available!
<129>Sep 21 10:09:01 node-2 haproxy[31378]: 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 21 10:09:01 node-2 haproxy[31378]: 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 21 10:09:01 node-2 haproxy[31378]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:01 node-2 haproxy[31378]: proxy nova-novncproxy has no server available!
<27>Sep 21 10:09:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:02 node-2 multipathd: uevent trigger error
<129>Sep 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:05 node-2 haproxy[446]: proxy keystone-1 has no server available!
<129>Sep 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:05 node-2 haproxy[446]: proxy keystone-2 has no server available!
<129>Sep 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:05 node-2 haproxy[446]: proxy nova-api has no server available!
<129>Sep 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:05 node-2 haproxy[446]: proxy nova-metadata-api has no server available!
<129>Sep 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:05 node-2 haproxy[446]: proxy cinder-api has no server available!
<129>Sep 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:05 node-2 haproxy[446]: proxy glance-api has no server available!
<129>Sep 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: 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 21 10:09:05 node-2 haproxy[446]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:05 node-2 haproxy[446]: proxy glance-glare has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy neutron has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy glance-registry has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy mysqld has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy object-storage has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy aodh has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy ceilometer has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy heat-api has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy heat-api-cfn has no server available!
<129>Sep 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: 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 21 10:09:06 node-2 haproxy[450]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:06 node-2 haproxy[450]: proxy heat-api-cloudwatch has no server available!
<129>Sep 21 10:09:07 node-2 haproxy[450]: 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 21 10:09:07 node-2 haproxy[450]: 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 21 10:09:07 node-2 haproxy[450]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 10:09:07 node-2 haproxy[450]: proxy nova-novncproxy has no server available!
<27>Sep 21 10:09:08 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:08 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:08 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:09 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:09 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:09:19 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 21 10:09:43 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 21 10:09:45 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 21 10:10:12 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:10:16 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 10:10:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:10:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:10:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:10:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:10:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:34 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:34 node-2 multipathd: uevent trigger error
<43>Sep 21 10:12:45 node-2 apache2_error [Wed Sep 21 10:12:44.781403 2016] [mpm_event:notice] [pid 6701:tid 139764821596032] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 21 10:12:45 node-2 apache2_error [Wed Sep 21 10:12:44.781496 2016] [core:notice] [pid 6701:tid 139764821596032] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 10:12:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:53 node-2 multipathd: uevent trigger error
<43>Sep 21 10:12:55 node-2 apache2_error [Wed Sep 21 10:12:47.746465 2016] [mpm_event:notice] [pid 6701:tid 139764821596032] AH00491: caught SIGTERM, shutting down
<43>Sep 21 10:12:55 node-2 apache2_error [Wed Sep 21 10:12:48.829700 2016] [mpm_worker:notice] [pid 7079:tid 140527031777152] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 21 10:12:55 node-2 apache2_error [Wed Sep 21 10:12:48.829740 2016] [core:notice] [pid 7079:tid 140527031777152] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 10:12:56 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:56 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:56 node-2 multipathd: uevent trigger error
<27>Sep 21 10:12:56 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:14 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:13:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:41 node-2 multipathd: uevent trigger error
<43>Sep 21 10:13:45 node-2 apache2_error [Wed Sep 21 10:13:38.256062 2016] [mpm_worker:notice] [pid 7079:tid 140527031777152] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 10:13:45 node-2 apache2_error [Wed Sep 21 10:13:38.263297 2016] [mpm_worker:warn] [pid 7079:tid 140527031777152] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 10:13:45 node-2 apache2_error [Wed Sep 21 10:13:38.264194 2016] [mpm_worker:notice] [pid 7079:tid 140527031777152] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 21 10:13:45 node-2 apache2_error [Wed Sep 21 10:13:38.264214 2016] [core:notice] [pid 7079:tid 140527031777152] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 10:13:46 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:46 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:46 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:46 node-2 multipathd: uevent trigger error
<27>Sep 21 10:13:46 node-2 multipathd: uevent trigger error
<43>Sep 21 10:14:56 node-2 apache2_error [Wed Sep 21 10:14:47.879777 2016] [mpm_worker:notice] [pid 7079:tid 140527031777152] AH00295: caught SIGTERM, shutting down
<43>Sep 21 10:14:56 node-2 apache2_error [Wed Sep 21 10:14:48.627886 2016] [mpm_worker:notice] [pid 28064:tid 140230490093440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 10:14:56 node-2 apache2_error [Wed Sep 21 10:14:48.627918 2016] [core:notice] [pid 28064:tid 140230490093440] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 21 10:15:36 node-2 apache2_error [Wed Sep 21 10:15:32.728139 2016] [mpm_worker:notice] [pid 28064:tid 140230490093440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 10:15:36 node-2 apache2_error [Wed Sep 21 10:15:32.739217 2016] [mpm_worker:warn] [pid 28064:tid 140230490093440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 10:15:36 node-2 apache2_error [Wed Sep 21 10:15:32.744865 2016] [mpm_worker:notice] [pid 28064:tid 140230490093440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 10:15:36 node-2 apache2_error [Wed Sep 21 10:15:32.744895 2016] [core:notice] [pid 28064:tid 140230490093440] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 10:16:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:16:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:53 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:16:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:02 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:17 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:38 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:38 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:38 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:39 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:17:58 node-2 multipathd: uevent trigger error
<27>Sep 21 10:18:47 node-2 multipathd: uevent trigger error
<27>Sep 21 10:18:47 node-2 multipathd: uevent trigger error
<27>Sep 21 10:18:47 node-2 multipathd: uevent trigger error
<27>Sep 21 10:18:47 node-2 multipathd: uevent trigger error
<27>Sep 21 10:18:47 node-2 multipathd: uevent trigger error
<27>Sep 21 10:19:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:19:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:19:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:19:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:19:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:19:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:20:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:20:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:20:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:20:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:20:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:18 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:23 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:23 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:23 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:23 node-2 multipathd: uevent trigger error
<27>Sep 21 10:21:23 node-2 multipathd: uevent trigger error
<27>Sep 21 10:22:21 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:23:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:43 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:23:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:04 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:24:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:25:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:25:57 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 21 10:26:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 21 10:26:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 21 10:26:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Sep 21 10:26:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Sep 21 10:26:06 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:06 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:06 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:06 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:06 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:34 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:34 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:34 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:34 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:34 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:26:51 node-2 multipathd: uevent trigger error
<27>Sep 21 10:28:24 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:29:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:11 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:29:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:37 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:37 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:37 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:37 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:37 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:49 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:30:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:31:26 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 10:31:36 node-2 multipathd: uevent trigger error
<27>Sep 21 10:31:36 node-2 multipathd: uevent trigger error
<27>Sep 21 10:31:36 node-2 multipathd: uevent trigger error
<27>Sep 21 10:31:36 node-2 multipathd: uevent trigger error
<27>Sep 21 10:31:36 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:59 node-2 multipathd: uevent trigger error
<27>Sep 21 10:32:59 node-2 multipathd: uevent trigger error
<11>Sep 21 10:33:12 node-2 liberasurecode[21813]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:12 node-2 liberasurecode[21813]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:12 node-2 liberasurecode[21813]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:12 node-2 liberasurecode[21813]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:12 node-2 liberasurecode[21839]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:12 node-2 liberasurecode[21839]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:12 node-2 liberasurecode[21839]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:12 node-2 liberasurecode[21839]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:14 node-2 liberasurecode[22223]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:14 node-2 liberasurecode[22223]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:14 node-2 liberasurecode[22223]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:14 node-2 liberasurecode[22223]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22935]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22935]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22935]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22935]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22976]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22976]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22976]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[22976]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[23014]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[23014]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[23014]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:18 node-2 liberasurecode[23014]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23084]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23084]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23084]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23084]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23096]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23096]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23096]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23096]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23110]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23110]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23110]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23110]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23122]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23122]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23122]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:19 node-2 liberasurecode[23122]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:35 node-2 liberasurecode[25360]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:35 node-2 liberasurecode[25360]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:35 node-2 liberasurecode[25360]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:33:35 node-2 liberasurecode[25360]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 21 10:33:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:33:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:33:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:33:44 node-2 multipathd: uevent trigger error
<27>Sep 21 10:34:27 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 21 10:34:37 node-2 apache2_error [Wed Sep 21 10:34:32.130158 2016] [mpm_worker:notice] [pid 28064:tid 140230490093440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 10:34:37 node-2 apache2_error [Wed Sep 21 10:34:32.514331 2016] [mpm_worker:warn] [pid 28064:tid 140230490093440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 10:34:37 node-2 apache2_error [Wed Sep 21 10:34:32.517917 2016] [mpm_worker:notice] [pid 28064:tid 140230490093440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 10:34:37 node-2 apache2_error [Wed Sep 21 10:34:32.517933 2016] [core:notice] [pid 28064:tid 140230490093440] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 21 10:35:01 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:35:01 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:35:01 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:35:01 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 21 10:35:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:13 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:13 node-2 multipathd: uevent trigger error
<43>Sep 21 10:35:17 node-2 apache2_error [Wed Sep 21 10:35:09.257215 2016] [mpm_worker:notice] [pid 28064:tid 140230490093440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 10:35:17 node-2 apache2_error [Wed Sep 21 10:35:09.641523 2016] [mpm_worker:warn] [pid 28064:tid 140230490093440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 10:35:17 node-2 apache2_error [Wed Sep 21 10:35:09.654247 2016] [mpm_worker:notice] [pid 28064:tid 140230490093440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 10:35:17 node-2 apache2_error [Wed Sep 21 10:35:09.654277 2016] [core:notice] [pid 28064:tid 140230490093440] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 10:35:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:19 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:20 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:24 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:39 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:39 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:39 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:39 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:39 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:35:55 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:14 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:20 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 21 10:36:29 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:30 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:35 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:41 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:54 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:54 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:54 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:54 node-2 multipathd: uevent trigger error
<27>Sep 21 10:36:54 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:20 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 10:37:21 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:21 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:21 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:21 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:21 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:28 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:32 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:32 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:32 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:32 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:32 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:45 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:50 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:50 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:50 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:50 node-2 multipathd: uevent trigger error
<27>Sep 21 10:37:50 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:03 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:03 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:03 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:03 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:07 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:16 node-2 multipathd: uevent trigger error
<27>Sep 21 10:38:16 node-2 multipathd: uevent trigger error
<11>Sep 21 10:40:01 node-2 liberasurecode[6524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:40:01 node-2 liberasurecode[6524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:40:01 node-2 liberasurecode[6524]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 10:40:01 node-2 liberasurecode[6524]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
