Sep 29 17:57:51 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8382" x-info="http://www.rsyslog.com"] start
Sep 29 17:57:51 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 29 17:57:51 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep 29 17:57:51 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep 29 17:57:51 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 29 17:57:51 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 29 17:57:51 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 29 17:57:51 node-2 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Sep 29 17:57:51 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4938e27d-3fd8-46d4-a591-9a968a3f822c nomdmonddf nomdmonisw
Sep 29 17:57:51 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep 29 17:57:51 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep 29 17:57:51 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep 29 17:57:51 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep 29 17:57:51 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 29 17:57:51 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 29 17:57:51 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 29 17:57:51 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 29 17:57:51 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 29 17:57:51 node-2 kernel: [    0.000000] No AGP bridge found
Sep 29 17:57:51 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 29 17:57:51 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep 29 17:57:51 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 29 17:57:51 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep 29 17:57:51 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 29 17:57:51 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 29 17:57:51 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 29 17:57:51 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 29 17:57:51 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 29 17:57:51 node-2 kernel: [    0.000000]   2 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000]   3 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000]   4 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000]   5 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000]   6 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000]   7 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000]   8 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000]   9 disabled
Sep 29 17:57:51 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 29 17:57:51 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 29 17:57:51 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 29 17:57:51 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 29 17:57:51 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 29 17:57:51 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 29 17:57:51 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 29 17:57:51 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 29 17:57:51 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 29 17:57:51 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 29 17:57:51 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 29 17:57:51 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 29 17:57:51 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 29 17:57:51 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 29 17:57:51 node-2 kernel: [    0.000000] Zone ranges:
Sep 29 17:57:51 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] Movable zone start for each node
Sep 29 17:57:51 node-2 kernel: [    0.000000] Early memory node ranges
Sep 29 17:57:51 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep 29 17:57:51 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 29 17:57:51 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 29 17:57:51 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 29 17:57:51 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep 29 17:57:51 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep 29 17:57:51 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 29 17:57:51 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 29 17:57:51 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 29 17:57:51 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 29 17:57:51 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 29 17:57:51 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 29 17:57:51 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 29 17:57:51 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 29 17:57:51 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 29 17:57:51 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 29 17:57:51 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 29 17:57:51 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 29 17:57:51 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 29 17:57:51 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 29 17:57:51 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 29 17:57:51 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 29 17:57:51 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 29 17:57:51 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 29 17:57:51 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep 29 17:57:51 node-2 kernel: [    0.000000] Policy zone: Normal
Sep 29 17:57:51 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4938e27d-3fd8-46d4-a591-9a968a3f822c nomdmonddf nomdmonisw
Sep 29 17:57:51 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 29 17:57:51 node-2 kernel: [    0.000000] Checking aperture...
Sep 29 17:57:51 node-2 kernel: [    0.000000] No AGP bridge found
Sep 29 17:57:51 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 29 17:57:51 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 29 17:57:51 node-2 kernel: [    0.000000] Memory: 32653452K/33280636K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Sep 29 17:57:51 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 29 17:57:51 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 29 17:57:51 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 29 17:57:51 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 29 17:57:51 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 29 17:57:51 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 29 17:57:51 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 29 17:57:51 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 29 17:57:51 node-2 kernel: [    0.000000] console [tty0] enabled
Sep 29 17:57:51 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 29 17:57:51 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 29 17:57:51 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 29 17:57:51 node-2 kernel: [    0.000000] hpet clockevent registered
Sep 29 17:57:51 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 29 17:57:51 node-2 kernel: [    0.004000] tsc: Detected 3492.193 MHz processor
Sep 29 17:57:51 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.38 BogoMIPS (lpj=13968772)
Sep 29 17:57:51 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 29 17:57:51 node-2 kernel: [    0.000043] Security Framework initialized
Sep 29 17:57:51 node-2 kernel: [    0.000060] AppArmor: AppArmor initialized
Sep 29 17:57:51 node-2 kernel: [    0.000061] Yama: becoming mindful.
Sep 29 17:57:51 node-2 kernel: [    0.001447] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.006355] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.008284] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.008311] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.008605] Initializing cgroup subsys memory
Sep 29 17:57:51 node-2 kernel: [    0.008613] Initializing cgroup subsys devices
Sep 29 17:57:51 node-2 kernel: [    0.008615] Initializing cgroup subsys freezer
Sep 29 17:57:51 node-2 kernel: [    0.008617] Initializing cgroup subsys blkio
Sep 29 17:57:51 node-2 kernel: [    0.008618] Initializing cgroup subsys perf_event
Sep 29 17:57:51 node-2 kernel: [    0.008621] Initializing cgroup subsys hugetlb
Sep 29 17:57:51 node-2 kernel: [    0.008640] CPU: Physical Processor ID: 0
Sep 29 17:57:51 node-2 kernel: [    0.008641] CPU: Processor Core ID: 0
Sep 29 17:57:51 node-2 kernel: [    0.008645] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 29 17:57:51 node-2 kernel: [    0.008645] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 29 17:57:51 node-2 kernel: [    0.009338] mce: CPU supports 22 MCE banks
Sep 29 17:57:51 node-2 kernel: [    0.009366] CPU0: Thermal monitoring enabled (TM1)
Sep 29 17:57:51 node-2 kernel: [    0.009386] process: using mwait in idle threads
Sep 29 17:57:51 node-2 kernel: [    0.009390] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 29 17:57:51 node-2 kernel: [    0.009390] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 29 17:57:51 node-2 kernel: [    0.009390] tlb_flushall_shift: 6
Sep 29 17:57:51 node-2 kernel: [    0.009478] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 29 17:57:51 node-2 kernel: [    0.010202] ACPI: Core revision 20131115
Sep 29 17:57:51 node-2 kernel: [    0.022856] ACPI: All ACPI Tables successfully acquired
Sep 29 17:57:51 node-2 kernel: [    0.023018] ftrace: allocating 28614 entries in 112 pages
Sep 29 17:57:51 node-2 kernel: [    0.031719] dmar: Host address width 46
Sep 29 17:57:51 node-2 kernel: [    0.031722] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 29 17:57:51 node-2 kernel: [    0.031727] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 29 17:57:51 node-2 kernel: [    0.031729] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 29 17:57:51 node-2 kernel: [    0.031733] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 29 17:57:51 node-2 kernel: [    0.031735] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 29 17:57:51 node-2 kernel: [    0.031736] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 29 17:57:51 node-2 kernel: [    0.031737] dmar: ATSR flags: 0x0
Sep 29 17:57:51 node-2 kernel: [    0.031738] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 29 17:57:51 node-2 kernel: [    0.031739] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 29 17:57:51 node-2 kernel: [    0.031855] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 29 17:57:51 node-2 kernel: [    0.031856] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 29 17:57:51 node-2 kernel: [    0.031857] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 29 17:57:51 node-2 kernel: [    0.031858] HPET id 0 under DRHD base 0xc7ffc000
Sep 29 17:57:51 node-2 kernel: [    0.031859] Your BIOS is broken and requested that x2apic be disabled.
Sep 29 17:57:51 node-2 kernel: [    0.031859] This will slightly decrease performance.
Sep 29 17:57:51 node-2 kernel: [    0.031859] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 29 17:57:51 node-2 kernel: [    0.032291] Enabled IRQ remapping in xapic mode
Sep 29 17:57:51 node-2 kernel: [    0.032292] x2apic not enabled, IRQ remapping is in xapic mode
Sep 29 17:57:51 node-2 kernel: [    0.032296] Switched APIC routing to physical flat.
Sep 29 17:57:51 node-2 kernel: [    0.032873] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 29 17:57:51 node-2 kernel: [    0.072526] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 29 17:57:51 node-2 kernel: [    0.072532] TSC deadline timer enabled
Sep 29 17:57:51 node-2 kernel: [    0.072539] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 29 17:57:51 node-2 kernel: [    0.072545] ... version:                3
Sep 29 17:57:51 node-2 kernel: [    0.072546] ... bit width:              48
Sep 29 17:57:51 node-2 kernel: [    0.072547] ... generic registers:      4
Sep 29 17:57:51 node-2 kernel: [    0.072548] ... value mask:             0000ffffffffffff
Sep 29 17:57:51 node-2 kernel: [    0.072549] ... max period:             0000ffffffffffff
Sep 29 17:57:51 node-2 kernel: [    0.072550] ... fixed-purpose events:   3
Sep 29 17:57:51 node-2 kernel: [    0.072550] ... event mask:             000000070000000f
Sep 29 17:57:51 node-2 kernel: [    0.073940] x86: Booting SMP configuration:
Sep 29 17:57:51 node-2 kernel: [    0.088043] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 29 17:57:51 node-2 kernel: [    0.073941] .... node  #0, CPUs:        #1  #2  #3
Sep 29 17:57:51 node-2 kernel: [    0.115951] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 29 17:57:51 node-2 kernel: [    0.269815] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 29 17:57:51 node-2 kernel: [    0.325430] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 29 17:57:51 node-2 kernel: [    0.382286] x86: Booted up 2 nodes, 16 CPUs
Sep 29 17:57:51 node-2 kernel: [    0.382289] smpboot: Total of 16 processors activated (111763.61 BogoMIPS)
Sep 29 17:57:51 node-2 kernel: [    0.406092] devtmpfs: initialized
Sep 29 17:57:51 node-2 kernel: [    0.408635] EVM: security.selinux
Sep 29 17:57:51 node-2 kernel: [    0.408637] EVM: security.SMACK64
Sep 29 17:57:51 node-2 kernel: [    0.408638] EVM: security.ima
Sep 29 17:57:51 node-2 kernel: [    0.408639] EVM: security.capability
Sep 29 17:57:51 node-2 kernel: [    0.408691] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.409333] pinctrl core: initialized pinctrl subsystem
Sep 29 17:57:51 node-2 kernel: [    0.409392] regulator-dummy: no parameters
Sep 29 17:57:51 node-2 kernel: [    0.409423] RTC time: 17:57:16, date: 09/29/16
Sep 29 17:57:51 node-2 kernel: [    0.409457] NET: Registered protocol family 16
Sep 29 17:57:51 node-2 kernel: [    0.409540] cpuidle: using governor ladder
Sep 29 17:57:51 node-2 kernel: [    0.409542] cpuidle: using governor menu
Sep 29 17:57:51 node-2 kernel: [    0.409577] ACPI: bus type PCI registered
Sep 29 17:57:51 node-2 kernel: [    0.409580] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 29 17:57:51 node-2 kernel: [    0.409648] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 29 17:57:51 node-2 kernel: [    0.409651] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 29 17:57:51 node-2 kernel: [    0.423394] PCI: Using configuration type 1 for base access
Sep 29 17:57:51 node-2 kernel: [    0.424394] bio: create slab <bio-0> at 0
Sep 29 17:57:51 node-2 kernel: [    0.424665] ACPI: Added _OSI(Module Device)
Sep 29 17:57:51 node-2 kernel: [    0.424667] ACPI: Added _OSI(Processor Device)
Sep 29 17:57:51 node-2 kernel: [    0.424668] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 29 17:57:51 node-2 kernel: [    0.424669] ACPI: Added _OSI(Processor Aggregator Device)
Sep 29 17:57:51 node-2 kernel: [    0.437421] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 29 17:57:51 node-2 kernel: [    0.447872] ACPI: Interpreter enabled
Sep 29 17:57:51 node-2 kernel: [    0.447877] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 29 17:57:51 node-2 kernel: [    0.447881] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 29 17:57:51 node-2 kernel: [    0.447884] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 29 17:57:51 node-2 kernel: [    0.447891] ACPI: (supports S0 S4 S5)
Sep 29 17:57:51 node-2 kernel: [    0.447892] ACPI: Using IOAPIC for interrupt routing
Sep 29 17:57:51 node-2 kernel: [    0.447935] HEST: Table parsing has been initialized.
Sep 29 17:57:51 node-2 kernel: [    0.447938] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 29 17:57:51 node-2 kernel: [    0.448494] ACPI: No dock devices found.
Sep 29 17:57:51 node-2 kernel: [    0.460145] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 29 17:57:51 node-2 kernel: [    0.460150] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 29 17:57:51 node-2 kernel: [    0.460153] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 29 17:57:51 node-2 kernel: [    0.460182] PCI host bridge to bus 0000:ff
Sep 29 17:57:51 node-2 kernel: [    0.460184] pci_bus 0000:ff: root bus resource [bus ff]
Sep 29 17:57:51 node-2 kernel: [    0.460192] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460231] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.460261] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460297] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460326] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.460356] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.460387] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460416] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460447] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460477] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460503] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460530] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460558] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460584] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460611] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460637] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460665] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460692] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460718] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.460746] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460771] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.460797] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460823] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460852] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.460886] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460917] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460946] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.460976] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461007] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461037] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461067] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461097] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461127] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461159] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461191] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461223] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461256] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461286] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461313] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461343] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461377] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461414] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461449] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461482] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461511] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461540] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461569] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461598] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461628] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461658] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461689] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461717] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461746] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461773] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461802] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461833] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461864] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461920] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 29 17:57:51 node-2 kernel: [    0.461923] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 29 17:57:51 node-2 kernel: [    0.461926] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 29 17:57:51 node-2 kernel: [    0.461944] PCI host bridge to bus 0000:7f
Sep 29 17:57:51 node-2 kernel: [    0.461945] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 29 17:57:51 node-2 kernel: [    0.461950] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.461979] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.462008] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462037] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462059] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.462083] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.462109] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462134] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462156] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462179] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462204] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462229] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462255] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462279] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462304] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462332] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462353] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462376] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462399] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.462422] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462444] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.462466] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462488] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462514] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 29 17:57:51 node-2 kernel: [    0.462547] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462573] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462599] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462625] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462650] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462677] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462705] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462734] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462758] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462784] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462812] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462839] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462868] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462893] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462919] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462947] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462972] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.462998] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463026] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463052] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463077] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463101] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463127] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463153] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463178] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463204] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463233] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463257] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463279] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463302] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463327] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463356] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.463381] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.464625] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 29 17:57:51 node-2 kernel: [    0.464628] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 29 17:57:51 node-2 kernel: [    0.465768] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 29 17:57:51 node-2 kernel: [    0.466280] PCI host bridge to bus 0000:00
Sep 29 17:57:51 node-2 kernel: [    0.466282] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 29 17:57:51 node-2 kernel: [    0.466284] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 29 17:57:51 node-2 kernel: [    0.466285] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 29 17:57:51 node-2 kernel: [    0.466286] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 29 17:57:51 node-2 kernel: [    0.466288] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 29 17:57:51 node-2 kernel: [    0.466289] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 29 17:57:51 node-2 kernel: [    0.466290] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 29 17:57:51 node-2 kernel: [    0.466296] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 29 17:57:51 node-2 kernel: [    0.466379] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.466410] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.466451] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 29 17:57:51 node-2 kernel: [    0.466470] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.466500] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.466540] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 29 17:57:51 node-2 kernel: [    0.466560] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.466590] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.466630] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 29 17:57:51 node-2 kernel: [    0.466646] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.466716] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.466793] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.466869] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 29 17:57:51 node-2 kernel: [    0.466874] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 29 17:57:51 node-2 kernel: [    0.466958] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 29 17:57:51 node-2 kernel: [    0.467105] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 29 17:57:51 node-2 kernel: [    0.467122] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 29 17:57:51 node-2 kernel: [    0.467200] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.467254] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 29 17:57:51 node-2 kernel: [    0.467275] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.467331] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.467374] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 29 17:57:51 node-2 kernel: [    0.467401] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.467456] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.467499] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 29 17:57:51 node-2 kernel: [    0.467523] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 29 17:57:51 node-2 kernel: [    0.467541] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 29 17:57:51 node-2 kernel: [    0.467619] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.467669] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 29 17:57:51 node-2 kernel: [    0.467695] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 29 17:57:51 node-2 kernel: [    0.467942] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 29 17:57:51 node-2 kernel: [    0.467948] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 29 17:57:51 node-2 kernel: [    0.467954] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.467960] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.467967] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 29 17:57:51 node-2 kernel: [    0.467998] pci 0000:01:00.0: supports D1 D2
Sep 29 17:57:51 node-2 kernel: [    0.478216] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 29 17:57:51 node-2 kernel: [    0.478222] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 29 17:57:51 node-2 kernel: [    0.478226] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 29 17:57:51 node-2 kernel: [    0.478493] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.478553] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 29 17:57:51 node-2 kernel: [    0.490220] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 29 17:57:51 node-2 kernel: [    0.490226] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.490230] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 29 17:57:51 node-2 kernel: [    0.490314] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.490387] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.490486] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.490569] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 29 17:57:51 node-2 kernel: [    0.490576] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.490580] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 29 17:57:51 node-2 kernel: [    0.490659] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.490782] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.490836] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 29 17:57:51 node-2 kernel: [    0.490838] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.490840] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.490889] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.491028] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.491068] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.491188] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.491224] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.491343] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.491379] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 29 17:57:51 node-2 kernel: [    0.491500] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 29 17:57:51 node-2 kernel: [    0.491541] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 29 17:57:51 node-2 kernel: [    0.491544] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.491546] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.491607] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 29 17:57:51 node-2 kernel: [    0.491669] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.491721] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.491763] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 29 17:57:51 node-2 kernel: [    0.491845] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 29 17:57:51 node-2 kernel: [    0.491971] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 29 17:57:51 node-2 kernel: [    0.491973] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.491975] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.492033] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 29 17:57:51 node-2 kernel: [    0.492090] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.492138] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.492352] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 29 17:57:51 node-2 kernel: [    0.492356] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 29 17:57:51 node-2 kernel: [    0.492419] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 29 17:57:51 node-2 kernel: [    0.492472] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.492521] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.492732] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 29 17:57:51 node-2 kernel: [    0.492735] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 29 17:57:51 node-2 kernel: [    0.492794] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 29 17:57:51 node-2 kernel: [    0.492854] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.492906] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 29 17:57:51 node-2 kernel: [    0.493177] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 29 17:57:51 node-2 kernel: [    0.493181] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 29 17:57:51 node-2 kernel: [    0.493357] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 29 17:57:51 node-2 kernel: [    0.493396] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 29 17:57:51 node-2 kernel: [    0.493474] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 29 17:57:51 node-2 kernel: [    0.493493] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 29 17:57:51 node-2 kernel: [    0.493506] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 29 17:57:51 node-2 kernel: [    0.493519] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 29 17:57:51 node-2 kernel: [    0.493569] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 29 17:57:51 node-2 kernel: [    0.502227] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 29 17:57:51 node-2 kernel: [    0.502236] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 29 17:57:51 node-2 kernel: [    0.502288] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 29 17:57:51 node-2 kernel: [    0.502809] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 29 17:57:51 node-2 kernel: [    0.502812] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 29 17:57:51 node-2 kernel: [    0.502932] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 29 17:57:51 node-2 kernel: [    0.503049] PCI host bridge to bus 0000:80
Sep 29 17:57:51 node-2 kernel: [    0.503051] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 29 17:57:51 node-2 kernel: [    0.503053] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 29 17:57:51 node-2 kernel: [    0.503054] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 29 17:57:51 node-2 kernel: [    0.503062] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.503126] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.503195] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 29 17:57:51 node-2 kernel: [    0.503258] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 29 17:57:51 node-2 kernel: [    0.503263] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 29 17:57:51 node-2 kernel: [    0.503337] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 29 17:57:51 node-2 kernel: [    0.503636] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 29 17:57:51 node-2 kernel: [    0.503668] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 29 17:57:51 node-2 kernel: [    0.503698] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 29 17:57:51 node-2 kernel: [    0.503727] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 29 17:57:51 node-2 kernel: [    0.503757] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 29 17:57:51 node-2 kernel: [    0.503787] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 29 17:57:51 node-2 kernel: [    0.503817] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 29 17:57:51 node-2 kernel: [    0.503847] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 29 17:57:51 node-2 kernel: [    0.503933] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 29 17:57:51 node-2 kernel: [    0.503938] ACPI: \_SB_.UNC1: notify handler is installed
Sep 29 17:57:51 node-2 kernel: [    0.503939] ACPI: \_SB_.UNC0: notify handler is installed
Sep 29 17:57:51 node-2 kernel: [    0.503954] ACPI: \_SB_.PCI0: notify handler is installed
Sep 29 17:57:51 node-2 kernel: [    0.504007] ACPI: \_SB_.PCI1: notify handler is installed
Sep 29 17:57:51 node-2 kernel: [    0.504087] Found 4 acpi root devices
Sep 29 17:57:51 node-2 kernel: [    0.504200] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 29 17:57:51 node-2 kernel: [    0.504202] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 29 17:57:51 node-2 kernel: [    0.504204] vgaarb: loaded
Sep 29 17:57:51 node-2 kernel: [    0.504205] vgaarb: bridge control possible 0000:0c:00.0
Sep 29 17:57:51 node-2 kernel: [    0.504331] SCSI subsystem initialized
Sep 29 17:57:51 node-2 kernel: [    0.504394] libata version 3.00 loaded.
Sep 29 17:57:51 node-2 kernel: [    0.504411] ACPI: bus type USB registered
Sep 29 17:57:51 node-2 kernel: [    0.504421] usbcore: registered new interface driver usbfs
Sep 29 17:57:51 node-2 kernel: [    0.504426] usbcore: registered new interface driver hub
Sep 29 17:57:51 node-2 kernel: [    0.504450] usbcore: registered new device driver usb
Sep 29 17:57:51 node-2 kernel: [    0.504622] PCI: Using ACPI for IRQ routing
Sep 29 17:57:51 node-2 kernel: [    0.508229] PCI: pci_cache_line_size set to 64 bytes
Sep 29 17:57:51 node-2 kernel: [    0.508438] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 29 17:57:51 node-2 kernel: [    0.508439] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep 29 17:57:51 node-2 kernel: [    0.508440] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 29 17:57:51 node-2 kernel: [    0.508507] NetLabel: Initializing
Sep 29 17:57:51 node-2 kernel: [    0.508508] NetLabel:  domain hash size = 128
Sep 29 17:57:51 node-2 kernel: [    0.508509] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 29 17:57:51 node-2 kernel: [    0.508519] NetLabel:  unlabeled traffic allowed by default
Sep 29 17:57:51 node-2 kernel: [    0.508576] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 29 17:57:51 node-2 kernel: [    0.508580] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 29 17:57:51 node-2 kernel: [    0.510635] Switched to clocksource hpet
Sep 29 17:57:51 node-2 kernel: [    0.514675] AppArmor: AppArmor Filesystem Enabled
Sep 29 17:57:51 node-2 kernel: [    0.514688] pnp: PnP ACPI init
Sep 29 17:57:51 node-2 kernel: [    0.514694] ACPI: bus type PNP registered
Sep 29 17:57:51 node-2 kernel: [    0.514805] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 29 17:57:51 node-2 kernel: [    0.514813] pnp 00:01: [dma 4]
Sep 29 17:57:51 node-2 kernel: [    0.514825] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 29 17:57:51 node-2 kernel: [    0.514852] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 29 17:57:51 node-2 kernel: [    0.514872] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 29 17:57:51 node-2 kernel: [    0.514890] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 29 17:57:51 node-2 kernel: [    0.514922] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 29 17:57:51 node-2 kernel: [    0.514975] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514978] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 29 17:57:51 node-2 kernel: [    0.514979] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514981] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514982] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514987] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514989] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 29 17:57:51 node-2 kernel: [    0.514991] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514992] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514994] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514995] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514997] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.514998] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 29 17:57:51 node-2 kernel: [    0.515000] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 29 17:57:51 node-2 kernel: [    0.515084] pnp 00:07: [dma 0 disabled]
Sep 29 17:57:51 node-2 kernel: [    0.515112] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 29 17:57:51 node-2 kernel: [    0.515187] pnp 00:08: [dma 0 disabled]
Sep 29 17:57:51 node-2 kernel: [    0.515220] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 29 17:57:51 node-2 kernel: [    0.515271] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 29 17:57:51 node-2 kernel: [    0.515620] pnp: PnP ACPI: found 10 devices
Sep 29 17:57:51 node-2 kernel: [    0.515622] ACPI: bus type PNP unregistered
Sep 29 17:57:51 node-2 kernel: [    0.521855] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 29 17:57:51 node-2 kernel: [    0.521858] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 29 17:57:51 node-2 kernel: [    0.521861] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 29 17:57:51 node-2 kernel: [    0.521865] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 29 17:57:51 node-2 kernel: [    0.521867] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.521881] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.521910] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 29 17:57:51 node-2 kernel: [    0.521925] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 29 17:57:51 node-2 kernel: [    0.521976] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 29 17:57:51 node-2 kernel: [    0.521991] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 29 17:57:51 node-2 kernel: [    0.522020] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 29 17:57:51 node-2 kernel: [    0.522034] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 29 17:57:51 node-2 kernel: [    0.522062] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 29 17:57:51 node-2 kernel: [    0.522064] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522081] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522112] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 29 17:57:51 node-2 kernel: [    0.522114] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522129] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522157] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 29 17:57:51 node-2 kernel: [    0.522159] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522162] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522166] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 29 17:57:51 node-2 kernel: [    0.522168] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522170] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522174] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 29 17:57:51 node-2 kernel: [    0.522179] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 29 17:57:51 node-2 kernel: [    0.522187] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 29 17:57:51 node-2 kernel: [    0.522190] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 29 17:57:51 node-2 kernel: [    0.522196] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 29 17:57:51 node-2 kernel: [    0.522197] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 29 17:57:51 node-2 kernel: [    0.522198] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 29 17:57:51 node-2 kernel: [    0.522199] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 29 17:57:51 node-2 kernel: [    0.522200] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 29 17:57:51 node-2 kernel: [    0.522201] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 29 17:57:51 node-2 kernel: [    0.522202] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 29 17:57:51 node-2 kernel: [    0.522203] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 29 17:57:51 node-2 kernel: [    0.522204] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522204] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522205] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522206] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522207] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522208] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522209] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522210] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522211] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 29 17:57:51 node-2 kernel: [    0.522212] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522213] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 29 17:57:51 node-2 kernel: [    0.522214] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 29 17:57:51 node-2 kernel: [    0.522215] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 29 17:57:51 node-2 kernel: [    0.522216] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 29 17:57:51 node-2 kernel: [    0.522218] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 29 17:57:51 node-2 kernel: [    0.522219] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 29 17:57:51 node-2 kernel: [    0.522256] NET: Registered protocol family 2
Sep 29 17:57:51 node-2 kernel: [    0.522522] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.522858] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.523002] TCP: Hash tables configured (established 262144 bind 65536)
Sep 29 17:57:51 node-2 kernel: [    0.523039] TCP: reno registered
Sep 29 17:57:51 node-2 kernel: [    0.523067] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.523162] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.523317] NET: Registered protocol family 1
Sep 29 17:57:51 node-2 kernel: [    0.562740] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 29 17:57:51 node-2 kernel: [    0.562756] PCI: CLS 64 bytes, default 64
Sep 29 17:57:51 node-2 kernel: [    0.562832] Trying to unpack rootfs image as initramfs...
Sep 29 17:57:51 node-2 kernel: [    0.781802] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Sep 29 17:57:51 node-2 kernel: [    0.781857] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 29 17:57:51 node-2 kernel: [    0.781860] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep 29 17:57:51 node-2 kernel: [    0.782290] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782296] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782301] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782307] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782316] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782327] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782336] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782344] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782352] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782362] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782368] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782374] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782381] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782389] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782396] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782415] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 29 17:57:51 node-2 kernel: [    0.782517] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 29 17:57:51 node-2 kernel: [    0.782520] Scanning for low memory corruption every 60 seconds
Sep 29 17:57:51 node-2 kernel: [    0.782884] Initialise system trusted keyring
Sep 29 17:57:51 node-2 kernel: [    0.782937] audit: initializing netlink socket (disabled)
Sep 29 17:57:51 node-2 kernel: [    0.782952] type=2000 audit(1475171835.732:1): initialized
Sep 29 17:57:51 node-2 kernel: [    0.800718] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 29 17:57:51 node-2 kernel: [    0.802266] zbud: loaded
Sep 29 17:57:51 node-2 kernel: [    0.802400] VFS: Disk quotas dquot_6.5.2
Sep 29 17:57:51 node-2 kernel: [    0.802441] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 29 17:57:51 node-2 kernel: [    0.802821] fuse init (API version 7.22)
Sep 29 17:57:51 node-2 kernel: [    0.802880] msgmni has been set to 32768
Sep 29 17:57:51 node-2 kernel: [    0.802928] Key type big_key registered
Sep 29 17:57:51 node-2 kernel: [    0.803418] Key type asymmetric registered
Sep 29 17:57:51 node-2 kernel: [    0.803419] Asymmetric key parser 'x509' registered
Sep 29 17:57:51 node-2 kernel: [    0.803442] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 29 17:57:51 node-2 kernel: [    0.803516] io scheduler noop registered
Sep 29 17:57:51 node-2 kernel: [    0.803517] io scheduler deadline registered (default)
Sep 29 17:57:51 node-2 kernel: [    0.803536] io scheduler cfq registered
Sep 29 17:57:51 node-2 kernel: [    0.803957] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    0.804119] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    0.804229] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    0.804349] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    0.804457] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    0.804546] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    0.804901] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 29 17:57:51 node-2 kernel: [    0.804927] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 29 17:57:51 node-2 kernel: [    0.804943] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 29 17:57:51 node-2 kernel: [    0.804953] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804955] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804958] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 29 17:57:51 node-2 kernel: [    0.804963] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804965] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804966] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804967] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804969] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804970] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804971] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804973] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804974] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804976] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804977] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804978] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804981] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 29 17:57:51 node-2 kernel: [    0.804986] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.804988] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 29 17:57:51 node-2 kernel: [    0.805003] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.805006] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 29 17:57:51 node-2 kernel: [    0.805017] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.805018] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 29 17:57:51 node-2 kernel: [    0.805021] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 29 17:57:51 node-2 kernel: [    0.805054] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 29 17:57:51 node-2 kernel: [    0.805061] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 29 17:57:51 node-2 kernel: [    0.805065] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 29 17:57:51 node-2 kernel: [    0.805074] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 29 17:57:51 node-2 kernel: [    0.805115] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 29 17:57:51 node-2 kernel: [    0.805117] vesafb: scrolling: redraw
Sep 29 17:57:51 node-2 kernel: [    0.805118] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 29 17:57:51 node-2 kernel: [    0.825821] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 29 17:57:51 node-2 kernel: [    0.834530] Console: switching to colour frame buffer device 80x30
Sep 29 17:57:51 node-2 kernel: [    0.843299] fb0: VESA VGA frame buffer device
Sep 29 17:57:51 node-2 kernel: [    0.843496] intel_idle: MWAIT substates: 0x2120
Sep 29 17:57:51 node-2 kernel: [    0.843497] intel_idle: v0.4 model 0x3F
Sep 29 17:57:51 node-2 kernel: [    0.843498] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 29 17:57:51 node-2 kernel: [    0.843726] ipmi message handler version 39.2
Sep 29 17:57:51 node-2 kernel: [    0.844003] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 29 17:57:51 node-2 kernel: [    0.844441] ACPI: AC Adapter [P111] (on-line)
Sep 29 17:57:51 node-2 kernel: [    0.849695] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 29 17:57:51 node-2 kernel: [    0.860817] ACPI: Power Button [PWRB]
Sep 29 17:57:51 node-2 kernel: [    0.866618] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 29 17:57:51 node-2 kernel: [    0.878267] ACPI: Power Button [PWRF]
Sep 29 17:57:51 node-2 kernel: [    0.900222] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 29 17:57:51 node-2 kernel: [    0.911898] pstore: Registered erst as persistent store backend
Sep 29 17:57:51 node-2 kernel: [    0.918095] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 29 17:57:51 node-2 kernel: [    0.930047] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 29 17:57:51 node-2 kernel: [    0.956791] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 29 17:57:51 node-2 kernel: [    0.990081] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 29 17:57:51 node-2 kernel: [    1.004174] Linux agpgart interface v0.103
Sep 29 17:57:51 node-2 kernel: [    1.011814] brd: module loaded
Sep 29 17:57:51 node-2 kernel: [    1.018810] loop: module loaded
Sep 29 17:57:51 node-2 kernel: [    1.025490] libphy: Fixed MDIO Bus: probed
Sep 29 17:57:51 node-2 kernel: [    1.031938] tun: Universal TUN/TAP device driver, 1.6
Sep 29 17:57:51 node-2 kernel: [    1.038384] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 29 17:57:51 node-2 kernel: [    1.044882] PPP generic driver version 2.4.2
Sep 29 17:57:51 node-2 kernel: [    1.051251] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 29 17:57:51 node-2 kernel: [    1.057660] ehci-pci: EHCI PCI platform driver
Sep 29 17:57:51 node-2 kernel: [    1.064159] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 29 17:57:51 node-2 kernel: [    1.070555] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 29 17:57:51 node-2 kernel: [    1.083021] ehci-pci 0000:00:1a.0: debug port 2
Sep 29 17:57:51 node-2 kernel: [    1.093187] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 29 17:57:51 node-2 kernel: [    1.093206] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 29 17:57:51 node-2 kernel: [    1.110132] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 29 17:57:51 node-2 kernel: [    1.116187] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 29 17:57:51 node-2 kernel: [    1.122328] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 29 17:57:51 node-2 kernel: [    1.134193] usb usb1: Product: EHCI Host Controller
Sep 29 17:57:51 node-2 kernel: [    1.140198] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 29 17:57:51 node-2 kernel: [    1.146214] usb usb1: SerialNumber: 0000:00:1a.0
Sep 29 17:57:51 node-2 kernel: [    1.152138] hub 1-0:1.0: USB hub found
Sep 29 17:57:51 node-2 kernel: [    1.157940] hub 1-0:1.0: 2 ports detected
Sep 29 17:57:51 node-2 kernel: [    1.163836] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 29 17:57:51 node-2 kernel: [    1.169419] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 29 17:57:51 node-2 kernel: [    1.180267] ehci-pci 0000:00:1d.0: debug port 2
Sep 29 17:57:51 node-2 kernel: [    1.189570] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 29 17:57:51 node-2 kernel: [    1.189573] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 29 17:57:51 node-2 kernel: [    1.206051] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 29 17:57:51 node-2 kernel: [    1.211239] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 29 17:57:51 node-2 kernel: [    1.216535] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 29 17:57:51 node-2 kernel: [    1.227095] usb usb2: Product: EHCI Host Controller
Sep 29 17:57:51 node-2 kernel: [    1.232564] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 29 17:57:51 node-2 kernel: [    1.238110] usb usb2: SerialNumber: 0000:00:1d.0
Sep 29 17:57:51 node-2 kernel: [    1.243621] hub 2-0:1.0: USB hub found
Sep 29 17:57:51 node-2 kernel: [    1.248971] hub 2-0:1.0: 2 ports detected
Sep 29 17:57:51 node-2 kernel: [    1.254268] ehci-platform: EHCI generic platform driver
Sep 29 17:57:51 node-2 kernel: [    1.259538] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 29 17:57:51 node-2 kernel: [    1.264846] ohci-pci: OHCI PCI platform driver
Sep 29 17:57:51 node-2 kernel: [    1.270150] ohci-platform: OHCI generic platform driver
Sep 29 17:57:51 node-2 kernel: [    1.275336] uhci_hcd: USB Universal Host Controller Interface driver
Sep 29 17:57:51 node-2 kernel: [    1.280674] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 29 17:57:51 node-2 kernel: [    1.473831] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 29 17:57:51 node-2 kernel: [    1.777628] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 29 17:57:51 node-2 kernel: [    1.793954] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 29 17:57:51 node-2 kernel: [    1.799568] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 29 17:57:51 node-2 kernel: [    1.805346] hub 1-1:1.0: USB hub found
Sep 29 17:57:51 node-2 kernel: [    1.810941] hub 1-1:1.0: 6 ports detected
Sep 29 17:57:51 node-2 kernel: [    1.925468] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 29 17:57:51 node-2 kernel: [    2.319578] i8042: No controller found
Sep 29 17:57:51 node-2 kernel: [    2.325143] mousedev: PS/2 mouse device common for all mice
Sep 29 17:57:51 node-2 kernel: [    2.330871] rtc_cmos 00:02: RTC can wake from S4
Sep 29 17:57:51 node-2 kernel: [    2.333938] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 29 17:57:51 node-2 kernel: [    2.333939] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 29 17:57:51 node-2 kernel: [    2.334334] hub 2-1:1.0: USB hub found
Sep 29 17:57:51 node-2 kernel: [    2.334557] hub 2-1:1.0: 8 ports detected
Sep 29 17:57:51 node-2 kernel: [    2.359235] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 29 17:57:51 node-2 kernel: [    2.365004] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 29 17:57:51 node-2 kernel: [    2.376447] device-mapper: uevent: version 1.0.3
Sep 29 17:57:51 node-2 kernel: [    2.382156] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 29 17:57:51 node-2 kernel: [    2.393566] ledtrig-cpu: registered to indicate activity on CPUs
Sep 29 17:57:51 node-2 kernel: [    2.399550] TCP: cubic registered
Sep 29 17:57:51 node-2 kernel: [    2.405415] NET: Registered protocol family 10
Sep 29 17:57:51 node-2 kernel: [    2.411481] NET: Registered protocol family 17
Sep 29 17:57:51 node-2 kernel: [    2.417255] Key type dns_resolver registered
Sep 29 17:57:51 node-2 kernel: [    2.423325] Loading compiled-in X.509 certificates
Sep 29 17:57:51 node-2 kernel: [    2.429551] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Sep 29 17:57:51 node-2 kernel: [    2.441186] registered taskstats version 1
Sep 29 17:57:51 node-2 kernel: [    2.449250] Key type trusted registered
Sep 29 17:57:51 node-2 kernel: [    2.456895] Key type encrypted registered
Sep 29 17:57:51 node-2 kernel: [    2.462395] AppArmor: AppArmor sha1 policy hashing enabled
Sep 29 17:57:51 node-2 kernel: [    2.467905] IMA: No TPM chip found, activating TPM-bypass!
Sep 29 17:57:51 node-2 kernel: [    2.473984] regulator-dummy: disabling
Sep 29 17:57:51 node-2 kernel: [    2.479487]   Magic number: 0:445:998
Sep 29 17:57:51 node-2 kernel: [    2.484971] pnp 00:00: hash matches
Sep 29 17:57:51 node-2 kernel: [    2.490563] rtc_cmos 00:02: setting system clock to 2016-09-29 17:57:18 UTC (1475171838)
Sep 29 17:57:51 node-2 kernel: [    2.502881] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 29 17:57:51 node-2 kernel: [    2.508473] EDD information not available.
Sep 29 17:57:51 node-2 kernel: [    2.513983] PM: Hibernation image not present or could not be loaded.
Sep 29 17:57:51 node-2 kernel: [    2.514854] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 29 17:57:51 node-2 kernel: [    2.526032] Write protecting the kernel read-only data: 12288k
Sep 29 17:57:51 node-2 kernel: [    2.532353] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 29 17:57:51 node-2 kernel: [    2.545135] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 29 17:57:51 node-2 kernel: [    2.576721] device-mapper: multipath: version 1.6.0 loaded
Sep 29 17:57:51 node-2 kernel: [    2.584430] systemd-udevd[215]: starting version 204
Sep 29 17:57:51 node-2 kernel: [    2.607000] md: linear personality registered for level -1
Sep 29 17:57:51 node-2 kernel: [    2.612929] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 29 17:57:51 node-2 kernel: [    2.627378] md: multipath personality registered for level -4
Sep 29 17:57:51 node-2 kernel: [    2.635305] md: raid0 personality registered for level 0
Sep 29 17:57:51 node-2 kernel: [    2.643829] md: raid1 personality registered for level 1
Sep 29 17:57:51 node-2 kernel: [    2.651903] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 29 17:57:51 node-2 kernel: [    2.658111] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 29 17:57:51 node-2 kernel: [    2.664356] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 29 17:57:51 node-2 kernel: [    2.665571] megasas: FW now in Ready state
Sep 29 17:57:51 node-2 kernel: [    2.665989] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.666126] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.666251] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.666340] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.666488] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.666674] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.666808] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.666963] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.667085] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.667299] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.667425] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.667606] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.667721] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.667885] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.668006] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.668132] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.669282] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 29 17:57:51 node-2 kernel: [    2.697505] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep 29 17:57:51 node-2 kernel: [    2.710666] 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 29 17:57:51 node-2 kernel: [    2.724497] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 29 17:57:51 node-2 kernel: [    2.729188] raid6: sse2x1    1887 MB/s
Sep 29 17:57:51 node-2 kernel: [    2.738309] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.738313] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.738317] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.738321] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.738358] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 29 17:57:51 node-2 kernel: [    2.750223] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 29 17:57:51 node-2 kernel: [    2.750229] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 29 17:57:51 node-2 kernel: [    2.750230] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 29 17:57:51 node-2 kernel: [    2.750237] usb 2-1.4: Manufacturer: Avocent
Sep 29 17:57:51 node-2 kernel: [    2.750237] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 29 17:57:51 node-2 kernel: [    2.796709] raid6: sse2x2    1227 MB/s
Sep 29 17:57:51 node-2 kernel: [    2.868654] raid6: sse2x4   10131 MB/s
Sep 29 17:57:51 node-2 kernel: [    2.940589] raid6: avx2x1   14956 MB/s
Sep 29 17:57:51 node-2 kernel: [    3.012524] raid6: avx2x2   18865 MB/s
Sep 29 17:57:51 node-2 kernel: [    3.084466] raid6: avx2x4   21317 MB/s
Sep 29 17:57:51 node-2 kernel: [    3.090247] raid6: using algorithm avx2x4 (21317 MB/s)
Sep 29 17:57:51 node-2 kernel: [    3.095984] raid6: using avx2x2 recovery algorithm
Sep 29 17:57:51 node-2 kernel: [    3.101598] megasas:IOC Init cmd success
Sep 29 17:57:51 node-2 kernel: [    3.101599] Switched to clocksource tsc
Sep 29 17:57:51 node-2 kernel: [    3.112107] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep 29 17:57:51 node-2 kernel: [    3.112109] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 29 17:57:51 node-2 kernel: [    3.112111] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 29 17:57:51 node-2 kernel: [    3.112202] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.112240] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.112277] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.112316] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.112351] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.112388] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.112502] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.122052] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep 29 17:57:51 node-2 kernel: [    3.122053] 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 29 17:57:51 node-2 kernel: [    3.122054] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 29 17:57:51 node-2 kernel: [    3.122121] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.122155] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.122195] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.122230] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.122314] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.128527] megasas: INIT adapter done
Sep 29 17:57:51 node-2 kernel: [    3.130236] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep 29 17:57:51 node-2 kernel: [    3.130237] 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 29 17:57:51 node-2 kernel: [    3.130238] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 29 17:57:51 node-2 kernel: [    3.130288] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.130323] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.130365] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.130405] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.130495] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 29 17:57:51 node-2 kernel: [    3.181996] xor: automatically using best checksumming function:
Sep 29 17:57:51 node-2 kernel: [    3.182022] hidraw: raw HID events driver (C) Jiri Kosina
Sep 29 17:57:51 node-2 kernel: [    3.204367] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 29 17:57:51 node-2 kernel: [    3.204723] scsi0 : LSI SAS based MegaRAID driver
Sep 29 17:57:51 node-2 kernel: [    3.211748] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 29 17:57:51 node-2 kernel: [    3.220337]    avx       : 36754.000 MB/sec
Sep 29 17:57:51 node-2 kernel: [    3.223989] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 29 17:57:51 node-2 kernel: [    3.228979] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 29 17:57:51 node-2 kernel: [    3.229211] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 29 17:57:51 node-2 kernel: [    3.229526] sd 0:2:0:0: [sda] Write Protect is off
Sep 29 17:57:51 node-2 kernel: [    3.229527] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 29 17:57:51 node-2 kernel: [    3.229598] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 29 17:57:51 node-2 kernel: [    3.252559]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 29 17:57:51 node-2 kernel: [    3.254281] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 29 17:57:51 node-2 kernel: [    3.260543] usbcore: registered new interface driver usbhid
Sep 29 17:57:51 node-2 kernel: [    3.260543] usbhid: USB HID core driver
Sep 29 17:57:51 node-2 kernel: [    3.303556] async_tx: api initialized (async)
Sep 29 17:57:51 node-2 kernel: [    3.367222] 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 29 17:57:51 node-2 kernel: [    3.380046] 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 29 17:57:51 node-2 kernel: [    3.393098] 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 29 17:57:51 node-2 kernel: [    3.406118] 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 29 17:57:51 node-2 kernel: [    3.419583] 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 29 17:57:51 node-2 kernel: [    3.420302] md: raid6 personality registered for level 6
Sep 29 17:57:51 node-2 kernel: [    3.420303] md: raid5 personality registered for level 5
Sep 29 17:57:51 node-2 kernel: [    3.420303] md: raid4 personality registered for level 4
Sep 29 17:57:51 node-2 kernel: [    3.453176] 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 29 17:57:51 node-2 kernel: [    3.466517] random: lvm urandom read with 32 bits of entropy available
Sep 29 17:57:51 node-2 kernel: [    3.474458] md: raid10 personality registered for level 10
Sep 29 17:57:51 node-2 kernel: [    3.530120] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Sep 29 17:57:51 node-2 kernel: [    3.649679] bio: create slab <bio-1> at 1
Sep 29 17:57:51 node-2 kernel: [    4.433260] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 29 17:57:51 node-2 kernel: [    5.019033] random: nonblocking pool is initialized
Sep 29 17:57:51 node-2 kernel: [    5.140625] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 29 17:57:51 node-2 kernel: [    5.186625] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 29 17:57:51 node-2 kernel: [    5.341440] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 29 17:57:51 node-2 kernel: [    5.371368] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 29 17:57:51 node-2 kernel: [    5.446491] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 29 17:57:51 node-2 kernel: [    5.604204] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 29 17:57:51 node-2 kernel: [    5.638242] XFS (dm-0): Mounting Filesystem
Sep 29 17:57:51 node-2 kernel: [    5.927619] XFS (dm-0): Ending clean mount
Sep 29 17:57:51 node-2 kernel: [    5.985672] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 29 17:57:51 node-2 kernel: [    6.012994] XFS (dm-1): Mounting Filesystem
Sep 29 17:57:51 node-2 kernel: [    6.129445] XFS (dm-1): Ending clean mount
Sep 29 17:57:51 node-2 kernel: [    7.942081] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 29 17:57:51 node-2 kernel: [    7.955706] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 29 17:57:51 node-2 kernel: [    8.079349] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 29 17:57:51 node-2 kernel: [    8.079354] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 29 17:57:51 node-2 kernel: [    8.079357] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 29 17:57:51 node-2 kernel: [    8.079361] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 29 17:57:51 node-2 kernel: [    8.119887] systemd-udevd[777]: starting version 204
Sep 29 17:57:51 node-2 kernel: [    8.306378] power_meter ACPI000D:00: Found ACPI power meter.
Sep 29 17:57:51 node-2 kernel: [    8.306398] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 29 17:57:51 node-2 kernel: [    8.315278] wmi: Mapper loaded
Sep 29 17:57:51 node-2 kernel: [    8.327550] IPMI System Interface driver.
Sep 29 17:57:51 node-2 kernel: [    8.327613] ipmi_si: probing via ACPI
Sep 29 17:57:51 node-2 kernel: [    8.327630] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 29 17:57:51 node-2 kernel: [    8.327632] ipmi_si: Adding ACPI-specified kcs state machine
Sep 29 17:57:51 node-2 kernel: [    8.327647] ipmi_si: probing via SMBIOS
Sep 29 17:57:51 node-2 kernel: [    8.327648] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 29 17:57:51 node-2 kernel: [    8.327649] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 29 17:57:51 node-2 kernel: [    8.327651] ipmi_si: probing via SPMI
Sep 29 17:57:51 node-2 kernel: [    8.327652] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 29 17:57:51 node-2 kernel: [    8.327653] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 29 17:57:51 node-2 kernel: [    8.327654] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 29 17:57:51 node-2 kernel: [    8.348548] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 29 17:57:51 node-2 kernel: [    8.348555] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 29 17:57:51 node-2 kernel: [    8.348559] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 29 17:57:51 node-2 kernel: [    8.348562] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 29 17:57:51 node-2 kernel: [    8.348580] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 29 17:57:51 node-2 kernel: [    8.355398] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 29 17:57:51 node-2 kernel: [    8.412425] systemd-udevd[805]: renamed network interface eth2 to enp8s0
Sep 29 17:57:51 node-2 kernel: [    8.436268] systemd-udevd[806]: renamed network interface eth1 to enp7s0
Sep 29 17:57:51 node-2 kernel: [    8.460301] systemd-udevd[795]: renamed network interface eth0 to enp6s0
Sep 29 17:57:51 node-2 kernel: [    8.465762] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 29 17:57:51 node-2 kernel: [    8.465768] ipmi_si 00:09: IPMI kcs interface initialized
Sep 29 17:57:51 node-2 kernel: [    8.494318] systemd-udevd[808]: renamed network interface eth3 to enp9s0
Sep 29 17:57:51 node-2 kernel: [    8.721281] type=1400 audit(1475171844.733:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.721460] type=1400 audit(1475171844.733:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.721501] type=1400 audit(1475171844.733:4): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1051 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.721589] type=1400 audit(1475171844.733:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.721649] type=1400 audit(1475171844.733:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1051 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.721772] type=1400 audit(1475171844.733:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1051 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.730458] type=1400 audit(1475171844.741:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.730589] type=1400 audit(1475171844.741:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1055 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.730705] type=1400 audit(1475171844.741:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1055 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    8.731175] type=1400 audit(1475171844.741:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Sep 29 17:57:51 node-2 kernel: [    9.214492] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 29 17:57:51 node-2 kernel: [    9.215419] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 29 17:57:51 node-2 kernel: [    9.399138] enic 0000:06:00.0 enp6s0: Link UP
Sep 29 17:57:51 node-2 kernel: [    9.400281] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 29 17:57:51 node-2 kernel: [    9.400290] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 29 17:57:51 node-2 kernel: [   18.473915] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 29 17:57:51 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 29 17:57:52 node-2 failsafe: Failsafe of 120 seconds reached.
Sep 29 17:57:52 node-2 kernel: [   37.409855] init: failsafe main process (8409) killed by TERM signal
Sep 29 17:57:53 node-2 dbus[8437]: [system] AppArmor D-Bus mediation is enabled
Sep 29 17:57:53 node-2 kernel: [   37.780837] audit_printk_skb: 30 callbacks suppressed
Sep 29 17:57:53 node-2 kernel: [   37.780839] type=1400 audit(1475171873.337:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8535 comm="apparmor_parser"
Sep 29 17:57:53 node-2 kernel: [   37.781425] type=1400 audit(1475171873.337:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8534 comm="apparmor_parser"
Sep 29 17:57:53 node-2 kernel: [   37.781430] type=1400 audit(1475171873.337:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Sep 29 17:57:53 node-2 kernel: [   37.781433] type=1400 audit(1475171873.337:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Sep 29 17:57:53 node-2 kernel: [   37.781649] type=1400 audit(1475171873.337:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Sep 29 17:57:53 node-2 kernel: [   37.781651] type=1400 audit(1475171873.337:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Sep 29 17:57:53 node-2 kernel: [   37.781762] type=1400 audit(1475171873.337:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Sep 29 17:57:53 node-2 kernel: [   37.842928] type=1400 audit(1475171873.401:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8537 comm="apparmor_parser"
Sep 29 17:57:53 node-2 anacron[8604]: Anacron 2.3 started on 2016-09-29
Sep 29 17:57:53 node-2 cron[8568]: (CRON) INFO (pidfile fd = 3)
Sep 29 17:57:53 node-2 anacron[8604]: Will run job `cron.daily' in 5 min.
Sep 29 17:57:53 node-2 anacron[8604]: Will run job `cron.weekly' in 10 min.
Sep 29 17:57:53 node-2 anacron[8604]: Will run job `cron.monthly' in 15 min.
Sep 29 17:57:53 node-2 anacron[8604]: Jobs will be executed sequentially
Sep 29 17:57:53 node-2 cron[8616]: (CRON) STARTUP (fork ok)
Sep 29 17:57:53 node-2 multipathd: path checkers start up
Sep 29 17:57:53 node-2 cron[8616]: (CRON) INFO (Running @reboot jobs)
Sep 29 17:57:54 node-2 postfix/master[8746]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 29 17:57:57 node-2 puppet-agent[8931]: Reopening log files
Sep 29 17:57:59 node-2 puppet-agent[8931]: Could not request certificate: Connection refused - connect(2)
Sep 29 17:58:01 node-2 CRON[9091]: (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 29 17:58:03 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 29 17:58:03 node-2 nailgun-agent: D, [2016-09-29T17:58:01.820304 #9094] DEBUG -- : Sleep for 2 seconds before sending request
Sep 29 17:58:03 node-2 nailgun-agent: I, [2016-09-29T17:58:03.835387 #9094]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 29 17:58:04 node-2 nailgun-agent: D, [2016-09-29T17:58:04.198019 #9094] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep 29 17:58:13 node-2 puppet-user[9459]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 29 17:58:13 node-2 puppet-user[9459]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 29 17:58:14 node-2 puppet-user[9459]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 29 17:58:14 node-2 puppet-user[9459]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 29 17:58:14 node-2 puppet-user[9459]: Finished catalog run in 0.89 seconds
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.200308 #9094] DEBUG -- : Trying to find block devices
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.200382 #9094] DEBUG -- : Found block device: sda
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.200421 #9094] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.200467 #9094] DEBUG -- : Trying to get list of physical devices
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.200607 #9094] DEBUG -- : Getting udev properties for device: sda
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.202323 #9094] 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 29 17:58:16 node-2 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5645", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.202349 #9094] DEBUG -- : Trying to find out if device sda is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.202392 #9094] DEBUG -- : Device sda removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.202407 #9094] DEBUG -- : Device sda seems to be appropriate
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.202800 #9094] DEBUG -- : Getting udev properties for device: dm-0
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.204356 #9094] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-Qz5JNXiyPXVxdhR0d7Oke6kQ9kVfO090b5Dw22lEueVy7kjEOHbZuvpozUQ6l1X3 /dev/disk/by-uuid/e6217b5c-58a9-49f8-a2c6-5b0acc73bd26 /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-Qz5JNXiyPXVxdhR0d7Oke6kQ9kVfO090b5Dw22lEueVy7kjEOHbZuvpozUQ6l1X3", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e6217b5c-58a9-49f8-a2c6-5b0acc73bd26", "ID_FS_UUID_ENC"=>"e6217b5c-58a9-49f8-a2c6-5b0acc73bd26", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1610", "nomdmonddf"=>"1", "nomdm
Sep 29 17:58:16 node-2 nailgun-agent: onisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.204393 #9094] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.204425 #9094] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.204441 #9094] DEBUG -- : Device dm-0 seems to be appropriate
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.204472 #9094] DEBUG -- : Getting udev properties for device: dm-1
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.205995 #9094] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-sNCDDs2lrCq3ZH1OOdUdWK3IEcaTYoO6HThyb6fbcTQot6JC9UfxQxwYdAWOuIa8 /dev/disk/by-uuid/d7e80c82-556d-491f-9696-a1fa76e938a1 /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-sNCDDs2lrCq3ZH1OOdUdWK3IEcaTYoO6HThyb6fbcTQot6JC9UfxQxwYdAWOuIa8", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d7e80c82-556d-491f-9696-a1fa76e938a1", "ID_FS_UUID_ENC"=>"d7e80c82-556d-491f-9696-a1fa76e938a1", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29
Sep 29 17:58:16 node-2 nailgun-agent: 916", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.206065 #9094] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.206095 #9094] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.206108 #9094] DEBUG -- : Device dm-1 seems to be appropriate
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.206122 #9094] DEBUG -- : Getting udev properties for device: dm-2
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.207699 #9094] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-dGRRslvYzfEkCui08W5C9Q46gXA5KfQJCZ1CtstYT9NjqJSAybEa6KeL3V8X5gRo /dev/disk/by-uuid/937437ac-6c4d-4b14-b715-7fbf862cbda6 /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-dGRRslvYzfEkCui08W5C9Q46gXA5KfQJCZ1CtstYT9NjqJSAybEa6KeL3V8X5gRo", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"937437ac-6c4d-4b14-b715-7fbf862cbda6", "ID_FS_UUID_ENC"=>"937437ac-6c4d-4b14-b715-7fbf862cbda6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56743", "nomdmond
Sep 29 17:58:16 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.207726 #9094] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.207769 #9094] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.207795 #9094] DEBUG -- : Device dm-2 seems to be appropriate
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.207809 #9094] DEBUG -- : Getting udev properties for device: dm-3
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.209469 #9094] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-bywEtGItTqQ44M8yq8BDMQq0L2dPd5Dcn4gZSNvcNcuLmBBkeZiowESlpRL304tx /dev/disk/by-uuid/563fe585-e0dc-4aeb-b1ee-4e29b6b9f59d /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-bywEtGItTqQ44M8yq8BDMQq0L2dPd5Dcn4gZSNvcNcuLmBBkeZiowESlpRL304tx", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"563fe585-e0dc-4aeb-b1ee-4e29b6b9f59d", "ID_FS_UUID_ENC"=>"563fe585-e0dc-4aeb-b1ee-4e29b6b9f59d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"68079", "nomdmonddf"=>"1", 
Sep 29 17:58:16 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.209495 #9094] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.209524 #9094] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.209538 #9094] DEBUG -- : Device dm-3 seems to be appropriate
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.209569 #9094] DEBUG -- : Getting udev properties for device: dm-4
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.211138 #9094] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-VmvPHJdN5cGujqF2plQEtnKp4ef6qCfyNqRgljweoSD0KfoV508OeBeUwdiND63C /dev/disk/by-uuid/4938e27d-3fd8-46d4-a591-9a968a3f822c /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-VmvPHJdN5cGujqF2plQEtnKp4ef6qCfyNqRgljweoSD0KfoV508OeBeUwdiND63C", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4938e27d-3fd8-46d4-a591-9a968a3f822c", "ID_FS_UUID_ENC"=>"4938e27d-3fd8-46d4-a591-9a968a3f822c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69510", "nomdmonddf"=>"1", "nomd
Sep 29 17:58:16 node-2 nailgun-agent: monisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.211165 #9094] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.211225 #9094] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.211239 #9094] DEBUG -- : Device dm-4 seems to be appropriate
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.211254 #9094] DEBUG -- : Getting udev properties for device: dm-5
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.212799 #9094] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-VmvPHJdN5cGujqF2plQEtnKp4ef6qCfy2UcWlsIxd0l3vGLU5JeKa5MyomxvjPPy /dev/disk/by-uuid/94f497fa-c3b0-4a0f-bf38-ab17576ead7b /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-VmvPHJdN5cGujqF2plQEtnKp4ef6qCfy2UcWlsIxd0l3vGLU5JeKa5MyomxvjPPy", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"94f497fa-c3b0-4a0f-bf38-ab17576ead7b", "ID_FS_UUID_ENC"=>"94f497fa-c3b0-4a0f-bf38-ab17576ead7b", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69910", "nomdmonddf"=>"1", "nomdmonisw"
Sep 29 17:58:16 node-2 nailgun-agent: =>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.212827 #9094] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.212859 #9094] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.212894 #9094] DEBUG -- : Device dm-5 seems to be appropriate
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.212908 #9094] DEBUG -- : Getting udev properties for device: ram0
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.214272 #9094] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53563", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.214298 #9094] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.214341 #9094] DEBUG -- : Device ram0 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.214361 #9094] DEBUG -- : Getting udev properties for device: ram1
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.215767 #9094] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53582", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.215806 #9094] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.215841 #9094] DEBUG -- : Device ram1 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.215861 #9094] DEBUG -- : Getting udev properties for device: ram2
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.217232 #9094] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53694", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.217270 #9094] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.217314 #9094] DEBUG -- : Device ram2 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.217344 #9094] DEBUG -- : Getting udev properties for device: ram3
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.218728 #9094] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53709", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.218767 #9094] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.218801 #9094] DEBUG -- : Device ram3 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.218820 #9094] DEBUG -- : Getting udev properties for device: ram4
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.220239 #9094] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53727", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.220264 #9094] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.220304 #9094] DEBUG -- : Device ram4 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.220332 #9094] DEBUG -- : Getting udev properties for device: ram5
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.221778 #9094] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53903", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.221803 #9094] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.221847 #9094] DEBUG -- : Device ram5 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.221875 #9094] DEBUG -- : Getting udev properties for device: ram6
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.223274 #9094] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53916", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.223307 #9094] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.223344 #9094] DEBUG -- : Device ram6 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.223370 #9094] DEBUG -- : Getting udev properties for device: ram7
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.225020 #9094] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53929", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.225045 #9094] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.225089 #9094] DEBUG -- : Device ram7 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.225109 #9094] DEBUG -- : Getting udev properties for device: ram8
Sep 29 17:58:16 node-2 multipathd: uevent trigger error
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.226631 #9094] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53939", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.226656 #9094] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.226691 #9094] DEBUG -- : Device ram8 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.226719 #9094] DEBUG -- : Getting udev properties for device: ram9
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.228178 #9094] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53949", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.228227 #9094] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.228265 #9094] DEBUG -- : Device ram9 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.228284 #9094] DEBUG -- : Getting udev properties for device: loop0
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.229727 #9094] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53456", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.229752 #9094] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.229796 #9094] DEBUG -- : Device loop0 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.229814 #9094] DEBUG -- : Getting udev properties for device: loop1
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.231209 #9094] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53470", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.231234 #9094] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.231279 #9094] DEBUG -- : Device loop1 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.231298 #9094] DEBUG -- : Getting udev properties for device: loop2
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.232681 #9094] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53484", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.232719 #9094] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.232753 #9094] DEBUG -- : Device loop2 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.232770 #9094] DEBUG -- : Getting udev properties for device: loop3
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.238464 #9094] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53496", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.238492 #9094] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.238530 #9094] DEBUG -- : Device loop3 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.238547 #9094] DEBUG -- : Getting udev properties for device: loop4
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.240105 #9094] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53511", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.240130 #9094] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.240168 #9094] DEBUG -- : Device loop4 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.240186 #9094] DEBUG -- : Getting udev properties for device: loop5
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.241628 #9094] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53520", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.241653 #9094] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.241691 #9094] DEBUG -- : Device loop5 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.241710 #9094] DEBUG -- : Getting udev properties for device: loop6
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.243111 #9094] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53533", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.243136 #9094] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.243175 #9094] DEBUG -- : Device loop6 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.243194 #9094] DEBUG -- : Getting udev properties for device: loop7
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.244575 #9094] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53548", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.244600 #9094] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.244670 #9094] DEBUG -- : Device loop7 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.244689 #9094] DEBUG -- : Getting udev properties for device: ram10
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.246206 #9094] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53598", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.246234 #9094] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.246268 #9094] DEBUG -- : Device ram10 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.246307 #9094] DEBUG -- : Getting udev properties for device: ram11
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.248670 #9094] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53612", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.248702 #9094] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.248748 #9094] DEBUG -- : Device ram11 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.248778 #9094] DEBUG -- : Getting udev properties for device: ram12
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.250347 #9094] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53629", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.250392 #9094] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.250458 #9094] DEBUG -- : Device ram12 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.250490 #9094] DEBUG -- : Getting udev properties for device: ram13
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.252274 #9094] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53647", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.252299 #9094] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.252333 #9094] DEBUG -- : Device ram13 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.252352 #9094] DEBUG -- : Getting udev properties for device: ram14
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.253799 #9094] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53664", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.253824 #9094] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.253859 #9094] DEBUG -- : Device ram14 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.253877 #9094] DEBUG -- : Getting udev properties for device: ram15
Sep 29 17:58:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 29 17:58:16 node-2 puppet-user[9889]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255333 #9094] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53677", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255356 #9094] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255394 #9094] DEBUG -- : Device ram15 removable parameter: "0"
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255428 #9094] 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 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255443 #9094] DEBUG -- : Block device seems to be physical data storage: sda
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255485 #9094] DEBUG -- : Found block device: dm-0
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255507 #9094] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255523 #9094] DEBUG -- : Found block device: dm-1
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255534 #9094] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255543 #9094] DEBUG -- : Found block device: dm-2
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255580 #9094] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255590 #9094] DEBUG -- : Found block device: dm-3
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255600 #9094] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255609 #9094] DEBUG -- : Found block device: dm-4
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255619 #9094] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255628 #9094] DEBUG -- : Found block device: dm-5
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255641 #9094] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255652 #9094] DEBUG -- : Found block device: ram0
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255668 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255685 #9094] DEBUG -- : Found block device: ram1
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255737 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255759 #9094] DEBUG -- : Found block device: ram2
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255781 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255802 #9094] DEBUG -- : Found block device: ram3
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255824 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255844 #9094] DEBUG -- : Found block device: ram4
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255864 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255882 #9094] DEBUG -- : Found block device: ram5
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255899 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255914 #9094] DEBUG -- : Found block device: ram6
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255962 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255978 #9094] DEBUG -- : Found block device: ram7
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.255995 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256014 #9094] DEBUG -- : Found block device: ram8
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256037 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256057 #9094] DEBUG -- : Found block device: ram9
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256078 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256097 #9094] DEBUG -- : Found block device: loop0
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256118 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256139 #9094] DEBUG -- : Found block device: loop1
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256194 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256213 #9094] DEBUG -- : Found block device: loop2
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256232 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256250 #9094] DEBUG -- : Found block device: loop3
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256267 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256280 #9094] DEBUG -- : Found block device: loop4
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256291 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256299 #9094] DEBUG -- : Found block device: loop5
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256309 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256318 #9094] DEBUG -- : Found block device: loop6
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256350 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256359 #9094] DEBUG -- : Found block device: loop7
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256369 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256378 #9094] DEBUG -- : Found block device: ram10
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256389 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256399 #9094] DEBUG -- : Found block device: ram11
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256409 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256417 #9094] DEBUG -- : Found block device: ram12
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256427 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256435 #9094] DEBUG -- : Found block device: ram13
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256478 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256488 #9094] DEBUG -- : Found block device: ram14
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256499 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256507 #9094] DEBUG -- : Found block device: ram15
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256518 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.256549 #9094] 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 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.349396 #9094] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep 29 17:58:16 node-2 nailgun-agent: D, [2016-09-29T17:58:16.349456 #9094] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 29 17:58:16 node-2 puppet-user[9889]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Sep 29 17:58:16 node-2 puppet-user[9889]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 29 17:58:16 node-2 puppet-user[9889]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 29 17:58:16 node-2 puppet-user[9889]: (/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 29 17:58:16 node-2 puppet-user[9889]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 29 17:58:16 node-2 puppet-user[9889]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 29 17:58:16 node-2 puppet-user[9889]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 29 17:58:16 node-2 puppet-user[9889]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 29 17:58:16 node-2 puppet-user[9889]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 29 17:58:16 node-2 puppet-user[9889]: Finished catalog run in 0.07 seconds
Sep 29 17:58:17 node-2 puppet-user[10535]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 29 17:58:17 node-2 puppet-user[10535]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep 29 17:58:18 node-2 puppet-user[10535]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 29 17:58:18 node-2 puppet-user[10535]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 29 17:58:18 node-2 puppet-user[10535]: Finished catalog run in 0.04 seconds
Sep 29 17:58:19 node-2 puppet-user[11003]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 29 17:58:19 node-2 puppet-user[11003]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Sep 29 17:58:20 node-2 puppet-user[11003]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 29 17:58:20 node-2 puppet-user[11003]: Finished catalog run in 0.04 seconds
Sep 29 17:58:21 node-2 puppet-user[11455]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 29 17:58:21 node-2 puppet-user[11455]: Compiled catalog for node-2.domain.tld in environment production in 0.22 seconds
Sep 29 17:58:21 node-2 puppet-user[11455]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 29 17:58:22 node-2 puppet-user[11455]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Sep 29 17:58:22 node-2 puppet-user[11455]: Finished catalog run in 0.45 seconds
Sep 29 17:58:23 node-2 puppet-user[11939]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 29 17:58:23 node-2 puppet-user[11939]: Compiled catalog for node-2.domain.tld in environment production in 0.24 seconds
Sep 29 17:58:23 node-2 puppet-user[11939]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 29 17:58:23 node-2 puppet-user[11939]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 29 17:58:24 node-2 puppet-user[11939]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Sep 29 17:58:24 node-2 kernel: [   68.536341] init: plymouth-upstart-bridge main process ended, respawning
Sep 29 17:58:24 node-2 puppet-user[11939]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 29 17:58:24 node-2 puppet-user[11939]: Finished catalog run in 0.24 seconds
Sep 29 17:58:24 node-2 puppet-agent[8931]: Could not run: SIGTERM
Sep 29 17:58:24 node-2 kernel: [   68.855713] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 29 17:58:24 node-2 ec2: 
Sep 29 17:58:24 node-2 ec2: #############################################################
Sep 29 17:58:24 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 29 17:58:24 node-2 ec2: 1024 d4:07:49:53:bc:2e:72:50:08:0f:1f:12:e2:72:e7:64  root@node-2.domain.tld (DSA)
Sep 29 17:58:24 node-2 ec2: 256 c2:fd:68:04:e9:4a:10:59:eb:b8:f1:38:82:1f:c2:80  root@node-2.domain.tld (ECDSA)
Sep 29 17:58:24 node-2 ec2: 256 5e:d2:0d:d4:8c:c5:5c:20:48:05:95:da:23:69:46:c1  root@node-2.domain.tld (ED25519)
Sep 29 17:58:24 node-2 ec2: 2048 48:0a:8c:7e:0b:37:35:c1:9d:c8:bc:64:85:1f:7d:d3  root@node-2.domain.tld (RSA)
Sep 29 17:58:24 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 29 17:58:24 node-2 ec2: #############################################################
Sep 29 17:58:25 node-2 puppet-user[12586]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 29 17:58:25 node-2 puppet-user[12586]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Sep 29 17:58:25 node-2 puppet-user[12586]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 29 17:58:25 node-2 kernel: [   70.405282] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 29 17:58:25 node-2 kernel: [   70.405331] 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 29 17:58:25 node-2 puppet-user[12586]: (/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 29 17:58:26 node-2 puppet-user[12586]: Finished catalog run in 0.05 seconds
Sep 29 17:58:27 node-2 puppet-user[13039]: (Scope(Class[main])) MODULAR: sync_time
Sep 29 17:58:27 node-2 puppet-user[13039]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 29 17:58:27 node-2 ntpdate[13450]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 29 17:58:28 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369076 #9094] DEBUG -- : Trying to find block devices
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369162 #9094] DEBUG -- : Found block device: sda
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369191 #9094] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369219 #9094] DEBUG -- : Block device seems to be physical data storage: sda
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369239 #9094] DEBUG -- : Found block device: dm-0
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369252 #9094] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369263 #9094] DEBUG -- : Found block device: dm-1
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369274 #9094] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369283 #9094] DEBUG -- : Found block device: dm-2
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369312 #9094] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369322 #9094] DEBUG -- : Found block device: dm-3
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369332 #9094] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369341 #9094] DEBUG -- : Found block device: dm-4
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369350 #9094] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369359 #9094] DEBUG -- : Found block device: dm-5
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369369 #9094] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369377 #9094] DEBUG -- : Found block device: ram0
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369386 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369409 #9094] DEBUG -- : Found block device: ram1
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369420 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369429 #9094] DEBUG -- : Found block device: ram2
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369438 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369446 #9094] DEBUG -- : Found block device: ram3
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369456 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369463 #9094] DEBUG -- : Found block device: ram4
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369472 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369481 #9094] DEBUG -- : Found block device: ram5
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369490 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369520 #9094] DEBUG -- : Found block device: ram6
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369530 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369538 #9094] DEBUG -- : Found block device: ram7
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369548 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369556 #9094] DEBUG -- : Found block device: ram8
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369564 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369572 #9094] DEBUG -- : Found block device: ram9
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369581 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369589 #9094] DEBUG -- : Found block device: loop0
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369614 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369623 #9094] DEBUG -- : Found block device: loop1
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369631 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369639 #9094] DEBUG -- : Found block device: loop2
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369648 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369656 #9094] DEBUG -- : Found block device: loop3
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369664 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369672 #9094] DEBUG -- : Found block device: loop4
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369680 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369705 #9094] DEBUG -- : Found block device: loop5
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369715 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369723 #9094] DEBUG -- : Found block device: loop6
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369732 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369740 #9094] DEBUG -- : Found block device: loop7
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369749 #9094] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369758 #9094] DEBUG -- : Found block device: ram10
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369767 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369775 #9094] DEBUG -- : Found block device: ram11
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369784 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369807 #9094] DEBUG -- : Found block device: ram12
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369817 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369825 #9094] DEBUG -- : Found block device: ram13
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369834 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369842 #9094] DEBUG -- : Found block device: ram14
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369851 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369858 #9094] DEBUG -- : Found block device: ram15
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369867 #9094] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.369894 #9094] 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 29 17:58:28 node-2 nailgun-agent: D, [2016-09-29T17:58:28.511314 #9094] DEBUG -- : Response: status: 200 body: {"id": 2}
Sep 29 17:58:28 node-2 nailgun-agent: I, [2016-09-29T17:58:28.511514 #9094]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep 29 17:58:33 node-2 ntpdate[13450]: adjust time server 10.20.0.2 offset 0.239411 sec
Sep 29 17:58:33 node-2 puppet-user[13039]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 29 17:58:33 node-2 puppet-user[13039]: Finished catalog run in 6.18 seconds
Sep 29 17:58:38 node-2 puppet-user[13758]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 29 17:58:39 node-2 puppet-user[13758]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Sep 29 17:58:39 node-2 puppet-user[13758]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 29 17:58:39 node-2 puppet-user[13758]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Sep 29 17:58:39 node-2 puppet-user[13758]: Finished catalog run in 0.06 seconds
Sep 29 17:58:40 node-2 puppet-user[14216]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 29 17:58:41 node-2 puppet-user[14216]: Compiled catalog for node-2.domain.tld in environment production in 0.48 seconds
Sep 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:41 node-2 puppet-user[14216]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:41 node-2 puppet-user[14216]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:41 node-2 puppet-user[14216]: (/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 29 17:58:42 node-2 puppet-user[14216]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 29 17:58:42 node-2 puppet-user[14216]: Finished catalog run in 0.80 seconds
Sep 29 17:58:43 node-2 puppet-user[14721]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 29 17:58:43 node-2 puppet-user[14721]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Sep 29 17:58:46 node-2 puppet-user[14721]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 29 17:59:01 node-2 CRON[16299]: (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 29 17:59:12 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 29 17:59:12 node-2 nailgun-agent: I, [2016-09-29T17:59:12.686409 #16302]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 29 17:59:13 node-2 puppet-user[14721]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 29 17:59:13 node-2 puppet-user[14721]: Finished catalog run in 29.25 seconds
Sep 29 17:59:14 node-2 puppet-user[17241]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 29 17:59:15 node-2 puppet-user[17241]: Compiled catalog for node-2.domain.tld in environment production in 0.54 seconds
Sep 29 17:59:15 node-2 puppet-user[17241]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 29 17:59:15 node-2 puppet-user[17241]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 29 17:59:15 node-2 puppet-user[17241]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 29 17:59:15 node-2 puppet-user[17241]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 29 17:59:15 node-2 puppet-user[17241]: Finished catalog run in 0.07 seconds
Sep 29 17:59:17 node-2 puppet-user[17699]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 29 17:59:18 node-2 puppet-user[17699]: Compiled catalog for node-2.domain.tld in environment production in 0.81 seconds
Sep 29 17:59:18 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 29 17:59:18 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 29 17:59:18 node-2 crontab[18140]: (root) LIST (root)
Sep 29 17:59:18 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 29 17:59:18 node-2 crontab[18141]: (root) REPLACE (root)
Sep 29 17:59:19 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/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 29 17:59:20 node-2 puppet-user[17699]: (/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 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/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 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 29 17:59:20 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 29 17:59:21 node-2 puppet-user[17699]: (/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 29 17:59:21 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8382" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 29 17:59:21 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 29 17:59:23 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:23 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:23 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:23 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:23 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:35 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:35 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:35 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:35 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:35 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:37 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:37 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:37 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:37 node-2 multipathd: uevent trigger error
<27>Sep 29 17:59:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:00:32 node-2 ntpdate[29047]: no servers can be used, exiting
<27>Sep 29 18:01:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:01:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:15 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:15 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:15 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:15 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:15 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:15 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:24 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:24 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:24 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:24 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:24 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:26 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 29 18:02:26 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 29 18:02:32 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 29 18:02:32 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 29 18:02:38 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 29 18:02:44 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 29 18:02:44 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 29 18:02:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:02:53 node-2 ntpdate[14293]: the NTP socket is in use, exiting
<27>Sep 29 18:02:53 node-2 ntpdate[14345]: the NTP socket is in use, exiting
<27>Sep 29 18:03:03 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:03 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:03 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:05 node-2 haproxy[16776]: 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 29 18:03:06 node-2 haproxy[16780]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:07 node-2 haproxy[16780]: 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 29 18:03:07 node-2 haproxy[16780]: proxy mysqld has no server available!
<27>Sep 29 18:03:09 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:09 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:09 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:09 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:09 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:12 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:15 node-2 haproxy[19295]: 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 29 18:03:15 node-2 haproxy[19295]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:15 node-2 haproxy[19295]: 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 29 18:03:15 node-2 haproxy[19295]: proxy mysqld has no server available!
<129>Sep 29 18:03:16 node-2 haproxy[19299]: 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 29 18:03:16 node-2 haproxy[19299]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:16 node-2 haproxy[19299]: 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 29 18:03:16 node-2 haproxy[19299]: proxy object-storage has no server available!
<27>Sep 29 18:03:18 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:18 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:18 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:18 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:18 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:20 node-2 haproxy[20654]: 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 29 18:03:20 node-2 haproxy[20654]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:20 node-2 haproxy[20654]: 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 29 18:03:20 node-2 haproxy[20654]: proxy neutron has no server available!
<129>Sep 29 18:03:21 node-2 haproxy[20658]: 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 29 18:03:21 node-2 haproxy[20658]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:21 node-2 haproxy[20658]: 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 29 18:03:21 node-2 haproxy[20658]: proxy mysqld has no server available!
<129>Sep 29 18:03:21 node-2 haproxy[20658]: 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 29 18:03:21 node-2 haproxy[20658]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:22 node-2 haproxy[20658]: 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 29 18:03:22 node-2 haproxy[20658]: proxy object-storage has no server available!
<27>Sep 29 18:03:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:23 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:25 node-2 haproxy[22152]: 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 29 18:03:25 node-2 haproxy[22152]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:26 node-2 haproxy[22156]: 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 29 18:03:26 node-2 haproxy[22156]: proxy keystone-1 has no server available!
<129>Sep 29 18:03:26 node-2 haproxy[22156]: 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 29 18:03:26 node-2 haproxy[22156]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:26 node-2 haproxy[22156]: 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 29 18:03:26 node-2 haproxy[22156]: proxy keystone-2 has no server available!
<129>Sep 29 18:03:26 node-2 haproxy[22156]: 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 29 18:03:26 node-2 haproxy[22156]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:26 node-2 haproxy[22156]: 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 29 18:03:26 node-2 haproxy[22156]: proxy neutron has no server available!
<129>Sep 29 18:03:26 node-2 haproxy[22156]: 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 29 18:03:27 node-2 haproxy[22156]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:27 node-2 haproxy[22156]: 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 29 18:03:27 node-2 haproxy[22156]: proxy mysqld has no server available!
<129>Sep 29 18:03:27 node-2 haproxy[22156]: 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 29 18:03:27 node-2 haproxy[22156]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:27 node-2 haproxy[22156]: 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 29 18:03:27 node-2 haproxy[22156]: proxy object-storage has no server available!
<27>Sep 29 18:03:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:28 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:30 node-2 haproxy[23484]: 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 29 18:03:30 node-2 haproxy[23484]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:31 node-2 haproxy[23488]: 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 29 18:03:31 node-2 haproxy[23488]: proxy keystone-1 has no server available!
<129>Sep 29 18:03:31 node-2 haproxy[23488]: 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 29 18:03:31 node-2 haproxy[23488]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:31 node-2 haproxy[23488]: 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 29 18:03:31 node-2 haproxy[23488]: proxy keystone-2 has no server available!
<129>Sep 29 18:03:31 node-2 haproxy[23488]: 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 29 18:03:31 node-2 haproxy[23488]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:31 node-2 haproxy[23488]: 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 29 18:03:31 node-2 haproxy[23488]: proxy neutron has no server available!
<129>Sep 29 18:03:31 node-2 haproxy[23488]: 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 29 18:03:31 node-2 haproxy[23488]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:32 node-2 haproxy[23488]: 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 29 18:03:32 node-2 haproxy[23488]: proxy mysqld has no server available!
<129>Sep 29 18:03:32 node-2 haproxy[23488]: 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 29 18:03:32 node-2 haproxy[23488]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:32 node-2 haproxy[23488]: 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 29 18:03:32 node-2 haproxy[23488]: proxy object-storage has no server available!
<129>Sep 29 18:03:32 node-2 haproxy[23488]: 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 29 18:03:32 node-2 haproxy[23488]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:32 node-2 haproxy[23488]: 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 29 18:03:32 node-2 haproxy[23488]: proxy aodh has no server available!
<27>Sep 29 18:03:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:34 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:36 node-2 haproxy[25023]: 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 29 18:03:36 node-2 haproxy[25023]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:36 node-2 haproxy[25023]: 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 29 18:03:36 node-2 haproxy[25023]: proxy keystone-1 has no server available!
<129>Sep 29 18:03:36 node-2 haproxy[25023]: 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 29 18:03:36 node-2 haproxy[25023]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:36 node-2 haproxy[25023]: 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 29 18:03:36 node-2 haproxy[25023]: proxy keystone-2 has no server available!
<129>Sep 29 18:03:36 node-2 haproxy[25023]: 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 29 18:03:36 node-2 haproxy[25023]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:37 node-2 haproxy[25027]: proxy neutron has no server available!
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:37 node-2 haproxy[25027]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:37 node-2 haproxy[25027]: proxy mysqld has no server available!
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:37 node-2 haproxy[25027]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:37 node-2 haproxy[25027]: proxy object-storage has no server available!
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:37 node-2 haproxy[25027]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:37 node-2 haproxy[25027]: proxy aodh has no server available!
<129>Sep 29 18:03:37 node-2 haproxy[25027]: 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 29 18:03:38 node-2 haproxy[25027]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:38 node-2 haproxy[25027]: 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 29 18:03:38 node-2 haproxy[25027]: proxy ceilometer has no server available!
<27>Sep 29 18:03:39 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:39 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:39 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:39 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:39 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:39 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:41 node-2 haproxy[26407]: 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 29 18:03:41 node-2 haproxy[26407]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:41 node-2 haproxy[26407]: 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 29 18:03:41 node-2 haproxy[26407]: proxy keystone-1 has no server available!
<129>Sep 29 18:03:41 node-2 haproxy[26407]: 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 29 18:03:42 node-2 haproxy[26411]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:42 node-2 haproxy[26411]: 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 29 18:03:42 node-2 haproxy[26411]: proxy keystone-2 has no server available!
<129>Sep 29 18:03:42 node-2 haproxy[26411]: 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 29 18:03:42 node-2 haproxy[26411]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:42 node-2 haproxy[26411]: 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 29 18:03:42 node-2 haproxy[26411]: proxy neutron has no server available!
<129>Sep 29 18:03:42 node-2 haproxy[26411]: 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 29 18:03:42 node-2 haproxy[26411]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:42 node-2 haproxy[26411]: 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 29 18:03:42 node-2 haproxy[26411]: proxy mysqld has no server available!
<129>Sep 29 18:03:42 node-2 haproxy[26411]: 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 29 18:03:42 node-2 haproxy[26411]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:43 node-2 haproxy[26411]: 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 29 18:03:43 node-2 haproxy[26411]: proxy object-storage has no server available!
<129>Sep 29 18:03:43 node-2 haproxy[26411]: 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 29 18:03:43 node-2 haproxy[26411]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:43 node-2 haproxy[26411]: 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 29 18:03:43 node-2 haproxy[26411]: proxy aodh has no server available!
<129>Sep 29 18:03:43 node-2 haproxy[26411]: 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 29 18:03:43 node-2 haproxy[26411]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:43 node-2 haproxy[26411]: 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 29 18:03:43 node-2 haproxy[26411]: proxy ceilometer has no server available!
<27>Sep 29 18:03:44 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:44 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:44 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:44 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:44 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:46 node-2 haproxy[27736]: 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 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:47 node-2 haproxy[27740]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:47 node-2 haproxy[27740]: proxy keystone-1 has no server available!
<129>Sep 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:47 node-2 haproxy[27740]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:47 node-2 haproxy[27740]: proxy keystone-2 has no server available!
<129>Sep 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:47 node-2 haproxy[27740]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:47 node-2 haproxy[27740]: proxy neutron has no server available!
<129>Sep 29 18:03:47 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:48 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: proxy mysqld has no server available!
<129>Sep 29 18:03:48 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:48 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: proxy object-storage has no server available!
<129>Sep 29 18:03:48 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:48 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: proxy aodh has no server available!
<129>Sep 29 18:03:48 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:48 node-2 haproxy[27740]: 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 29 18:03:48 node-2 haproxy[27740]: proxy ceilometer has no server available!
<27>Sep 29 18:03:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:50 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:50 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:50 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:52 node-2 haproxy[29139]: 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 29 18:03:52 node-2 haproxy[29139]: 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 29 18:03:52 node-2 haproxy[29139]: 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 29 18:03:52 node-2 haproxy[29139]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: proxy keystone-1 has no server available!
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: proxy keystone-2 has no server available!
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: proxy glance-api has no server available!
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: proxy glance-glare has no server available!
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: proxy neutron has no server available!
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:53 node-2 haproxy[29143]: proxy glance-registry has no server available!
<129>Sep 29 18:03:53 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:54 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: proxy mysqld has no server available!
<129>Sep 29 18:03:54 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:54 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: proxy object-storage has no server available!
<129>Sep 29 18:03:54 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:54 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: proxy aodh has no server available!
<129>Sep 29 18:03:54 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:54 node-2 haproxy[29143]: 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 29 18:03:54 node-2 haproxy[29143]: proxy ceilometer has no server available!
<27>Sep 29 18:03:55 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:55 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:55 node-2 multipathd: uevent trigger error
<27>Sep 29 18:03:55 node-2 multipathd: uevent trigger error
<129>Sep 29 18:03:58 node-2 haproxy[30511]: 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 29 18:03:58 node-2 haproxy[30511]: 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 29 18:03:58 node-2 haproxy[30511]: 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 29 18:03:58 node-2 haproxy[30511]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:58 node-2 haproxy[30511]: 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 29 18:03:58 node-2 haproxy[30511]: proxy keystone-1 has no server available!
<129>Sep 29 18:03:58 node-2 haproxy[30511]: 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 29 18:03:58 node-2 haproxy[30511]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: proxy keystone-2 has no server available!
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: proxy nova-api has no server available!
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: proxy nova-metadata-api has no server available!
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: proxy glance-api has no server available!
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: proxy glance-glare has no server available!
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: proxy neutron has no server available!
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: proxy glance-registry has no server available!
<129>Sep 29 18:03:59 node-2 haproxy[30515]: 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 29 18:03:59 node-2 haproxy[30515]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: proxy mysqld has no server available!
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: proxy object-storage has no server available!
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: proxy aodh has no server available!
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: proxy ceilometer has no server available!
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:00 node-2 haproxy[30515]: 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 29 18:04:00 node-2 haproxy[30515]: proxy nova-novncproxy has no server available!
<27>Sep 29 18:04:02 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:02 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:02 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:02 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:02 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:02 node-2 multipathd: uevent trigger error
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: proxy keystone-1 has no server available!
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: proxy keystone-2 has no server available!
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: proxy nova-api has no server available!
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: proxy nova-metadata-api has no server available!
<129>Sep 29 18:04:04 node-2 haproxy[31863]: 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 29 18:04:04 node-2 haproxy[31863]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy cinder-api has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy glance-api has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy glance-glare has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy neutron has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy glance-registry has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy mysqld has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy object-storage has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:05 node-2 haproxy[31867]: proxy aodh has no server available!
<129>Sep 29 18:04:05 node-2 haproxy[31867]: 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 29 18:04:06 node-2 haproxy[31867]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:06 node-2 haproxy[31867]: 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 29 18:04:06 node-2 haproxy[31867]: proxy ceilometer has no server available!
<129>Sep 29 18:04:06 node-2 haproxy[31867]: 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 29 18:04:06 node-2 haproxy[31867]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:06 node-2 haproxy[31867]: 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 29 18:04:06 node-2 haproxy[31867]: proxy nova-novncproxy has no server available!
<27>Sep 29 18:04:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:07 node-2 multipathd: uevent trigger error
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy keystone-1 has no server available!
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy keystone-2 has no server available!
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy nova-api has no server available!
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy nova-metadata-api has no server available!
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy cinder-api has no server available!
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy glance-api has no server available!
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy glance-glare has no server available!
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:10 node-2 haproxy[799]: 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 29 18:04:10 node-2 haproxy[799]: proxy neutron has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy glance-registry has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy mysqld has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy object-storage has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy aodh has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy ceilometer has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy heat-api has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy heat-api-cfn has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy heat-api-cloudwatch has no server available!
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 29 18:04:11 node-2 haproxy[806]: 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 29 18:04:11 node-2 haproxy[806]: proxy nova-novncproxy has no server available!
<27>Sep 29 18:04:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:16 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:16 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:16 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:16 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:16 node-2 multipathd: uevent trigger error
<27>Sep 29 18:04:23 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 29 18:04:47 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 29 18:04:49 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 29 18:05:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:05:17 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 29 18:05:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:05:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:05:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:05:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:05:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:05:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:05:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:27 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:27 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:27 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:27 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:33 node-2 multipathd: uevent trigger error
<43>Sep 29 18:07:52 node-2 apache2_error [Thu Sep 29 18:07:44.395094 2016] [mpm_event:notice] [pid 6978:tid 140518491305856] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 29 18:07:52 node-2 apache2_error [Thu Sep 29 18:07:44.395259 2016] [core:notice] [pid 6978:tid 140518491305856] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 29 18:07:52 node-2 apache2_error [Thu Sep 29 18:07:47.479495 2016] [mpm_event:notice] [pid 6978:tid 140518491305856] AH00491: caught SIGTERM, shutting down
<43>Sep 29 18:07:52 node-2 apache2_error [Thu Sep 29 18:07:48.587005 2016] [mpm_worker:notice] [pid 7352:tid 140558016841600] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 29 18:07:52 node-2 apache2_error [Thu Sep 29 18:07:48.587042 2016] [core:notice] [pid 7352:tid 140558016841600] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 29 18:07:53 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:53 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:53 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:53 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:07:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:08:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:41 node-2 multipathd: uevent trigger error
<43>Sep 29 18:08:42 node-2 apache2_error [Thu Sep 29 18:08:38.137135 2016] [mpm_worker:notice] [pid 7352:tid 140558016841600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 29 18:08:42 node-2 apache2_error [Thu Sep 29 18:08:38.144027 2016] [mpm_worker:warn] [pid 7352:tid 140558016841600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 29 18:08:42 node-2 apache2_error [Thu Sep 29 18:08:38.144870 2016] [mpm_worker:notice] [pid 7352:tid 140558016841600] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 29 18:08:42 node-2 apache2_error [Thu Sep 29 18:08:38.144887 2016] [core:notice] [pid 7352:tid 140558016841600] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 29 18:08:46 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:46 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:46 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:46 node-2 multipathd: uevent trigger error
<27>Sep 29 18:08:46 node-2 multipathd: uevent trigger error
<43>Sep 29 18:09:52 node-2 apache2_error [Thu Sep 29 18:09:47.237619 2016] [mpm_worker:notice] [pid 7352:tid 140558016841600] AH00295: caught SIGTERM, shutting down
<43>Sep 29 18:09:52 node-2 apache2_error [Thu Sep 29 18:09:47.992132 2016] [mpm_worker:notice] [pid 28318:tid 140225096263552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 29 18:09:52 node-2 apache2_error [Thu Sep 29 18:09:47.992160 2016] [core:notice] [pid 28318:tid 140225096263552] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 29 18:10:32 node-2 apache2_error [Thu Sep 29 18:10:32.040102 2016] [mpm_worker:notice] [pid 28318:tid 140225096263552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 29 18:10:32 node-2 apache2_error [Thu Sep 29 18:10:32.054534 2016] [mpm_worker:warn] [pid 28318:tid 140225096263552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 29 18:10:32 node-2 apache2_error [Thu Sep 29 18:10:32.058997 2016] [mpm_worker:notice] [pid 28318:tid 140225096263552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 29 18:10:32 node-2 apache2_error [Thu Sep 29 18:10:32.059017 2016] [core:notice] [pid 28318:tid 140225096263552] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 29 18:11:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:11:52 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:52 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:52 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:52 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:11:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:12:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:13:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:13:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:13:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:13:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:13:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:14:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:14:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:14:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:14:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:14:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:14:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:14:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:14:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:15:54 node-2 multipathd: uevent trigger error
<27>Sep 29 18:15:54 node-2 multipathd: uevent trigger error
<27>Sep 29 18:15:54 node-2 multipathd: uevent trigger error
<27>Sep 29 18:15:54 node-2 multipathd: uevent trigger error
<27>Sep 29 18:15:54 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:16:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:17:22 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:18:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:18:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:18:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:18:45 node-2 multipathd: uevent trigger error
<27>Sep 29 18:18:46 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:11 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:11 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:11 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:11 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:11 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:50 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:50 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:50 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:50 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:50 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:19:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:20:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:20:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:20:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:20:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:20:21 node-2 multipathd: uevent trigger error
<27>Sep 29 18:20:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:21:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:04 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 29 18:21:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 29 18:21:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 29 18:21:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Sep 29 18:21:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Sep 29 18:21:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:26 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:41 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:21:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:23:25 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:24:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:24:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:16 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:16 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:28 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:37 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:43 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:43 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:43 node-2 multipathd: uevent trigger error
<27>Sep 29 18:25:43 node-2 multipathd: uevent trigger error
<27>Sep 29 18:26:26 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:26:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:26:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:26:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:26:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:26:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:42 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:57 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:58 node-2 multipathd: uevent trigger error
<27>Sep 29 18:27:58 node-2 multipathd: uevent trigger error
<11>Sep 29 18:28:10 node-2 liberasurecode[19854]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:10 node-2 liberasurecode[19854]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:10 node-2 liberasurecode[19854]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:10 node-2 liberasurecode[19854]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:10 node-2 liberasurecode[19878]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:10 node-2 liberasurecode[19878]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:10 node-2 liberasurecode[19878]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:10 node-2 liberasurecode[19878]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:12 node-2 liberasurecode[20278]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:12 node-2 liberasurecode[20278]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:12 node-2 liberasurecode[20278]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:12 node-2 liberasurecode[20278]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:16 node-2 liberasurecode[20934]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:16 node-2 liberasurecode[20934]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:16 node-2 liberasurecode[20934]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:16 node-2 liberasurecode[20934]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[20973]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[20973]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[20973]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[20973]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21018]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21018]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21083]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21083]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21083]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21083]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21097]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21097]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21115]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21115]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21115]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21115]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21130]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21130]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21130]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:17 node-2 liberasurecode[21130]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:26 node-2 liberasurecode[21630]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:26 node-2 liberasurecode[21630]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:26 node-2 liberasurecode[21630]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:28:26 node-2 liberasurecode[21630]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 29 18:28:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:28:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:28:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:28:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:28:34 node-2 multipathd: uevent trigger error
<27>Sep 29 18:28:34 node-2 multipathd: uevent trigger error
<43>Sep 29 18:29:24 node-2 apache2_error [Thu Sep 29 18:29:20.088711 2016] [mpm_worker:notice] [pid 28318:tid 140225096263552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 29 18:29:24 node-2 apache2_error [Thu Sep 29 18:29:20.474700 2016] [mpm_worker:warn] [pid 28318:tid 140225096263552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 29 18:29:24 node-2 apache2_error [Thu Sep 29 18:29:20.478219 2016] [mpm_worker:notice] [pid 28318:tid 140225096263552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 29 18:29:24 node-2 apache2_error [Thu Sep 29 18:29:20.478231 2016] [core:notice] [pid 28318:tid 140225096263552] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 29 18:29:28 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 29 18:30:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:01 node-2 multipathd: uevent trigger error
<11>Sep 29 18:30:02 node-2 liberasurecode[4308]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:30:02 node-2 liberasurecode[4308]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:30:02 node-2 liberasurecode[4308]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:30:02 node-2 liberasurecode[4308]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Sep 29 18:30:04 node-2 apache2_error [Thu Sep 29 18:29:57.131606 2016] [mpm_worker:notice] [pid 28318:tid 140225096263552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 29 18:30:04 node-2 apache2_error [Thu Sep 29 18:29:57.326773 2016] [mpm_worker:warn] [pid 28318:tid 140225096263552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 29 18:30:04 node-2 apache2_error [Thu Sep 29 18:29:57.335652 2016] [mpm_worker:notice] [pid 28318:tid 140225096263552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 29 18:30:04 node-2 apache2_error [Thu Sep 29 18:29:57.335686 2016] [core:notice] [pid 28318:tid 140225096263552] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 29 18:30:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:07 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:13 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:29 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:29 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:29 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:29 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:29 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:30:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:03 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 29 18:31:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:12 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:17 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:23 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:35 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:35 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:35 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:36 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:36 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:39 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 29 18:31:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:31:49 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:06 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:06 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:06 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:06 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:06 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:20 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:33 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:38 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:38 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:38 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:38 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:38 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:51 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:32:56 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:01 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:05 node-2 multipathd: uevent trigger error
<27>Sep 29 18:33:05 node-2 multipathd: uevent trigger error
<11>Sep 29 18:35:01 node-2 liberasurecode[3825]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:35:01 node-2 liberasurecode[3825]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:35:01 node-2 liberasurecode[3825]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 29 18:35:01 node-2 liberasurecode[3825]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
