Sep  7 04:32:44 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8397" x-info="http://www.rsyslog.com"] start
Sep  7 04:32:44 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep  7 04:32:44 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep  7 04:32:44 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep  7 04:32:44 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep  7 04:32:44 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep  7 04:32:44 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep  7 04:32:44 node-2 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep  7 04:32:44 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e28a5e06-e224-4b3b-96f9-d76bc3dd1c77 nomdmonddf nomdmonisw
Sep  7 04:32:44 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep  7 04:32:44 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep  7 04:32:44 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep  7 04:32:44 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep  7 04:32:44 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep  7 04:32:44 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep  7 04:32:44 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep  7 04:32:44 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  7 04:32:44 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep  7 04:32:44 node-2 kernel: [    0.000000] No AGP bridge found
Sep  7 04:32:44 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep  7 04:32:44 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep  7 04:32:44 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep  7 04:32:44 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep  7 04:32:44 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep  7 04:32:44 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep  7 04:32:44 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep  7 04:32:44 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep  7 04:32:44 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep  7 04:32:44 node-2 kernel: [    0.000000]   2 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000]   3 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000]   4 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000]   5 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000]   6 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000]   7 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000]   8 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000]   9 disabled
Sep  7 04:32:44 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep  7 04:32:44 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep  7 04:32:44 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep  7 04:32:44 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep  7 04:32:44 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep  7 04:32:44 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep  7 04:32:44 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep  7 04:32:44 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep  7 04:32:44 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep  7 04:32:44 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep  7 04:32:44 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep  7 04:32:44 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep  7 04:32:44 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep  7 04:32:44 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep  7 04:32:44 node-2 kernel: [    0.000000] Zone ranges:
Sep  7 04:32:44 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] Movable zone start for each node
Sep  7 04:32:44 node-2 kernel: [    0.000000] Early memory node ranges
Sep  7 04:32:44 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep  7 04:32:44 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep  7 04:32:44 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep  7 04:32:44 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep  7 04:32:44 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep  7 04:32:44 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep  7 04:32:44 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep  7 04:32:44 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep  7 04:32:44 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep  7 04:32:44 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep  7 04:32:44 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep  7 04:32:44 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep  7 04:32:44 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep  7 04:32:44 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep  7 04:32:44 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep  7 04:32:44 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep  7 04:32:44 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep  7 04:32:44 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep  7 04:32:44 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep  7 04:32:44 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep  7 04:32:44 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep  7 04:32:44 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep  7 04:32:44 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep  7 04:32:44 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep  7 04:32:44 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  7 04:32:44 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep  7 04:32:44 node-2 kernel: [    0.000000] Policy zone: Normal
Sep  7 04:32:44 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e28a5e06-e224-4b3b-96f9-d76bc3dd1c77 nomdmonddf nomdmonisw
Sep  7 04:32:44 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep  7 04:32:44 node-2 kernel: [    0.000000] Checking aperture...
Sep  7 04:32:44 node-2 kernel: [    0.000000] No AGP bridge found
Sep  7 04:32:44 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep  7 04:32:44 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep  7 04:32:44 node-2 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep  7 04:32:44 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep  7 04:32:44 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep  7 04:32:44 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep  7 04:32:44 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep  7 04:32:44 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep  7 04:32:44 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep  7 04:32:44 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep  7 04:32:44 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep  7 04:32:44 node-2 kernel: [    0.000000] console [tty0] enabled
Sep  7 04:32:44 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep  7 04:32:44 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep  7 04:32:44 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep  7 04:32:44 node-2 kernel: [    0.000000] hpet clockevent registered
Sep  7 04:32:44 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep  7 04:32:44 node-2 kernel: [    0.004000] tsc: Detected 3491.895 MHz processor
Sep  7 04:32:44 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.79 BogoMIPS (lpj=13967580)
Sep  7 04:32:44 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep  7 04:32:44 node-2 kernel: [    0.000043] Security Framework initialized
Sep  7 04:32:44 node-2 kernel: [    0.000062] AppArmor: AppArmor initialized
Sep  7 04:32:44 node-2 kernel: [    0.000063] Yama: becoming mindful.
Sep  7 04:32:44 node-2 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.006302] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.008230] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.008258] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.008549] Initializing cgroup subsys memory
Sep  7 04:32:44 node-2 kernel: [    0.008558] Initializing cgroup subsys devices
Sep  7 04:32:44 node-2 kernel: [    0.008559] Initializing cgroup subsys freezer
Sep  7 04:32:44 node-2 kernel: [    0.008561] Initializing cgroup subsys blkio
Sep  7 04:32:44 node-2 kernel: [    0.008562] Initializing cgroup subsys perf_event
Sep  7 04:32:44 node-2 kernel: [    0.008565] Initializing cgroup subsys hugetlb
Sep  7 04:32:44 node-2 kernel: [    0.008584] CPU: Physical Processor ID: 0
Sep  7 04:32:44 node-2 kernel: [    0.008585] CPU: Processor Core ID: 0
Sep  7 04:32:44 node-2 kernel: [    0.008589] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep  7 04:32:44 node-2 kernel: [    0.008589] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep  7 04:32:44 node-2 kernel: [    0.009282] mce: CPU supports 22 MCE banks
Sep  7 04:32:44 node-2 kernel: [    0.009310] CPU0: Thermal monitoring enabled (TM1)
Sep  7 04:32:44 node-2 kernel: [    0.009330] process: using mwait in idle threads
Sep  7 04:32:44 node-2 kernel: [    0.009333] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep  7 04:32:44 node-2 kernel: [    0.009333] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep  7 04:32:44 node-2 kernel: [    0.009333] tlb_flushall_shift: 6
Sep  7 04:32:44 node-2 kernel: [    0.009422] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep  7 04:32:44 node-2 kernel: [    0.010148] ACPI: Core revision 20131115
Sep  7 04:32:44 node-2 kernel: [    0.022821] ACPI: All ACPI Tables successfully acquired
Sep  7 04:32:44 node-2 kernel: [    0.022982] ftrace: allocating 28617 entries in 112 pages
Sep  7 04:32:44 node-2 kernel: [    0.031956] dmar: Host address width 46
Sep  7 04:32:44 node-2 kernel: [    0.031958] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep  7 04:32:44 node-2 kernel: [    0.031964] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  7 04:32:44 node-2 kernel: [    0.031966] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep  7 04:32:44 node-2 kernel: [    0.031970] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  7 04:32:44 node-2 kernel: [    0.031971] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep  7 04:32:44 node-2 kernel: [    0.031973] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep  7 04:32:44 node-2 kernel: [    0.031974] dmar: ATSR flags: 0x0
Sep  7 04:32:44 node-2 kernel: [    0.031975] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep  7 04:32:44 node-2 kernel: [    0.031976] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep  7 04:32:44 node-2 kernel: [    0.032092] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep  7 04:32:44 node-2 kernel: [    0.032093] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep  7 04:32:44 node-2 kernel: [    0.032094] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep  7 04:32:44 node-2 kernel: [    0.032095] HPET id 0 under DRHD base 0xc7ffc000
Sep  7 04:32:44 node-2 kernel: [    0.032096] Your BIOS is broken and requested that x2apic be disabled.
Sep  7 04:32:44 node-2 kernel: [    0.032096] This will slightly decrease performance.
Sep  7 04:32:44 node-2 kernel: [    0.032096] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep  7 04:32:44 node-2 kernel: [    0.032529] Enabled IRQ remapping in xapic mode
Sep  7 04:32:44 node-2 kernel: [    0.032530] x2apic not enabled, IRQ remapping is in xapic mode
Sep  7 04:32:44 node-2 kernel: [    0.032534] Switched APIC routing to physical flat.
Sep  7 04:32:44 node-2 kernel: [    0.033115] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep  7 04:32:44 node-2 kernel: [    0.072765] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep  7 04:32:44 node-2 kernel: [    0.072770] TSC deadline timer enabled
Sep  7 04:32:44 node-2 kernel: [    0.072778] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep  7 04:32:44 node-2 kernel: [    0.072784] ... version:                3
Sep  7 04:32:44 node-2 kernel: [    0.072785] ... bit width:              48
Sep  7 04:32:44 node-2 kernel: [    0.072785] ... generic registers:      4
Sep  7 04:32:44 node-2 kernel: [    0.072786] ... value mask:             0000ffffffffffff
Sep  7 04:32:44 node-2 kernel: [    0.072787] ... max period:             0000ffffffffffff
Sep  7 04:32:44 node-2 kernel: [    0.072788] ... fixed-purpose events:   3
Sep  7 04:32:44 node-2 kernel: [    0.072789] ... event mask:             000000070000000f
Sep  7 04:32:44 node-2 kernel: [    0.074184] x86: Booting SMP configuration:
Sep  7 04:32:44 node-2 kernel: [    0.088288] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep  7 04:32:44 node-2 kernel: [    0.074186] .... node  #0, CPUs:        #1  #2  #3
Sep  7 04:32:44 node-2 kernel: [    0.116196] .... node  #1, CPUs:    #4  #5  #6  #7
Sep  7 04:32:44 node-2 kernel: [    0.270137] .... node  #0, CPUs:    #8  #9 #10 #11
Sep  7 04:32:44 node-2 kernel: [    0.325750] .... node  #1, CPUs:   #12 #13 #14 #15
Sep  7 04:32:44 node-2 kernel: [    0.382209] x86: Booted up 2 nodes, 16 CPUs
Sep  7 04:32:44 node-2 kernel: [    0.382212] smpboot: Total of 16 processors activated (111752.81 BogoMIPS)
Sep  7 04:32:44 node-2 kernel: [    0.404959] devtmpfs: initialized
Sep  7 04:32:44 node-2 kernel: [    0.408103] EVM: security.selinux
Sep  7 04:32:44 node-2 kernel: [    0.408105] EVM: security.SMACK64
Sep  7 04:32:44 node-2 kernel: [    0.408106] EVM: security.ima
Sep  7 04:32:44 node-2 kernel: [    0.408107] EVM: security.capability
Sep  7 04:32:44 node-2 kernel: [    0.408155] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.408834] pinctrl core: initialized pinctrl subsystem
Sep  7 04:32:44 node-2 kernel: [    0.408894] regulator-dummy: no parameters
Sep  7 04:32:44 node-2 kernel: [    0.408925] RTC time:  4:32:08, date: 09/07/16
Sep  7 04:32:44 node-2 kernel: [    0.408959] NET: Registered protocol family 16
Sep  7 04:32:44 node-2 kernel: [    0.409043] cpuidle: using governor ladder
Sep  7 04:32:44 node-2 kernel: [    0.409044] cpuidle: using governor menu
Sep  7 04:32:44 node-2 kernel: [    0.409079] ACPI: bus type PCI registered
Sep  7 04:32:44 node-2 kernel: [    0.409081] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep  7 04:32:44 node-2 kernel: [    0.409125] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep  7 04:32:44 node-2 kernel: [    0.409128] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep  7 04:32:44 node-2 kernel: [    0.422854] PCI: Using configuration type 1 for base access
Sep  7 04:32:44 node-2 kernel: [    0.423846] bio: create slab <bio-0> at 0
Sep  7 04:32:44 node-2 kernel: [    0.424120] ACPI: Added _OSI(Module Device)
Sep  7 04:32:44 node-2 kernel: [    0.424121] ACPI: Added _OSI(Processor Device)
Sep  7 04:32:44 node-2 kernel: [    0.424123] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep  7 04:32:44 node-2 kernel: [    0.424124] ACPI: Added _OSI(Processor Aggregator Device)
Sep  7 04:32:44 node-2 kernel: [    0.436780] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep  7 04:32:44 node-2 kernel: [    0.447465] ACPI: Interpreter enabled
Sep  7 04:32:44 node-2 kernel: [    0.447471] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep  7 04:32:44 node-2 kernel: [    0.447475] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep  7 04:32:44 node-2 kernel: [    0.447477] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep  7 04:32:44 node-2 kernel: [    0.447484] ACPI: (supports S0 S4 S5)
Sep  7 04:32:44 node-2 kernel: [    0.447485] ACPI: Using IOAPIC for interrupt routing
Sep  7 04:32:44 node-2 kernel: [    0.447526] HEST: Table parsing has been initialized.
Sep  7 04:32:44 node-2 kernel: [    0.447529] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep  7 04:32:44 node-2 kernel: [    0.448084] ACPI: No dock devices found.
Sep  7 04:32:44 node-2 kernel: [    0.459706] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep  7 04:32:44 node-2 kernel: [    0.459710] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 04:32:44 node-2 kernel: [    0.459714] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  7 04:32:44 node-2 kernel: [    0.459740] PCI host bridge to bus 0000:ff
Sep  7 04:32:44 node-2 kernel: [    0.459742] pci_bus 0000:ff: root bus resource [bus ff]
Sep  7 04:32:44 node-2 kernel: [    0.459750] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.459787] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.459817] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.459851] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.459880] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.459909] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.459939] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.459966] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.459996] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460023] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460049] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460075] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460102] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460128] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460154] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460180] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460207] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460234] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460259] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.460287] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460312] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.460337] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460363] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460391] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.460426] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460456] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460485] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460517] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460549] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460581] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460613] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460644] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460674] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460704] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460736] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460767] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460800] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460831] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460858] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460888] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460920] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460956] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.460990] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461023] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461053] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461081] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461113] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461144] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461177] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461207] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461239] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461269] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461298] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461328] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461357] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461388] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461419] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461475] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep  7 04:32:44 node-2 kernel: [    0.461478] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 04:32:44 node-2 kernel: [    0.461481] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  7 04:32:44 node-2 kernel: [    0.461498] PCI host bridge to bus 0000:7f
Sep  7 04:32:44 node-2 kernel: [    0.461500] pci_bus 0000:7f: root bus resource [bus 7f]
Sep  7 04:32:44 node-2 kernel: [    0.461505] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461532] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.461563] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461593] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461615] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.461639] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.461665] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461690] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461713] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461735] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461757] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461780] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461804] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461826] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461849] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461874] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461896] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461919] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461941] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.461965] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.461987] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.462008] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462031] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462057] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep  7 04:32:44 node-2 kernel: [    0.462090] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462117] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462143] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462173] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462198] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462225] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462251] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462280] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462307] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462336] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462364] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462392] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462422] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462447] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462471] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462500] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462525] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462553] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462584] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462611] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462638] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462665] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462693] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462720] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462748] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462775] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462806] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462831] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462854] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462879] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462905] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462933] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.462959] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.464201] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep  7 04:32:44 node-2 kernel: [    0.464204] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 04:32:44 node-2 kernel: [    0.465319] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  7 04:32:44 node-2 kernel: [    0.465829] PCI host bridge to bus 0000:00
Sep  7 04:32:44 node-2 kernel: [    0.465831] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep  7 04:32:44 node-2 kernel: [    0.465833] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep  7 04:32:44 node-2 kernel: [    0.465834] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep  7 04:32:44 node-2 kernel: [    0.465836] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep  7 04:32:44 node-2 kernel: [    0.465837] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep  7 04:32:44 node-2 kernel: [    0.465839] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep  7 04:32:44 node-2 kernel: [    0.465840] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep  7 04:32:44 node-2 kernel: [    0.465846] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep  7 04:32:44 node-2 kernel: [    0.465928] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.465959] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.466000] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep  7 04:32:44 node-2 kernel: [    0.466019] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.466048] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.466088] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep  7 04:32:44 node-2 kernel: [    0.466105] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.466135] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.466177] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep  7 04:32:44 node-2 kernel: [    0.466194] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.466264] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.466341] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.466416] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep  7 04:32:44 node-2 kernel: [    0.466421] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep  7 04:32:44 node-2 kernel: [    0.466505] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep  7 04:32:44 node-2 kernel: [    0.466652] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep  7 04:32:44 node-2 kernel: [    0.466670] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep  7 04:32:44 node-2 kernel: [    0.466748] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.466803] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep  7 04:32:44 node-2 kernel: [    0.466825] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.466881] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.466924] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep  7 04:32:44 node-2 kernel: [    0.466952] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.467008] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.467051] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep  7 04:32:44 node-2 kernel: [    0.467075] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep  7 04:32:44 node-2 kernel: [    0.467092] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep  7 04:32:44 node-2 kernel: [    0.467170] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.467220] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep  7 04:32:44 node-2 kernel: [    0.467246] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep  7 04:32:44 node-2 kernel: [    0.467494] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep  7 04:32:44 node-2 kernel: [    0.467500] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep  7 04:32:44 node-2 kernel: [    0.467506] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.467512] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.467519] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep  7 04:32:44 node-2 kernel: [    0.467549] pci 0000:01:00.0: supports D1 D2
Sep  7 04:32:44 node-2 kernel: [    0.477567] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  7 04:32:44 node-2 kernel: [    0.477574] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  7 04:32:44 node-2 kernel: [    0.477578] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  7 04:32:44 node-2 kernel: [    0.477841] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.477901] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep  7 04:32:44 node-2 kernel: [    0.489563] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  7 04:32:44 node-2 kernel: [    0.489569] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.489573] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 04:32:44 node-2 kernel: [    0.489666] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.489737] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.489814] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.489860] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  7 04:32:44 node-2 kernel: [    0.489863] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.489865] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 04:32:44 node-2 kernel: [    0.489926] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.490051] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.490107] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  7 04:32:44 node-2 kernel: [    0.490109] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.490111] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.490160] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.490279] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.490318] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.490437] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.490473] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.490613] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.490651] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep  7 04:32:44 node-2 kernel: [    0.490770] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep  7 04:32:44 node-2 kernel: [    0.490813] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  7 04:32:44 node-2 kernel: [    0.490815] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.490817] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.490875] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep  7 04:32:44 node-2 kernel: [    0.490939] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.490991] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.491036] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep  7 04:32:44 node-2 kernel: [    0.491118] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep  7 04:32:44 node-2 kernel: [    0.491223] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  7 04:32:44 node-2 kernel: [    0.491226] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.491228] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.491284] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep  7 04:32:44 node-2 kernel: [    0.491337] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.491386] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.491621] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  7 04:32:44 node-2 kernel: [    0.491624] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  7 04:32:44 node-2 kernel: [    0.491687] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep  7 04:32:44 node-2 kernel: [    0.491743] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.491792] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.492002] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  7 04:32:44 node-2 kernel: [    0.492005] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  7 04:32:44 node-2 kernel: [    0.492063] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep  7 04:32:44 node-2 kernel: [    0.492126] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.492178] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep  7 04:32:44 node-2 kernel: [    0.492400] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  7 04:32:44 node-2 kernel: [    0.492403] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  7 04:32:44 node-2 kernel: [    0.492577] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  7 04:32:44 node-2 kernel: [    0.492616] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  7 04:32:44 node-2 kernel: [    0.492690] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep  7 04:32:44 node-2 kernel: [    0.492709] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep  7 04:32:44 node-2 kernel: [    0.492722] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep  7 04:32:44 node-2 kernel: [    0.492735] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep  7 04:32:44 node-2 kernel: [    0.492785] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep  7 04:32:44 node-2 kernel: [    0.497567] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  7 04:32:44 node-2 kernel: [    0.497572] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  7 04:32:44 node-2 kernel: [    0.497604] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep  7 04:32:44 node-2 kernel: [    0.498097] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep  7 04:32:44 node-2 kernel: [    0.498100] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 04:32:44 node-2 kernel: [    0.498224] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  7 04:32:44 node-2 kernel: [    0.498330] PCI host bridge to bus 0000:80
Sep  7 04:32:44 node-2 kernel: [    0.498332] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep  7 04:32:44 node-2 kernel: [    0.498333] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep  7 04:32:44 node-2 kernel: [    0.498335] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep  7 04:32:44 node-2 kernel: [    0.498343] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.498406] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.498473] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep  7 04:32:44 node-2 kernel: [    0.498535] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep  7 04:32:44 node-2 kernel: [    0.498540] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep  7 04:32:44 node-2 kernel: [    0.498613] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep  7 04:32:44 node-2 kernel: [    0.498913] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep  7 04:32:44 node-2 kernel: [    0.498945] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep  7 04:32:44 node-2 kernel: [    0.498975] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep  7 04:32:44 node-2 kernel: [    0.499004] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  7 04:32:44 node-2 kernel: [    0.499033] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 04:32:44 node-2 kernel: [    0.499063] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 04:32:44 node-2 kernel: [    0.499093] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 04:32:44 node-2 kernel: [    0.499123] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 04:32:44 node-2 kernel: [    0.499207] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep  7 04:32:44 node-2 kernel: [    0.499212] ACPI: \_SB_.UNC1: notify handler is installed
Sep  7 04:32:44 node-2 kernel: [    0.499213] ACPI: \_SB_.UNC0: notify handler is installed
Sep  7 04:32:44 node-2 kernel: [    0.499228] ACPI: \_SB_.PCI0: notify handler is installed
Sep  7 04:32:44 node-2 kernel: [    0.499281] ACPI: \_SB_.PCI1: notify handler is installed
Sep  7 04:32:44 node-2 kernel: [    0.499361] Found 4 acpi root devices
Sep  7 04:32:44 node-2 kernel: [    0.499466] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep  7 04:32:44 node-2 kernel: [    0.499469] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep  7 04:32:44 node-2 kernel: [    0.499470] vgaarb: loaded
Sep  7 04:32:44 node-2 kernel: [    0.499471] vgaarb: bridge control possible 0000:0c:00.0
Sep  7 04:32:44 node-2 kernel: [    0.499588] SCSI subsystem initialized
Sep  7 04:32:44 node-2 kernel: [    0.499652] libata version 3.00 loaded.
Sep  7 04:32:44 node-2 kernel: [    0.499667] ACPI: bus type USB registered
Sep  7 04:32:44 node-2 kernel: [    0.499677] usbcore: registered new interface driver usbfs
Sep  7 04:32:44 node-2 kernel: [    0.499682] usbcore: registered new interface driver hub
Sep  7 04:32:44 node-2 kernel: [    0.499707] usbcore: registered new device driver usb
Sep  7 04:32:44 node-2 kernel: [    0.499871] PCI: Using ACPI for IRQ routing
Sep  7 04:32:44 node-2 kernel: [    0.503478] PCI: pci_cache_line_size set to 64 bytes
Sep  7 04:32:44 node-2 kernel: [    0.503695] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep  7 04:32:44 node-2 kernel: [    0.503696] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep  7 04:32:44 node-2 kernel: [    0.503697] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep  7 04:32:44 node-2 kernel: [    0.503761] NetLabel: Initializing
Sep  7 04:32:44 node-2 kernel: [    0.503762] NetLabel:  domain hash size = 128
Sep  7 04:32:44 node-2 kernel: [    0.503763] NetLabel:  protocols = UNLABELED CIPSOv4
Sep  7 04:32:44 node-2 kernel: [    0.503772] NetLabel:  unlabeled traffic allowed by default
Sep  7 04:32:44 node-2 kernel: [    0.503828] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep  7 04:32:44 node-2 kernel: [    0.503832] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep  7 04:32:44 node-2 kernel: [    0.505904] Switched to clocksource hpet
Sep  7 04:32:44 node-2 kernel: [    0.510448] AppArmor: AppArmor Filesystem Enabled
Sep  7 04:32:44 node-2 kernel: [    0.510486] pnp: PnP ACPI init
Sep  7 04:32:44 node-2 kernel: [    0.510498] ACPI: bus type PNP registered
Sep  7 04:32:44 node-2 kernel: [    0.510679] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep  7 04:32:44 node-2 kernel: [    0.510690] pnp 00:01: [dma 4]
Sep  7 04:32:44 node-2 kernel: [    0.510709] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep  7 04:32:44 node-2 kernel: [    0.510743] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep  7 04:32:44 node-2 kernel: [    0.510767] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep  7 04:32:44 node-2 kernel: [    0.510789] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep  7 04:32:44 node-2 kernel: [    0.510837] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep  7 04:32:44 node-2 kernel: [    0.510949] system 00:06: [io  0x0500-0x057f] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510951] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep  7 04:32:44 node-2 kernel: [    0.510953] system 00:06: [io  0x0580-0x059f] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510954] system 00:06: [io  0x0600-0x061f] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510956] system 00:06: [io  0x0880-0x0883] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510957] system 00:06: [io  0x0800-0x081f] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510961] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep  7 04:32:44 node-2 kernel: [    0.510962] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510964] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510966] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510967] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510969] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510970] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep  7 04:32:44 node-2 kernel: [    0.510973] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  7 04:32:44 node-2 kernel: [    0.511073] pnp 00:07: [dma 0 disabled]
Sep  7 04:32:44 node-2 kernel: [    0.511106] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  7 04:32:44 node-2 kernel: [    0.511187] pnp 00:08: [dma 0 disabled]
Sep  7 04:32:44 node-2 kernel: [    0.511224] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  7 04:32:44 node-2 kernel: [    0.511283] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep  7 04:32:44 node-2 kernel: [    0.511730] pnp: PnP ACPI: found 10 devices
Sep  7 04:32:44 node-2 kernel: [    0.511732] ACPI: bus type PNP unregistered
Sep  7 04:32:44 node-2 kernel: [    0.517772] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  7 04:32:44 node-2 kernel: [    0.517776] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  7 04:32:44 node-2 kernel: [    0.517779] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  7 04:32:44 node-2 kernel: [    0.517784] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  7 04:32:44 node-2 kernel: [    0.517786] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.517801] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.517830] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  7 04:32:44 node-2 kernel: [    0.517844] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  7 04:32:44 node-2 kernel: [    0.517881] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  7 04:32:44 node-2 kernel: [    0.517895] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  7 04:32:44 node-2 kernel: [    0.517924] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  7 04:32:44 node-2 kernel: [    0.517939] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  7 04:32:44 node-2 kernel: [    0.517967] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  7 04:32:44 node-2 kernel: [    0.517969] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.517984] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518013] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  7 04:32:44 node-2 kernel: [    0.518015] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518030] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518058] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  7 04:32:44 node-2 kernel: [    0.518060] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518063] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518068] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  7 04:32:44 node-2 kernel: [    0.518070] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518073] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518077] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  7 04:32:44 node-2 kernel: [    0.518083] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  7 04:32:44 node-2 kernel: [    0.518092] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  7 04:32:44 node-2 kernel: [    0.518096] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  7 04:32:44 node-2 kernel: [    0.518103] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep  7 04:32:44 node-2 kernel: [    0.518104] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep  7 04:32:44 node-2 kernel: [    0.518105] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep  7 04:32:44 node-2 kernel: [    0.518106] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep  7 04:32:44 node-2 kernel: [    0.518106] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep  7 04:32:44 node-2 kernel: [    0.518107] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep  7 04:32:44 node-2 kernel: [    0.518108] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep  7 04:32:44 node-2 kernel: [    0.518109] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep  7 04:32:44 node-2 kernel: [    0.518110] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518111] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518112] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518113] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518114] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518115] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518116] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518117] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518118] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep  7 04:32:44 node-2 kernel: [    0.518119] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518120] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep  7 04:32:44 node-2 kernel: [    0.518121] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep  7 04:32:44 node-2 kernel: [    0.518122] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep  7 04:32:44 node-2 kernel: [    0.518123] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep  7 04:32:44 node-2 kernel: [    0.518126] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep  7 04:32:44 node-2 kernel: [    0.518127] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep  7 04:32:44 node-2 kernel: [    0.518168] NET: Registered protocol family 2
Sep  7 04:32:44 node-2 kernel: [    0.518465] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.518840] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.519019] TCP: Hash tables configured (established 262144 bind 65536)
Sep  7 04:32:44 node-2 kernel: [    0.519064] TCP: reno registered
Sep  7 04:32:44 node-2 kernel: [    0.519095] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.519201] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.519364] NET: Registered protocol family 1
Sep  7 04:32:44 node-2 kernel: [    0.553999] pci 0000:0c:00.0: Video device with shadowed ROM
Sep  7 04:32:44 node-2 kernel: [    0.554015] PCI: CLS 64 bytes, default 64
Sep  7 04:32:44 node-2 kernel: [    0.554106] Trying to unpack rootfs image as initramfs...
Sep  7 04:32:44 node-2 kernel: [    0.777232] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep  7 04:32:44 node-2 kernel: [    0.777293] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep  7 04:32:44 node-2 kernel: [    0.777296] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep  7 04:32:44 node-2 kernel: [    0.777739] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777747] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777755] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777762] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777770] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777778] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777785] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777792] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777799] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777806] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777816] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777823] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777829] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777835] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777841] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777845] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 04:32:44 node-2 kernel: [    0.777918] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep  7 04:32:44 node-2 kernel: [    0.777920] Scanning for low memory corruption every 60 seconds
Sep  7 04:32:44 node-2 kernel: [    0.778282] Initialise system trusted keyring
Sep  7 04:32:44 node-2 kernel: [    0.778330] audit: initializing netlink socket (disabled)
Sep  7 04:32:44 node-2 kernel: [    0.778345] type=2000 audit(1473222728.732:1): initialized
Sep  7 04:32:44 node-2 kernel: [    0.796134] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep  7 04:32:44 node-2 kernel: [    0.797584] zbud: loaded
Sep  7 04:32:44 node-2 kernel: [    0.797726] VFS: Disk quotas dquot_6.5.2
Sep  7 04:32:44 node-2 kernel: [    0.797761] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep  7 04:32:44 node-2 kernel: [    0.798124] fuse init (API version 7.22)
Sep  7 04:32:44 node-2 kernel: [    0.798174] msgmni has been set to 32768
Sep  7 04:32:44 node-2 kernel: [    0.798223] Key type big_key registered
Sep  7 04:32:44 node-2 kernel: [    0.798732] Key type asymmetric registered
Sep  7 04:32:44 node-2 kernel: [    0.798733] Asymmetric key parser 'x509' registered
Sep  7 04:32:44 node-2 kernel: [    0.798754] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep  7 04:32:44 node-2 kernel: [    0.798839] io scheduler noop registered
Sep  7 04:32:44 node-2 kernel: [    0.798841] io scheduler deadline registered (default)
Sep  7 04:32:44 node-2 kernel: [    0.798861] io scheduler cfq registered
Sep  7 04:32:44 node-2 kernel: [    0.799278] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    0.799420] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    0.799533] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    0.799643] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    0.799755] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    0.799852] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    0.800247] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep  7 04:32:44 node-2 kernel: [    0.800287] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep  7 04:32:44 node-2 kernel: [    0.800317] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep  7 04:32:44 node-2 kernel: [    0.800340] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800345] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800351] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep  7 04:32:44 node-2 kernel: [    0.800361] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800365] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800368] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800372] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800376] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800380] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800394] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800396] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800397] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800399] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800400] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800401] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800404] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep  7 04:32:44 node-2 kernel: [    0.800409] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800411] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep  7 04:32:44 node-2 kernel: [    0.800423] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800426] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep  7 04:32:44 node-2 kernel: [    0.800436] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800438] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep  7 04:32:44 node-2 kernel: [    0.800441] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep  7 04:32:44 node-2 kernel: [    0.800468] ioapic: probe of 0000:00:05.4 failed with error -22
Sep  7 04:32:44 node-2 kernel: [    0.800474] ioapic: probe of 0000:80:05.4 failed with error -22
Sep  7 04:32:44 node-2 kernel: [    0.800478] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  7 04:32:44 node-2 kernel: [    0.800492] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep  7 04:32:44 node-2 kernel: [    0.800530] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep  7 04:32:44 node-2 kernel: [    0.800531] vesafb: scrolling: redraw
Sep  7 04:32:44 node-2 kernel: [    0.800532] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep  7 04:32:44 node-2 kernel: [    0.820751] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep  7 04:32:44 node-2 kernel: [    0.829251] Console: switching to colour frame buffer device 80x30
Sep  7 04:32:44 node-2 kernel: [    0.837922] fb0: VESA VGA frame buffer device
Sep  7 04:32:44 node-2 kernel: [    0.838121] intel_idle: MWAIT substates: 0x2120
Sep  7 04:32:44 node-2 kernel: [    0.838122] intel_idle: v0.4 model 0x3F
Sep  7 04:32:44 node-2 kernel: [    0.838123] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep  7 04:32:44 node-2 kernel: [    0.838370] ipmi message handler version 39.2
Sep  7 04:32:44 node-2 kernel: [    0.838633] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep  7 04:32:44 node-2 kernel: [    0.839064] ACPI: AC Adapter [P111] (on-line)
Sep  7 04:32:44 node-2 kernel: [    0.844287] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep  7 04:32:44 node-2 kernel: [    0.855289] ACPI: Power Button [PWRB]
Sep  7 04:32:44 node-2 kernel: [    0.861046] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep  7 04:32:44 node-2 kernel: [    0.872662] ACPI: Power Button [PWRF]
Sep  7 04:32:44 node-2 kernel: [    0.899468] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep  7 04:32:44 node-2 kernel: [    0.911113] pstore: Registered erst as persistent store backend
Sep  7 04:32:44 node-2 kernel: [    0.917292] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep  7 04:32:44 node-2 kernel: [    0.929221] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep  7 04:32:44 node-2 kernel: [    0.955952] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep  7 04:32:44 node-2 kernel: [    0.989225] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep  7 04:32:44 node-2 kernel: [    1.003292] Linux agpgart interface v0.103
Sep  7 04:32:44 node-2 kernel: [    1.010926] brd: module loaded
Sep  7 04:32:44 node-2 kernel: [    1.018038] loop: module loaded
Sep  7 04:32:44 node-2 kernel: [    1.024735] libphy: Fixed MDIO Bus: probed
Sep  7 04:32:44 node-2 kernel: [    1.031190] tun: Universal TUN/TAP device driver, 1.6
Sep  7 04:32:44 node-2 kernel: [    1.037667] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep  7 04:32:44 node-2 kernel: [    1.044195] PPP generic driver version 2.4.2
Sep  7 04:32:44 node-2 kernel: [    1.050573] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep  7 04:32:44 node-2 kernel: [    1.057011] ehci-pci: EHCI PCI platform driver
Sep  7 04:32:44 node-2 kernel: [    1.063526] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep  7 04:32:44 node-2 kernel: [    1.069925] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep  7 04:32:44 node-2 kernel: [    1.082441] ehci-pci 0000:00:1a.0: debug port 2
Sep  7 04:32:44 node-2 kernel: [    1.092639] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep  7 04:32:44 node-2 kernel: [    1.092658] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep  7 04:32:44 node-2 kernel: [    1.109382] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep  7 04:32:44 node-2 kernel: [    1.115446] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep  7 04:32:44 node-2 kernel: [    1.121615] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  7 04:32:44 node-2 kernel: [    1.133522] usb usb1: Product: EHCI Host Controller
Sep  7 04:32:44 node-2 kernel: [    1.139543] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  7 04:32:44 node-2 kernel: [    1.145595] usb usb1: SerialNumber: 0000:00:1a.0
Sep  7 04:32:44 node-2 kernel: [    1.151541] hub 1-0:1.0: USB hub found
Sep  7 04:32:44 node-2 kernel: [    1.157300] hub 1-0:1.0: 2 ports detected
Sep  7 04:32:44 node-2 kernel: [    1.163093] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep  7 04:32:44 node-2 kernel: [    1.168664] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep  7 04:32:44 node-2 kernel: [    1.179569] ehci-pci 0000:00:1d.0: debug port 2
Sep  7 04:32:44 node-2 kernel: [    1.188870] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep  7 04:32:44 node-2 kernel: [    1.188873] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep  7 04:32:44 node-2 kernel: [    1.205301] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep  7 04:32:44 node-2 kernel: [    1.210507] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep  7 04:32:44 node-2 kernel: [    1.215806] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  7 04:32:44 node-2 kernel: [    1.226384] usb usb2: Product: EHCI Host Controller
Sep  7 04:32:44 node-2 kernel: [    1.231856] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  7 04:32:44 node-2 kernel: [    1.237404] usb usb2: SerialNumber: 0000:00:1d.0
Sep  7 04:32:44 node-2 kernel: [    1.242921] hub 2-0:1.0: USB hub found
Sep  7 04:32:44 node-2 kernel: [    1.248273] hub 2-0:1.0: 2 ports detected
Sep  7 04:32:44 node-2 kernel: [    1.253582] ehci-platform: EHCI generic platform driver
Sep  7 04:32:44 node-2 kernel: [    1.258815] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep  7 04:32:44 node-2 kernel: [    1.264128] ohci-pci: OHCI PCI platform driver
Sep  7 04:32:44 node-2 kernel: [    1.269435] ohci-platform: OHCI generic platform driver
Sep  7 04:32:44 node-2 kernel: [    1.274638] uhci_hcd: USB Universal Host Controller Interface driver
Sep  7 04:32:44 node-2 kernel: [    1.279978] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep  7 04:32:44 node-2 kernel: [    1.473079] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep  7 04:32:44 node-2 kernel: [    1.817151] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep  7 04:32:44 node-2 kernel: [    1.822659] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  7 04:32:44 node-2 kernel: [    1.828419] hub 1-1:1.0: USB hub found
Sep  7 04:32:44 node-2 kernel: [    1.833887] hub 1-1:1.0: 6 ports detected
Sep  7 04:32:44 node-2 kernel: [    1.948695] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep  7 04:32:44 node-2 kernel: [    2.317777] i8042: No controller found
Sep  7 04:32:44 node-2 kernel: [    2.323217] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep  7 04:32:44 node-2 kernel: [    2.324171] mousedev: PS/2 mouse device common for all mice
Sep  7 04:32:44 node-2 kernel: [    2.325857] rtc_cmos 00:02: RTC can wake from S4
Sep  7 04:32:44 node-2 kernel: [    2.327343] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep  7 04:32:44 node-2 kernel: [    2.327882] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep  7 04:32:44 node-2 kernel: [    2.328755] device-mapper: uevent: version 1.0.3
Sep  7 04:32:44 node-2 kernel: [    2.329474] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep  7 04:32:44 node-2 kernel: [    2.329553] ledtrig-cpu: registered to indicate activity on CPUs
Sep  7 04:32:44 node-2 kernel: [    2.330560] TCP: cubic registered
Sep  7 04:32:44 node-2 kernel: [    2.331034] NET: Registered protocol family 10
Sep  7 04:32:44 node-2 kernel: [    2.332737] NET: Registered protocol family 17
Sep  7 04:32:44 node-2 kernel: [    2.332864] Key type dns_resolver registered
Sep  7 04:32:44 node-2 kernel: [    2.333160] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep  7 04:32:44 node-2 kernel: [    2.333161] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  7 04:32:44 node-2 kernel: [    2.333792] hub 2-1:1.0: USB hub found
Sep  7 04:32:44 node-2 kernel: [    2.334027] hub 2-1:1.0: 8 ports detected
Sep  7 04:32:44 node-2 kernel: [    2.337271] Loading compiled-in X.509 certificates
Sep  7 04:32:44 node-2 kernel: [    2.338055] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep  7 04:32:44 node-2 kernel: [    2.338176] registered taskstats version 1
Sep  7 04:32:44 node-2 kernel: [    2.365960] Key type trusted registered
Sep  7 04:32:44 node-2 kernel: [    2.378122] Key type encrypted registered
Sep  7 04:32:44 node-2 kernel: [    2.378129] AppArmor: AppArmor sha1 policy hashing enabled
Sep  7 04:32:44 node-2 kernel: [    2.378139] IMA: No TPM chip found, activating TPM-bypass!
Sep  7 04:32:44 node-2 kernel: [    2.383418] regulator-dummy: disabling
Sep  7 04:32:44 node-2 kernel: [    2.384075]   Magic number: 0:443:514
Sep  7 04:32:44 node-2 kernel: [    2.481005] rtc_cmos 00:02: setting system clock to 2016-09-07 04:32:10 UTC (1473222730)
Sep  7 04:32:44 node-2 kernel: [    2.493274] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep  7 04:32:44 node-2 kernel: [    2.498830] EDD information not available.
Sep  7 04:32:44 node-2 kernel: [    2.504341] PM: Hibernation image not present or could not be loaded.
Sep  7 04:32:44 node-2 kernel: [    2.505201] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep  7 04:32:44 node-2 kernel: [    2.516479] Write protecting the kernel read-only data: 12288k
Sep  7 04:32:44 node-2 kernel: [    2.522755] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep  7 04:32:44 node-2 kernel: [    2.535516] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep  7 04:32:44 node-2 kernel: [    2.567085] device-mapper: multipath: version 1.6.0 loaded
Sep  7 04:32:44 node-2 kernel: [    2.574825] systemd-udevd[215]: starting version 204
Sep  7 04:32:44 node-2 kernel: [    2.599780] md: linear personality registered for level -1
Sep  7 04:32:44 node-2 kernel: [    2.608268] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep  7 04:32:44 node-2 kernel: [    2.620756] md: multipath personality registered for level -4
Sep  7 04:32:44 node-2 kernel: [    2.628667] md: raid0 personality registered for level 0
Sep  7 04:32:44 node-2 kernel: [    2.637006] md: raid1 personality registered for level 1
Sep  7 04:32:44 node-2 kernel: [    2.644357] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep  7 04:32:44 node-2 kernel: [    2.650711] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep  7 04:32:44 node-2 kernel: [    2.656927] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep  7 04:32:44 node-2 kernel: [    2.657755] megasas: FW now in Ready state
Sep  7 04:32:44 node-2 kernel: [    2.657869] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.657903] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.657954] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.657999] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658035] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658046] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658051] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658089] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658127] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658162] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658184] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658221] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658258] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658293] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658339] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658374] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.658533] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep  7 04:32:44 node-2 kernel: [    2.690331] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep  7 04:32:44 node-2 kernel: [    2.703576] 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  7 04:32:44 node-2 kernel: [    2.717400] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 04:32:44 node-2 kernel: [    2.724411] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.724417] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.724423] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.724429] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.724476] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.747774] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep  7 04:32:44 node-2 kernel: [    2.748055] raid6: sse2x1   10462 MB/s
Sep  7 04:32:44 node-2 kernel: [    2.767922] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep  7 04:32:44 node-2 kernel: [    2.781393] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 04:32:44 node-2 kernel: [    2.788185] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.788190] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.788194] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.788198] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.788235] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.809555] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep  7 04:32:44 node-2 kernel: [    2.815984] raid6: sse2x2   14218 MB/s
Sep  7 04:32:44 node-2 kernel: [    2.829507] 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  7 04:32:44 node-2 kernel: [    2.842838] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 04:32:44 node-2 kernel: [    2.849590] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.849594] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.849597] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.849602] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.849636] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.863894] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep  7 04:32:44 node-2 kernel: [    2.870755] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep  7 04:32:44 node-2 kernel: [    2.872744] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep  7 04:32:44 node-2 kernel: [    2.872757] 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  7 04:32:44 node-2 kernel: [    2.872765] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 04:32:44 node-2 kernel: [    2.873194] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.873259] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.873336] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.873454] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.873681] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 04:32:44 node-2 kernel: [    2.883954] raid6: sse2x4   16577 MB/s
Sep  7 04:32:44 node-2 kernel: [    2.938671] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep  7 04:32:44 node-2 kernel: [    2.945340] usb 2-1.4: Manufacturer: Avocent
Sep  7 04:32:44 node-2 kernel: [    2.951857] raid6: avx2x1   22048 MB/s
Sep  7 04:32:44 node-2 kernel: [    2.951859] usb 2-1.4: SerialNumber: 20111102-00000001
Sep  7 04:32:44 node-2 kernel: [    2.964761] hidraw: raw HID events driver (C) Jiri Kosina
Sep  7 04:32:44 node-2 kernel: [    2.973968] usbcore: registered new interface driver usbhid
Sep  7 04:32:44 node-2 kernel: [    2.980298] usbhid: USB HID core driver
Sep  7 04:32:44 node-2 kernel: [    2.986470] megasas:IOC Init cmd success
Sep  7 04:32:44 node-2 kernel: [    2.993573] 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  7 04:32:44 node-2 kernel: [    3.006383] 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  7 04:32:44 node-2 kernel: [    3.016229] megasas: INIT adapter done
Sep  7 04:32:44 node-2 kernel: [    3.025645] 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  7 04:32:44 node-2 kernel: [    3.031798] raid6: avx2x2   25288 MB/s
Sep  7 04:32:44 node-2 kernel: [    3.045061] 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  7 04:32:44 node-2 kernel: [    3.058479] 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  7 04:32:44 node-2 kernel: [    3.072117] 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  7 04:32:44 node-2 kernel: [    3.099701] raid6: avx2x4   29860 MB/s
Sep  7 04:32:44 node-2 kernel: [    3.106434] raid6: using algorithm avx2x4 (29860 MB/s)
Sep  7 04:32:44 node-2 kernel: [    3.111773] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep  7 04:32:44 node-2 kernel: [    3.112130] scsi0 : LSI SAS based MegaRAID driver
Sep  7 04:32:44 node-2 kernel: [    3.119326] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  7 04:32:44 node-2 kernel: [    3.134489] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  7 04:32:44 node-2 kernel: [    3.140024] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep  7 04:32:44 node-2 kernel: [    3.140308] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep  7 04:32:44 node-2 kernel: [    3.140750] sd 0:2:0:0: [sda] Write Protect is off
Sep  7 04:32:44 node-2 kernel: [    3.140751] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep  7 04:32:44 node-2 kernel: [    3.140846] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep  7 04:32:44 node-2 kernel: [    3.177617]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep  7 04:32:44 node-2 kernel: [    3.180124] sd 0:2:0:0: [sda] Attached SCSI disk
Sep  7 04:32:44 node-2 kernel: [    3.208605] raid6: using avx2x2 recovery algorithm
Sep  7 04:32:44 node-2 kernel: [    3.216452] xor: automatically using best checksumming function:
Sep  7 04:32:44 node-2 kernel: [    3.259549]    avx       : 35567.000 MB/sec
Sep  7 04:32:44 node-2 kernel: [    3.267124] async_tx: api initialized (async)
Sep  7 04:32:44 node-2 kernel: [    3.278113] md: raid6 personality registered for level 6
Sep  7 04:32:44 node-2 kernel: [    3.284762] md: raid5 personality registered for level 5
Sep  7 04:32:44 node-2 kernel: [    3.291172] md: raid4 personality registered for level 4
Sep  7 04:32:44 node-2 kernel: [    3.300639] md: raid10 personality registered for level 10
Sep  7 04:32:44 node-2 kernel: [    3.342591] random: lvm urandom read with 28 bits of entropy available
Sep  7 04:32:44 node-2 kernel: [    3.357690] multipathd (365): /proc/365/oom_adj is deprecated, please use /proc/365/oom_score_adj instead.
Sep  7 04:32:44 node-2 kernel: [    3.483510] Switched to clocksource tsc
Sep  7 04:32:44 node-2 kernel: [    3.514475] bio: create slab <bio-1> at 1
Sep  7 04:32:44 node-2 kernel: [    4.253110] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep  7 04:32:44 node-2 kernel: [    4.858767] init: plymouth-upstart-bridge main process (552) terminated with status 1
Sep  7 04:32:44 node-2 kernel: [    4.870777] init: plymouth-upstart-bridge main process ended, respawning
Sep  7 04:32:44 node-2 kernel: [    4.880171] init: plymouth-upstart-bridge main process (564) terminated with status 1
Sep  7 04:32:44 node-2 kernel: [    4.892398] init: plymouth-upstart-bridge main process ended, respawning
Sep  7 04:32:44 node-2 kernel: [    5.068568] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep  7 04:32:44 node-2 kernel: [    5.096081] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep  7 04:32:44 node-2 kernel: [    5.139416] random: nonblocking pool is initialized
Sep  7 04:32:44 node-2 kernel: [    5.233406] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep  7 04:32:44 node-2 kernel: [    5.299313] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep  7 04:32:44 node-2 kernel: [    5.398524] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep  7 04:32:44 node-2 kernel: [    5.565288] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep  7 04:32:44 node-2 kernel: [    5.602702] XFS (dm-0): Mounting Filesystem
Sep  7 04:32:44 node-2 kernel: [    5.893737] XFS (dm-0): Ending clean mount
Sep  7 04:32:44 node-2 kernel: [    5.985073] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep  7 04:32:44 node-2 kernel: [    6.015582] XFS (dm-1): Mounting Filesystem
Sep  7 04:32:44 node-2 kernel: [    6.119441] XFS (dm-1): Ending clean mount
Sep  7 04:32:44 node-2 kernel: [    8.083507] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep  7 04:32:44 node-2 kernel: [    8.108324] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep  7 04:32:44 node-2 kernel: [    8.296104] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  7 04:32:44 node-2 kernel: [    8.296110] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep  7 04:32:44 node-2 kernel: [    8.296115] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep  7 04:32:44 node-2 kernel: [    8.296120] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep  7 04:32:44 node-2 kernel: [    8.335023] systemd-udevd[778]: starting version 204
Sep  7 04:32:44 node-2 kernel: [    8.482309] power_meter ACPI000D:00: Found ACPI power meter.
Sep  7 04:32:44 node-2 kernel: [    8.482324] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep  7 04:32:44 node-2 kernel: [    8.509435] IPMI System Interface driver.
Sep  7 04:32:44 node-2 kernel: [    8.509473] ipmi_si: probing via ACPI
Sep  7 04:32:44 node-2 kernel: [    8.509491] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep  7 04:32:44 node-2 kernel: [    8.509492] ipmi_si: Adding ACPI-specified kcs state machine
Sep  7 04:32:44 node-2 kernel: [    8.509499] ipmi_si: probing via SMBIOS
Sep  7 04:32:44 node-2 kernel: [    8.509500] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep  7 04:32:44 node-2 kernel: [    8.509500] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep  7 04:32:44 node-2 kernel: [    8.509502] ipmi_si: probing via SPMI
Sep  7 04:32:44 node-2 kernel: [    8.509503] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep  7 04:32:44 node-2 kernel: [    8.509504] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep  7 04:32:44 node-2 kernel: [    8.509505] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep  7 04:32:44 node-2 kernel: [    8.509814] wmi: Mapper loaded
Sep  7 04:32:44 node-2 kernel: [    8.551523] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep  7 04:32:44 node-2 kernel: [    8.551529] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  7 04:32:44 node-2 kernel: [    8.551532] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep  7 04:32:44 node-2 kernel: [    8.551533] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  7 04:32:44 node-2 kernel: [    8.551546] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep  7 04:32:44 node-2 kernel: [    8.554405] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  7 04:32:44 node-2 kernel: [    8.595562] systemd-udevd[807]: renamed network interface eth0 to enp6s0
Sep  7 04:32:44 node-2 kernel: [    8.619394] systemd-udevd[798]: renamed network interface eth1 to enp7s0
Sep  7 04:32:44 node-2 kernel: [    8.658372] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep  7 04:32:44 node-2 kernel: [    8.658378] ipmi_si 00:09: IPMI kcs interface initialized
Sep  7 04:32:44 node-2 kernel: [    8.679701] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Sep  7 04:32:44 node-2 kernel: [    8.719314] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Sep  7 04:32:44 node-2 kernel: [    9.021331] type=1400 audit(1473222737.134:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.021486] type=1400 audit(1473222737.134:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1064 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.021616] type=1400 audit(1473222737.134:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1064 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.033373] type=1400 audit(1473222737.146:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1015 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.033514] type=1400 audit(1473222737.146:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1015 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.033634] type=1400 audit(1473222737.146:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1015 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.044652] type=1400 audit(1473222737.158:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=987 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.044807] type=1400 audit(1473222737.158:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=987 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.044924] type=1400 audit(1473222737.158:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=987 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.045230] type=1400 audit(1473222737.158:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1016 comm="apparmor_parser"
Sep  7 04:32:44 node-2 kernel: [    9.659975] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep  7 04:32:44 node-2 kernel: [    9.660690] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep  7 04:32:44 node-2 kernel: [    9.890478] enic 0000:06:00.0 enp6s0: Link UP
Sep  7 04:32:44 node-2 kernel: [    9.891598] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep  7 04:32:44 node-2 kernel: [    9.891603] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep  7 04:32:44 node-2 kernel: [   18.767783] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep  7 04:32:45 node-2 failsafe: Failsafe of 120 seconds reached.
Sep  7 04:32:45 node-2 kernel: [   37.819774] init: failsafe main process (8424) killed by TERM signal
Sep  7 04:32:46 node-2 dbus[8460]: [system] AppArmor D-Bus mediation is enabled
Sep  7 04:32:46 node-2 kernel: [   38.116757] audit_printk_skb: 30 callbacks suppressed
Sep  7 04:32:46 node-2 kernel: [   38.116759] type=1400 audit(1473222766.201:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8552 comm="apparmor_parser"
Sep  7 04:32:46 node-2 kernel: [   38.117020] type=1400 audit(1473222766.201:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8551 comm="apparmor_parser"
Sep  7 04:32:46 node-2 kernel: [   38.117025] type=1400 audit(1473222766.201:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8551 comm="apparmor_parser"
Sep  7 04:32:46 node-2 kernel: [   38.117028] type=1400 audit(1473222766.201:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Sep  7 04:32:46 node-2 kernel: [   38.117249] type=1400 audit(1473222766.201:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8551 comm="apparmor_parser"
Sep  7 04:32:46 node-2 kernel: [   38.117251] type=1400 audit(1473222766.201:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Sep  7 04:32:46 node-2 kernel: [   38.117367] type=1400 audit(1473222766.201:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Sep  7 04:32:46 node-2 kernel: [   38.182740] type=1400 audit(1473222766.269:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8554 comm="apparmor_parser"
Sep  7 04:32:46 node-2 cron[8582]: (CRON) INFO (pidfile fd = 3)
Sep  7 04:32:46 node-2 anacron[8620]: Anacron 2.3 started on 2016-09-07
Sep  7 04:32:46 node-2 cron[8621]: (CRON) STARTUP (fork ok)
Sep  7 04:32:46 node-2 anacron[8620]: Will run job `cron.daily' in 5 min.
Sep  7 04:32:46 node-2 anacron[8620]: Will run job `cron.weekly' in 10 min.
Sep  7 04:32:46 node-2 anacron[8620]: Will run job `cron.monthly' in 15 min.
Sep  7 04:32:46 node-2 anacron[8620]: Jobs will be executed sequentially
Sep  7 04:32:46 node-2 multipathd: path checkers start up
Sep  7 04:32:46 node-2 cron[8621]: (CRON) INFO (Running @reboot jobs)
Sep  7 04:32:46 node-2 postfix/master[8762]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep  7 04:32:50 node-2 puppet-agent[9055]: Reopening log files
Sep  7 04:32:50 node-2 puppet-agent[9055]: Could not request certificate: Connection refused - connect(2)
Sep  7 04:33:01 node-2 CRON[9106]: (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  7 04:33:12 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 04:33:12 node-2 nailgun-agent: D, [2016-09-07T04:33:01.663265 #9109] DEBUG -- : Sleep for 11 seconds before sending request
Sep  7 04:33:12 node-2 nailgun-agent: I, [2016-09-07T04:33:12.679095 #9109]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  7 04:33:13 node-2 nailgun-agent: D, [2016-09-07T04:33:13.122049 #9109] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep  7 04:33:16 node-2 kernel: [   67.964849] init: plymouth-upstart-bridge main process ended, respawning
Sep  7 04:33:16 node-2 puppet-agent[9055]: Could not run: SIGTERM
Sep  7 04:33:16 node-2 kernel: [   68.245606] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep  7 04:33:16 node-2 ec2: 
Sep  7 04:33:16 node-2 ec2: #############################################################
Sep  7 04:33:16 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep  7 04:33:16 node-2 ec2: 1024 c1:e5:94:a5:39:34:4a:81:4e:f1:ab:a8:4f:30:a3:3c  root@node-2.domain.tld (DSA)
Sep  7 04:33:16 node-2 ec2: 256 73:9f:38:c3:da:85:58:13:bb:d5:a0:f5:14:20:bb:92  root@node-2.domain.tld (ECDSA)
Sep  7 04:33:16 node-2 ec2: 256 bc:c5:47:4b:fe:5c:cf:71:d1:4a:43:0b:4f:56:52:79  root@node-2.domain.tld (ED25519)
Sep  7 04:33:16 node-2 ec2: 2048 1c:8d:48:05:d9:59:6a:bc:80:14:99:b2:60:cd:7f:31  root@node-2.domain.tld (RSA)
Sep  7 04:33:16 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep  7 04:33:16 node-2 ec2: #############################################################
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.267478 #9109] DEBUG -- : Trying to find block devices
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.267543 #9109] DEBUG -- : Found block device: sda
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.267645 #9109] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.267671 #9109] DEBUG -- : Trying to get list of physical devices
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.267852 #9109] DEBUG -- : Getting udev properties for device: sda
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.269674 #9109] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /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"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Sep  7 04:33:25 node-2 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35854", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.269705 #9109] DEBUG -- : Trying to find out if device sda is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.269746 #9109] DEBUG -- : Device sda removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.269783 #9109] DEBUG -- : Device sda seems to be appropriate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.270277 #9109] DEBUG -- : Getting udev properties for device: dm-0
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.271851 #9109] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-gz1oIed8lj7s7gkmmrL4FGZxTcbXw3uX5lrDtxqzuSn4HEoncO7IGdd3nb1CKkd2 /dev/disk/by-uuid/ad3404ba-1a5d-4917-8a78-1a3c190a988f /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-gz1oIed8lj7s7gkmmrL4FGZxTcbXw3uX5lrDtxqzuSn4HEoncO7IGdd3nb1CKkd2", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ad3404ba-1a5d-4917-8a78-1a3c190a988f", "ID_FS_UUID_ENC"=>"ad3404ba-1a5d-4917-8a78-1a3c190a988f", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71045", "nomdmonddf"=>"1", "nomd
Sep  7 04:33:25 node-2 nailgun-agent: monisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.271876 #9109] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.271931 #9109] DEBUG -- : Device dm-0 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.271944 #9109] DEBUG -- : Device dm-0 seems to be appropriate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.271958 #9109] DEBUG -- : Getting udev properties for device: dm-1
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.273604 #9109] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-kHg0fuG1E5UXQEB6Z93JcnOCXXWG6y1H4e2qomt0qvqMzqreVKhcGAi7E6sn0VjN /dev/disk/by-uuid/b355abbe-37dc-416b-be0e-89194686b199 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-kHg0fuG1E5UXQEB6Z93JcnOCXXWG6y1H4e2qomt0qvqMzqreVKhcGAi7E6sn0VjN", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b355abbe-37dc-416b-be0e-89194686b199", "ID_FS_UUID_ENC"=>"b355abbe-37dc-416b-be0e-89194686b199", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71
Sep  7 04:33:25 node-2 nailgun-agent: 45", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.273632 #9109] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.273661 #9109] DEBUG -- : Device dm-1 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.273675 #9109] DEBUG -- : Device dm-1 seems to be appropriate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.273709 #9109] DEBUG -- : Getting udev properties for device: dm-2
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.275677 #9109] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-YurOEHfpSlZVMnbc02N93M2xyNZDMxT5NW9qIcJjyZ5Rpa68cvTNeCrXW0HZ4HaP /dev/disk/by-uuid/44c31063-768f-488a-aea3-fc8cdfe5b27b /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-YurOEHfpSlZVMnbc02N93M2xyNZDMxT5NW9qIcJjyZ5Rpa68cvTNeCrXW0HZ4HaP", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"44c31063-768f-488a-aea3-fc8cdfe5b27b", "ID_FS_UUID_ENC"=>"44c31063-768f-488a-aea3-fc8cdfe5b27b", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17634", "nomdmond
Sep  7 04:33:25 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.275704 #9109] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.275733 #9109] DEBUG -- : Device dm-2 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.275764 #9109] DEBUG -- : Device dm-2 seems to be appropriate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.275777 #9109] DEBUG -- : Getting udev properties for device: dm-3
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.277620 #9109] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-mo7Cfr3aeKtoGhfxSNKIuJ5f4NV7J60qlLl4dV3OOEsBEfQGvpTki0zVqIc2KcSv /dev/disk/by-uuid/bb56ca32-3612-4a94-b027-bf3bd67d2d67 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-mo7Cfr3aeKtoGhfxSNKIuJ5f4NV7J60qlLl4dV3OOEsBEfQGvpTki0zVqIc2KcSv", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"bb56ca32-3612-4a94-b027-bf3bd67d2d67", "ID_FS_UUID_ENC"=>"bb56ca32-3612-4a94-b027-bf3bd67d2d67", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15863", "nomdmonddf"=>"1", 
Sep  7 04:33:25 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.277646 #9109] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.277676 #9109] DEBUG -- : Device dm-3 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.277708 #9109] DEBUG -- : Device dm-3 seems to be appropriate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.277723 #9109] DEBUG -- : Getting udev properties for device: dm-4
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.279396 #9109] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-wm0UMe3vGkcp2WxPHR8EwIvryVwrzYOd1cd0r6ChH6Q4gUcE4AMARP9mW4h1qNcH /dev/disk/by-uuid/e28a5e06-e224-4b3b-96f9-d76bc3dd1c77 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-wm0UMe3vGkcp2WxPHR8EwIvryVwrzYOd1cd0r6ChH6Q4gUcE4AMARP9mW4h1qNcH", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e28a5e06-e224-4b3b-96f9-d76bc3dd1c77", "ID_FS_UUID_ENC"=>"e28a5e06-e224-4b3b-96f9-d76bc3dd1c77", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24551", "nomdmonddf"=>"1", "nomd
Sep  7 04:33:25 node-2 nailgun-agent: monisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.279441 #9109] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.279470 #9109] DEBUG -- : Device dm-4 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.279484 #9109] DEBUG -- : Device dm-4 seems to be appropriate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.279500 #9109] DEBUG -- : Getting udev properties for device: dm-5
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.281095 #9109] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-wm0UMe3vGkcp2WxPHR8EwIvryVwrzYOdvPdqkdibNoDkTD14djcu6VKKw921Gls4 /dev/disk/by-uuid/701eb100-555c-4bf9-9b7f-74444334f601 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-wm0UMe3vGkcp2WxPHR8EwIvryVwrzYOdvPdqkdibNoDkTD14djcu6VKKw921Gls4", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"701eb100-555c-4bf9-9b7f-74444334f601", "ID_FS_UUID_ENC"=>"701eb100-555c-4bf9-9b7f-74444334f601", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24927", "nomdmonddf"=>"1", "nomdmonisw"
Sep  7 04:33:25 node-2 nailgun-agent: =>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.281120 #9109] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.281150 #9109] DEBUG -- : Device dm-5 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.281191 #9109] DEBUG -- : Device dm-5 seems to be appropriate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.281204 #9109] DEBUG -- : Getting udev properties for device: ram0
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.282956 #9109] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44955", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.282980 #9109] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.283024 #9109] DEBUG -- : Device ram0 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.283043 #9109] DEBUG -- : Getting udev properties for device: ram1
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.284617 #9109] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44966", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.284655 #9109] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.284688 #9109] DEBUG -- : Device ram1 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.284707 #9109] DEBUG -- : Getting udev properties for device: ram2
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.286139 #9109] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45061", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.286163 #9109] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.286254 #9109] DEBUG -- : Device ram2 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.286275 #9109] DEBUG -- : Getting udev properties for device: ram3
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.287723 #9109] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45076", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.287747 #9109] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.287780 #9109] DEBUG -- : Device ram3 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.287809 #9109] DEBUG -- : Getting udev properties for device: ram4
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.289362 #9109] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45097", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.289400 #9109] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.289432 #9109] DEBUG -- : Device ram4 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.289450 #9109] DEBUG -- : Getting udev properties for device: ram5
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.290963 #9109] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45116", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.291000 #9109] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.291049 #9109] DEBUG -- : Device ram5 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.291068 #9109] DEBUG -- : Getting udev properties for device: ram6
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.292557 #9109] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45135", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.292581 #9109] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.292612 #9109] DEBUG -- : Device ram6 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.292630 #9109] DEBUG -- : Getting udev properties for device: ram7
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.294056 #9109] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45155", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.294090 #9109] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.294121 #9109] DEBUG -- : Device ram7 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.294141 #9109] DEBUG -- : Getting udev properties for device: ram8
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.295795 #9109] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45174", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.295819 #9109] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.295862 #9109] DEBUG -- : Device ram8 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.295881 #9109] DEBUG -- : Getting udev properties for device: ram9
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.297462 #9109] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45194", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.297488 #9109] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.297542 #9109] DEBUG -- : Device ram9 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.297561 #9109] DEBUG -- : Getting udev properties for device: loop0
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.299151 #9109] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44857", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.299175 #9109] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.299206 #9109] DEBUG -- : Device loop0 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.299223 #9109] DEBUG -- : Getting udev properties for device: loop1
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.300688 #9109] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44869", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.300713 #9109] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.300751 #9109] DEBUG -- : Device loop1 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.300779 #9109] DEBUG -- : Getting udev properties for device: loop2
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.302427 #9109] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44880", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.302451 #9109] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.302525 #9109] DEBUG -- : Device loop2 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.302544 #9109] DEBUG -- : Getting udev properties for device: loop3
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.304247 #9109] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44894", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.304271 #9109] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.304301 #9109] DEBUG -- : Device loop3 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.304328 #9109] DEBUG -- : Getting udev properties for device: loop4
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.306000 #9109] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44906", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.306024 #9109] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.306058 #9109] DEBUG -- : Device loop4 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.306076 #9109] DEBUG -- : Getting udev properties for device: loop5
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.307627 #9109] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44917", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.307651 #9109] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.307686 #9109] DEBUG -- : Device loop5 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.307727 #9109] DEBUG -- : Getting udev properties for device: loop6
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.309361 #9109] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44928", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.309392 #9109] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.309435 #9109] DEBUG -- : Device loop6 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.309452 #9109] DEBUG -- : Getting udev properties for device: loop7
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.310943 #9109] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44937", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.310974 #9109] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.315211 #9109] DEBUG -- : Device loop7 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.315235 #9109] DEBUG -- : Getting udev properties for device: ram10
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.316840 #9109] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44978", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.316863 #9109] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.316896 #9109] DEBUG -- : Device ram10 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.316940 #9109] DEBUG -- : Getting udev properties for device: ram11
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.318457 #9109] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44993", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.318481 #9109] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.318522 #9109] DEBUG -- : Device ram11 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.318541 #9109] DEBUG -- : Getting udev properties for device: ram12
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.320019 #9109] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45007", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.320045 #9109] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.320075 #9109] DEBUG -- : Device ram12 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.320092 #9109] DEBUG -- : Getting udev properties for device: ram13
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.321716 #9109] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45020", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.321739 #9109] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.321774 #9109] DEBUG -- : Device ram13 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.321791 #9109] DEBUG -- : Getting udev properties for device: ram14
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.323350 #9109] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45032", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.323374 #9109] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.323408 #9109] DEBUG -- : Device ram14 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.323426 #9109] DEBUG -- : Getting udev properties for device: ram15
Sep  7 04:33:25 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325022 #9109] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45044", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325046 #9109] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325078 #9109] DEBUG -- : Device ram15 removable parameter: "0"
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325111 #9109] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325125 #9109] DEBUG -- : Block device seems to be physical data storage: sda
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325158 #9109] DEBUG -- : Found block device: dm-0
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325172 #9109] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325185 #9109] DEBUG -- : Found block device: dm-1
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325196 #9109] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325206 #9109] DEBUG -- : Found block device: dm-2
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325241 #9109] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325250 #9109] DEBUG -- : Found block device: dm-3
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325260 #9109] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325268 #9109] DEBUG -- : Found block device: dm-4
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325278 #9109] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325286 #9109] DEBUG -- : Found block device: dm-5
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325296 #9109] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325304 #9109] DEBUG -- : Found block device: ram0
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325313 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325321 #9109] DEBUG -- : Found block device: ram1
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325360 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325369 #9109] DEBUG -- : Found block device: ram2
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325379 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325387 #9109] DEBUG -- : Found block device: ram3
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325397 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325405 #9109] DEBUG -- : Found block device: ram4
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325415 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325423 #9109] DEBUG -- : Found block device: ram5
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325433 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325441 #9109] DEBUG -- : Found block device: ram6
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325482 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325491 #9109] DEBUG -- : Found block device: ram7
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325501 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325509 #9109] DEBUG -- : Found block device: ram8
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325519 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325528 #9109] DEBUG -- : Found block device: ram9
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325537 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325545 #9109] DEBUG -- : Found block device: loop0
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325554 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325562 #9109] DEBUG -- : Found block device: loop1
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325572 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325620 #9109] DEBUG -- : Found block device: loop2
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325630 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325639 #9109] DEBUG -- : Found block device: loop3
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325648 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325656 #9109] DEBUG -- : Found block device: loop4
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325665 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325674 #9109] DEBUG -- : Found block device: loop5
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325683 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325690 #9109] DEBUG -- : Found block device: loop6
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325743 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325752 #9109] DEBUG -- : Found block device: loop7
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325762 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325770 #9109] DEBUG -- : Found block device: ram10
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325779 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325787 #9109] DEBUG -- : Found block device: ram11
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325796 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325804 #9109] DEBUG -- : Found block device: ram12
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325813 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325854 #9109] DEBUG -- : Found block device: ram13
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325864 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325873 #9109] DEBUG -- : Found block device: ram14
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325883 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325891 #9109] DEBUG -- : Found block device: ram15
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325901 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.325927 #9109] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.416443 #9109] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep  7 04:33:25 node-2 nailgun-agent: D, [2016-09-07T04:33:25.416484 #9109] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep  7 04:33:37 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425651 #9109] DEBUG -- : Trying to find block devices
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425760 #9109] DEBUG -- : Found block device: sda
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425790 #9109] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425811 #9109] DEBUG -- : Block device seems to be physical data storage: sda
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425832 #9109] DEBUG -- : Found block device: dm-0
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425866 #9109] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425879 #9109] DEBUG -- : Found block device: dm-1
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425890 #9109] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425900 #9109] DEBUG -- : Found block device: dm-2
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425910 #9109] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425919 #9109] DEBUG -- : Found block device: dm-3
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425929 #9109] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425967 #9109] DEBUG -- : Found block device: dm-4
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425978 #9109] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425988 #9109] DEBUG -- : Found block device: dm-5
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.425998 #9109] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426007 #9109] DEBUG -- : Found block device: ram0
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426016 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426025 #9109] DEBUG -- : Found block device: ram1
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426036 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426062 #9109] DEBUG -- : Found block device: ram2
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426073 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426082 #9109] DEBUG -- : Found block device: ram3
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426092 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426101 #9109] DEBUG -- : Found block device: ram4
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426111 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426119 #9109] DEBUG -- : Found block device: ram5
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426129 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426137 #9109] DEBUG -- : Found block device: ram6
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426147 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426155 #9109] DEBUG -- : Found block device: ram7
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426184 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426212 #9109] DEBUG -- : Found block device: ram8
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426232 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426243 #9109] DEBUG -- : Found block device: ram9
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426253 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426262 #9109] DEBUG -- : Found block device: loop0
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426272 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426281 #9109] DEBUG -- : Found block device: loop1
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426290 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426299 #9109] DEBUG -- : Found block device: loop2
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426336 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426346 #9109] DEBUG -- : Found block device: loop3
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426356 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426365 #9109] DEBUG -- : Found block device: loop4
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426375 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426384 #9109] DEBUG -- : Found block device: loop5
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426393 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426401 #9109] DEBUG -- : Found block device: loop6
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426411 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426447 #9109] DEBUG -- : Found block device: loop7
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426457 #9109] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426466 #9109] DEBUG -- : Found block device: ram10
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426475 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426484 #9109] DEBUG -- : Found block device: ram11
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426493 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426501 #9109] DEBUG -- : Found block device: ram12
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426511 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426519 #9109] DEBUG -- : Found block device: ram13
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426529 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426563 #9109] DEBUG -- : Found block device: ram14
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426574 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426582 #9109] DEBUG -- : Found block device: ram15
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426592 #9109] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.426624 #9109] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Sep  7 04:33:37 node-2 nailgun-agent: D, [2016-09-07T04:33:37.567513 #9109] DEBUG -- : Response: status: 200 body: {"id": 2}
Sep  7 04:33:37 node-2 nailgun-agent: I, [2016-09-07T04:33:37.567786 #9109]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep  7 04:33:38 node-2 puppet-user[9937]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep  7 04:33:38 node-2 puppet-user[9937]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Sep  7 04:33:39 node-2 puppet-user[9937]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep  7 04:33:39 node-2 puppet-user[9937]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep  7 04:33:39 node-2 puppet-user[9937]: Finished catalog run in 0.70 seconds
Sep  7 04:33:41 node-2 multipathd: uevent trigger error
Sep  7 04:33:41 node-2 puppet-user[10362]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  7 04:33:41 node-2 puppet-user[10362]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Sep  7 04:33:41 node-2 puppet-user[10362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep  7 04:33:41 node-2 puppet-user[10362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep  7 04:33:41 node-2 puppet-user[10362]: (/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  7 04:33:41 node-2 puppet-user[10362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep  7 04:33:41 node-2 puppet-user[10362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep  7 04:33:41 node-2 puppet-user[10362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep  7 04:33:41 node-2 puppet-user[10362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep  7 04:33:41 node-2 puppet-user[10362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep  7 04:33:41 node-2 puppet-user[10362]: Finished catalog run in 0.08 seconds
Sep  7 04:33:42 node-2 puppet-user[10827]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep  7 04:33:42 node-2 puppet-user[10827]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Sep  7 04:33:42 node-2 puppet-user[10827]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep  7 04:33:42 node-2 puppet-user[10827]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep  7 04:33:42 node-2 puppet-user[10827]: Finished catalog run in 0.04 seconds
Sep  7 04:33:44 node-2 puppet-user[11294]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep  7 04:33:44 node-2 puppet-user[11294]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Sep  7 04:33:44 node-2 puppet-user[11294]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep  7 04:33:44 node-2 puppet-user[11294]: Finished catalog run in 0.03 seconds
Sep  7 04:33:46 node-2 puppet-user[11750]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep  7 04:33:46 node-2 puppet-user[11750]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Sep  7 04:33:46 node-2 puppet-user[11750]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep  7 04:33:46 node-2 puppet-user[11750]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep  7 04:33:47 node-2 puppet-user[11750]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep  7 04:33:47 node-2 puppet-user[11750]: Finished catalog run in 0.82 seconds
Sep  7 04:33:48 node-2 puppet-user[12247]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep  7 04:33:49 node-2 puppet-user[12247]: Compiled catalog for node-2.domain.tld in environment production in 0.40 seconds
Sep  7 04:33:49 node-2 puppet-user[12247]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep  7 04:33:49 node-2 puppet-user[12247]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep  7 04:33:49 node-2 puppet-user[12247]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep  7 04:33:49 node-2 puppet-user[12247]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep  7 04:33:49 node-2 puppet-user[12247]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep  7 04:33:49 node-2 puppet-user[12247]: Finished catalog run in 0.35 seconds
Sep  7 04:33:51 node-2 puppet-user[12724]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep  7 04:33:52 node-2 puppet-user[12724]: Compiled catalog for node-2.domain.tld in environment production in 0.21 seconds
Sep  7 04:33:52 node-2 puppet-user[12724]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep  7 04:33:52 node-2 kernel: [  104.104562] nr_pdflush_threads exported in /proc is scheduled for removal
Sep  7 04:33:52 node-2 kernel: [  104.104616] 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  7 04:33:52 node-2 puppet-user[12724]: (/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  7 04:33:52 node-2 puppet-user[12724]: Finished catalog run in 0.09 seconds
Sep  7 04:33:54 node-2 puppet-user[13185]: (Scope(Class[main])) MODULAR: sync_time
Sep  7 04:33:54 node-2 puppet-user[13185]: Compiled catalog for node-2.domain.tld in environment production in 0.04 seconds
Sep  7 04:33:54 node-2 ntpdate[13605]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep  7 04:34:00 node-2 ntpdate[13605]: adjust time server 10.20.0.2 offset 0.029260 sec
Sep  7 04:34:00 node-2 puppet-user[13185]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep  7 04:34:00 node-2 puppet-user[13185]: Finished catalog run in 6.18 seconds
Sep  7 04:34:01 node-2 CRON[13752]: (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  7 04:34:01 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 04:34:01 node-2 nailgun-agent: I, [2016-09-07T04:34:01.750153 #13755]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  7 04:34:05 node-2 puppet-user[13917]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  7 04:34:05 node-2 puppet-user[13917]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep  7 04:34:05 node-2 puppet-user[13917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep  7 04:34:05 node-2 puppet-user[13917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep  7 04:34:05 node-2 puppet-user[13917]: Finished catalog run in 0.07 seconds
Sep  7 04:34:07 node-2 puppet-user[14374]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep  7 04:34:08 node-2 puppet-user[14374]: Compiled catalog for node-2.domain.tld in environment production in 0.98 seconds
Sep  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:09 node-2 puppet-user[14374]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Sep  7 04:34:09 node-2 puppet-user[14374]: (/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  7 04:34:14 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 04:34:14 node-2 nailgun-agent: I, [2016-09-07T04:34:14.797202 #13755]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep  7 04:34:18 node-2 puppet-user[14374]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep  7 04:34:18 node-2 puppet-user[14374]: Finished catalog run in 9.63 seconds
Sep  7 04:34:20 node-2 puppet-user[15276]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep  7 04:34:20 node-2 puppet-user[15276]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Sep  7 04:34:25 node-2 puppet-user[15276]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep  7 04:34:55 node-2 puppet-user[15276]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep  7 04:34:55 node-2 puppet-user[15276]: Finished catalog run in 34.50 seconds
Sep  7 04:34:57 node-2 puppet-user[17701]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep  7 04:34:57 node-2 puppet-user[17701]: Compiled catalog for node-2.domain.tld in environment production in 0.58 seconds
Sep  7 04:34:57 node-2 puppet-user[17701]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep  7 04:34:57 node-2 puppet-user[17701]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep  7 04:34:57 node-2 puppet-user[17701]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep  7 04:34:57 node-2 puppet-user[17701]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep  7 04:34:58 node-2 puppet-user[17701]: Finished catalog run in 0.11 seconds
Sep  7 04:34:59 node-2 puppet-user[18163]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep  7 04:35:00 node-2 puppet-user[18163]: Compiled catalog for node-2.domain.tld in environment production in 0.97 seconds
Sep  7 04:35:01 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep  7 04:35:01 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep  7 04:35:01 node-2 crontab[18608]: (root) LIST (root)
Sep  7 04:35:01 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep  7 04:35:01 node-2 crontab[18609]: (root) REPLACE (root)
Sep  7 04:35:01 node-2 CRON[18637]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep  7 04:35:03 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep  7 04:35:04 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep  7 04:35:05 node-2 puppet-user[18163]: (/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  7 04:35:05 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8397" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 04:35:05 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep  7 04:35:08 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:08 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:08 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:08 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:08 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:08 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:28 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:28 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:28 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:28 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:28 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:28 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:35:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:36:32 node-2 ntpdate[30024]: no servers can be used, exiting
<27>Sep  7 04:36:32 node-2 ntpdate[30150]: no servers can be used, exiting
<27>Sep  7 04:36:32 node-2 ntpdate[30437]: no servers can be used, exiting
<27>Sep  7 04:37:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:07 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:07 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:07 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:07 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:07 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:07 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:07 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:19 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:19 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:19 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:22 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:22 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:22 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:22 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:22 node-2 multipathd: uevent trigger error
<27>Sep  7 04:37:22 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:32 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 04:38:32 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 04:38:38 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 04:38:38 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 04:38:44 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 04:38:49 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 04:38:49 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 04:38:56 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:56 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:56 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:56 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:56 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:56 node-2 multipathd: uevent trigger error
<27>Sep  7 04:38:57 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:16 node-2 multipathd: uevent trigger error
<129>Sep  7 04:39:18 node-2 haproxy[20402]: 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  7 04:39:18 node-2 haproxy[20402]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:18 node-2 haproxy[20402]: 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  7 04:39:18 node-2 haproxy[20402]: proxy mysqld has no server available!
<27>Sep  7 04:39:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:21 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:25 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:25 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:25 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:25 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:25 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:25 node-2 multipathd: uevent trigger error
<129>Sep  7 04:39:27 node-2 haproxy[23122]: 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  7 04:39:27 node-2 haproxy[23122]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:28 node-2 haproxy[23126]: 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  7 04:39:28 node-2 haproxy[23126]: proxy mysqld has no server available!
<129>Sep  7 04:39:28 node-2 haproxy[23126]: 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  7 04:39:28 node-2 haproxy[23126]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:28 node-2 haproxy[23126]: 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  7 04:39:28 node-2 haproxy[23126]: proxy object-storage has no server available!
<27>Sep  7 04:39:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:30 node-2 multipathd: uevent trigger error
<129>Sep  7 04:39:32 node-2 haproxy[24459]: 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  7 04:39:32 node-2 haproxy[24459]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:33 node-2 haproxy[24463]: 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  7 04:39:33 node-2 haproxy[24463]: proxy neutron has no server available!
<129>Sep  7 04:39:33 node-2 haproxy[24463]: 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  7 04:39:33 node-2 haproxy[24463]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:33 node-2 haproxy[24463]: 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  7 04:39:33 node-2 haproxy[24463]: proxy mysqld has no server available!
<129>Sep  7 04:39:33 node-2 haproxy[24463]: 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  7 04:39:34 node-2 haproxy[24463]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:34 node-2 haproxy[24463]: 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  7 04:39:34 node-2 haproxy[24463]: proxy object-storage has no server available!
<27>Sep  7 04:39:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:35 node-2 multipathd: uevent trigger error
<129>Sep  7 04:39:38 node-2 haproxy[25855]: 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  7 04:39:38 node-2 haproxy[25855]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:38 node-2 haproxy[25855]: Server keystone-1/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  7 04:39:38 node-2 haproxy[25855]: proxy keystone-1 has no server available!
<129>Sep  7 04:39:38 node-2 haproxy[25855]: 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  7 04:39:38 node-2 haproxy[25855]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:38 node-2 haproxy[25855]: Server keystone-2/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  7 04:39:38 node-2 haproxy[25855]: proxy keystone-2 has no server available!
<129>Sep  7 04:39:38 node-2 haproxy[25855]: 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  7 04:39:39 node-2 haproxy[25859]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:39 node-2 haproxy[25859]: 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  7 04:39:39 node-2 haproxy[25859]: proxy neutron has no server available!
<129>Sep  7 04:39:39 node-2 haproxy[25859]: 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  7 04:39:39 node-2 haproxy[25859]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:39 node-2 haproxy[25859]: 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  7 04:39:39 node-2 haproxy[25859]: proxy mysqld has no server available!
<129>Sep  7 04:39:39 node-2 haproxy[25859]: 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  7 04:39:39 node-2 haproxy[25859]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:39 node-2 haproxy[25859]: 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  7 04:39:39 node-2 haproxy[25859]: proxy object-storage has no server available!
<27>Sep  7 04:39:41 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:41 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:41 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:41 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:41 node-2 multipathd: uevent trigger error
<129>Sep  7 04:39:43 node-2 haproxy[27395]: 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  7 04:39:43 node-2 haproxy[27395]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:43 node-2 haproxy[27395]: Server keystone-1/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  7 04:39:43 node-2 haproxy[27395]: proxy keystone-1 has no server available!
<129>Sep  7 04:39:44 node-2 haproxy[27399]: 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  7 04:39:44 node-2 haproxy[27399]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:44 node-2 haproxy[27399]: Server keystone-2/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  7 04:39:44 node-2 haproxy[27399]: proxy keystone-2 has no server available!
<129>Sep  7 04:39:44 node-2 haproxy[27399]: 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  7 04:39:44 node-2 haproxy[27399]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:44 node-2 haproxy[27399]: 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  7 04:39:44 node-2 haproxy[27399]: proxy neutron has no server available!
<129>Sep  7 04:39:44 node-2 haproxy[27399]: 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  7 04:39:44 node-2 haproxy[27399]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:44 node-2 haproxy[27399]: 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  7 04:39:44 node-2 haproxy[27399]: proxy mysqld has no server available!
<129>Sep  7 04:39:44 node-2 haproxy[27399]: 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  7 04:39:45 node-2 haproxy[27399]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:45 node-2 haproxy[27399]: 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  7 04:39:45 node-2 haproxy[27399]: proxy object-storage has no server available!
<129>Sep  7 04:39:45 node-2 haproxy[27399]: 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  7 04:39:45 node-2 haproxy[27399]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:45 node-2 haproxy[27399]: 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  7 04:39:45 node-2 haproxy[27399]: proxy aodh has no server available!
<27>Sep  7 04:39:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:47 node-2 multipathd: uevent trigger error
<129>Sep  7 04:39:49 node-2 haproxy[28761]: 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  7 04:39:49 node-2 haproxy[28761]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:49 node-2 haproxy[28761]: Server keystone-1/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  7 04:39:49 node-2 haproxy[28761]: proxy keystone-1 has no server available!
<129>Sep  7 04:39:49 node-2 haproxy[28761]: 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  7 04:39:49 node-2 haproxy[28761]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:49 node-2 haproxy[28761]: Server keystone-2/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  7 04:39:49 node-2 haproxy[28761]: proxy keystone-2 has no server available!
<129>Sep  7 04:39:49 node-2 haproxy[28761]: 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  7 04:39:49 node-2 haproxy[28761]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:49 node-2 haproxy[28761]: 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  7 04:39:49 node-2 haproxy[28761]: proxy neutron has no server available!
<129>Sep  7 04:39:49 node-2 haproxy[28761]: 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  7 04:39:50 node-2 haproxy[28770]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:50 node-2 haproxy[28770]: 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  7 04:39:50 node-2 haproxy[28770]: proxy mysqld has no server available!
<129>Sep  7 04:39:50 node-2 haproxy[28770]: 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  7 04:39:50 node-2 haproxy[28770]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:50 node-2 haproxy[28770]: 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  7 04:39:50 node-2 haproxy[28770]: proxy object-storage has no server available!
<129>Sep  7 04:39:50 node-2 haproxy[28770]: 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  7 04:39:50 node-2 haproxy[28770]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:50 node-2 haproxy[28770]: 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  7 04:39:50 node-2 haproxy[28770]: proxy aodh has no server available!
<129>Sep  7 04:39:50 node-2 haproxy[28770]: 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  7 04:39:50 node-2 haproxy[28770]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:50 node-2 haproxy[28770]: 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  7 04:39:50 node-2 haproxy[28770]: proxy ceilometer has no server available!
<27>Sep  7 04:39:52 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:52 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:52 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:52 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:52 node-2 multipathd: uevent trigger error
<129>Sep  7 04:39:54 node-2 haproxy[30124]: 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  7 04:39:54 node-2 haproxy[30124]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:54 node-2 haproxy[30124]: Server keystone-1/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  7 04:39:54 node-2 haproxy[30124]: proxy keystone-1 has no server available!
<129>Sep  7 04:39:54 node-2 haproxy[30124]: 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  7 04:39:55 node-2 haproxy[30134]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:55 node-2 haproxy[30134]: Server keystone-2/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  7 04:39:55 node-2 haproxy[30134]: proxy keystone-2 has no server available!
<129>Sep  7 04:39:55 node-2 haproxy[30134]: 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  7 04:39:55 node-2 haproxy[30134]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:55 node-2 haproxy[30134]: 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  7 04:39:55 node-2 haproxy[30134]: proxy neutron has no server available!
<129>Sep  7 04:39:55 node-2 haproxy[30134]: 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  7 04:39:55 node-2 haproxy[30134]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:55 node-2 haproxy[30134]: 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  7 04:39:55 node-2 haproxy[30134]: proxy mysqld has no server available!
<129>Sep  7 04:39:55 node-2 haproxy[30134]: 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  7 04:39:55 node-2 haproxy[30134]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:55 node-2 haproxy[30134]: 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  7 04:39:55 node-2 haproxy[30134]: proxy object-storage has no server available!
<129>Sep  7 04:39:55 node-2 haproxy[30134]: 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  7 04:39:56 node-2 haproxy[30134]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:56 node-2 haproxy[30134]: 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  7 04:39:56 node-2 haproxy[30134]: proxy aodh has no server available!
<129>Sep  7 04:39:56 node-2 haproxy[30134]: 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  7 04:39:56 node-2 haproxy[30134]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:39:56 node-2 haproxy[30134]: 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  7 04:39:56 node-2 haproxy[30134]: proxy ceilometer has no server available!
<27>Sep  7 04:39:57 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:57 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:57 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:57 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:57 node-2 multipathd: uevent trigger error
<27>Sep  7 04:39:57 node-2 multipathd: uevent trigger error
<129>Sep  7 04:40:00 node-2 haproxy[31465]: 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  7 04:40:00 node-2 haproxy[31465]: Server horizon/node-5 is DOWN, reason: Layer4 connection 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  7 04:40:00 node-2 haproxy[31465]: 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  7 04:40:00 node-2 haproxy[31465]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:00 node-2 haproxy[31465]: Server keystone-1/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  7 04:40:00 node-2 haproxy[31465]: proxy keystone-1 has no server available!
<129>Sep  7 04:40:00 node-2 haproxy[31465]: 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  7 04:40:00 node-2 haproxy[31465]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:00 node-2 haproxy[31465]: Server keystone-2/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  7 04:40:00 node-2 haproxy[31465]: proxy keystone-2 has no server available!
<129>Sep  7 04:40:00 node-2 haproxy[31465]: 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  7 04:40:00 node-2 haproxy[31465]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:00 node-2 haproxy[31465]: 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  7 04:40:00 node-2 haproxy[31465]: proxy neutron has no server available!
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: proxy mysqld has no server available!
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: proxy object-storage has no server available!
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: proxy aodh has no server available!
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:01 node-2 haproxy[31471]: 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  7 04:40:01 node-2 haproxy[31471]: proxy ceilometer has no server available!
<27>Sep  7 04:40:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:03 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:03 node-2 multipathd: uevent trigger error
<129>Sep  7 04:40:05 node-2 haproxy[455]: 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  7 04:40:06 node-2 haproxy[459]: Server horizon/node-5 is DOWN, reason: Layer4 connection 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  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:06 node-2 haproxy[459]: Server keystone-1/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  7 04:40:06 node-2 haproxy[459]: proxy keystone-1 has no server available!
<129>Sep  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:06 node-2 haproxy[459]: Server keystone-2/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  7 04:40:06 node-2 haproxy[459]: proxy keystone-2 has no server available!
<129>Sep  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: proxy glance-api has no server available!
<129>Sep  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: proxy glance-glare has no server available!
<129>Sep  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:06 node-2 haproxy[459]: 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  7 04:40:06 node-2 haproxy[459]: proxy neutron has no server available!
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: proxy glance-registry has no server available!
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: proxy mysqld has no server available!
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: proxy object-storage has no server available!
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: proxy aodh has no server available!
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:07 node-2 haproxy[459]: 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  7 04:40:07 node-2 haproxy[459]: proxy ceilometer has no server available!
<27>Sep  7 04:40:09 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:09 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:09 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:09 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:09 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:09 node-2 multipathd: uevent trigger error
<129>Sep  7 04:40:11 node-2 haproxy[1896]: 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  7 04:40:12 node-2 haproxy[1900]: Server horizon/node-5 is DOWN, reason: Layer4 connection 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  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:12 node-2 haproxy[1900]: Server keystone-1/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  7 04:40:12 node-2 haproxy[1900]: proxy keystone-1 has no server available!
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:12 node-2 haproxy[1900]: Server keystone-2/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  7 04:40:12 node-2 haproxy[1900]: proxy keystone-2 has no server available!
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: proxy nova-api has no server available!
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: proxy nova-metadata-api has no server available!
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: proxy glance-api has no server available!
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: proxy glance-glare has no server available!
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:12 node-2 haproxy[1900]: 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  7 04:40:12 node-2 haproxy[1900]: proxy neutron has no server available!
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: proxy glance-registry has no server available!
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: proxy mysqld has no server available!
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: proxy object-storage has no server available!
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: proxy aodh has no server available!
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: proxy ceilometer has no server available!
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:13 node-2 haproxy[1900]: 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  7 04:40:13 node-2 haproxy[1900]: proxy nova-novncproxy has no server available!
<27>Sep  7 04:40:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:15 node-2 multipathd: uevent trigger error
<129>Sep  7 04:40:17 node-2 haproxy[3362]: 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  7 04:40:17 node-2 haproxy[3362]: Server horizon/node-5 is DOWN, reason: Layer4 connection 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  7 04:40:17 node-2 haproxy[3362]: 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  7 04:40:17 node-2 haproxy[3362]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:17 node-2 haproxy[3362]: Server keystone-1/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  7 04:40:17 node-2 haproxy[3362]: proxy keystone-1 has no server available!
<129>Sep  7 04:40:17 node-2 haproxy[3362]: 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  7 04:40:17 node-2 haproxy[3362]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:17 node-2 haproxy[3362]: Server keystone-2/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  7 04:40:17 node-2 haproxy[3362]: proxy keystone-2 has no server available!
<129>Sep  7 04:40:17 node-2 haproxy[3362]: 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  7 04:40:17 node-2 haproxy[3362]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:17 node-2 haproxy[3362]: 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  7 04:40:17 node-2 haproxy[3362]: proxy nova-api has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: proxy nova-metadata-api has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: proxy cinder-api has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: proxy glance-api has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: proxy glance-glare has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: proxy neutron has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: proxy glance-registry has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: proxy mysqld has no server available!
<129>Sep  7 04:40:18 node-2 haproxy[3366]: 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  7 04:40:18 node-2 haproxy[3366]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:19 node-2 haproxy[3366]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  7 04:40:19 node-2 haproxy[3366]: proxy object-storage has no server available!
<129>Sep  7 04:40:19 node-2 haproxy[3366]: 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  7 04:40:19 node-2 haproxy[3366]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:19 node-2 haproxy[3366]: 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  7 04:40:19 node-2 haproxy[3366]: proxy aodh has no server available!
<129>Sep  7 04:40:19 node-2 haproxy[3366]: 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  7 04:40:19 node-2 haproxy[3366]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:19 node-2 haproxy[3366]: 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  7 04:40:19 node-2 haproxy[3366]: proxy ceilometer has no server available!
<129>Sep  7 04:40:19 node-2 haproxy[3366]: 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  7 04:40:19 node-2 haproxy[3366]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:19 node-2 haproxy[3366]: 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  7 04:40:19 node-2 haproxy[3366]: proxy nova-novncproxy has no server available!
<27>Sep  7 04:40:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:20 node-2 multipathd: uevent trigger error
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: Server horizon/node-5 is DOWN, reason: Layer4 connection 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  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:23 node-2 haproxy[4788]: Server keystone-1/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  7 04:40:23 node-2 haproxy[4788]: proxy keystone-1 has no server available!
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:23 node-2 haproxy[4788]: Server keystone-2/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  7 04:40:23 node-2 haproxy[4788]: proxy keystone-2 has no server available!
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: proxy nova-api has no server available!
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: proxy nova-metadata-api has no server available!
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:23 node-2 haproxy[4788]: 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  7 04:40:23 node-2 haproxy[4788]: proxy cinder-api has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy glance-api has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy glance-glare has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy neutron has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy glance-registry has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy mysqld has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy object-storage has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy aodh has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy ceilometer has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:24 node-2 haproxy[4792]: proxy heat-api has no server available!
<129>Sep  7 04:40:24 node-2 haproxy[4792]: 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  7 04:40:25 node-2 haproxy[4792]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:25 node-2 haproxy[4792]: 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  7 04:40:25 node-2 haproxy[4792]: proxy heat-api-cfn has no server available!
<129>Sep  7 04:40:25 node-2 haproxy[4792]: 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  7 04:40:25 node-2 haproxy[4792]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:25 node-2 haproxy[4792]: 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  7 04:40:25 node-2 haproxy[4792]: proxy heat-api-cloudwatch has no server available!
<129>Sep  7 04:40:25 node-2 haproxy[4792]: 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  7 04:40:25 node-2 haproxy[4792]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  7 04:40:25 node-2 haproxy[4792]: 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  7 04:40:25 node-2 haproxy[4792]: proxy nova-novncproxy has no server available!
<27>Sep  7 04:40:26 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:26 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:26 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:26 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:26 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:40:39 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep  7 04:41:04 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  7 04:41:06 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep  7 04:41:49 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 04:41:56 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 04:41:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:41:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:41:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:41:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:41:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:43:53 node-2 multipathd: uevent trigger error
<27>Sep  7 04:43:53 node-2 multipathd: uevent trigger error
<27>Sep  7 04:43:53 node-2 multipathd: uevent trigger error
<27>Sep  7 04:43:53 node-2 multipathd: uevent trigger error
<27>Sep  7 04:43:53 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:00 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:00 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:00 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:00 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:00 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:00 node-2 multipathd: uevent trigger error
<43>Sep  7 04:44:16 node-2 apache2_error [Wed Sep 07 04:44:13.438429 2016] [mpm_event:notice] [pid 11777:tid 140192522971008] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  7 04:44:16 node-2 apache2_error [Wed Sep 07 04:44:13.438510 2016] [core:notice] [pid 11777:tid 140192522971008] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep  7 04:44:16 node-2 apache2_error [Wed Sep 07 04:44:15.329660 2016] [mpm_event:notice] [pid 11777:tid 140192522971008] AH00491: caught SIGTERM, shutting down
<43>Sep  7 04:44:16 node-2 apache2_error [Wed Sep 07 04:44:16.465135 2016] [mpm_worker:notice] [pid 12103:tid 140526483888000] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  7 04:44:16 node-2 apache2_error [Wed Sep 07 04:44:16.465209 2016] [core:notice] [pid 12103:tid 140526483888000] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 04:44:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:24 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:24 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:24 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:24 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:24 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:24 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:24 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:33 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:33 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:33 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:33 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:33 node-2 multipathd: uevent trigger error
<27>Sep  7 04:44:58 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep  7 04:45:06 node-2 apache2_error [Wed Sep 07 04:45:06.652782 2016] [mpm_worker:notice] [pid 12103:tid 140526483888000] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 04:45:06 node-2 apache2_error [Wed Sep 07 04:45:06.662297 2016] [mpm_worker:warn] [pid 12103:tid 140526483888000] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 04:45:06 node-2 apache2_error [Wed Sep 07 04:45:06.663066 2016] [mpm_worker:notice] [pid 12103:tid 140526483888000] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  7 04:45:06 node-2 apache2_error [Wed Sep 07 04:45:06.663079 2016] [core:notice] [pid 12103:tid 140526483888000] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 04:45:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:45:15 node-2 multipathd: uevent trigger error
<43>Sep  7 04:46:26 node-2 apache2_error [Wed Sep 07 04:46:23.907072 2016] [mpm_worker:notice] [pid 12103:tid 140526483888000] AH00295: caught SIGTERM, shutting down
<43>Sep  7 04:46:26 node-2 apache2_error [Wed Sep 07 04:46:24.658589 2016] [mpm_worker:notice] [pid 1122:tid 139676545353600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 04:46:26 node-2 apache2_error [Wed Sep 07 04:46:24.658617 2016] [core:notice] [pid 1122:tid 139676545353600] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep  7 04:47:17 node-2 apache2_error [Wed Sep 07 04:47:09.041550 2016] [mpm_worker:notice] [pid 1122:tid 139676545353600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 04:47:17 node-2 apache2_error [Wed Sep 07 04:47:09.051087 2016] [mpm_worker:warn] [pid 1122:tid 139676545353600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 04:47:17 node-2 apache2_error [Wed Sep 07 04:47:09.057648 2016] [mpm_worker:notice] [pid 1122:tid 139676545353600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 04:47:17 node-2 apache2_error [Wed Sep 07 04:47:09.057674 2016] [core:notice] [pid 1122:tid 139676545353600] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 04:48:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 04:48:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:29 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:38 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:38 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:38 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:38 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:38 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:38 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:38 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:54 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:54 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:54 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:54 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:54 node-2 multipathd: uevent trigger error
<27>Sep  7 04:48:54 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:15 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:20 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:49:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:50:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:50:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:50:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:50:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:50:32 node-2 multipathd: uevent trigger error
<27>Sep  7 04:51:05 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 04:51:48 node-2 multipathd: uevent trigger error
<27>Sep  7 04:51:48 node-2 multipathd: uevent trigger error
<27>Sep  7 04:51:48 node-2 multipathd: uevent trigger error
<27>Sep  7 04:51:48 node-2 multipathd: uevent trigger error
<27>Sep  7 04:51:48 node-2 multipathd: uevent trigger error
<27>Sep  7 04:51:48 node-2 multipathd: uevent trigger error
<27>Sep  7 04:52:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:52:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:52:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:52:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:52:47 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:11 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:11 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:11 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:11 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:11 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:16 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:16 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:16 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:16 node-2 multipathd: uevent trigger error
<27>Sep  7 04:53:16 node-2 multipathd: uevent trigger error
<27>Sep  7 04:54:07 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 04:55:43 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:43 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:43 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:43 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:44 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:44 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:04 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:04 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:04 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:04 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:04 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:10 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:30 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:31 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:31 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:56:34 node-2 multipathd: uevent trigger error
<27>Sep  7 04:57:10 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 04:57:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:57:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:57:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:57:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:57:18 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:01 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:01 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:01 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:01 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:01 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:17 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:17 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:17 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:17 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:17 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:17 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:35 node-2 multipathd: uevent trigger error
<27>Sep  7 04:58:35 node-2 multipathd: uevent trigger error
<27>Sep  7 05:00:12 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 05:00:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:00:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:00:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:00:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:00:59 node-2 multipathd: uevent trigger error
<27>Sep  7 05:00:59 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:13 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:14 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:14 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:21 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:21 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:21 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:21 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:21 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:21 node-2 multipathd: uevent trigger error
<27>Sep  7 05:01:21 node-2 multipathd: sda: spurious uevent, path already in pathvec
<27>Sep  7 05:02:29 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:29 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:29 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:29 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:29 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:29 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:39 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:39 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:39 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:39 node-2 multipathd: uevent trigger error
<27>Sep  7 05:02:39 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 05:03:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:17 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:17 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:17 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:34 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:34 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:34 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:34 node-2 multipathd: uevent trigger error
<27>Sep  7 05:03:34 node-2 multipathd: uevent trigger error
<27>Sep  7 05:04:00 node-2 multipathd: uevent trigger error
<27>Sep  7 05:04:00 node-2 multipathd: uevent trigger error
<27>Sep  7 05:04:00 node-2 multipathd: uevent trigger error
<27>Sep  7 05:04:00 node-2 multipathd: uevent trigger error
<27>Sep  7 05:04:00 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:23 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:23 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:23 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:23 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:23 node-2 multipathd: uevent trigger error
<27>Sep  7 05:05:23 node-2 multipathd: uevent trigger error
<11>Sep  7 05:05:37 node-2 liberasurecode[59072]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:37 node-2 liberasurecode[59072]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:37 node-2 liberasurecode[59072]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:37 node-2 liberasurecode[59072]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:37 node-2 liberasurecode[59096]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:37 node-2 liberasurecode[59096]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:37 node-2 liberasurecode[59096]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:37 node-2 liberasurecode[59096]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:40 node-2 liberasurecode[59612]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:40 node-2 liberasurecode[59612]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:40 node-2 liberasurecode[59612]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:40 node-2 liberasurecode[59612]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60276]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60276]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60276]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60276]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60317]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60317]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60317]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:45 node-2 liberasurecode[60317]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60361]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60361]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60361]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60361]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60421]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60421]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60421]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60421]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60438]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60438]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60438]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60438]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60450]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60450]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60450]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60450]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60464]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60464]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60464]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:46 node-2 liberasurecode[60464]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:55 node-2 liberasurecode[61449]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:55 node-2 liberasurecode[61449]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:55 node-2 liberasurecode[61449]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:05:55 node-2 liberasurecode[61449]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  7 05:06:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:06:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:06:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:06:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:06:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:06:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:06:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep  7 05:06:58 node-2 apache2_error [Wed Sep 07 05:06:51.920730 2016] [mpm_worker:notice] [pid 1122:tid 139676545353600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 05:06:58 node-2 apache2_error [Wed Sep 07 05:06:52.304749 2016] [mpm_worker:warn] [pid 1122:tid 139676545353600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 05:06:58 node-2 apache2_error [Wed Sep 07 05:06:52.308465 2016] [mpm_worker:notice] [pid 1122:tid 139676545353600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 05:06:58 node-2 apache2_error [Wed Sep 07 05:06:52.308482 2016] [core:notice] [pid 1122:tid 139676545353600] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 05:07:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:33 node-2 multipathd: uevent trigger error
<43>Sep  7 05:07:38 node-2 apache2_error [Wed Sep 07 05:07:29.350834 2016] [mpm_worker:notice] [pid 1122:tid 139676545353600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 05:07:38 node-2 apache2_error [Wed Sep 07 05:07:30.111665 2016] [mpm_worker:warn] [pid 1122:tid 139676545353600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 05:07:38 node-2 apache2_error [Wed Sep 07 05:07:30.124158 2016] [mpm_worker:notice] [pid 1122:tid 139676545353600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 05:07:38 node-2 apache2_error [Wed Sep 07 05:07:30.124195 2016] [core:notice] [pid 1122:tid 139676545353600] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 05:07:40 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:40 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:40 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:40 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:40 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:40 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:46 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:46 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:46 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:46 node-2 multipathd: uevent trigger error
<27>Sep  7 05:07:46 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:26 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:33 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:41 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep  7 05:08:50 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:50 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:50 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:50 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:50 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:50 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:55 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:55 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:55 node-2 multipathd: uevent trigger error
<27>Sep  7 05:08:55 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:05 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:24 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:24 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:24 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:24 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:24 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:27 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 05:09:51 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:51 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:51 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:51 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:51 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:56 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:56 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:56 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:56 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:56 node-2 multipathd: uevent trigger error
<27>Sep  7 05:09:56 node-2 multipathd: uevent trigger error
<11>Sep  7 05:10:01 node-2 liberasurecode[113184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:10:01 node-2 liberasurecode[113184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:10:01 node-2 liberasurecode[113184]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 05:10:01 node-2 liberasurecode[113184]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  7 05:10:04 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:04 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:04 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:04 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:04 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:11 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:28 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:10:58 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:03 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:08 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:12 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:16 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:20 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:20 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:20 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:20 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:20 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:25 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:25 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:25 node-2 multipathd: uevent trigger error
<27>Sep  7 05:11:25 node-2 multipathd: uevent trigger error
