Sep 28 01:16:48 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8428" x-info="http://www.rsyslog.com"] start
Sep 28 01:16:48 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 28 01:16:48 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep 28 01:16:48 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep 28 01:16:48 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 28 01:16:48 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 28 01:16:48 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 28 01:16:48 node-2 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Sep 28 01:16:48 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1c4b4239-f827-4c53-b9f6-db3ad33917a8 nomdmonddf nomdmonisw
Sep 28 01:16:48 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep 28 01:16:48 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep 28 01:16:48 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep 28 01:16:48 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep 28 01:16:48 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 28 01:16:48 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 28 01:16:48 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 28 01:16: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 28 01:16:48 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 28 01:16:48 node-2 kernel: [    0.000000] No AGP bridge found
Sep 28 01:16:48 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 28 01:16:48 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep 28 01:16:48 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 28 01:16:48 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep 28 01:16:48 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 28 01:16:48 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 28 01:16:48 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 28 01:16:48 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 28 01:16:48 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 28 01:16:48 node-2 kernel: [    0.000000]   2 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000]   3 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000]   4 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000]   5 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000]   6 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000]   7 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000]   8 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000]   9 disabled
Sep 28 01:16:48 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 28 01:16:48 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 28 01:16:48 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 28 01:16:48 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 28 01:16:48 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 28 01:16:48 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 28 01:16:48 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 28 01:16:48 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 28 01:16:48 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 28 01:16:48 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 28 01:16:48 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 28 01:16:48 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 28 01:16:48 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 28 01:16:48 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 28 01:16:48 node-2 kernel: [    0.000000] Zone ranges:
Sep 28 01:16:48 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] Movable zone start for each node
Sep 28 01:16:48 node-2 kernel: [    0.000000] Early memory node ranges
Sep 28 01:16:48 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 28 01:16:48 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 28 01:16:48 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 28 01:16:48 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 28 01:16:48 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 28 01:16:48 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 28 01:16:48 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 28 01:16:48 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 28 01:16:48 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 28 01:16:48 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 28 01:16:48 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 28 01:16: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 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 28 01:16:48 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 28 01:16:48 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 28 01:16:48 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 28 01:16:48 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 28 01:16:48 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 28 01:16:48 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 28 01:16:48 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 28 01:16:48 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 28 01:16:48 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 28 01:16:48 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 28 01:16:48 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 28 01:16:48 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 28 01:16: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 28 01:16:48 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 28 01:16:48 node-2 kernel: [    0.000000] Policy zone: Normal
Sep 28 01:16:48 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1c4b4239-f827-4c53-b9f6-db3ad33917a8 nomdmonddf nomdmonisw
Sep 28 01:16:48 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 28 01:16:48 node-2 kernel: [    0.000000] Checking aperture...
Sep 28 01:16:48 node-2 kernel: [    0.000000] No AGP bridge found
Sep 28 01:16:48 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 28 01:16:48 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 28 01:16:48 node-2 kernel: [    0.000000] Memory: 32653312K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Sep 28 01:16:48 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 28 01:16:48 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 28 01:16:48 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 28 01:16:48 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 28 01:16:48 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 28 01:16:48 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 28 01:16:48 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 28 01:16:48 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 28 01:16:48 node-2 kernel: [    0.000000] console [tty0] enabled
Sep 28 01:16:48 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 28 01:16:48 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 28 01:16:48 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 28 01:16:48 node-2 kernel: [    0.000000] hpet clockevent registered
Sep 28 01:16:48 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 28 01:16:48 node-2 kernel: [    0.004000] tsc: Detected 3492.217 MHz processor
Sep 28 01:16:48 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.43 BogoMIPS (lpj=13968868)
Sep 28 01:16:48 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 28 01:16:48 node-2 kernel: [    0.000045] Security Framework initialized
Sep 28 01:16:48 node-2 kernel: [    0.000062] AppArmor: AppArmor initialized
Sep 28 01:16:48 node-2 kernel: [    0.000064] Yama: becoming mindful.
Sep 28 01:16:48 node-2 kernel: [    0.001445] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.006369] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.008295] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.008323] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.008602] Initializing cgroup subsys memory
Sep 28 01:16:48 node-2 kernel: [    0.008609] Initializing cgroup subsys devices
Sep 28 01:16:48 node-2 kernel: [    0.008611] Initializing cgroup subsys freezer
Sep 28 01:16:48 node-2 kernel: [    0.008613] Initializing cgroup subsys blkio
Sep 28 01:16:48 node-2 kernel: [    0.008614] Initializing cgroup subsys perf_event
Sep 28 01:16:48 node-2 kernel: [    0.008617] Initializing cgroup subsys hugetlb
Sep 28 01:16:48 node-2 kernel: [    0.008636] CPU: Physical Processor ID: 0
Sep 28 01:16:48 node-2 kernel: [    0.008637] CPU: Processor Core ID: 0
Sep 28 01:16:48 node-2 kernel: [    0.008641] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 28 01:16:48 node-2 kernel: [    0.008641] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 28 01:16:48 node-2 kernel: [    0.009335] mce: CPU supports 22 MCE banks
Sep 28 01:16:48 node-2 kernel: [    0.009362] CPU0: Thermal monitoring enabled (TM1)
Sep 28 01:16:48 node-2 kernel: [    0.009383] process: using mwait in idle threads
Sep 28 01:16:48 node-2 kernel: [    0.009386] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 28 01:16:48 node-2 kernel: [    0.009386] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 28 01:16:48 node-2 kernel: [    0.009386] tlb_flushall_shift: 6
Sep 28 01:16:48 node-2 kernel: [    0.009475] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 28 01:16:48 node-2 kernel: [    0.010199] ACPI: Core revision 20131115
Sep 28 01:16:48 node-2 kernel: [    0.022878] ACPI: All ACPI Tables successfully acquired
Sep 28 01:16:48 node-2 kernel: [    0.023037] ftrace: allocating 28614 entries in 112 pages
Sep 28 01:16:48 node-2 kernel: [    0.031738] dmar: Host address width 46
Sep 28 01:16:48 node-2 kernel: [    0.031740] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 28 01:16:48 node-2 kernel: [    0.031746] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 28 01:16:48 node-2 kernel: [    0.031748] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 28 01:16:48 node-2 kernel: [    0.031752] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 28 01:16:48 node-2 kernel: [    0.031753] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 28 01:16:48 node-2 kernel: [    0.031754] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 28 01:16:48 node-2 kernel: [    0.031755] dmar: ATSR flags: 0x0
Sep 28 01:16:48 node-2 kernel: [    0.031757] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 28 01:16:48 node-2 kernel: [    0.031758] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 28 01:16:48 node-2 kernel: [    0.031873] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 28 01:16:48 node-2 kernel: [    0.031874] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 28 01:16:48 node-2 kernel: [    0.031875] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 28 01:16:48 node-2 kernel: [    0.031876] HPET id 0 under DRHD base 0xc7ffc000
Sep 28 01:16:48 node-2 kernel: [    0.031877] Your BIOS is broken and requested that x2apic be disabled.
Sep 28 01:16:48 node-2 kernel: [    0.031877] This will slightly decrease performance.
Sep 28 01:16:48 node-2 kernel: [    0.031877] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 28 01:16:48 node-2 kernel: [    0.032309] Enabled IRQ remapping in xapic mode
Sep 28 01:16:48 node-2 kernel: [    0.032310] x2apic not enabled, IRQ remapping is in xapic mode
Sep 28 01:16:48 node-2 kernel: [    0.032314] Switched APIC routing to physical flat.
Sep 28 01:16:48 node-2 kernel: [    0.032939] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 28 01:16:48 node-2 kernel: [    0.072592] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 28 01:16:48 node-2 kernel: [    0.072598] TSC deadline timer enabled
Sep 28 01:16:48 node-2 kernel: [    0.072605] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 28 01:16:48 node-2 kernel: [    0.072611] ... version:                3
Sep 28 01:16:48 node-2 kernel: [    0.072612] ... bit width:              48
Sep 28 01:16:48 node-2 kernel: [    0.072613] ... generic registers:      4
Sep 28 01:16:48 node-2 kernel: [    0.072614] ... value mask:             0000ffffffffffff
Sep 28 01:16:48 node-2 kernel: [    0.072615] ... max period:             0000ffffffffffff
Sep 28 01:16:48 node-2 kernel: [    0.072616] ... fixed-purpose events:   3
Sep 28 01:16:48 node-2 kernel: [    0.072617] ... event mask:             000000070000000f
Sep 28 01:16:48 node-2 kernel: [    0.073997] x86: Booting SMP configuration:
Sep 28 01:16:48 node-2 kernel: [    0.088124] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 28 01:16:48 node-2 kernel: [    0.073999] .... node  #0, CPUs:        #1  #2  #3
Sep 28 01:16:48 node-2 kernel: [    0.116040] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 28 01:16:48 node-2 kernel: [    0.270196] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 28 01:16:48 node-2 kernel: [    0.325867] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 28 01:16:48 node-2 kernel: [    0.382928] x86: Booted up 2 nodes, 16 CPUs
Sep 28 01:16:48 node-2 kernel: [    0.382932] smpboot: Total of 16 processors activated (111763.69 BogoMIPS)
Sep 28 01:16:48 node-2 kernel: [    0.407886] devtmpfs: initialized
Sep 28 01:16:48 node-2 kernel: [    0.410347] EVM: security.selinux
Sep 28 01:16:48 node-2 kernel: [    0.410348] EVM: security.SMACK64
Sep 28 01:16:48 node-2 kernel: [    0.410349] EVM: security.ima
Sep 28 01:16:48 node-2 kernel: [    0.410350] EVM: security.capability
Sep 28 01:16:48 node-2 kernel: [    0.410403] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.411059] pinctrl core: initialized pinctrl subsystem
Sep 28 01:16:48 node-2 kernel: [    0.411120] regulator-dummy: no parameters
Sep 28 01:16:48 node-2 kernel: [    0.411151] RTC time:  1:16:11, date: 09/28/16
Sep 28 01:16:48 node-2 kernel: [    0.411183] NET: Registered protocol family 16
Sep 28 01:16:48 node-2 kernel: [    0.411267] cpuidle: using governor ladder
Sep 28 01:16:48 node-2 kernel: [    0.411268] cpuidle: using governor menu
Sep 28 01:16:48 node-2 kernel: [    0.411302] ACPI: bus type PCI registered
Sep 28 01:16:48 node-2 kernel: [    0.411304] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 28 01:16:48 node-2 kernel: [    0.411348] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 28 01:16:48 node-2 kernel: [    0.411351] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 28 01:16:48 node-2 kernel: [    0.425104] PCI: Using configuration type 1 for base access
Sep 28 01:16:48 node-2 kernel: [    0.426105] bio: create slab <bio-0> at 0
Sep 28 01:16:48 node-2 kernel: [    0.426378] ACPI: Added _OSI(Module Device)
Sep 28 01:16:48 node-2 kernel: [    0.426380] ACPI: Added _OSI(Processor Device)
Sep 28 01:16:48 node-2 kernel: [    0.426381] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 28 01:16:48 node-2 kernel: [    0.426382] ACPI: Added _OSI(Processor Aggregator Device)
Sep 28 01:16:48 node-2 kernel: [    0.439138] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 28 01:16:48 node-2 kernel: [    0.450882] ACPI: Interpreter enabled
Sep 28 01:16:48 node-2 kernel: [    0.450887] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 28 01:16:48 node-2 kernel: [    0.450891] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 28 01:16:48 node-2 kernel: [    0.450894] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 28 01:16:48 node-2 kernel: [    0.450901] ACPI: (supports S0 S4 S5)
Sep 28 01:16:48 node-2 kernel: [    0.450902] ACPI: Using IOAPIC for interrupt routing
Sep 28 01:16:48 node-2 kernel: [    0.450944] HEST: Table parsing has been initialized.
Sep 28 01:16:48 node-2 kernel: [    0.450947] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 28 01:16:48 node-2 kernel: [    0.451505] ACPI: No dock devices found.
Sep 28 01:16:48 node-2 kernel: [    0.463173] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 28 01:16:48 node-2 kernel: [    0.463178] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 01:16:48 node-2 kernel: [    0.463181] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 28 01:16:48 node-2 kernel: [    0.463210] PCI host bridge to bus 0000:ff
Sep 28 01:16:48 node-2 kernel: [    0.463212] pci_bus 0000:ff: root bus resource [bus ff]
Sep 28 01:16:48 node-2 kernel: [    0.463221] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463259] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.463290] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463325] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463355] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.463384] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.463414] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463443] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463472] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463501] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463527] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463553] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463581] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463607] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463634] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463660] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463688] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463715] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463742] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.463770] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463795] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.463821] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463847] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463877] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.463911] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463942] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.463972] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464002] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464033] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464064] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464094] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464124] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464155] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464188] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464220] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464253] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464286] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464316] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464343] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464376] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464410] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464446] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464479] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464513] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464542] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464571] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464601] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464629] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464660] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464690] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464721] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464750] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464778] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464807] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464836] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464867] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464898] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.464959] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 28 01:16:48 node-2 kernel: [    0.464962] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 01:16:48 node-2 kernel: [    0.464965] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 28 01:16:48 node-2 kernel: [    0.464983] PCI host bridge to bus 0000:7f
Sep 28 01:16:48 node-2 kernel: [    0.464985] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 28 01:16:48 node-2 kernel: [    0.464990] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465017] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.465045] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465074] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465096] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.465121] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.465146] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465172] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465194] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465217] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465239] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465261] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465285] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465307] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465330] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465355] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465377] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465400] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465424] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.465447] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465469] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.465491] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465514] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465540] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 28 01:16:48 node-2 kernel: [    0.465572] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465599] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465625] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465651] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465676] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465702] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465727] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465755] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465779] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465805] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465831] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465857] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465886] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465911] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465938] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465967] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.465993] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466019] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466047] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466074] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466099] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466123] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466149] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466175] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466201] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466228] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466257] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466282] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466304] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466329] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466355] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466384] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.466409] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.467654] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 28 01:16:48 node-2 kernel: [    0.467657] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 01:16:48 node-2 kernel: [    0.468786] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 28 01:16:48 node-2 kernel: [    0.469294] PCI host bridge to bus 0000:00
Sep 28 01:16:48 node-2 kernel: [    0.469297] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 28 01:16:48 node-2 kernel: [    0.469299] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 28 01:16:48 node-2 kernel: [    0.469300] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 28 01:16:48 node-2 kernel: [    0.469301] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 28 01:16:48 node-2 kernel: [    0.469303] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 28 01:16:48 node-2 kernel: [    0.469304] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 28 01:16:48 node-2 kernel: [    0.469305] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 28 01:16:48 node-2 kernel: [    0.469311] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 28 01:16:48 node-2 kernel: [    0.469394] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.469425] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.469466] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 28 01:16:48 node-2 kernel: [    0.469485] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.469514] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.469555] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 28 01:16:48 node-2 kernel: [    0.469573] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.469603] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.469646] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 28 01:16:48 node-2 kernel: [    0.469664] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.469735] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.469814] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.469892] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 28 01:16:48 node-2 kernel: [    0.469897] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 28 01:16:48 node-2 kernel: [    0.469983] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 28 01:16:48 node-2 kernel: [    0.470130] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 28 01:16:48 node-2 kernel: [    0.470148] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 28 01:16:48 node-2 kernel: [    0.470226] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.470279] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 28 01:16:48 node-2 kernel: [    0.470302] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.470357] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.470400] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 28 01:16:48 node-2 kernel: [    0.470432] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.470488] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.470531] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 28 01:16:48 node-2 kernel: [    0.470557] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 28 01:16:48 node-2 kernel: [    0.470574] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 28 01:16:48 node-2 kernel: [    0.470652] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.470703] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 28 01:16:48 node-2 kernel: [    0.470730] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 28 01:16:48 node-2 kernel: [    0.470980] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 28 01:16:48 node-2 kernel: [    0.470985] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 28 01:16:48 node-2 kernel: [    0.470991] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.470997] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.471004] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 28 01:16:48 node-2 kernel: [    0.471035] pci 0000:01:00.0: supports D1 D2
Sep 28 01:16:48 node-2 kernel: [    0.480960] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 28 01:16:48 node-2 kernel: [    0.480966] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 28 01:16:48 node-2 kernel: [    0.480970] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 28 01:16:48 node-2 kernel: [    0.481186] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.481219] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 28 01:16:48 node-2 kernel: [    0.492955] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 28 01:16:48 node-2 kernel: [    0.492961] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.492965] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 01:16:48 node-2 kernel: [    0.493051] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.493124] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.493242] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.493288] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 28 01:16:48 node-2 kernel: [    0.493292] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.493293] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 01:16:48 node-2 kernel: [    0.493347] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.493469] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.493524] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 28 01:16:48 node-2 kernel: [    0.493526] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.493528] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.493577] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.493696] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.493739] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.493858] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.493895] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.494017] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.494053] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 28 01:16:48 node-2 kernel: [    0.494187] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 28 01:16:48 node-2 kernel: [    0.494229] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 28 01:16:48 node-2 kernel: [    0.494232] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.494234] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.494292] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 28 01:16:48 node-2 kernel: [    0.494355] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.494407] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.494449] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 28 01:16:48 node-2 kernel: [    0.494534] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 28 01:16:48 node-2 kernel: [    0.494640] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 28 01:16:48 node-2 kernel: [    0.494642] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.494644] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.494700] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 28 01:16:48 node-2 kernel: [    0.494753] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.494802] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.495016] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 28 01:16:48 node-2 kernel: [    0.495019] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 28 01:16:48 node-2 kernel: [    0.495083] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 28 01:16:48 node-2 kernel: [    0.495136] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.495218] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.495437] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 28 01:16:48 node-2 kernel: [    0.495440] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 28 01:16:48 node-2 kernel: [    0.495502] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 28 01:16:48 node-2 kernel: [    0.495566] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.495620] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 28 01:16:48 node-2 kernel: [    0.495847] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 28 01:16:48 node-2 kernel: [    0.495851] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 28 01:16:48 node-2 kernel: [    0.496028] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 28 01:16:48 node-2 kernel: [    0.496066] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 28 01:16:48 node-2 kernel: [    0.496142] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 28 01:16:48 node-2 kernel: [    0.496160] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 28 01:16:48 node-2 kernel: [    0.496173] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 28 01:16:48 node-2 kernel: [    0.496187] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 28 01:16:48 node-2 kernel: [    0.496237] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 28 01:16:48 node-2 kernel: [    0.504963] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 28 01:16:48 node-2 kernel: [    0.504968] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 28 01:16:48 node-2 kernel: [    0.504999] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 28 01:16:48 node-2 kernel: [    0.505510] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 28 01:16:48 node-2 kernel: [    0.505513] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 01:16:48 node-2 kernel: [    0.505638] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 28 01:16:48 node-2 kernel: [    0.505748] PCI host bridge to bus 0000:80
Sep 28 01:16:48 node-2 kernel: [    0.505750] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 28 01:16:48 node-2 kernel: [    0.505752] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 28 01:16:48 node-2 kernel: [    0.505753] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 28 01:16:48 node-2 kernel: [    0.505761] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.505825] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.505894] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 28 01:16:48 node-2 kernel: [    0.505957] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 28 01:16:48 node-2 kernel: [    0.505963] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 28 01:16:48 node-2 kernel: [    0.506037] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 28 01:16:48 node-2 kernel: [    0.506340] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 28 01:16:48 node-2 kernel: [    0.506372] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 28 01:16:48 node-2 kernel: [    0.506401] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 28 01:16:48 node-2 kernel: [    0.506431] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 28 01:16:48 node-2 kernel: [    0.506460] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 01:16:48 node-2 kernel: [    0.506490] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 01:16:48 node-2 kernel: [    0.506520] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 01:16:48 node-2 kernel: [    0.506550] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 01:16:48 node-2 kernel: [    0.506636] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 28 01:16:48 node-2 kernel: [    0.506641] ACPI: \_SB_.UNC1: notify handler is installed
Sep 28 01:16:48 node-2 kernel: [    0.506642] ACPI: \_SB_.UNC0: notify handler is installed
Sep 28 01:16:48 node-2 kernel: [    0.506657] ACPI: \_SB_.PCI0: notify handler is installed
Sep 28 01:16:48 node-2 kernel: [    0.506711] ACPI: \_SB_.PCI1: notify handler is installed
Sep 28 01:16:48 node-2 kernel: [    0.506791] Found 4 acpi root devices
Sep 28 01:16:48 node-2 kernel: [    0.506903] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 28 01:16:48 node-2 kernel: [    0.506906] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 28 01:16:48 node-2 kernel: [    0.506907] vgaarb: loaded
Sep 28 01:16:48 node-2 kernel: [    0.506909] vgaarb: bridge control possible 0000:0c:00.0
Sep 28 01:16:48 node-2 kernel: [    0.507032] SCSI subsystem initialized
Sep 28 01:16:48 node-2 kernel: [    0.507104] libata version 3.00 loaded.
Sep 28 01:16:48 node-2 kernel: [    0.507120] ACPI: bus type USB registered
Sep 28 01:16:48 node-2 kernel: [    0.507130] usbcore: registered new interface driver usbfs
Sep 28 01:16:48 node-2 kernel: [    0.507135] usbcore: registered new interface driver hub
Sep 28 01:16:48 node-2 kernel: [    0.507157] usbcore: registered new device driver usb
Sep 28 01:16:48 node-2 kernel: [    0.507336] PCI: Using ACPI for IRQ routing
Sep 28 01:16:48 node-2 kernel: [    0.510926] PCI: pci_cache_line_size set to 64 bytes
Sep 28 01:16:48 node-2 kernel: [    0.511138] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 28 01:16:48 node-2 kernel: [    0.511139] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 28 01:16:48 node-2 kernel: [    0.511140] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 28 01:16:48 node-2 kernel: [    0.511206] NetLabel: Initializing
Sep 28 01:16:48 node-2 kernel: [    0.511207] NetLabel:  domain hash size = 128
Sep 28 01:16:48 node-2 kernel: [    0.511208] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 28 01:16:48 node-2 kernel: [    0.511218] NetLabel:  unlabeled traffic allowed by default
Sep 28 01:16:48 node-2 kernel: [    0.511277] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 28 01:16:48 node-2 kernel: [    0.511281] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 28 01:16:48 node-2 kernel: [    0.513350] Switched to clocksource hpet
Sep 28 01:16:48 node-2 kernel: [    0.517755] AppArmor: AppArmor Filesystem Enabled
Sep 28 01:16:48 node-2 kernel: [    0.517794] pnp: PnP ACPI init
Sep 28 01:16:48 node-2 kernel: [    0.517806] ACPI: bus type PNP registered
Sep 28 01:16:48 node-2 kernel: [    0.517993] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518004] pnp 00:01: [dma 4]
Sep 28 01:16:48 node-2 kernel: [    0.518022] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518057] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518082] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518103] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518150] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518261] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518264] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 28 01:16:48 node-2 kernel: [    0.518266] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518267] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518268] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518270] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518273] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 28 01:16:48 node-2 kernel: [    0.518275] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518276] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518278] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518279] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518281] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518282] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 28 01:16:48 node-2 kernel: [    0.518285] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518385] pnp 00:07: [dma 0 disabled]
Sep 28 01:16:48 node-2 kernel: [    0.518418] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518500] pnp 00:08: [dma 0 disabled]
Sep 28 01:16:48 node-2 kernel: [    0.518535] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 28 01:16:48 node-2 kernel: [    0.518593] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 28 01:16:48 node-2 kernel: [    0.519040] pnp: PnP ACPI: found 10 devices
Sep 28 01:16:48 node-2 kernel: [    0.519042] ACPI: bus type PNP unregistered
Sep 28 01:16:48 node-2 kernel: [    0.525044] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 28 01:16:48 node-2 kernel: [    0.525048] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 28 01:16:48 node-2 kernel: [    0.525051] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 28 01:16:48 node-2 kernel: [    0.525056] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 28 01:16:48 node-2 kernel: [    0.525058] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525073] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525102] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 28 01:16:48 node-2 kernel: [    0.525117] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525160] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 28 01:16:48 node-2 kernel: [    0.525174] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 28 01:16:48 node-2 kernel: [    0.525207] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 28 01:16:48 node-2 kernel: [    0.525221] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 28 01:16:48 node-2 kernel: [    0.525250] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 28 01:16:48 node-2 kernel: [    0.525252] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525267] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525296] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 28 01:16:48 node-2 kernel: [    0.525298] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525313] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525345] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 28 01:16:48 node-2 kernel: [    0.525347] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525350] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525355] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 28 01:16:48 node-2 kernel: [    0.525357] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525359] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525364] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 28 01:16:48 node-2 kernel: [    0.525370] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 28 01:16:48 node-2 kernel: [    0.525379] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 28 01:16:48 node-2 kernel: [    0.525382] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 28 01:16:48 node-2 kernel: [    0.525390] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 28 01:16:48 node-2 kernel: [    0.525391] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 28 01:16:48 node-2 kernel: [    0.525392] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 28 01:16:48 node-2 kernel: [    0.525392] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 28 01:16:48 node-2 kernel: [    0.525393] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 28 01:16:48 node-2 kernel: [    0.525394] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 28 01:16:48 node-2 kernel: [    0.525395] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 28 01:16:48 node-2 kernel: [    0.525396] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 28 01:16:48 node-2 kernel: [    0.525397] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525398] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525399] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525400] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525401] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525402] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525403] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525404] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525405] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 28 01:16:48 node-2 kernel: [    0.525406] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525407] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 28 01:16:48 node-2 kernel: [    0.525409] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 28 01:16:48 node-2 kernel: [    0.525410] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 28 01:16:48 node-2 kernel: [    0.525411] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 28 01:16:48 node-2 kernel: [    0.525414] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 28 01:16:48 node-2 kernel: [    0.525415] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 28 01:16:48 node-2 kernel: [    0.525458] NET: Registered protocol family 2
Sep 28 01:16:48 node-2 kernel: [    0.525760] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.526135] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.526303] TCP: Hash tables configured (established 262144 bind 65536)
Sep 28 01:16:48 node-2 kernel: [    0.526348] TCP: reno registered
Sep 28 01:16:48 node-2 kernel: [    0.526389] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.526498] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.526665] NET: Registered protocol family 1
Sep 28 01:16:48 node-2 kernel: [    0.561446] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 28 01:16:48 node-2 kernel: [    0.561461] PCI: CLS 64 bytes, default 64
Sep 28 01:16:48 node-2 kernel: [    0.561547] Trying to unpack rootfs image as initramfs...
Sep 28 01:16:48 node-2 kernel: [    0.783182] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Sep 28 01:16:48 node-2 kernel: [    0.783239] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 28 01:16:48 node-2 kernel: [    0.783249] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 28 01:16:48 node-2 kernel: [    0.783747] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783754] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783761] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783768] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783777] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783786] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783797] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783804] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783812] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783819] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783826] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783833] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783839] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783847] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783853] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783860] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 01:16:48 node-2 kernel: [    0.783933] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 28 01:16:48 node-2 kernel: [    0.783936] Scanning for low memory corruption every 60 seconds
Sep 28 01:16:48 node-2 kernel: [    0.784258] Initialise system trusted keyring
Sep 28 01:16:48 node-2 kernel: [    0.784306] audit: initializing netlink socket (disabled)
Sep 28 01:16:48 node-2 kernel: [    0.784316] type=2000 audit(1475025371.732:1): initialized
Sep 28 01:16:48 node-2 kernel: [    0.802070] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 28 01:16:48 node-2 kernel: [    0.803529] zbud: loaded
Sep 28 01:16:48 node-2 kernel: [    0.803649] VFS: Disk quotas dquot_6.5.2
Sep 28 01:16:48 node-2 kernel: [    0.803690] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 28 01:16:48 node-2 kernel: [    0.804034] fuse init (API version 7.22)
Sep 28 01:16:48 node-2 kernel: [    0.804097] msgmni has been set to 32768
Sep 28 01:16:48 node-2 kernel: [    0.804144] Key type big_key registered
Sep 28 01:16:48 node-2 kernel: [    0.804652] Key type asymmetric registered
Sep 28 01:16:48 node-2 kernel: [    0.804654] Asymmetric key parser 'x509' registered
Sep 28 01:16:48 node-2 kernel: [    0.804677] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 28 01:16:48 node-2 kernel: [    0.804739] io scheduler noop registered
Sep 28 01:16:48 node-2 kernel: [    0.804741] io scheduler deadline registered (default)
Sep 28 01:16:48 node-2 kernel: [    0.804760] io scheduler cfq registered
Sep 28 01:16:48 node-2 kernel: [    0.805214] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    0.805449] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    0.805577] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    0.805695] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    0.805824] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    0.805916] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    0.806309] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 28 01:16:48 node-2 kernel: [    0.806334] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 28 01:16:48 node-2 kernel: [    0.806350] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 28 01:16:48 node-2 kernel: [    0.806363] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806365] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806368] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 28 01:16:48 node-2 kernel: [    0.806373] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806374] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806376] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806377] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806378] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806379] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806381] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806382] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806383] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806385] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806386] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806387] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806390] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 28 01:16:48 node-2 kernel: [    0.806400] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806403] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 28 01:16:48 node-2 kernel: [    0.806414] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806417] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 28 01:16:48 node-2 kernel: [    0.806427] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806429] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 28 01:16:48 node-2 kernel: [    0.806432] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 28 01:16:48 node-2 kernel: [    0.806458] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 28 01:16:48 node-2 kernel: [    0.806463] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 28 01:16:48 node-2 kernel: [    0.806467] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 28 01:16:48 node-2 kernel: [    0.806476] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 28 01:16:48 node-2 kernel: [    0.806512] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 28 01:16:48 node-2 kernel: [    0.806513] vesafb: scrolling: redraw
Sep 28 01:16:48 node-2 kernel: [    0.806515] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 28 01:16:48 node-2 kernel: [    0.827034] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 28 01:16:48 node-2 kernel: [    0.835527] Console: switching to colour frame buffer device 80x30
Sep 28 01:16:48 node-2 kernel: [    0.844197] fb0: VESA VGA frame buffer device
Sep 28 01:16:48 node-2 kernel: [    0.844396] intel_idle: MWAIT substates: 0x2120
Sep 28 01:16:48 node-2 kernel: [    0.844397] intel_idle: v0.4 model 0x3F
Sep 28 01:16:48 node-2 kernel: [    0.844398] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 28 01:16:48 node-2 kernel: [    0.844625] ipmi message handler version 39.2
Sep 28 01:16:48 node-2 kernel: [    0.844898] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 28 01:16:48 node-2 kernel: [    0.845340] ACPI: AC Adapter [P111] (on-line)
Sep 28 01:16:48 node-2 kernel: [    0.850564] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 28 01:16:48 node-2 kernel: [    0.861646] ACPI: Power Button [PWRB]
Sep 28 01:16:48 node-2 kernel: [    0.867524] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 28 01:16:48 node-2 kernel: [    0.879131] ACPI: Power Button [PWRF]
Sep 28 01:16:48 node-2 kernel: [    0.898917] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 28 01:16:48 node-2 kernel: [    0.910551] pstore: Registered erst as persistent store backend
Sep 28 01:16:48 node-2 kernel: [    0.916745] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 28 01:16:48 node-2 kernel: [    0.928712] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 28 01:16:48 node-2 kernel: [    0.955567] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 28 01:16:48 node-2 kernel: [    0.988820] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 28 01:16:48 node-2 kernel: [    1.002872] Linux agpgart interface v0.103
Sep 28 01:16:48 node-2 kernel: [    1.010535] brd: module loaded
Sep 28 01:16:48 node-2 kernel: [    1.017569] loop: module loaded
Sep 28 01:16:48 node-2 kernel: [    1.024260] libphy: Fixed MDIO Bus: probed
Sep 28 01:16:48 node-2 kernel: [    1.030718] tun: Universal TUN/TAP device driver, 1.6
Sep 28 01:16:48 node-2 kernel: [    1.037181] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 28 01:16:48 node-2 kernel: [    1.043684] PPP generic driver version 2.4.2
Sep 28 01:16:48 node-2 kernel: [    1.050083] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 28 01:16:48 node-2 kernel: [    1.056495] ehci-pci: EHCI PCI platform driver
Sep 28 01:16:48 node-2 kernel: [    1.063001] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 28 01:16:48 node-2 kernel: [    1.069397] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 28 01:16:48 node-2 kernel: [    1.081893] ehci-pci 0000:00:1a.0: debug port 2
Sep 28 01:16:48 node-2 kernel: [    1.092064] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 28 01:16:48 node-2 kernel: [    1.092083] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 28 01:16:48 node-2 kernel: [    1.108837] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 28 01:16:48 node-2 kernel: [    1.114896] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 28 01:16:48 node-2 kernel: [    1.121046] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 28 01:16:48 node-2 kernel: [    1.132902] usb usb1: Product: EHCI Host Controller
Sep 28 01:16:48 node-2 kernel: [    1.138916] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 28 01:16:48 node-2 kernel: [    1.144938] usb usb1: SerialNumber: 0000:00:1a.0
Sep 28 01:16:48 node-2 kernel: [    1.150908] hub 1-0:1.0: USB hub found
Sep 28 01:16:48 node-2 kernel: [    1.156653] hub 1-0:1.0: 2 ports detected
Sep 28 01:16:48 node-2 kernel: [    1.162433] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 28 01:16:48 node-2 kernel: [    1.167989] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 28 01:16:48 node-2 kernel: [    1.178969] ehci-pci 0000:00:1d.0: debug port 2
Sep 28 01:16:48 node-2 kernel: [    1.188290] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 28 01:16:48 node-2 kernel: [    1.188293] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 28 01:16:48 node-2 kernel: [    1.204756] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 28 01:16:48 node-2 kernel: [    1.209941] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 28 01:16:48 node-2 kernel: [    1.215228] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 28 01:16:48 node-2 kernel: [    1.225788] usb usb2: Product: EHCI Host Controller
Sep 28 01:16:48 node-2 kernel: [    1.231243] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 28 01:16:48 node-2 kernel: [    1.236778] usb usb2: SerialNumber: 0000:00:1d.0
Sep 28 01:16:48 node-2 kernel: [    1.242304] hub 2-0:1.0: USB hub found
Sep 28 01:16:48 node-2 kernel: [    1.247644] hub 2-0:1.0: 2 ports detected
Sep 28 01:16:48 node-2 kernel: [    1.252958] ehci-platform: EHCI generic platform driver
Sep 28 01:16:48 node-2 kernel: [    1.258194] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 28 01:16:48 node-2 kernel: [    1.263487] ohci-pci: OHCI PCI platform driver
Sep 28 01:16:48 node-2 kernel: [    1.268778] ohci-platform: OHCI generic platform driver
Sep 28 01:16:48 node-2 kernel: [    1.273966] uhci_hcd: USB Universal Host Controller Interface driver
Sep 28 01:16:48 node-2 kernel: [    1.279304] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 28 01:16:48 node-2 kernel: [    1.472536] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 28 01:16:48 node-2 kernel: [    1.644729] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 28 01:16:48 node-2 kernel: [    1.650245] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 28 01:16:48 node-2 kernel: [    1.655997] hub 1-1:1.0: USB hub found
Sep 28 01:16:48 node-2 kernel: [    1.661464] hub 1-1:1.0: 6 ports detected
Sep 28 01:16:48 node-2 kernel: [    1.776269] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 28 01:16:48 node-2 kernel: [    1.804243] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 28 01:16:48 node-2 kernel: [    2.044389] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 28 01:16:48 node-2 kernel: [    2.049948] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 28 01:16:48 node-2 kernel: [    2.055782] hub 2-1:1.0: USB hub found
Sep 28 01:16:48 node-2 kernel: [    2.061500] hub 2-1:1.0: 8 ports detected
Sep 28 01:16:48 node-2 kernel: [    2.320809] i8042: No controller found
Sep 28 01:16:48 node-2 kernel: [    2.326259] mousedev: PS/2 mouse device common for all mice
Sep 28 01:16:48 node-2 kernel: [    2.331798] rtc_cmos 00:02: RTC can wake from S4
Sep 28 01:16:48 node-2 kernel: [    2.337387] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 28 01:16:48 node-2 kernel: [    2.339865] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 28 01:16:48 node-2 kernel: [    2.348535] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 28 01:16:48 node-2 kernel: [    2.359636] device-mapper: uevent: version 1.0.3
Sep 28 01:16:48 node-2 kernel: [    2.365280] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 28 01:16:48 node-2 kernel: [    2.376499] ledtrig-cpu: registered to indicate activity on CPUs
Sep 28 01:16:48 node-2 kernel: [    2.382429] TCP: cubic registered
Sep 28 01:16:48 node-2 kernel: [    2.388316] NET: Registered protocol family 10
Sep 28 01:16:48 node-2 kernel: [    2.394306] NET: Registered protocol family 17
Sep 28 01:16:48 node-2 kernel: [    2.399974] Key type dns_resolver registered
Sep 28 01:16:48 node-2 kernel: [    2.405943] Loading compiled-in X.509 certificates
Sep 28 01:16:48 node-2 kernel: [    2.412110] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Sep 28 01:16:48 node-2 kernel: [    2.423484] registered taskstats version 1
Sep 28 01:16:48 node-2 kernel: [    2.431402] Key type trusted registered
Sep 28 01:16:48 node-2 kernel: [    2.438955] Key type encrypted registered
Sep 28 01:16:48 node-2 kernel: [    2.444415] AppArmor: AppArmor sha1 policy hashing enabled
Sep 28 01:16:48 node-2 kernel: [    2.449889] IMA: No TPM chip found, activating TPM-bypass!
Sep 28 01:16:48 node-2 kernel: [    2.456052] regulator-dummy: disabling
Sep 28 01:16:48 node-2 kernel: [    2.461599]   Magic number: 0:944:256
Sep 28 01:16:48 node-2 kernel: [    2.467093] acpi device:95: hash matches
Sep 28 01:16:48 node-2 kernel: [    2.472557] rtc_cmos 00:02: setting system clock to 2016-09-28 01:16:13 UTC (1475025373)
Sep 28 01:16:48 node-2 kernel: [    2.480875] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 28 01:16:48 node-2 kernel: [    2.480878] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 28 01:16:48 node-2 kernel: [    2.480880] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 28 01:16:48 node-2 kernel: [    2.480881] usb 2-1.4: Manufacturer: Avocent
Sep 28 01:16:48 node-2 kernel: [    2.480883] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 28 01:16:48 node-2 kernel: [    2.518890] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 28 01:16:48 node-2 kernel: [    2.524538] EDD information not available.
Sep 28 01:16:48 node-2 kernel: [    2.530082] PM: Hibernation image not present or could not be loaded.
Sep 28 01:16:48 node-2 kernel: [    2.530950] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 28 01:16:48 node-2 kernel: [    2.542119] Write protecting the kernel read-only data: 12288k
Sep 28 01:16:48 node-2 kernel: [    2.548251] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 28 01:16:48 node-2 kernel: [    2.560600] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 28 01:16:48 node-2 kernel: [    2.593057] device-mapper: multipath: version 1.6.0 loaded
Sep 28 01:16:48 node-2 kernel: [    2.601011] systemd-udevd[215]: starting version 204
Sep 28 01:16:48 node-2 kernel: [    2.623280] md: linear personality registered for level -1
Sep 28 01:16:48 node-2 kernel: [    2.637243] md: multipath personality registered for level -4
Sep 28 01:16:48 node-2 kernel: [    2.645199] md: raid0 personality registered for level 0
Sep 28 01:16:48 node-2 kernel: [    2.653538] md: raid1 personality registered for level 1
Sep 28 01:16:48 node-2 kernel: [    2.664086] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 28 01:16:48 node-2 kernel: [    2.670423] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 28 01:16:48 node-2 kernel: [    2.676722] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 28 01:16:48 node-2 kernel: [    2.678208] megasas: FW now in Ready state
Sep 28 01:16:48 node-2 kernel: [    2.678526] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.678580] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.678704] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.678866] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.679002] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.679070] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.679219] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.679380] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.679483] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.679839] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.680027] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.680142] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.680249] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.680376] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.680577] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.680682] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.681425] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 28 01:16:48 node-2 kernel: [    2.702406] hidraw: raw HID events driver (C) Jiri Kosina
Sep 28 01:16:48 node-2 kernel: [    2.710847] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 28 01:16:48 node-2 kernel: [    2.720323] usbcore: registered new interface driver usbhid
Sep 28 01:16:48 node-2 kernel: [    2.720324] usbhid: USB HID core driver
Sep 28 01:16:48 node-2 kernel: [    2.727525] raid6: sse2x1   10180 MB/s
Sep 28 01:16:48 node-2 kernel: [    2.743331] 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 28 01:16:48 node-2 kernel: [    2.756505] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 28 01:16:48 node-2 kernel: [    2.763245] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.763250] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.763253] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.763258] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.763306] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 28 01:16:48 node-2 kernel: [    2.786620] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 28 01:16:48 node-2 kernel: [    2.795537] raid6: sse2x2   14400 MB/s
Sep 28 01:16:48 node-2 kernel: [    2.805570] 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 28 01:16:48 node-2 kernel: [    2.818318] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 28 01:16:48 node-2 kernel: [    2.863361] raid6: sse2x4    9828 MB/s
Sep 28 01:16:48 node-2 kernel: [    2.935301] raid6: avx2x1   14954 MB/s
Sep 28 01:16:48 node-2 kernel: [    3.007234] raid6: avx2x2   18890 MB/s
Sep 28 01:16:48 node-2 kernel: [    3.079172] raid6: avx2x4   21329 MB/s
Sep 28 01:16:48 node-2 kernel: [    3.085037] raid6: using algorithm avx2x4 (21329 MB/s)
Sep 28 01:16:48 node-2 kernel: [    3.090931] raid6: using avx2x2 recovery algorithm
Sep 28 01:16:48 node-2 kernel: [    3.096901] Switched to clocksource tsc
Sep 28 01:16:48 node-2 kernel: [    3.096902] megasas:IOC Init cmd success
Sep 28 01:16:48 node-2 kernel: [    3.096964] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.097004] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.097046] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.097071] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.097104] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.097141] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.097271] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.109833] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 28 01:16:48 node-2 kernel: [    3.109834] 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 28 01:16:48 node-2 kernel: [    3.109835] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 28 01:16:48 node-2 kernel: [    3.109898] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.109934] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.109970] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.110006] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.110079] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.120239] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 28 01:16:48 node-2 kernel: [    3.120240] 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 28 01:16:48 node-2 kernel: [    3.120241] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 28 01:16:48 node-2 kernel: [    3.120311] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.120350] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.120391] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.120430] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.120517] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 28 01:16:48 node-2 kernel: [    3.123163] megasas: INIT adapter done
Sep 28 01:16:48 node-2 kernel: [    3.204905] 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 28 01:16:48 node-2 kernel: [    3.206018] 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 28 01:16:48 node-2 kernel: [    3.206878] 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 28 01:16:48 node-2 kernel: [    3.207831] 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 28 01:16:48 node-2 kernel: [    3.208811] 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 28 01:16:48 node-2 kernel: [    3.209699] 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 28 01:16:48 node-2 kernel: [    3.215077] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 28 01:16:48 node-2 kernel: [    3.215473] scsi0 : LSI SAS based MegaRAID driver
Sep 28 01:16:48 node-2 kernel: [    3.222825] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 28 01:16:48 node-2 kernel: [    3.223083] xor: automatically using best checksumming function:
Sep 28 01:16:48 node-2 kernel: [    3.233966] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 28 01:16:48 node-2 kernel: [    3.238210] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 28 01:16:48 node-2 kernel: [    3.238268] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 28 01:16:48 node-2 kernel: [    3.238524] sd 0:2:0:0: [sda] Write Protect is off
Sep 28 01:16:48 node-2 kernel: [    3.238525] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 28 01:16:48 node-2 kernel: [    3.238595] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 28 01:16:48 node-2 kernel: [    3.263020]    avx       : 37917.000 MB/sec
Sep 28 01:16:48 node-2 kernel: [    3.263923]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 28 01:16:48 node-2 kernel: [    3.265419] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 28 01:16:48 node-2 kernel: [    3.394077] async_tx: api initialized (async)
Sep 28 01:16:48 node-2 kernel: [    3.419001] md: raid6 personality registered for level 6
Sep 28 01:16:48 node-2 kernel: [    3.426076] md: raid5 personality registered for level 5
Sep 28 01:16:48 node-2 kernel: [    3.432902] md: raid4 personality registered for level 4
Sep 28 01:16:48 node-2 kernel: [    3.442518] md: raid10 personality registered for level 10
Sep 28 01:16:48 node-2 kernel: [    3.494696] multipathd (364): /proc/364/oom_adj is deprecated, please use /proc/364/oom_score_adj instead.
Sep 28 01:16:48 node-2 kernel: [    3.497137] random: lvm urandom read with 30 bits of entropy available
Sep 28 01:16:48 node-2 kernel: [    3.634330] bio: create slab <bio-1> at 1
Sep 28 01:16:48 node-2 kernel: [    4.569534] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 01:16:48 node-2 kernel: [    5.109548] random: nonblocking pool is initialized
Sep 28 01:16:48 node-2 kernel: [    5.286416] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 28 01:16:48 node-2 kernel: [    5.325023] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 28 01:16:48 node-2 kernel: [    5.462211] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 28 01:16:48 node-2 kernel: [    5.534035] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 28 01:16:48 node-2 kernel: [    5.591921] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 01:16:48 node-2 kernel: [    5.804899] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 28 01:16:48 node-2 kernel: [    5.888009] XFS (dm-1): Mounting Filesystem
Sep 28 01:16:48 node-2 kernel: [    6.203706] XFS (dm-1): Ending clean mount
Sep 28 01:16:48 node-2 kernel: [    6.250298] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 01:16:48 node-2 kernel: [    6.281344] XFS (dm-2): Mounting Filesystem
Sep 28 01:16:48 node-2 kernel: [    6.366431] XFS (dm-2): Ending clean mount
Sep 28 01:16:48 node-2 kernel: [    6.499341] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 01:16:48 node-2 kernel: [    8.145269] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 28 01:16:48 node-2 kernel: [    8.160053] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 28 01:16:48 node-2 kernel: [    8.305465] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 28 01:16:48 node-2 kernel: [    8.305470] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 28 01:16:48 node-2 kernel: [    8.305474] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 28 01:16:48 node-2 kernel: [    8.305478] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 28 01:16:48 node-2 kernel: [    8.337643] systemd-udevd[804]: starting version 204
Sep 28 01:16:48 node-2 kernel: [    8.511322] power_meter ACPI000D:00: Found ACPI power meter.
Sep 28 01:16:48 node-2 kernel: [    8.511363] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 28 01:16:48 node-2 kernel: [    8.518284] IPMI System Interface driver.
Sep 28 01:16:48 node-2 kernel: [    8.518415] ipmi_si: probing via ACPI
Sep 28 01:16:48 node-2 kernel: [    8.518433] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 28 01:16:48 node-2 kernel: [    8.518434] ipmi_si: Adding ACPI-specified kcs state machine
Sep 28 01:16:48 node-2 kernel: [    8.518465] wmi: Mapper loaded
Sep 28 01:16:48 node-2 kernel: [    8.518472] ipmi_si: probing via SMBIOS
Sep 28 01:16:48 node-2 kernel: [    8.518474] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 28 01:16:48 node-2 kernel: [    8.518474] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 28 01:16:48 node-2 kernel: [    8.518477] ipmi_si: probing via SPMI
Sep 28 01:16:48 node-2 kernel: [    8.518478] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 28 01:16:48 node-2 kernel: [    8.518478] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 28 01:16:48 node-2 kernel: [    8.518481] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 28 01:16:48 node-2 kernel: [    8.522618] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 28 01:16:48 node-2 kernel: [    8.522624] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 28 01:16:48 node-2 kernel: [    8.522627] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 28 01:16:48 node-2 kernel: [    8.522630] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 28 01:16:48 node-2 kernel: [    8.522698] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 28 01:16:48 node-2 kernel: [    8.533372] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 28 01:16:48 node-2 kernel: [    8.611001] systemd-udevd[822]: renamed network interface eth0 to enp6s0
Sep 28 01:16:48 node-2 kernel: [    8.638841] systemd-udevd[833]: renamed network interface eth2 to enp8s0
Sep 28 01:16:48 node-2 kernel: [    8.671295] systemd-udevd[827]: renamed network interface eth1 to enp7s0
Sep 28 01:16:48 node-2 kernel: [    8.693470] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 28 01:16:48 node-2 kernel: [    8.693476] ipmi_si 00:09: IPMI kcs interface initialized
Sep 28 01:16:48 node-2 kernel: [    8.694804] systemd-udevd[821]: renamed network interface eth3 to enp9s0
Sep 28 01:16:48 node-2 kernel: [    8.939497] type=1400 audit(1475025379.969:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1106 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.939650] type=1400 audit(1475025379.969:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1106 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.939776] type=1400 audit(1475025379.969:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1106 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.946584] type=1400 audit(1475025379.977:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1105 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.946729] type=1400 audit(1475025379.977:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1105 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.946847] type=1400 audit(1475025379.977:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1105 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.955046] type=1400 audit(1475025379.985:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1107 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.955193] type=1400 audit(1475025379.985:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1107 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.955309] type=1400 audit(1475025379.985:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1107 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    8.958169] type=1400 audit(1475025379.989:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1104 comm="apparmor_parser"
Sep 28 01:16:48 node-2 kernel: [    9.443753] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 28 01:16:48 node-2 kernel: [    9.444579] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 28 01:16:48 node-2 kernel: [    9.620507] enic 0000:06:00.0 enp6s0: Link UP
Sep 28 01:16:48 node-2 kernel: [    9.621031] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 28 01:16:48 node-2 kernel: [    9.621036] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 28 01:16:48 node-2 kernel: [   20.080490] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 28 01:16:49 node-2 failsafe: Failsafe of 120 seconds reached.
Sep 28 01:16:49 node-2 kernel: [   38.600649] init: failsafe main process (8456) killed by TERM signal
Sep 28 01:16:49 node-2 dbus[8494]: [system] AppArmor D-Bus mediation is enabled
Sep 28 01:16:50 node-2 kernel: [   38.847791] audit_printk_skb: 30 callbacks suppressed
Sep 28 01:16:50 node-2 kernel: [   38.847793] type=1400 audit(1475025410.001:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8581 comm="apparmor_parser"
Sep 28 01:16:50 node-2 kernel: [   38.847798] type=1400 audit(1475025410.001:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8581 comm="apparmor_parser"
Sep 28 01:16:50 node-2 kernel: [   38.847801] type=1400 audit(1475025410.001:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8581 comm="apparmor_parser"
Sep 28 01:16:50 node-2 kernel: [   38.848017] type=1400 audit(1475025410.001:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8581 comm="apparmor_parser"
Sep 28 01:16:50 node-2 kernel: [   38.848019] type=1400 audit(1475025410.001:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8581 comm="apparmor_parser"
Sep 28 01:16:50 node-2 kernel: [   38.848132] type=1400 audit(1475025410.001:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8581 comm="apparmor_parser"
Sep 28 01:16:50 node-2 kernel: [   38.849250] type=1400 audit(1475025410.005:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8582 comm="apparmor_parser"
Sep 28 01:16:50 node-2 kernel: [   38.914021] type=1400 audit(1475025410.069:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8584 comm="apparmor_parser"
Sep 28 01:16:50 node-2 anacron[8649]: Anacron 2.3 started on 2016-09-28
Sep 28 01:16:50 node-2 cron[8614]: (CRON) INFO (pidfile fd = 3)
Sep 28 01:16:50 node-2 cron[8656]: (CRON) STARTUP (fork ok)
Sep 28 01:16:50 node-2 anacron[8649]: Will run job `cron.daily' in 5 min.
Sep 28 01:16:50 node-2 anacron[8649]: Will run job `cron.weekly' in 10 min.
Sep 28 01:16:50 node-2 anacron[8649]: Will run job `cron.monthly' in 15 min.
Sep 28 01:16:50 node-2 anacron[8649]: Jobs will be executed sequentially
Sep 28 01:16:50 node-2 multipathd: path checkers start up
Sep 28 01:16:50 node-2 cron[8656]: (CRON) INFO (Running @reboot jobs)
Sep 28 01:16:50 node-2 postfix/master[8793]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 28 01:16:53 node-2 puppet-agent[8977]: Reopening log files
Sep 28 01:16:54 node-2 puppet-agent[8977]: Could not request certificate: Connection refused - connect(2)
Sep 28 01:17:01 node-2 CRON[9009]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 28 01:17:01 node-2 CRON[9010]: (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 28 01:17:05 node-2 puppet-user[9070]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 28 01:17:05 node-2 puppet-user[9070]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 28 01:17:06 node-2 puppet-user[9070]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 28 01:17:06 node-2 puppet-user[9070]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 28 01:17:06 node-2 puppet-user[9070]: Finished catalog run in 0.62 seconds
Sep 28 01:17:08 node-2 multipathd: uevent trigger error
Sep 28 01:17:08 node-2 puppet-user[9495]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 28 01:17:08 node-2 puppet-user[9495]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep 28 01:17:08 node-2 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 28 01:17:08 node-2 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 28 01:17:08 node-2 puppet-user[9495]: (/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 28 01:17:08 node-2 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 28 01:17:08 node-2 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 28 01:17:08 node-2 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 28 01:17:08 node-2 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 28 01:17:08 node-2 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 28 01:17:08 node-2 puppet-user[9495]: Finished catalog run in 0.07 seconds
Sep 28 01:17:09 node-2 puppet-user[9959]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 28 01:17:09 node-2 puppet-user[9959]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep 28 01:17:10 node-2 puppet-user[9959]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 28 01:17:10 node-2 puppet-user[9959]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 28 01:17:10 node-2 puppet-user[9959]: Finished catalog run in 0.03 seconds
Sep 28 01:17:11 node-2 puppet-user[10424]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 28 01:17:11 node-2 puppet-user[10424]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Sep 28 01:17:12 node-2 puppet-user[10424]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 28 01:17:12 node-2 puppet-user[10424]: Finished catalog run in 0.04 seconds
Sep 28 01:17:13 node-2 puppet-user[10956]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 28 01:17:14 node-2 puppet-user[10956]: Compiled catalog for node-2.domain.tld in environment production in 0.22 seconds
Sep 28 01:17:14 node-2 puppet-user[10956]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 28 01:17:14 node-2 kernel: [   63.093246] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 28 01:17:14 node-2 kernel: [   63.093294] 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 28 01:17:14 node-2 puppet-user[10956]: (/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 28 01:17:14 node-2 puppet-user[10956]: Finished catalog run in 0.05 seconds
Sep 28 01:17:15 node-2 puppet-user[11473]: (Scope(Class[main])) MODULAR: sync_time
Sep 28 01:17:15 node-2 puppet-user[11473]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Sep 28 01:17:15 node-2 ntpdate[11890]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 28 01:17:22 node-2 ntpdate[11890]: adjust time server 10.20.0.2 offset 0.001493 sec
Sep 28 01:17:22 node-2 puppet-user[11473]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 28 01:17:22 node-2 puppet-user[11473]: Finished catalog run in 6.19 seconds
Sep 28 01:17:22 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 28 01:17:22 node-2 nailgun-agent: D, [2016-09-28T01:17:01.473502 #9014] DEBUG -- : Sleep for 21 seconds before sending request
Sep 28 01:17:22 node-2 nailgun-agent: I, [2016-09-28T01:17:22.486630 #9014]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 28 01:17:22 node-2 nailgun-agent: D, [2016-09-28T01:17:22.859408 #9014] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep 28 01:17:27 node-2 puppet-user[12413]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 28 01:17:27 node-2 puppet-user[12413]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Sep 28 01:17:27 node-2 puppet-user[12413]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 28 01:17:27 node-2 puppet-user[12413]: Finished catalog run in 0.09 seconds
Sep 28 01:17:28 node-2 puppet-user[12872]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 28 01:17:29 node-2 puppet-user[12872]: Compiled catalog for node-2.domain.tld in environment production in 0.52 seconds
Sep 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:29 node-2 puppet-user[12872]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:29 node-2 puppet-user[12872]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:29 node-2 puppet-user[12872]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:29 node-2 puppet-user[12872]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 28 01:17:29 node-2 puppet-user[12872]: (/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 28 01:17:30 node-2 puppet-user[12872]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 28 01:17:30 node-2 puppet-user[12872]: Finished catalog run in 0.82 seconds
Sep 28 01:17:31 node-2 puppet-user[13383]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 28 01:17:32 node-2 puppet-user[13383]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.933285 #9014] DEBUG -- : Trying to find block devices
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.933357 #9014] DEBUG -- : Found block device: sda
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.933419 #9014] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.933443 #9014] DEBUG -- : Trying to get list of physical devices
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.933594 #9014] DEBUG -- : Getting udev properties for device: sda
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.935424 #9014] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc7884
Sep 28 01:17:34 node-2 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18399", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.935449 #9014] DEBUG -- : Trying to find out if device sda is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.935490 #9014] DEBUG -- : Device sda removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.935520 #9014] DEBUG -- : Device sda seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.935955 #9014] DEBUG -- : Getting udev properties for device: dm-0
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.937556 #9014] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-Z98MzM9H0YWgtulvZ02qPRTzBfewSOEDajmGVbZ7dn0XaZx2WG7b0gAFK2YeIVkY /dev/disk/by-uuid/14627932-1c25-4a74-8a43-45a2e5f522de /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-Z98MzM9H0YWgtulvZ02qPRTzBfewSOEDajmGVbZ7dn0XaZx2WG7b0gAFK2YeIVkY", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"14627932-1c25-4a74-8a43-45a2e5f522de", "ID_FS_UUID_ENC"=>"14627932-1c25-4a74-8a43-45a2e5f522de", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87
Sep 28 01:17:34 node-2 nailgun-agent: 542", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.937578 #9014] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.937620 #9014] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.937633 #9014] DEBUG -- : Device dm-0 seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.937661 #9014] DEBUG -- : Getting udev properties for device: dm-1
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.939212 #9014] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-aQQZYCIUz9k02XImRiyIqXfwjm16L1e0r3Ah6DB2Sw3nN35ZJFOSepOZcb4L8TTF /dev/disk/by-uuid/29ac0953-83ea-40b4-88f7-6acf71d972bf /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-aQQZYCIUz9k02XImRiyIqXfwjm16L1e0r3Ah6DB2Sw3nN35ZJFOSepOZcb4L8TTF", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"29ac0953-83ea-40b4-88f7-6acf71d972bf", "ID_FS_UUID_ENC"=>"29ac0953-83ea-40b4-88f7-6acf71d972bf", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8034", "nomdmonddf"=>"1", "nomdm
Sep 28 01:17:34 node-2 nailgun-agent: onisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.939278 #9014] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.939317 #9014] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.939330 #9014] DEBUG -- : Device dm-1 seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.939343 #9014] DEBUG -- : Getting udev properties for device: dm-2
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.940924 #9014] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-1buskWOkzU4LWXyIiuwxdiS3o7kOFYvB9sEbj3lG2vxe7CHuW4xsrnbkaL3nCcBY /dev/disk/by-uuid/2252e5d9-9fc2-4329-a8dc-fafa5b37d15a /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-1buskWOkzU4LWXyIiuwxdiS3o7kOFYvB9sEbj3lG2vxe7CHuW4xsrnbkaL3nCcBY", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2252e5d9-9fc2-4329-a8dc-fafa5b37d15a", "ID_FS_UUID_ENC"=>"2252e5d9-9fc2-4329-a8dc-fafa5b37d15a", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29
Sep 28 01:17:34 node-2 nailgun-agent: 461", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.940947 #9014] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.940986 #9014] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.940998 #9014] DEBUG -- : Device dm-2 seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.941012 #9014] DEBUG -- : Getting udev properties for device: dm-3
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.942598 #9014] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-yZYcTdWcDv8Kf34eAmglmUw7Ag19o9YyRbqV9oPa6ZId1B9gMESseVANS4LIq8nU /dev/disk/by-uuid/8d53bcb6-c706-4cdc-b59a-ee85bc90dded /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-yZYcTdWcDv8Kf34eAmglmUw7Ag19o9YyRbqV9oPa6ZId1B9gMESseVANS4LIq8nU", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8d53bcb6-c706-4cdc-b59a-ee85bc90dded", "ID_FS_UUID_ENC"=>"8d53bcb6-c706-4cdc-b59a-ee85bc90dded", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33106", "nomdmond
Sep 28 01:17:34 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.942621 #9014] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.942652 #9014] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.942689 #9014] DEBUG -- : Device dm-3 seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.942713 #9014] DEBUG -- : Getting udev properties for device: dm-4
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.944235 #9014] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-xteBx7OJBt6Nfb6gSYMrpYYSpdfTl60Hs7xRDNPZS8BZMZTRfTPstQe4d9GFJ6qy /dev/disk/by-uuid/232d5b92-b42c-40ed-9516-5c6200ccaa96 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-xteBx7OJBt6Nfb6gSYMrpYYSpdfTl60Hs7xRDNPZS8BZMZTRfTPstQe4d9GFJ6qy", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"232d5b92-b42c-40ed-9516-5c6200ccaa96", "ID_FS_UUID_ENC"=>"232d5b92-b42c-40ed-9516-5c6200ccaa96", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36920", "nomdmonddf"=>"1", 
Sep 28 01:17:34 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.944259 #9014] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.944287 #9014] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.944300 #9014] DEBUG -- : Device dm-4 seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.944336 #9014] DEBUG -- : Getting udev properties for device: dm-5
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.945873 #9014] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-coOoahF9s7fpn8yCCgaBJ5bpGZhy6Azt9fxKYibwW1uhNGauaZQYnXBY4WOZTovF /dev/disk/by-uuid/1c4b4239-f827-4c53-b9f6-db3ad33917a8 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-coOoahF9s7fpn8yCCgaBJ5bpGZhy6Azt9fxKYibwW1uhNGauaZQYnXBY4WOZTovF", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1c4b4239-f827-4c53-b9f6-db3ad33917a8", "ID_FS_UUID_ENC"=>"1c4b4239-f827-4c53-b9f6-db3ad33917a8", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32156", "nomdmonddf"=>"1", "nomd
Sep 28 01:17:34 node-2 nailgun-agent: monisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.945896 #9014] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.945979 #9014] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.945993 #9014] DEBUG -- : Device dm-5 seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.946007 #9014] DEBUG -- : Getting udev properties for device: dm-6
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.947579 #9014] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-coOoahF9s7fpn8yCCgaBJ5bpGZhy6AztO5Wj2vCeMNse1ftKLdrfXK3a4MF50sJo /dev/disk/by-uuid/7b3d5c04-1798-4395-adc2-37e26a286d4c /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-coOoahF9s7fpn8yCCgaBJ5bpGZhy6AztO5Wj2vCeMNse1ftKLdrfXK3a4MF50sJo", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"7b3d5c04-1798-4395-adc2-37e26a286d4c", "ID_FS_UUID_ENC"=>"7b3d5c04-1798-4395-adc2-37e26a286d4c", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32462", "nomdmonddf"=>"1", "nomdmonisw"
Sep 28 01:17:34 node-2 nailgun-agent: =>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.947601 #9014] DEBUG -- : Trying to find out if device dm-6 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.947640 #9014] DEBUG -- : Device dm-6 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.947674 #9014] DEBUG -- : Device dm-6 seems to be appropriate
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.947687 #9014] DEBUG -- : Getting udev properties for device: ram0
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.949116 #9014] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33937", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.949150 #9014] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.949192 #9014] DEBUG -- : Device ram0 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.949210 #9014] DEBUG -- : Getting udev properties for device: ram1
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.950617 #9014] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33955", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.950650 #9014] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.950707 #9014] DEBUG -- : Device ram1 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.950727 #9014] DEBUG -- : Getting udev properties for device: ram2
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.952173 #9014] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34245", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.952199 #9014] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.952232 #9014] DEBUG -- : Device ram2 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.952252 #9014] DEBUG -- : Getting udev properties for device: ram3
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.953655 #9014] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34265", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.953680 #9014] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.953732 #9014] DEBUG -- : Device ram3 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.953752 #9014] DEBUG -- : Getting udev properties for device: ram4
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.955147 #9014] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34505", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.955173 #9014] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.955228 #9014] DEBUG -- : Device ram4 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.955249 #9014] DEBUG -- : Getting udev properties for device: ram5
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.956661 #9014] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34525", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.956686 #9014] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.956720 #9014] DEBUG -- : Device ram5 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.956742 #9014] DEBUG -- : Getting udev properties for device: ram6
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.958130 #9014] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34644", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.958155 #9014] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.958189 #9014] DEBUG -- : Device ram6 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.958208 #9014] DEBUG -- : Getting udev properties for device: ram7
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.959673 #9014] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34665", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.959698 #9014] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.959737 #9014] DEBUG -- : Device ram7 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.959757 #9014] DEBUG -- : Getting udev properties for device: ram8
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.961180 #9014] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34681", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.961205 #9014] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.961240 #9014] DEBUG -- : Device ram8 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.961271 #9014] DEBUG -- : Getting udev properties for device: ram9
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.962674 #9014] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34695", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.962699 #9014] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.962733 #9014] DEBUG -- : Device ram9 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.962778 #9014] DEBUG -- : Getting udev properties for device: loop0
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.964182 #9014] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33743", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.964207 #9014] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.964256 #9014] DEBUG -- : Device loop0 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.964283 #9014] DEBUG -- : Getting udev properties for device: loop1
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.965652 #9014] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33758", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.965673 #9014] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.965713 #9014] DEBUG -- : Device loop1 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.965760 #9014] DEBUG -- : Getting udev properties for device: loop2
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.967134 #9014] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33772", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.967169 #9014] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.967219 #9014] DEBUG -- : Device loop2 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.967239 #9014] DEBUG -- : Getting udev properties for device: loop3
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.968611 #9014] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33786", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.968632 #9014] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.968667 #9014] DEBUG -- : Device loop3 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.968699 #9014] DEBUG -- : Getting udev properties for device: loop4
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.970088 #9014] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33800", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.970109 #9014] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.970140 #9014] DEBUG -- : Device loop4 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.970175 #9014] DEBUG -- : Getting udev properties for device: loop5
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.971575 #9014] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33812", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.971610 #9014] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.971668 #9014] DEBUG -- : Device loop5 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.971690 #9014] DEBUG -- : Getting udev properties for device: loop6
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.973100 #9014] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33827", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.973123 #9014] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.973193 #9014] DEBUG -- : Device loop6 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.973212 #9014] DEBUG -- : Getting udev properties for device: loop7
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.974642 #9014] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33841", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.974665 #9014] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.974696 #9014] DEBUG -- : Device loop7 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.974720 #9014] DEBUG -- : Getting udev properties for device: ram10
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.976117 #9014] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33968", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.976139 #9014] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.976171 #9014] DEBUG -- : Device ram10 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.976204 #9014] DEBUG -- : Getting udev properties for device: ram11
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.977583 #9014] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33983", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.977604 #9014] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.977658 #9014] DEBUG -- : Device ram11 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.977676 #9014] DEBUG -- : Getting udev properties for device: ram12
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.979101 #9014] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34082", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.979126 #9014] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.979177 #9014] DEBUG -- : Device ram12 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.979218 #9014] DEBUG -- : Getting udev properties for device: ram13
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.985122 #9014] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34104", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.985151 #9014] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.985203 #9014] DEBUG -- : Device ram13 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.985223 #9014] DEBUG -- : Getting udev properties for device: ram14
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.986802 #9014] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34121", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.986863 #9014] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.986905 #9014] DEBUG -- : Device ram14 removable parameter: "0"
Sep 28 01:17:34 node-2 nailgun-agent: D, [2016-09-28T01:17:34.986923 #9014] DEBUG -- : Getting udev properties for device: ram15
Sep 28 01:17:35 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988279 #9014] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34228", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988348 #9014] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988392 #9014] DEBUG -- : Device ram15 removable parameter: "0"
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988426 #9014] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988440 #9014] DEBUG -- : Block device seems to be physical data storage: sda
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988488 #9014] DEBUG -- : Found block device: dm-0
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988501 #9014] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988514 #9014] DEBUG -- : Found block device: dm-1
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988524 #9014] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988533 #9014] DEBUG -- : Found block device: dm-2
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988582 #9014] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988593 #9014] DEBUG -- : Found block device: dm-3
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988603 #9014] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988612 #9014] DEBUG -- : Found block device: dm-4
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988622 #9014] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988630 #9014] DEBUG -- : Found block device: dm-5
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988640 #9014] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988649 #9014] DEBUG -- : Found block device: dm-6
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988659 #9014] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988668 #9014] DEBUG -- : Found block device: ram0
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988710 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988719 #9014] DEBUG -- : Found block device: ram1
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988728 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988737 #9014] DEBUG -- : Found block device: ram2
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988748 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988757 #9014] DEBUG -- : Found block device: ram3
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988767 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988775 #9014] DEBUG -- : Found block device: ram4
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988785 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988828 #9014] DEBUG -- : Found block device: ram5
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988839 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988848 #9014] DEBUG -- : Found block device: ram6
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988857 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988865 #9014] DEBUG -- : Found block device: ram7
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988874 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988883 #9014] DEBUG -- : Found block device: ram8
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988892 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988900 #9014] DEBUG -- : Found block device: ram9
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988945 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988955 #9014] DEBUG -- : Found block device: loop0
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988966 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988974 #9014] DEBUG -- : Found block device: loop1
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988983 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.988991 #9014] DEBUG -- : Found block device: loop2
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989001 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989009 #9014] DEBUG -- : Found block device: loop3
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989019 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989028 #9014] DEBUG -- : Found block device: loop4
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989074 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989083 #9014] DEBUG -- : Found block device: loop5
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989093 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989102 #9014] DEBUG -- : Found block device: loop6
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989112 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989120 #9014] DEBUG -- : Found block device: loop7
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989129 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989137 #9014] DEBUG -- : Found block device: ram10
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989148 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989189 #9014] DEBUG -- : Found block device: ram11
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989200 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989209 #9014] DEBUG -- : Found block device: ram12
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989219 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989228 #9014] DEBUG -- : Found block device: ram13
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989237 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989246 #9014] DEBUG -- : Found block device: ram14
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989256 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989264 #9014] DEBUG -- : Found block device: ram15
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989303 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:34.989332 #9014] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:35.077100 #9014] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep 28 01:17:35 node-2 nailgun-agent: D, [2016-09-28T01:17:35.077161 #9014] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 28 01:17:35 node-2 puppet-user[13383]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 28 01:17:38 node-2 kernel: [   86.886274] init: plymouth-upstart-bridge main process ended, respawning
Sep 28 01:17:38 node-2 puppet-agent[8977]: Could not run: SIGTERM
Sep 28 01:17:38 node-2 kernel: [   87.192137] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 28 01:17:38 node-2 ec2: 
Sep 28 01:17:38 node-2 ec2: #############################################################
Sep 28 01:17:38 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 28 01:17:38 node-2 ec2: 1024 15:95:f7:e9:44:e1:e9:27:7e:26:16:3c:24:54:f9:53  root@node-2.domain.tld (DSA)
Sep 28 01:17:38 node-2 ec2: 256 8f:4d:a8:35:6d:2b:56:8f:4f:1e:29:4d:de:49:36:98  root@node-2.domain.tld (ECDSA)
Sep 28 01:17:38 node-2 ec2: 256 7f:52:9c:84:b1:c3:33:3c:d9:af:c6:38:c1:43:a4:5e  root@node-2.domain.tld (ED25519)
Sep 28 01:17:38 node-2 ec2: 2048 e2:d1:d0:31:94:c6:bb:da:24:9d:3e:a6:8b:5b:7d:ab  root@node-2.domain.tld (RSA)
Sep 28 01:17:38 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 28 01:17:38 node-2 ec2: #############################################################
Sep 28 01:17:47 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143095 #9014] DEBUG -- : Trying to find block devices
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143216 #9014] DEBUG -- : Found block device: sda
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143243 #9014] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143263 #9014] DEBUG -- : Block device seems to be physical data storage: sda
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143295 #9014] DEBUG -- : Found block device: dm-0
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143309 #9014] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143320 #9014] DEBUG -- : Found block device: dm-1
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143330 #9014] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143339 #9014] DEBUG -- : Found block device: dm-2
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143349 #9014] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143385 #9014] DEBUG -- : Found block device: dm-3
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143396 #9014] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143405 #9014] DEBUG -- : Found block device: dm-4
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143416 #9014] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143424 #9014] DEBUG -- : Found block device: dm-5
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143434 #9014] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143442 #9014] DEBUG -- : Found block device: dm-6
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143452 #9014] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143460 #9014] DEBUG -- : Found block device: ram0
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143494 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143505 #9014] DEBUG -- : Found block device: ram1
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143514 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143522 #9014] DEBUG -- : Found block device: ram2
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143532 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143540 #9014] DEBUG -- : Found block device: ram3
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143549 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143557 #9014] DEBUG -- : Found block device: ram4
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143566 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143598 #9014] DEBUG -- : Found block device: ram5
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143608 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143616 #9014] DEBUG -- : Found block device: ram6
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143625 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143633 #9014] DEBUG -- : Found block device: ram7
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143643 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143651 #9014] DEBUG -- : Found block device: ram8
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143660 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143668 #9014] DEBUG -- : Found block device: ram9
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143677 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143707 #9014] DEBUG -- : Found block device: loop0
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143717 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143725 #9014] DEBUG -- : Found block device: loop1
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143735 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143743 #9014] DEBUG -- : Found block device: loop2
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143752 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143760 #9014] DEBUG -- : Found block device: loop3
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143769 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143777 #9014] DEBUG -- : Found block device: loop4
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143786 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143810 #9014] DEBUG -- : Found block device: loop5
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143820 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143828 #9014] DEBUG -- : Found block device: loop6
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143838 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143846 #9014] DEBUG -- : Found block device: loop7
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143855 #9014] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143884 #9014] DEBUG -- : Found block device: ram10
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143894 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143902 #9014] DEBUG -- : Found block device: ram11
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143911 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143919 #9014] DEBUG -- : Found block device: ram12
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143928 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143937 #9014] DEBUG -- : Found block device: ram13
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143966 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143975 #9014] DEBUG -- : Found block device: ram14
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143984 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.143993 #9014] DEBUG -- : Found block device: ram15
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.144002 #9014] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.144030 #9014] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Sep 28 01:17:47 node-2 nailgun-agent: D, [2016-09-28T01:17:47.302237 #9014] DEBUG -- : Response: status: 200 body: {"id": 2}
Sep 28 01:17:47 node-2 nailgun-agent: I, [2016-09-28T01:17:47.302420 #9014]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep 28 01:18:01 node-2 CRON[16204]: (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 28 01:18:03 node-2 puppet-user[13383]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 28 01:18:03 node-2 puppet-user[13383]: Finished catalog run in 30.82 seconds
Sep 28 01:18:04 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 28 01:18:04 node-2 nailgun-agent: I, [2016-09-28T01:18:04.478760 #16207]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 28 01:18:04 node-2 puppet-user[16306]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 28 01:18:05 node-2 puppet-user[16306]: Compiled catalog for node-2.domain.tld in environment production in 0.60 seconds
Sep 28 01:18:05 node-2 puppet-user[16306]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 28 01:18:05 node-2 puppet-user[16306]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 28 01:18:05 node-2 puppet-user[16306]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 28 01:18:05 node-2 puppet-user[16306]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 28 01:18:05 node-2 puppet-user[16306]: Finished catalog run in 0.09 seconds
Sep 28 01:18:07 node-2 puppet-user[16899]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 28 01:18:08 node-2 puppet-user[16899]: Compiled catalog for node-2.domain.tld in environment production in 0.88 seconds
Sep 28 01:18:08 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 28 01:18:08 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 28 01:18:08 node-2 crontab[17351]: (root) LIST (root)
Sep 28 01:18:08 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 28 01:18:08 node-2 crontab[17352]: (root) REPLACE (root)
Sep 28 01:18:09 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 28 01:18:10 node-2 puppet-user[16899]: (/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 28 01:18:10 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 28 01:18:11 node-2 puppet-user[16899]: (/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 28 01:18:11 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8428" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 01:18:11 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 28 01:18:13 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:13 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:13 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:13 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:18:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:22 node-2 ntpdate[27999]: no servers can be used, exiting
<27>Sep 28 01:19:22 node-2 ntpdate[28094]: no servers can be used, exiting
<27>Sep 28 01:19:22 node-2 ntpdate[28272]: no servers can be used, exiting
<27>Sep 28 01:19:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:19:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:08 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:08 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:08 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:08 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:08 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:11 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:11 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:11 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:11 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:11 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:11 node-2 multipathd: uevent trigger error
<27>Sep 28 01:20:11 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:18 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 28 01:21:18 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 28 01:21:24 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 28 01:21:24 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 28 01:21:30 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 28 01:21:35 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 28 01:21:35 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 28 01:21:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:21:55 node-2 multipathd: uevent trigger error
<129>Sep 28 01:21:57 node-2 haproxy[15727]: 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 28 01:21:58 node-2 haproxy[15731]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:21:59 node-2 haproxy[15731]: 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 28 01:21:59 node-2 haproxy[15731]: proxy mysqld has no server available!
<27>Sep 28 01:22:01 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:01 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:01 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:01 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:01 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:04 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:07 node-2 haproxy[18412]: 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 28 01:22:07 node-2 haproxy[18412]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:07 node-2 haproxy[18412]: 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 28 01:22:07 node-2 haproxy[18412]: proxy mysqld has no server available!
<129>Sep 28 01:22:08 node-2 haproxy[18421]: 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 28 01:22:08 node-2 haproxy[18421]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:08 node-2 haproxy[18421]: 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 28 01:22:08 node-2 haproxy[18421]: proxy object-storage has no server available!
<27>Sep 28 01:22:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:10 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:12 node-2 haproxy[19761]: 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 28 01:22:12 node-2 haproxy[19761]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:12 node-2 haproxy[19761]: 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 28 01:22:12 node-2 haproxy[19761]: proxy neutron has no server available!
<129>Sep 28 01:22:13 node-2 haproxy[19766]: 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 28 01:22:13 node-2 haproxy[19766]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:13 node-2 haproxy[19766]: 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 28 01:22:13 node-2 haproxy[19766]: proxy mysqld has no server available!
<129>Sep 28 01:22:13 node-2 haproxy[19766]: 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 28 01:22:13 node-2 haproxy[19766]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:14 node-2 haproxy[19766]: 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 28 01:22:14 node-2 haproxy[19766]: proxy object-storage has no server available!
<27>Sep 28 01:22:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:15 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:17 node-2 haproxy[21325]: 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 28 01:22:18 node-2 haproxy[21329]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:18 node-2 haproxy[21329]: 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 28 01:22:18 node-2 haproxy[21329]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:18 node-2 haproxy[21329]: 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 28 01:22:18 node-2 haproxy[21329]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:18 node-2 haproxy[21329]: 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 28 01:22:18 node-2 haproxy[21329]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:18 node-2 haproxy[21329]: 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 28 01:22:18 node-2 haproxy[21329]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:19 node-2 haproxy[21329]: 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 28 01:22:19 node-2 haproxy[21329]: proxy neutron has no server available!
<129>Sep 28 01:22:19 node-2 haproxy[21329]: 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 28 01:22:19 node-2 haproxy[21329]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:19 node-2 haproxy[21329]: 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 28 01:22:19 node-2 haproxy[21329]: proxy mysqld has no server available!
<129>Sep 28 01:22:19 node-2 haproxy[21329]: 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 28 01:22:19 node-2 haproxy[21329]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:19 node-2 haproxy[21329]: 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 28 01:22:19 node-2 haproxy[21329]: proxy object-storage has no server available!
<27>Sep 28 01:22:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:21 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:23 node-2 haproxy[22672]: 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 28 01:22:23 node-2 haproxy[22672]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:23 node-2 haproxy[22672]: 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 28 01:22:23 node-2 haproxy[22672]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:23 node-2 haproxy[22672]: 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 28 01:22:23 node-2 haproxy[22672]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:23 node-2 haproxy[22672]: 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 28 01:22:23 node-2 haproxy[22672]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:23 node-2 haproxy[22672]: 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 28 01:22:24 node-2 haproxy[22678]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:24 node-2 haproxy[22678]: 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 28 01:22:24 node-2 haproxy[22678]: proxy neutron has no server available!
<129>Sep 28 01:22:24 node-2 haproxy[22678]: 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 28 01:22:24 node-2 haproxy[22678]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:24 node-2 haproxy[22678]: 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 28 01:22:24 node-2 haproxy[22678]: proxy mysqld has no server available!
<129>Sep 28 01:22:24 node-2 haproxy[22678]: 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 28 01:22:24 node-2 haproxy[22678]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:24 node-2 haproxy[22678]: 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 28 01:22:24 node-2 haproxy[22678]: proxy object-storage has no server available!
<129>Sep 28 01:22:24 node-2 haproxy[22678]: 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 28 01:22:25 node-2 haproxy[22678]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:25 node-2 haproxy[22678]: 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 28 01:22:25 node-2 haproxy[22678]: proxy aodh has no server available!
<27>Sep 28 01:22:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:26 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:28 node-2 haproxy[24013]: 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 28 01:22:28 node-2 haproxy[24013]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:29 node-2 haproxy[24017]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:29 node-2 haproxy[24017]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:29 node-2 haproxy[24017]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:29 node-2 haproxy[24017]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:29 node-2 haproxy[24017]: proxy neutron has no server available!
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:29 node-2 haproxy[24017]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:29 node-2 haproxy[24017]: proxy mysqld has no server available!
<129>Sep 28 01:22:29 node-2 haproxy[24017]: 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 28 01:22:30 node-2 haproxy[24017]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:30 node-2 haproxy[24017]: 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 28 01:22:30 node-2 haproxy[24017]: proxy object-storage has no server available!
<129>Sep 28 01:22:30 node-2 haproxy[24017]: 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 28 01:22:30 node-2 haproxy[24017]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:30 node-2 haproxy[24017]: 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 28 01:22:30 node-2 haproxy[24017]: proxy aodh has no server available!
<129>Sep 28 01:22:30 node-2 haproxy[24017]: 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 28 01:22:30 node-2 haproxy[24017]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:30 node-2 haproxy[24017]: 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 28 01:22:30 node-2 haproxy[24017]: proxy ceilometer has no server available!
<27>Sep 28 01:22:32 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:32 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:32 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:32 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:32 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:34 node-2 haproxy[25365]: 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 28 01:22:34 node-2 haproxy[25365]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:34 node-2 haproxy[25365]: 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 28 01:22:34 node-2 haproxy[25365]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:34 node-2 haproxy[25365]: 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 28 01:22:34 node-2 haproxy[25365]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:34 node-2 haproxy[25365]: 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 28 01:22:34 node-2 haproxy[25365]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:34 node-2 haproxy[25365]: 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 28 01:22:34 node-2 haproxy[25365]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:34 node-2 haproxy[25365]: 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 28 01:22:34 node-2 haproxy[25365]: proxy neutron has no server available!
<129>Sep 28 01:22:35 node-2 haproxy[25369]: 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 28 01:22:35 node-2 haproxy[25369]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:35 node-2 haproxy[25369]: 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 28 01:22:35 node-2 haproxy[25369]: proxy mysqld has no server available!
<129>Sep 28 01:22:35 node-2 haproxy[25369]: 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 28 01:22:35 node-2 haproxy[25369]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:35 node-2 haproxy[25369]: 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 28 01:22:35 node-2 haproxy[25369]: proxy object-storage has no server available!
<129>Sep 28 01:22:35 node-2 haproxy[25369]: 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 28 01:22:35 node-2 haproxy[25369]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:35 node-2 haproxy[25369]: 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 28 01:22:35 node-2 haproxy[25369]: proxy aodh has no server available!
<129>Sep 28 01:22:35 node-2 haproxy[25369]: 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 28 01:22:35 node-2 haproxy[25369]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:36 node-2 haproxy[25369]: 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 28 01:22:36 node-2 haproxy[25369]: proxy ceilometer has no server available!
<27>Sep 28 01:22:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:37 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:39 node-2 haproxy[26728]: 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 28 01:22:39 node-2 haproxy[26728]: 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 28 01:22:39 node-2 haproxy[26728]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:39 node-2 haproxy[26728]: 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 28 01:22:39 node-2 haproxy[26728]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: proxy neutron has no server available!
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: proxy mysqld has no server available!
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:40 node-2 haproxy[26738]: 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 28 01:22:40 node-2 haproxy[26738]: proxy object-storage has no server available!
<129>Sep 28 01:22:41 node-2 haproxy[26738]: 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 28 01:22:41 node-2 haproxy[26738]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:41 node-2 haproxy[26738]: 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 28 01:22:41 node-2 haproxy[26738]: proxy aodh has no server available!
<129>Sep 28 01:22:41 node-2 haproxy[26738]: 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 28 01:22:41 node-2 haproxy[26738]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:41 node-2 haproxy[26738]: 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 28 01:22:41 node-2 haproxy[26738]: proxy ceilometer has no server available!
<27>Sep 28 01:22:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:42 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:45 node-2 haproxy[28105]: 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 28 01:22:45 node-2 haproxy[28105]: 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 28 01:22:45 node-2 haproxy[28105]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:45 node-2 haproxy[28105]: 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 28 01:22:45 node-2 haproxy[28105]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:45 node-2 haproxy[28105]: 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 28 01:22:45 node-2 haproxy[28105]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:45 node-2 haproxy[28105]: 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 28 01:22:45 node-2 haproxy[28105]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:45 node-2 haproxy[28105]: 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 28 01:22:46 node-2 haproxy[28109]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: proxy glance-api has no server available!
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: proxy glance-glare has no server available!
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: proxy neutron has no server available!
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: proxy glance-registry has no server available!
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: proxy mysqld has no server available!
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:46 node-2 haproxy[28109]: 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 28 01:22:46 node-2 haproxy[28109]: proxy object-storage has no server available!
<129>Sep 28 01:22:47 node-2 haproxy[28109]: 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 28 01:22:47 node-2 haproxy[28109]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:47 node-2 haproxy[28109]: 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 28 01:22:47 node-2 haproxy[28109]: proxy aodh has no server available!
<129>Sep 28 01:22:47 node-2 haproxy[28109]: 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 28 01:22:47 node-2 haproxy[28109]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:47 node-2 haproxy[28109]: 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 28 01:22:47 node-2 haproxy[28109]: proxy ceilometer has no server available!
<27>Sep 28 01:22:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:49 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: proxy nova-api has no server available!
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:52 node-2 haproxy[29534]: proxy nova-metadata-api has no server available!
<129>Sep 28 01:22:52 node-2 haproxy[29534]: 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 28 01:22:53 node-2 haproxy[29540]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: proxy glance-api has no server available!
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: proxy glance-glare has no server available!
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: proxy neutron has no server available!
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: proxy glance-registry has no server available!
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: proxy mysqld has no server available!
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: proxy object-storage has no server available!
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:53 node-2 haproxy[29540]: proxy aodh has no server available!
<129>Sep 28 01:22:53 node-2 haproxy[29540]: 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 28 01:22:54 node-2 haproxy[29540]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:54 node-2 haproxy[29540]: 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 28 01:22:54 node-2 haproxy[29540]: proxy ceilometer has no server available!
<129>Sep 28 01:22:54 node-2 haproxy[29540]: 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 28 01:22:54 node-2 haproxy[29540]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:54 node-2 haproxy[29540]: 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 28 01:22:54 node-2 haproxy[29540]: proxy nova-novncproxy has no server available!
<27>Sep 28 01:22:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:55 node-2 multipathd: uevent trigger error
<27>Sep 28 01:22:55 node-2 multipathd: uevent trigger error
<129>Sep 28 01:22:57 node-2 haproxy[30868]: 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 28 01:22:57 node-2 haproxy[30868]: 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 28 01:22:57 node-2 haproxy[30868]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:57 node-2 haproxy[30868]: 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 28 01:22:57 node-2 haproxy[30868]: proxy keystone-1 has no server available!
<129>Sep 28 01:22:57 node-2 haproxy[30868]: 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 28 01:22:57 node-2 haproxy[30868]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy keystone-2 has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy nova-api has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy nova-metadata-api has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy cinder-api has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy glance-api has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy glance-glare has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy neutron has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:58 node-2 haproxy[30872]: proxy glance-registry has no server available!
<129>Sep 28 01:22:58 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: proxy mysqld has no server available!
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: proxy object-storage has no server available!
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: proxy aodh has no server available!
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: proxy ceilometer has no server available!
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:22:59 node-2 haproxy[30872]: 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 28 01:22:59 node-2 haproxy[30872]: proxy nova-novncproxy has no server available!
<27>Sep 28 01:23:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:00 node-2 multipathd: uevent trigger error
<129>Sep 28 01:23:03 node-2 haproxy[32251]: 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 28 01:23:03 node-2 haproxy[32251]: 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 28 01:23:03 node-2 haproxy[32251]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:03 node-2 haproxy[32251]: 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 28 01:23:03 node-2 haproxy[32251]: proxy keystone-1 has no server available!
<129>Sep 28 01:23:03 node-2 haproxy[32251]: 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 28 01:23:03 node-2 haproxy[32251]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:03 node-2 haproxy[32251]: 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 28 01:23:03 node-2 haproxy[32251]: proxy keystone-2 has no server available!
<129>Sep 28 01:23:03 node-2 haproxy[32251]: 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 28 01:23:03 node-2 haproxy[32251]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy nova-api has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy nova-metadata-api has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy cinder-api has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy glance-api has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy glance-glare has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy neutron has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy glance-registry has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy mysqld has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: proxy object-storage has no server available!
<129>Sep 28 01:23:04 node-2 haproxy[32258]: 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 28 01:23:04 node-2 haproxy[32258]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: proxy aodh has no server available!
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: proxy ceilometer has no server available!
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: proxy heat-api has no server available!
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: proxy heat-api-cfn has no server available!
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: proxy heat-api-cloudwatch has no server available!
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 01:23:05 node-2 haproxy[32258]: 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 28 01:23:05 node-2 haproxy[32258]: proxy nova-novncproxy has no server available!
<27>Sep 28 01:23:06 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:06 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:06 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:06 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:06 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:23:17 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 28 01:23:41 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 28 01:23:43 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 28 01:24:08 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 01:24:11 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 28 01:24:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:24:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:24:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:24:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:24:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:49 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:26:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:09 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 28 01:27:12 node-2 apache2_error [Wed Sep 28 01:27:07.092004 2016] [mpm_event:notice] [pid 9228:tid 140673490950016] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 28 01:27:12 node-2 apache2_error [Wed Sep 28 01:27:07.092107 2016] [core:notice] [pid 9228:tid 140673490950016] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 28 01:27:12 node-2 apache2_error [Wed Sep 28 01:27:10.168555 2016] [mpm_event:notice] [pid 9228:tid 140673490950016] AH00491: caught SIGTERM, shutting down
<43>Sep 28 01:27:12 node-2 apache2_error [Wed Sep 28 01:27:11.266178 2016] [mpm_worker:notice] [pid 10144:tid 140494865188736] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 28 01:27:12 node-2 apache2_error [Wed Sep 28 01:27:11.266228 2016] [core:notice] [pid 10144:tid 140494865188736] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 01:27:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:15 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:24 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:24 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:24 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:24 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:24 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:24 node-2 multipathd: uevent trigger error
<27>Sep 28 01:27:24 node-2 multipathd: uevent trigger error
<43>Sep 28 01:28:32 node-2 apache2_error [Wed Sep 28 01:28:28.398835 2016] [mpm_worker:notice] [pid 10144:tid 140494865188736] AH00295: caught SIGTERM, shutting down
<43>Sep 28 01:28:32 node-2 apache2_error [Wed Sep 28 01:28:29.153022 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 01:28:32 node-2 apache2_error [Wed Sep 28 01:28:29.153054 2016] [core:notice] [pid 24181:tid 140236507490176] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 28 01:29:22 node-2 apache2_error [Wed Sep 28 01:29:14.091894 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 01:29:22 node-2 apache2_error [Wed Sep 28 01:29:14.288389 2016] [mpm_worker:warn] [pid 24181:tid 140236507490176] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 01:29:22 node-2 apache2_error [Wed Sep 28 01:29:14.292180 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 01:29:22 node-2 apache2_error [Wed Sep 28 01:29:14.292213 2016] [core:notice] [pid 24181:tid 140236507490176] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 01:29:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:29:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:29:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:29:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:29:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:10 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 01:30:19 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:19 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:19 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:20 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:41 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:41 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:41 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:41 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:41 node-2 multipathd: uevent trigger error
<27>Sep 28 01:30:41 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:23 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:23 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:23 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:23 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:23 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:31:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:32:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:32:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:32:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:32:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:32:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:33:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 01:33:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:33:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:33:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:33:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:33:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:33:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:39 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:39 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:39 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:39 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:39 node-2 multipathd: uevent trigger error
<27>Sep 28 01:34:39 node-2 multipathd: uevent trigger error
<27>Sep 28 01:35:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:35:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:35:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:35:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:35:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:35:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:36:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 01:37:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:37:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:38 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:38 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:38 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:38 node-2 multipathd: uevent trigger error
<27>Sep 28 01:38:38 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:00 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 01:39:47 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:47 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:47 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:47 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:47 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:47 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 28 01:39:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 28 01:39:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 28 01:39:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Sep 28 01:39:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Sep 28 01:39:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:39:56 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:10 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:25 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:25 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:25 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:25 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:25 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:25 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:43 node-2 multipathd: uevent trigger error
<27>Sep 28 01:40:43 node-2 multipathd: uevent trigger error
<27>Sep 28 01:42:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 01:43:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:46 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:43:52 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:35 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:53 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:44:59 node-2 multipathd: uevent trigger error
<27>Sep 28 01:45:18 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 01:45:43 node-2 multipathd: uevent trigger error
<27>Sep 28 01:45:43 node-2 multipathd: uevent trigger error
<27>Sep 28 01:45:43 node-2 multipathd: uevent trigger error
<27>Sep 28 01:45:43 node-2 multipathd: uevent trigger error
<27>Sep 28 01:45:43 node-2 multipathd: uevent trigger error
<27>Sep 28 01:46:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:46:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:46:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:46:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:46:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:04 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:04 node-2 multipathd: uevent trigger error
<11>Sep 28 01:47:17 node-2 liberasurecode[24733]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:17 node-2 liberasurecode[24733]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:17 node-2 liberasurecode[24733]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:17 node-2 liberasurecode[24733]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:18 node-2 liberasurecode[24757]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:18 node-2 liberasurecode[24757]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:18 node-2 liberasurecode[24757]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:18 node-2 liberasurecode[24757]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:19 node-2 liberasurecode[25213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:19 node-2 liberasurecode[25213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:19 node-2 liberasurecode[25213]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:19 node-2 liberasurecode[25213]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25827]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25827]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25896]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25896]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25896]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25896]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25941]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25941]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25941]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:24 node-2 liberasurecode[25941]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26088]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26088]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26088]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26088]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26143]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26143]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26143]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26143]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26161]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26161]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26161]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:25 node-2 liberasurecode[26161]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:41 node-2 liberasurecode[28598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:41 node-2 liberasurecode[28598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:41 node-2 liberasurecode[28598]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:47:41 node-2 liberasurecode[28598]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 28 01:47:50 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:50 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:50 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:50 node-2 multipathd: uevent trigger error
<27>Sep 28 01:47:50 node-2 multipathd: uevent trigger error
<27>Sep 28 01:48:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 28 01:48:44 node-2 apache2_error [Wed Sep 28 01:48:38.400687 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 01:48:44 node-2 apache2_error [Wed Sep 28 01:48:38.785608 2016] [mpm_worker:warn] [pid 24181:tid 140236507490176] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 01:48:44 node-2 apache2_error [Wed Sep 28 01:48:38.790556 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 01:48:44 node-2 apache2_error [Wed Sep 28 01:48:38.790578 2016] [core:notice] [pid 24181:tid 140236507490176] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 01:49:19 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:19 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:19 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:19 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:19 node-2 multipathd: uevent trigger error
<43>Sep 28 01:49:24 node-2 apache2_error [Wed Sep 28 01:49:15.636945 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 01:49:24 node-2 apache2_error [Wed Sep 28 01:49:15.831392 2016] [mpm_worker:warn] [pid 24181:tid 140236507490176] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 01:49:24 node-2 apache2_error [Wed Sep 28 01:49:15.840695 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 01:49:24 node-2 apache2_error [Wed Sep 28 01:49:15.840724 2016] [core:notice] [pid 24181:tid 140236507490176] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 01:49:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:49:27 node-2 multipathd: uevent trigger error
<11>Sep 28 01:50:01 node-2 liberasurecode[19026]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:50:01 node-2 liberasurecode[19026]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:50:01 node-2 liberasurecode[19026]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:50:01 node-2 liberasurecode[19026]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Sep 28 01:50:04 node-2 apache2_error [Wed Sep 28 01:50:01.406490 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 01:50:04 node-2 apache2_error [Wed Sep 28 01:50:01.792253 2016] [mpm_worker:warn] [pid 24181:tid 140236507490176] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 01:50:04 node-2 apache2_error [Wed Sep 28 01:50:01.802649 2016] [mpm_worker:notice] [pid 24181:tid 140236507490176] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 01:50:04 node-2 apache2_error [Wed Sep 28 01:50:01.802684 2016] [core:notice] [pid 24181:tid 140236507490176] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 01:50:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:05 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:18 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:18 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:18 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:18 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:18 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:27 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:50:42 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:06 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:12 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 28 01:51:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:26 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:31 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:37 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:48 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 28 01:51:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:51:48 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:16 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:21 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:33 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:40 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:40 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:40 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:40 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:40 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:40 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:45 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:45 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:45 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:45 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:45 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:58 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:58 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:58 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:58 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:58 node-2 multipathd: uevent trigger error
<27>Sep 28 01:52:58 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:02 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:02 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:02 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:03 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:07 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:12 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:17 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:17 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:17 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:17 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:17 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:22 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:22 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:22 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:22 node-2 multipathd: uevent trigger error
<27>Sep 28 01:53:22 node-2 multipathd: uevent trigger error
<11>Sep 28 01:55:02 node-2 liberasurecode[25374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:55:02 node-2 liberasurecode[25374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:55:02 node-2 liberasurecode[25374]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 01:55:02 node-2 liberasurecode[25374]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
