Jul 23 20:57:49 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] start
Jul 23 20:57:49 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 23 20:57:49 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 23 20:57:49 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 23 20:57:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 23 20:57:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 23 20:57:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 23 20:57:49 node-2 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 23 20:57:49 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=54f94713-5f25-4270-9e18-e1ed37a23278 nomdmonddf nomdmonisw
Jul 23 20:57:49 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 23 20:57:49 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 23 20:57:49 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 23 20:57:49 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 23 20:57:49 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 23 20:57:49 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 23 20:57:49 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 23 20:57:49 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
Jul 23 20:57:49 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 23 20:57:49 node-2 kernel: [    0.000000] No AGP bridge found
Jul 23 20:57:49 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 23 20:57:49 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 23 20:57:49 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 23 20:57:49 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 23 20:57:49 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 23 20:57:49 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 23 20:57:49 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 23 20:57:49 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 23 20:57:49 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 23 20:57:49 node-2 kernel: [    0.000000]   2 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000]   3 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000]   4 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000]   5 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000]   6 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000]   7 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000]   8 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000]   9 disabled
Jul 23 20:57:49 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 23 20:57:49 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 23 20:57:49 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 23 20:57:49 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 23 20:57:49 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 23 20:57:49 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 23 20:57:49 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 23 20:57:49 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 23 20:57:49 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 23 20:57:49 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 23 20:57:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 23 20:57:49 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 23 20:57:49 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 23 20:57:49 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 23 20:57:49 node-2 kernel: [    0.000000] Zone ranges:
Jul 23 20:57:49 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 23 20:57:49 node-2 kernel: [    0.000000] Early memory node ranges
Jul 23 20:57:49 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 23 20:57:49 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 23 20:57:49 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 23 20:57:49 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 23 20:57:49 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 23 20:57:49 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 23 20:57:49 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 23 20:57:49 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 23 20:57:49 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 23 20:57:49 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 23 20:57:49 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 23 20:57:49 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 23 20:57:49 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 23 20:57:49 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 23 20:57:49 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 23 20:57:49 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 23 20:57:49 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 23 20:57:49 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 23 20:57:49 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 23 20:57:49 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 23 20:57:49 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 23 20:57:49 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 23 20:57:49 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 23 20:57:49 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 23 20:57:49 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 
Jul 23 20:57:49 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 23 20:57:49 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 23 20:57:49 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=54f94713-5f25-4270-9e18-e1ed37a23278 nomdmonddf nomdmonisw
Jul 23 20:57:49 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 23 20:57:49 node-2 kernel: [    0.000000] Checking aperture...
Jul 23 20:57:49 node-2 kernel: [    0.000000] No AGP bridge found
Jul 23 20:57:49 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 23 20:57:49 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 23 20:57:49 node-2 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 23 20:57:49 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 23 20:57:49 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 23 20:57:49 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 23 20:57:49 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 23 20:57:49 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 23 20:57:49 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 23 20:57:49 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 23 20:57:49 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 23 20:57:49 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 23 20:57:49 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 23 20:57:49 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 23 20:57:49 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 23 20:57:49 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 23 20:57:49 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 23 20:57:49 node-2 kernel: [    0.004000] tsc: Detected 3492.265 MHz processor
Jul 23 20:57:49 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.53 BogoMIPS (lpj=13969060)
Jul 23 20:57:49 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 23 20:57:49 node-2 kernel: [    0.000047] Security Framework initialized
Jul 23 20:57:49 node-2 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 23 20:57:49 node-2 kernel: [    0.000066] Yama: becoming mindful.
Jul 23 20:57:49 node-2 kernel: [    0.001462] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.006348] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.008277] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.008305] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.008596] Initializing cgroup subsys memory
Jul 23 20:57:49 node-2 kernel: [    0.008605] Initializing cgroup subsys devices
Jul 23 20:57:49 node-2 kernel: [    0.008607] Initializing cgroup subsys freezer
Jul 23 20:57:49 node-2 kernel: [    0.008609] Initializing cgroup subsys blkio
Jul 23 20:57:49 node-2 kernel: [    0.008610] Initializing cgroup subsys perf_event
Jul 23 20:57:49 node-2 kernel: [    0.008613] Initializing cgroup subsys hugetlb
Jul 23 20:57:49 node-2 kernel: [    0.008632] CPU: Physical Processor ID: 0
Jul 23 20:57:49 node-2 kernel: [    0.008633] CPU: Processor Core ID: 0
Jul 23 20:57:49 node-2 kernel: [    0.008637] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 23 20:57:49 node-2 kernel: [    0.008637] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 23 20:57:49 node-2 kernel: [    0.009330] mce: CPU supports 22 MCE banks
Jul 23 20:57:49 node-2 kernel: [    0.009357] CPU0: Thermal monitoring enabled (TM1)
Jul 23 20:57:49 node-2 kernel: [    0.009379] process: using mwait in idle threads
Jul 23 20:57:49 node-2 kernel: [    0.009382] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 23 20:57:49 node-2 kernel: [    0.009382] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 23 20:57:49 node-2 kernel: [    0.009382] tlb_flushall_shift: 6
Jul 23 20:57:49 node-2 kernel: [    0.009470] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 23 20:57:49 node-2 kernel: [    0.010195] ACPI: Core revision 20131115
Jul 23 20:57:49 node-2 kernel: [    0.022863] ACPI: All ACPI Tables successfully acquired
Jul 23 20:57:49 node-2 kernel: [    0.023027] ftrace: allocating 28617 entries in 112 pages
Jul 23 20:57:49 node-2 kernel: [    0.031851] dmar: Host address width 46
Jul 23 20:57:49 node-2 kernel: [    0.031853] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 23 20:57:49 node-2 kernel: [    0.031859] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 23 20:57:49 node-2 kernel: [    0.031861] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 23 20:57:49 node-2 kernel: [    0.031864] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 23 20:57:49 node-2 kernel: [    0.031866] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 23 20:57:49 node-2 kernel: [    0.031867] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 23 20:57:49 node-2 kernel: [    0.031868] dmar: ATSR flags: 0x0
Jul 23 20:57:49 node-2 kernel: [    0.031870] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 23 20:57:49 node-2 kernel: [    0.031871] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 23 20:57:49 node-2 kernel: [    0.031986] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 23 20:57:49 node-2 kernel: [    0.031987] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 23 20:57:49 node-2 kernel: [    0.031988] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 23 20:57:49 node-2 kernel: [    0.031989] HPET id 0 under DRHD base 0xc7ffc000
Jul 23 20:57:49 node-2 kernel: [    0.031990] Your BIOS is broken and requested that x2apic be disabled.
Jul 23 20:57:49 node-2 kernel: [    0.031990] This will slightly decrease performance.
Jul 23 20:57:49 node-2 kernel: [    0.031990] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 23 20:57:49 node-2 kernel: [    0.032422] Enabled IRQ remapping in xapic mode
Jul 23 20:57:49 node-2 kernel: [    0.032423] x2apic not enabled, IRQ remapping is in xapic mode
Jul 23 20:57:49 node-2 kernel: [    0.032427] Switched APIC routing to physical flat.
Jul 23 20:57:49 node-2 kernel: [    0.033044] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 23 20:57:49 node-2 kernel: [    0.072697] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 23 20:57:49 node-2 kernel: [    0.072703] TSC deadline timer enabled
Jul 23 20:57:49 node-2 kernel: [    0.072710] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 23 20:57:49 node-2 kernel: [    0.072716] ... version:                3
Jul 23 20:57:49 node-2 kernel: [    0.072717] ... bit width:              48
Jul 23 20:57:49 node-2 kernel: [    0.072718] ... generic registers:      4
Jul 23 20:57:49 node-2 kernel: [    0.072719] ... value mask:             0000ffffffffffff
Jul 23 20:57:49 node-2 kernel: [    0.072720] ... max period:             0000ffffffffffff
Jul 23 20:57:49 node-2 kernel: [    0.072721] ... fixed-purpose events:   3
Jul 23 20:57:49 node-2 kernel: [    0.072722] ... event mask:             000000070000000f
Jul 23 20:57:49 node-2 kernel: [    0.074166] x86: Booting SMP configuration:
Jul 23 20:57:49 node-2 kernel: [    0.088373] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 23 20:57:49 node-2 kernel: [    0.074168] .... node  #0, CPUs:        #1  #2  #3
Jul 23 20:57:49 node-2 kernel: [    0.116299] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 23 20:57:49 node-2 kernel: [    0.270464] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 23 20:57:49 node-2 kernel: [    0.326090] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 23 20:57:49 node-2 kernel: [    0.383156] x86: Booted up 2 nodes, 16 CPUs
Jul 23 20:57:49 node-2 kernel: [    0.383159] smpboot: Total of 16 processors activated (111764.13 BogoMIPS)
Jul 23 20:57:49 node-2 kernel: [    0.407412] devtmpfs: initialized
Jul 23 20:57:49 node-2 kernel: [    0.410528] EVM: security.selinux
Jul 23 20:57:49 node-2 kernel: [    0.410529] EVM: security.SMACK64
Jul 23 20:57:49 node-2 kernel: [    0.410530] EVM: security.ima
Jul 23 20:57:49 node-2 kernel: [    0.410531] EVM: security.capability
Jul 23 20:57:49 node-2 kernel: [    0.410581] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.411242] pinctrl core: initialized pinctrl subsystem
Jul 23 20:57:49 node-2 kernel: [    0.411305] regulator-dummy: no parameters
Jul 23 20:57:49 node-2 kernel: [    0.411337] RTC time: 20:57:09, date: 07/23/16
Jul 23 20:57:49 node-2 kernel: [    0.411371] NET: Registered protocol family 16
Jul 23 20:57:49 node-2 kernel: [    0.411457] cpuidle: using governor ladder
Jul 23 20:57:49 node-2 kernel: [    0.411458] cpuidle: using governor menu
Jul 23 20:57:49 node-2 kernel: [    0.411493] ACPI: bus type PCI registered
Jul 23 20:57:49 node-2 kernel: [    0.411495] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 23 20:57:49 node-2 kernel: [    0.411541] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 23 20:57:49 node-2 kernel: [    0.411543] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 23 20:57:49 node-2 kernel: [    0.425280] PCI: Using configuration type 1 for base access
Jul 23 20:57:49 node-2 kernel: [    0.426270] bio: create slab <bio-0> at 0
Jul 23 20:57:49 node-2 kernel: [    0.426554] ACPI: Added _OSI(Module Device)
Jul 23 20:57:49 node-2 kernel: [    0.426556] ACPI: Added _OSI(Processor Device)
Jul 23 20:57:49 node-2 kernel: [    0.426557] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 23 20:57:49 node-2 kernel: [    0.426558] ACPI: Added _OSI(Processor Aggregator Device)
Jul 23 20:57:49 node-2 kernel: [    0.439202] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 23 20:57:49 node-2 kernel: [    0.449657] ACPI: Interpreter enabled
Jul 23 20:57:49 node-2 kernel: [    0.449663] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 23 20:57:49 node-2 kernel: [    0.449667] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 23 20:57:49 node-2 kernel: [    0.449669] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 23 20:57:49 node-2 kernel: [    0.449676] ACPI: (supports S0 S4 S5)
Jul 23 20:57:49 node-2 kernel: [    0.449677] ACPI: Using IOAPIC for interrupt routing
Jul 23 20:57:49 node-2 kernel: [    0.449720] HEST: Table parsing has been initialized.
Jul 23 20:57:49 node-2 kernel: [    0.449723] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 23 20:57:49 node-2 kernel: [    0.450274] ACPI: No dock devices found.
Jul 23 20:57:49 node-2 kernel: [    0.461869] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 23 20:57:49 node-2 kernel: [    0.461874] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 20:57:49 node-2 kernel: [    0.461878] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 23 20:57:49 node-2 kernel: [    0.461906] PCI host bridge to bus 0000:ff
Jul 23 20:57:49 node-2 kernel: [    0.461909] pci_bus 0000:ff: root bus resource [bus ff]
Jul 23 20:57:49 node-2 kernel: [    0.461917] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.461956] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.461986] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462022] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462052] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.462082] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.462113] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462144] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462176] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462204] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462231] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462258] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462287] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462313] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462340] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462367] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462398] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462425] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462452] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.462481] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462509] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.462537] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462566] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462599] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.462636] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462668] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462698] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462729] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462761] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462792] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462823] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462854] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462886] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462919] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462952] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.462984] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463016] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463047] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463075] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463107] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463142] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463180] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463217] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463250] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463279] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463308] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463341] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463370] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463403] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463434] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463466] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463496] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463526] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463556] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463586] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463618] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463651] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463709] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 23 20:57:49 node-2 kernel: [    0.463711] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 20:57:49 node-2 kernel: [    0.463714] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 23 20:57:49 node-2 kernel: [    0.463732] PCI host bridge to bus 0000:7f
Jul 23 20:57:49 node-2 kernel: [    0.463734] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 23 20:57:49 node-2 kernel: [    0.463739] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463767] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.463796] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463826] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463847] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.463873] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.463899] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463926] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463948] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463971] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.463999] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464024] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464050] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464074] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464098] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464125] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464147] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464170] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464192] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.464216] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464238] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.464260] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464283] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464310] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 23 20:57:49 node-2 kernel: [    0.464345] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464373] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464402] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464430] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464455] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464483] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464511] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464540] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464564] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464593] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464621] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464649] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464678] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464705] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464731] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464759] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464784] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464811] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464839] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464865] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464892] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464919] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464945] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.464971] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465000] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465027] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465057] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465083] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465106] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465131] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465157] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465188] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.465214] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.466474] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 23 20:57:49 node-2 kernel: [    0.466477] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 20:57:49 node-2 kernel: [    0.467596] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 23 20:57:49 node-2 kernel: [    0.468116] PCI host bridge to bus 0000:00
Jul 23 20:57:49 node-2 kernel: [    0.468119] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 23 20:57:49 node-2 kernel: [    0.468120] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 23 20:57:49 node-2 kernel: [    0.468122] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 23 20:57:49 node-2 kernel: [    0.468123] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 23 20:57:49 node-2 kernel: [    0.468124] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 23 20:57:49 node-2 kernel: [    0.468126] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 23 20:57:49 node-2 kernel: [    0.468127] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 23 20:57:49 node-2 kernel: [    0.468133] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 23 20:57:49 node-2 kernel: [    0.468216] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.468247] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.468288] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 23 20:57:49 node-2 kernel: [    0.468308] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.468337] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.468378] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 23 20:57:49 node-2 kernel: [    0.468397] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.468426] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.468466] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 23 20:57:49 node-2 kernel: [    0.468484] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.468555] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.468633] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.468710] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 23 20:57:49 node-2 kernel: [    0.468715] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 23 20:57:49 node-2 kernel: [    0.468800] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 23 20:57:49 node-2 kernel: [    0.468948] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 23 20:57:49 node-2 kernel: [    0.468965] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 23 20:57:49 node-2 kernel: [    0.469042] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.469098] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 23 20:57:49 node-2 kernel: [    0.469120] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.469175] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.469219] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 23 20:57:49 node-2 kernel: [    0.469247] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.469302] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.469345] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 23 20:57:49 node-2 kernel: [    0.469370] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 23 20:57:49 node-2 kernel: [    0.469387] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 23 20:57:49 node-2 kernel: [    0.469465] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.469514] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 23 20:57:49 node-2 kernel: [    0.469544] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 23 20:57:49 node-2 kernel: [    0.469791] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 23 20:57:49 node-2 kernel: [    0.469797] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 23 20:57:49 node-2 kernel: [    0.469803] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.469809] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.469816] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 23 20:57:49 node-2 kernel: [    0.469846] pci 0000:01:00.0: supports D1 D2
Jul 23 20:57:49 node-2 kernel: [    0.479999] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 23 20:57:49 node-2 kernel: [    0.480006] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 23 20:57:49 node-2 kernel: [    0.480010] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 23 20:57:49 node-2 kernel: [    0.480173] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.480207] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 23 20:57:49 node-2 kernel: [    0.487997] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 23 20:57:49 node-2 kernel: [    0.488003] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.488007] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 20:57:49 node-2 kernel: [    0.488092] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.488164] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.488253] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.488298] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 23 20:57:49 node-2 kernel: [    0.488302] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.488304] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 20:57:49 node-2 kernel: [    0.488356] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.488500] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.488554] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 23 20:57:49 node-2 kernel: [    0.488556] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.488558] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.488607] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.488726] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.488768] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.488887] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.488924] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.489043] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.489079] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 23 20:57:49 node-2 kernel: [    0.489197] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 23 20:57:49 node-2 kernel: [    0.489239] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 23 20:57:49 node-2 kernel: [    0.489241] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.489243] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.489303] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 23 20:57:49 node-2 kernel: [    0.489368] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.489420] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.489486] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 23 20:57:49 node-2 kernel: [    0.489566] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 23 20:57:49 node-2 kernel: [    0.489673] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 23 20:57:49 node-2 kernel: [    0.489676] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.489678] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.489734] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 23 20:57:49 node-2 kernel: [    0.489788] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.489836] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.490052] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 23 20:57:49 node-2 kernel: [    0.490056] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 23 20:57:49 node-2 kernel: [    0.490119] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 23 20:57:49 node-2 kernel: [    0.490171] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.490220] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.490449] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 23 20:57:49 node-2 kernel: [    0.490453] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 23 20:57:49 node-2 kernel: [    0.490513] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 23 20:57:49 node-2 kernel: [    0.490577] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.490629] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 23 20:57:49 node-2 kernel: [    0.490849] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 23 20:57:49 node-2 kernel: [    0.490852] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 23 20:57:49 node-2 kernel: [    0.491029] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 23 20:57:49 node-2 kernel: [    0.491067] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 23 20:57:49 node-2 kernel: [    0.491145] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 23 20:57:49 node-2 kernel: [    0.491164] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 23 20:57:49 node-2 kernel: [    0.491177] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 23 20:57:49 node-2 kernel: [    0.491191] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 23 20:57:49 node-2 kernel: [    0.491241] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 23 20:57:49 node-2 kernel: [    0.496004] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 23 20:57:49 node-2 kernel: [    0.496013] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 23 20:57:49 node-2 kernel: [    0.496066] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 23 20:57:49 node-2 kernel: [    0.496800] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 23 20:57:49 node-2 kernel: [    0.496803] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 20:57:49 node-2 kernel: [    0.496923] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 23 20:57:49 node-2 kernel: [    0.497035] PCI host bridge to bus 0000:80
Jul 23 20:57:49 node-2 kernel: [    0.497037] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 23 20:57:49 node-2 kernel: [    0.497038] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 23 20:57:49 node-2 kernel: [    0.497040] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 23 20:57:49 node-2 kernel: [    0.497048] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.497112] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.497180] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 23 20:57:49 node-2 kernel: [    0.497245] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 23 20:57:49 node-2 kernel: [    0.497250] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 23 20:57:49 node-2 kernel: [    0.497322] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 23 20:57:49 node-2 kernel: [    0.497619] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 23 20:57:49 node-2 kernel: [    0.497650] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 23 20:57:49 node-2 kernel: [    0.497680] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 23 20:57:49 node-2 kernel: [    0.497709] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 23 20:57:49 node-2 kernel: [    0.497738] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 20:57:49 node-2 kernel: [    0.497767] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 20:57:49 node-2 kernel: [    0.497797] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 20:57:49 node-2 kernel: [    0.497826] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 20:57:49 node-2 kernel: [    0.497911] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 23 20:57:49 node-2 kernel: [    0.497916] ACPI: \_SB_.UNC1: notify handler is installed
Jul 23 20:57:49 node-2 kernel: [    0.497917] ACPI: \_SB_.UNC0: notify handler is installed
Jul 23 20:57:49 node-2 kernel: [    0.497932] ACPI: \_SB_.PCI0: notify handler is installed
Jul 23 20:57:49 node-2 kernel: [    0.497985] ACPI: \_SB_.PCI1: notify handler is installed
Jul 23 20:57:49 node-2 kernel: [    0.498064] Found 4 acpi root devices
Jul 23 20:57:49 node-2 kernel: [    0.498174] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 23 20:57:49 node-2 kernel: [    0.498176] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 23 20:57:49 node-2 kernel: [    0.498178] vgaarb: loaded
Jul 23 20:57:49 node-2 kernel: [    0.498179] vgaarb: bridge control possible 0000:0c:00.0
Jul 23 20:57:49 node-2 kernel: [    0.498298] SCSI subsystem initialized
Jul 23 20:57:49 node-2 kernel: [    0.498362] libata version 3.00 loaded.
Jul 23 20:57:49 node-2 kernel: [    0.498378] ACPI: bus type USB registered
Jul 23 20:57:49 node-2 kernel: [    0.498389] usbcore: registered new interface driver usbfs
Jul 23 20:57:49 node-2 kernel: [    0.498394] usbcore: registered new interface driver hub
Jul 23 20:57:49 node-2 kernel: [    0.498418] usbcore: registered new device driver usb
Jul 23 20:57:49 node-2 kernel: [    0.498588] PCI: Using ACPI for IRQ routing
Jul 23 20:57:49 node-2 kernel: [    0.502197] PCI: pci_cache_line_size set to 64 bytes
Jul 23 20:57:49 node-2 kernel: [    0.502404] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 23 20:57:49 node-2 kernel: [    0.502405] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 23 20:57:49 node-2 kernel: [    0.502406] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 23 20:57:49 node-2 kernel: [    0.502472] NetLabel: Initializing
Jul 23 20:57:49 node-2 kernel: [    0.502474] NetLabel:  domain hash size = 128
Jul 23 20:57:49 node-2 kernel: [    0.502474] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 23 20:57:49 node-2 kernel: [    0.502484] NetLabel:  unlabeled traffic allowed by default
Jul 23 20:57:49 node-2 kernel: [    0.502552] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 23 20:57:49 node-2 kernel: [    0.502556] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 23 20:57:49 node-2 kernel: [    0.504620] Switched to clocksource hpet
Jul 23 20:57:49 node-2 kernel: [    0.508601] AppArmor: AppArmor Filesystem Enabled
Jul 23 20:57:49 node-2 kernel: [    0.508621] pnp: PnP ACPI init
Jul 23 20:57:49 node-2 kernel: [    0.508628] ACPI: bus type PNP registered
Jul 23 20:57:49 node-2 kernel: [    0.508738] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 23 20:57:49 node-2 kernel: [    0.508746] pnp 00:01: [dma 4]
Jul 23 20:57:49 node-2 kernel: [    0.508758] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 23 20:57:49 node-2 kernel: [    0.508784] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 23 20:57:49 node-2 kernel: [    0.508804] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 23 20:57:49 node-2 kernel: [    0.508822] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 23 20:57:49 node-2 kernel: [    0.508871] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 23 20:57:49 node-2 kernel: [    0.508924] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508926] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 23 20:57:49 node-2 kernel: [    0.508928] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508929] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508931] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508936] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508938] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 23 20:57:49 node-2 kernel: [    0.508939] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508941] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508942] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508944] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508945] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508947] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 23 20:57:49 node-2 kernel: [    0.508949] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 23 20:57:49 node-2 kernel: [    0.509032] pnp 00:07: [dma 0 disabled]
Jul 23 20:57:49 node-2 kernel: [    0.509061] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 23 20:57:49 node-2 kernel: [    0.509135] pnp 00:08: [dma 0 disabled]
Jul 23 20:57:49 node-2 kernel: [    0.509167] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 23 20:57:49 node-2 kernel: [    0.509218] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 23 20:57:49 node-2 kernel: [    0.509563] pnp: PnP ACPI: found 10 devices
Jul 23 20:57:49 node-2 kernel: [    0.509565] ACPI: bus type PNP unregistered
Jul 23 20:57:49 node-2 kernel: [    0.515880] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 23 20:57:49 node-2 kernel: [    0.515883] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 23 20:57:49 node-2 kernel: [    0.515886] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 23 20:57:49 node-2 kernel: [    0.515890] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 23 20:57:49 node-2 kernel: [    0.515892] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.515906] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.515939] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 23 20:57:49 node-2 kernel: [    0.515953] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 23 20:57:49 node-2 kernel: [    0.515982] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 23 20:57:49 node-2 kernel: [    0.515997] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 23 20:57:49 node-2 kernel: [    0.516025] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 23 20:57:49 node-2 kernel: [    0.516040] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 23 20:57:49 node-2 kernel: [    0.516068] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 23 20:57:49 node-2 kernel: [    0.516070] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516085] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516113] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 23 20:57:49 node-2 kernel: [    0.516115] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516130] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516159] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 23 20:57:49 node-2 kernel: [    0.516160] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516163] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516167] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 23 20:57:49 node-2 kernel: [    0.516169] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516171] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516175] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 23 20:57:49 node-2 kernel: [    0.516180] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 23 20:57:49 node-2 kernel: [    0.516188] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 23 20:57:49 node-2 kernel: [    0.516191] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 23 20:57:49 node-2 kernel: [    0.516198] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 23 20:57:49 node-2 kernel: [    0.516199] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 23 20:57:49 node-2 kernel: [    0.516199] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 23 20:57:49 node-2 kernel: [    0.516200] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 23 20:57:49 node-2 kernel: [    0.516201] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 23 20:57:49 node-2 kernel: [    0.516202] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 23 20:57:49 node-2 kernel: [    0.516203] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 23 20:57:49 node-2 kernel: [    0.516204] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 23 20:57:49 node-2 kernel: [    0.516205] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516206] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516207] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516207] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516208] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516209] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516210] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516211] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516212] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 23 20:57:49 node-2 kernel: [    0.516213] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516214] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 23 20:57:49 node-2 kernel: [    0.516215] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 23 20:57:49 node-2 kernel: [    0.516216] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 23 20:57:49 node-2 kernel: [    0.516217] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 23 20:57:49 node-2 kernel: [    0.516219] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 23 20:57:49 node-2 kernel: [    0.516220] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 23 20:57:49 node-2 kernel: [    0.516257] NET: Registered protocol family 2
Jul 23 20:57:49 node-2 kernel: [    0.516518] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.516860] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.517005] TCP: Hash tables configured (established 262144 bind 65536)
Jul 23 20:57:49 node-2 kernel: [    0.517043] TCP: reno registered
Jul 23 20:57:49 node-2 kernel: [    0.517071] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.517165] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.517309] NET: Registered protocol family 1
Jul 23 20:57:49 node-2 kernel: [    0.552720] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 23 20:57:49 node-2 kernel: [    0.552742] PCI: CLS 64 bytes, default 64
Jul 23 20:57:49 node-2 kernel: [    0.552784] Trying to unpack rootfs image as initramfs...
Jul 23 20:57:49 node-2 kernel: [    0.771754] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 23 20:57:49 node-2 kernel: [    0.771789] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 23 20:57:49 node-2 kernel: [    0.771791] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 23 20:57:49 node-2 kernel: [    0.772201] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772207] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772212] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772217] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772226] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772237] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772246] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772255] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772263] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772271] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772277] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772284] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772290] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772298] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772305] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772312] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 20:57:49 node-2 kernel: [    0.772404] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 23 20:57:49 node-2 kernel: [    0.772407] Scanning for low memory corruption every 60 seconds
Jul 23 20:57:49 node-2 kernel: [    0.772820] Initialise system trusted keyring
Jul 23 20:57:49 node-2 kernel: [    0.772872] audit: initializing netlink socket (disabled)
Jul 23 20:57:49 node-2 kernel: [    0.772887] type=2000 audit(1469307429.728:1): initialized
Jul 23 20:57:49 node-2 kernel: [    0.790782] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 23 20:57:49 node-2 kernel: [    0.792272] zbud: loaded
Jul 23 20:57:49 node-2 kernel: [    0.792412] VFS: Disk quotas dquot_6.5.2
Jul 23 20:57:49 node-2 kernel: [    0.792450] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 23 20:57:49 node-2 kernel: [    0.792827] fuse init (API version 7.22)
Jul 23 20:57:49 node-2 kernel: [    0.792886] msgmni has been set to 32768
Jul 23 20:57:49 node-2 kernel: [    0.792940] Key type big_key registered
Jul 23 20:57:49 node-2 kernel: [    0.793501] Key type asymmetric registered
Jul 23 20:57:49 node-2 kernel: [    0.793503] Asymmetric key parser 'x509' registered
Jul 23 20:57:49 node-2 kernel: [    0.793525] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 23 20:57:49 node-2 kernel: [    0.793594] io scheduler noop registered
Jul 23 20:57:49 node-2 kernel: [    0.793596] io scheduler deadline registered (default)
Jul 23 20:57:49 node-2 kernel: [    0.793616] io scheduler cfq registered
Jul 23 20:57:49 node-2 kernel: [    0.794003] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    0.794139] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    0.794257] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    0.794369] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    0.794484] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    0.794589] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    0.794948] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 23 20:57:49 node-2 kernel: [    0.794974] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 23 20:57:49 node-2 kernel: [    0.794996] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 23 20:57:49 node-2 kernel: [    0.795009] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795011] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795013] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 23 20:57:49 node-2 kernel: [    0.795019] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795020] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795021] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795023] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795024] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795026] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795027] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795029] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795030] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795031] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795033] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795034] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795037] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 23 20:57:49 node-2 kernel: [    0.795042] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795044] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 23 20:57:49 node-2 kernel: [    0.795056] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795059] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 23 20:57:49 node-2 kernel: [    0.795070] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795071] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 23 20:57:49 node-2 kernel: [    0.795074] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 23 20:57:49 node-2 kernel: [    0.795104] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 23 20:57:49 node-2 kernel: [    0.795109] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 23 20:57:49 node-2 kernel: [    0.795114] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 23 20:57:49 node-2 kernel: [    0.795130] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 23 20:57:49 node-2 kernel: [    0.795170] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 23 20:57:49 node-2 kernel: [    0.795172] vesafb: scrolling: redraw
Jul 23 20:57:49 node-2 kernel: [    0.795173] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 23 20:57:49 node-2 kernel: [    0.815759] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 23 20:57:49 node-2 kernel: [    0.824266] Console: switching to colour frame buffer device 80x30
Jul 23 20:57:49 node-2 kernel: [    0.833034] fb0: VESA VGA frame buffer device
Jul 23 20:57:49 node-2 kernel: [    0.833246] intel_idle: MWAIT substates: 0x2120
Jul 23 20:57:49 node-2 kernel: [    0.833247] intel_idle: v0.4 model 0x3F
Jul 23 20:57:49 node-2 kernel: [    0.833248] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 23 20:57:49 node-2 kernel: [    0.833477] ipmi message handler version 39.2
Jul 23 20:57:49 node-2 kernel: [    0.833752] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 23 20:57:49 node-2 kernel: [    0.834186] ACPI: AC Adapter [P111] (on-line)
Jul 23 20:57:49 node-2 kernel: [    0.839424] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 23 20:57:49 node-2 kernel: [    0.850477] ACPI: Power Button [PWRB]
Jul 23 20:57:49 node-2 kernel: [    0.856257] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 23 20:57:49 node-2 kernel: [    0.867941] ACPI: Power Button [PWRF]
Jul 23 20:57:49 node-2 kernel: [    0.894163] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 23 20:57:49 node-2 kernel: [    0.905895] pstore: Registered erst as persistent store backend
Jul 23 20:57:49 node-2 kernel: [    0.912149] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 23 20:57:49 node-2 kernel: [    0.924134] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 23 20:57:49 node-2 kernel: [    0.950901] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 23 20:57:49 node-2 kernel: [    0.984324] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 23 20:57:49 node-2 kernel: [    0.998429] Linux agpgart interface v0.103
Jul 23 20:57:49 node-2 kernel: [    1.006059] brd: module loaded
Jul 23 20:57:49 node-2 kernel: [    1.013082] loop: module loaded
Jul 23 20:57:49 node-2 kernel: [    1.019785] libphy: Fixed MDIO Bus: probed
Jul 23 20:57:49 node-2 kernel: [    1.026242] tun: Universal TUN/TAP device driver, 1.6
Jul 23 20:57:49 node-2 kernel: [    1.032703] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 23 20:57:49 node-2 kernel: [    1.039223] PPP generic driver version 2.4.2
Jul 23 20:57:49 node-2 kernel: [    1.045603] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 23 20:57:49 node-2 kernel: [    1.052045] ehci-pci: EHCI PCI platform driver
Jul 23 20:57:49 node-2 kernel: [    1.058558] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 23 20:57:49 node-2 kernel: [    1.064947] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 23 20:57:49 node-2 kernel: [    1.077438] ehci-pci 0000:00:1a.0: debug port 2
Jul 23 20:57:49 node-2 kernel: [    1.087622] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 23 20:57:49 node-2 kernel: [    1.087641] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 23 20:57:49 node-2 kernel: [    1.104117] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 23 20:57:49 node-2 kernel: [    1.110170] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 23 20:57:49 node-2 kernel: [    1.116326] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 23 20:57:49 node-2 kernel: [    1.128212] usb usb1: Product: EHCI Host Controller
Jul 23 20:57:49 node-2 kernel: [    1.134221] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 23 20:57:49 node-2 kernel: [    1.140253] usb usb1: SerialNumber: 0000:00:1a.0
Jul 23 20:57:49 node-2 kernel: [    1.146284] hub 1-0:1.0: USB hub found
Jul 23 20:57:49 node-2 kernel: [    1.152058] hub 1-0:1.0: 2 ports detected
Jul 23 20:57:49 node-2 kernel: [    1.157830] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 23 20:57:49 node-2 kernel: [    1.163398] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 23 20:57:49 node-2 kernel: [    1.174294] ehci-pci 0000:00:1d.0: debug port 2
Jul 23 20:57:49 node-2 kernel: [    1.183606] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 23 20:57:49 node-2 kernel: [    1.183615] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 23 20:57:49 node-2 kernel: [    1.200035] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 23 20:57:49 node-2 kernel: [    1.205233] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 23 20:57:49 node-2 kernel: [    1.210523] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 23 20:57:49 node-2 kernel: [    1.221070] usb usb2: Product: EHCI Host Controller
Jul 23 20:57:49 node-2 kernel: [    1.226538] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 23 20:57:49 node-2 kernel: [    1.232070] usb usb2: SerialNumber: 0000:00:1d.0
Jul 23 20:57:49 node-2 kernel: [    1.237587] hub 2-0:1.0: USB hub found
Jul 23 20:57:49 node-2 kernel: [    1.242925] hub 2-0:1.0: 2 ports detected
Jul 23 20:57:49 node-2 kernel: [    1.248218] ehci-platform: EHCI generic platform driver
Jul 23 20:57:49 node-2 kernel: [    1.253440] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 23 20:57:49 node-2 kernel: [    1.258747] ohci-pci: OHCI PCI platform driver
Jul 23 20:57:49 node-2 kernel: [    1.264033] ohci-platform: OHCI generic platform driver
Jul 23 20:57:49 node-2 kernel: [    1.269234] uhci_hcd: USB Universal Host Controller Interface driver
Jul 23 20:57:49 node-2 kernel: [    1.274568] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 23 20:57:49 node-2 kernel: [    1.467814] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 23 20:57:49 node-2 kernel: [    1.628041] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 23 20:57:49 node-2 kernel: [    1.633648] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 23 20:57:49 node-2 kernel: [    1.639433] hub 1-1:1.0: USB hub found
Jul 23 20:57:49 node-2 kernel: [    1.644902] hub 1-1:1.0: 6 ports detected
Jul 23 20:57:49 node-2 kernel: [    1.759559] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 23 20:57:49 node-2 kernel: [    1.767652] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 23 20:57:49 node-2 kernel: [    2.027702] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 23 20:57:49 node-2 kernel: [    2.033237] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 23 20:57:49 node-2 kernel: [    2.039091] hub 2-1:1.0: USB hub found
Jul 23 20:57:49 node-2 kernel: [    2.044688] hub 2-1:1.0: 8 ports detected
Jul 23 20:57:49 node-2 kernel: [    2.316239] i8042: No controller found
Jul 23 20:57:49 node-2 kernel: [    2.321662] mousedev: PS/2 mouse device common for all mice
Jul 23 20:57:49 node-2 kernel: [    2.323171] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 23 20:57:49 node-2 kernel: [    2.332767] rtc_cmos 00:02: RTC can wake from S4
Jul 23 20:57:49 node-2 kernel: [    2.338524] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 23 20:57:49 node-2 kernel: [    2.344192] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 23 20:57:49 node-2 kernel: [    2.355438] device-mapper: uevent: version 1.0.3
Jul 23 20:57:49 node-2 kernel: [    2.361082] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 23 20:57:49 node-2 kernel: [    2.372335] ledtrig-cpu: registered to indicate activity on CPUs
Jul 23 20:57:49 node-2 kernel: [    2.378275] TCP: cubic registered
Jul 23 20:57:49 node-2 kernel: [    2.384184] NET: Registered protocol family 10
Jul 23 20:57:49 node-2 kernel: [    2.390176] NET: Registered protocol family 17
Jul 23 20:57:49 node-2 kernel: [    2.395865] Key type dns_resolver registered
Jul 23 20:57:49 node-2 kernel: [    2.401824] Loading compiled-in X.509 certificates
Jul 23 20:57:49 node-2 kernel: [    2.407988] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 23 20:57:49 node-2 kernel: [    2.419380] registered taskstats version 1
Jul 23 20:57:49 node-2 kernel: [    2.427323] Key type trusted registered
Jul 23 20:57:49 node-2 kernel: [    2.434869] Key type encrypted registered
Jul 23 20:57:49 node-2 kernel: [    2.440323] AppArmor: AppArmor sha1 policy hashing enabled
Jul 23 20:57:49 node-2 kernel: [    2.445826] IMA: No TPM chip found, activating TPM-bypass!
Jul 23 20:57:49 node-2 kernel: [    2.451939] regulator-dummy: disabling
Jul 23 20:57:49 node-2 kernel: [    2.455785] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 23 20:57:49 node-2 kernel: [    2.455786] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 23 20:57:49 node-2 kernel: [    2.455787] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 23 20:57:49 node-2 kernel: [    2.455787] usb 2-1.4: Manufacturer: Avocent
Jul 23 20:57:49 node-2 kernel: [    2.455788] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 23 20:57:49 node-2 kernel: [    2.491056]   Magic number: 8:300:1004
Jul 23 20:57:49 node-2 kernel: [    2.496634] input input1: hash matches
Jul 23 20:57:49 node-2 kernel: [    2.502095] system 00:06: hash matches
Jul 23 20:57:49 node-2 kernel: [    2.507595] memory memory43: hash matches
Jul 23 20:57:49 node-2 kernel: [    2.512943] rtc_cmos 00:02: setting system clock to 2016-07-23 20:57:11 UTC (1469307431)
Jul 23 20:57:49 node-2 kernel: [    2.525007] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 23 20:57:49 node-2 kernel: [    2.530468] EDD information not available.
Jul 23 20:57:49 node-2 kernel: [    2.535892] PM: Hibernation image not present or could not be loaded.
Jul 23 20:57:49 node-2 kernel: [    2.536738] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 23 20:57:49 node-2 kernel: [    2.547460] Write protecting the kernel read-only data: 12288k
Jul 23 20:57:49 node-2 kernel: [    2.553400] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 23 20:57:49 node-2 kernel: [    2.565721] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 23 20:57:49 node-2 kernel: [    2.597646] device-mapper: multipath: version 1.6.0 loaded
Jul 23 20:57:49 node-2 kernel: [    2.605535] systemd-udevd[215]: starting version 204
Jul 23 20:57:49 node-2 kernel: [    2.629986] md: linear personality registered for level -1
Jul 23 20:57:49 node-2 kernel: [    2.644585] md: multipath personality registered for level -4
Jul 23 20:57:49 node-2 kernel: [    2.652502] md: raid0 personality registered for level 0
Jul 23 20:57:49 node-2 kernel: [    2.661032] md: raid1 personality registered for level 1
Jul 23 20:57:49 node-2 kernel: [    2.667258] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 23 20:57:49 node-2 kernel: [    2.673415] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 23 20:57:49 node-2 kernel: [    2.673620] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 23 20:57:49 node-2 kernel: [    2.675204] megasas: FW now in Ready state
Jul 23 20:57:49 node-2 kernel: [    2.675516] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.675587] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.675707] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.675824] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.675934] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.676038] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.676164] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.676287] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.676402] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.676659] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.676788] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.676916] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.677089] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.677202] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.677417] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.677555] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.678171] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 23 20:57:49 node-2 kernel: [    2.704415] hidraw: raw HID events driver (C) Jiri Kosina
Jul 23 20:57:49 node-2 kernel: [    2.712002] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 23 20:57:49 node-2 kernel: [    2.716249] usbcore: registered new interface driver usbhid
Jul 23 20:57:49 node-2 kernel: [    2.716249] usbhid: USB HID core driver
Jul 23 20:57:49 node-2 kernel: [    2.738424] 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
Jul 23 20:57:49 node-2 kernel: [    2.751830] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 20:57:49 node-2 kernel: [    2.758673] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.758677] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.758681] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.758684] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.758729] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 20:57:49 node-2 kernel: [    2.770956] raid6: sse2x1   10413 MB/s
Jul 23 20:57:49 node-2 kernel: [    2.838651] raid6: sse2x2    9725 MB/s
Jul 23 20:57:49 node-2 kernel: [    2.910601] raid6: sse2x4   10137 MB/s
Jul 23 20:57:49 node-2 kernel: [    2.982537] raid6: avx2x1   14949 MB/s
Jul 23 20:57:49 node-2 kernel: [    3.054476] raid6: avx2x2   18903 MB/s
Jul 23 20:57:49 node-2 kernel: [    3.126406] raid6: avx2x4   21398 MB/s
Jul 23 20:57:49 node-2 kernel: [    3.131924] raid6: using algorithm avx2x4 (21398 MB/s)
Jul 23 20:57:49 node-2 kernel: [    3.137436] raid6: using avx2x2 recovery algorithm
Jul 23 20:57:49 node-2 kernel: [    3.142879] megasas:IOC Init cmd success
Jul 23 20:57:49 node-2 kernel: [    3.142880] Switched to clocksource tsc
Jul 23 20:57:49 node-2 kernel: [    3.153636] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 23 20:57:49 node-2 kernel: [    3.164058] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 23 20:57:49 node-2 kernel: [    3.174770] megasas: INIT adapter done
Jul 23 20:57:49 node-2 kernel: [    3.180801] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 20:57:49 node-2 kernel: [    3.186520] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.186524] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.186529] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.186530] xor: automatically using best checksumming function:
Jul 23 20:57:49 node-2 kernel: [    3.192282] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.192345] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.214764] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 23 20:57:49 node-2 kernel: [    3.225988] 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
Jul 23 20:57:49 node-2 kernel: [    3.226308]    avx       : 38067.000 MB/sec
Jul 23 20:57:49 node-2 kernel: [    3.243140] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 20:57:49 node-2 kernel: [    3.246523] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 23 20:57:49 node-2 kernel: [    3.247886] scsi0 : LSI SAS based MegaRAID driver
Jul 23 20:57:49 node-2 kernel: [    3.256451] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 23 20:57:49 node-2 kernel: [    3.271713] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.271722] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.271728] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.271733] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.271775] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.271819] 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
Jul 23 20:57:49 node-2 kernel: [    3.271874] 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
Jul 23 20:57:49 node-2 kernel: [    3.271932] 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
Jul 23 20:57:49 node-2 kernel: [    3.271986] 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
Jul 23 20:57:49 node-2 kernel: [    3.272114] 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
Jul 23 20:57:49 node-2 kernel: [    3.272175] 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
Jul 23 20:57:49 node-2 kernel: [    3.370472] async_tx: api initialized (async)
Jul 23 20:57:49 node-2 kernel: [    3.371578] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 23 20:57:49 node-2 kernel: [    3.377888] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 23 20:57:49 node-2 kernel: [    3.378126] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 23 20:57:49 node-2 kernel: [    3.378343] sd 0:2:0:0: [sda] Write Protect is off
Jul 23 20:57:49 node-2 kernel: [    3.378344] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 23 20:57:49 node-2 kernel: [    3.378571] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 23 20:57:49 node-2 kernel: [    3.379513] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 23 20:57:49 node-2 kernel: [    3.379514] 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
Jul 23 20:57:49 node-2 kernel: [    3.379515] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 20:57:49 node-2 kernel: [    3.379579] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.379616] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.379653] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.379689] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.379775] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 20:57:49 node-2 kernel: [    3.405537]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 23 20:57:49 node-2 kernel: [    3.407437] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 23 20:57:49 node-2 kernel: [    3.510811] md: raid6 personality registered for level 6
Jul 23 20:57:49 node-2 kernel: [    3.518146] md: raid5 personality registered for level 5
Jul 23 20:57:49 node-2 kernel: [    3.525205] md: raid4 personality registered for level 4
Jul 23 20:57:49 node-2 kernel: [    3.535053] md: raid10 personality registered for level 10
Jul 23 20:57:49 node-2 kernel: [    3.589238] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Jul 23 20:57:49 node-2 kernel: [    3.649484] random: lvm urandom read with 31 bits of entropy available
Jul 23 20:57:49 node-2 kernel: [    3.745769] bio: create slab <bio-1> at 1
Jul 23 20:57:49 node-2 kernel: [    4.441528] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 23 20:57:49 node-2 kernel: [    4.994990] init: plymouth-upstart-bridge main process (546) terminated with status 1
Jul 23 20:57:49 node-2 kernel: [    5.007022] init: plymouth-upstart-bridge main process ended, respawning
Jul 23 20:57:49 node-2 kernel: [    5.158840] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 23 20:57:49 node-2 kernel: [    5.189706] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 23 20:57:49 node-2 kernel: [    5.282687] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 23 20:57:49 node-2 kernel: [    5.354550] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 23 20:57:49 node-2 kernel: [    5.448554] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 23 20:57:49 node-2 kernel: [    5.504466] random: nonblocking pool is initialized
Jul 23 20:57:49 node-2 kernel: [    5.668290] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 23 20:57:49 node-2 kernel: [    5.700812] XFS (dm-0): Mounting Filesystem
Jul 23 20:57:49 node-2 kernel: [    5.947971] XFS (dm-0): Ending clean mount
Jul 23 20:57:49 node-2 kernel: [    6.027371] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 23 20:57:49 node-2 kernel: [    6.068773] XFS (dm-1): Mounting Filesystem
Jul 23 20:57:49 node-2 kernel: [    6.180079] XFS (dm-1): Ending clean mount
Jul 23 20:57:49 node-2 kernel: [    7.924013] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 23 20:57:49 node-2 kernel: [    7.952284] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 23 20:57:49 node-2 kernel: [    8.088263] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 23 20:57:49 node-2 kernel: [    8.088281] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 23 20:57:49 node-2 kernel: [    8.088290] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 23 20:57:49 node-2 kernel: [    8.088298] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 23 20:57:49 node-2 kernel: [    8.148196] systemd-udevd[773]: starting version 204
Jul 23 20:57:49 node-2 kernel: [    8.324409] power_meter ACPI000D:00: Found ACPI power meter.
Jul 23 20:57:49 node-2 kernel: [    8.324419] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 23 20:57:49 node-2 kernel: [    8.331394] IPMI System Interface driver.
Jul 23 20:57:49 node-2 kernel: [    8.331437] ipmi_si: probing via ACPI
Jul 23 20:57:49 node-2 kernel: [    8.331454] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 23 20:57:49 node-2 kernel: [    8.331455] ipmi_si: Adding ACPI-specified kcs state machine
Jul 23 20:57:49 node-2 kernel: [    8.331463] ipmi_si: probing via SMBIOS
Jul 23 20:57:49 node-2 kernel: [    8.331463] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 23 20:57:49 node-2 kernel: [    8.331464] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 23 20:57:49 node-2 kernel: [    8.331466] ipmi_si: probing via SPMI
Jul 23 20:57:49 node-2 kernel: [    8.331466] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 23 20:57:49 node-2 kernel: [    8.331467] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 23 20:57:49 node-2 kernel: [    8.331468] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 23 20:57:49 node-2 kernel: [    8.385332] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 23 20:57:49 node-2 kernel: [    8.385338] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 23 20:57:49 node-2 kernel: [    8.385340] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 23 20:57:49 node-2 kernel: [    8.385342] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 23 20:57:49 node-2 kernel: [    8.385356] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 23 20:57:49 node-2 kernel: [    8.388280] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 23 20:57:49 node-2 kernel: [    8.393907] wmi: Mapper loaded
Jul 23 20:57:49 node-2 kernel: [    8.482333] systemd-udevd[792]: renamed network interface eth0 to enp6s0
Jul 23 20:57:49 node-2 kernel: [    8.486227] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 23 20:57:49 node-2 kernel: [    8.486233] ipmi_si 00:09: IPMI kcs interface initialized
Jul 23 20:57:49 node-2 kernel: [    8.502225] systemd-udevd[802]: renamed network interface eth1 to enp7s0
Jul 23 20:57:49 node-2 kernel: [    8.514236] systemd-udevd[796]: renamed network interface eth2 to enp8s0
Jul 23 20:57:49 node-2 kernel: [    8.548803] systemd-udevd[791]: renamed network interface eth3 to enp9s0
Jul 23 20:57:49 node-2 kernel: [    8.868049] type=1400 audit(1469307437.856:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1051 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.868200] type=1400 audit(1469307437.856:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1051 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.868329] type=1400 audit(1469307437.856:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1051 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.869589] type=1400 audit(1469307437.860:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.869746] type=1400 audit(1469307437.860:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.869830] type=1400 audit(1469307437.860:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.869866] type=1400 audit(1469307437.860:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.869967] type=1400 audit(1469307437.860:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1050 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.870085] type=1400 audit(1469307437.860:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1050 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    8.879725] type=1400 audit(1469307437.868:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Jul 23 20:57:49 node-2 kernel: [    9.389950] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 23 20:57:49 node-2 kernel: [    9.400129] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 23 20:57:49 node-2 kernel: [    9.582020] enic 0000:06:00.0 enp6s0: Link UP
Jul 23 20:57:49 node-2 kernel: [    9.582465] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 23 20:57:49 node-2 kernel: [    9.582474] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 23 20:57:49 node-2 kernel: [   18.485517] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 23 20:57:50 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 23 20:57:51 node-2 kernel: [   41.674110] init: failsafe main process (8397) killed by TERM signal
Jul 23 20:57:51 node-2 dbus[8441]: [system] AppArmor D-Bus mediation is enabled
Jul 23 20:57:51 node-2 kernel: [   41.855017] audit_printk_skb: 30 callbacks suppressed
Jul 23 20:57:51 node-2 kernel: [   41.855017] type=1400 audit(1469307471.232:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8522 comm="apparmor_parser"
Jul 23 20:57:51 node-2 kernel: [   41.855021] type=1400 audit(1469307471.232:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 23 20:57:51 node-2 kernel: [   41.855023] type=1400 audit(1469307471.232:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 23 20:57:51 node-2 kernel: [   41.855239] type=1400 audit(1469307471.232:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 23 20:57:51 node-2 kernel: [   41.855241] type=1400 audit(1469307471.232:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 23 20:57:51 node-2 kernel: [   41.855353] type=1400 audit(1469307471.232:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 23 20:57:51 node-2 kernel: [   41.856456] type=1400 audit(1469307471.232:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8523 comm="apparmor_parser"
Jul 23 20:57:51 node-2 kernel: [   41.960885] type=1400 audit(1469307471.340:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8525 comm="apparmor_parser"
Jul 23 20:57:51 node-2 cron[8555]: (CRON) INFO (pidfile fd = 3)
Jul 23 20:57:51 node-2 anacron[8591]: Anacron 2.3 started on 2016-07-23
Jul 23 20:57:51 node-2 cron[8592]: (CRON) STARTUP (fork ok)
Jul 23 20:57:51 node-2 anacron[8591]: Will run job `cron.daily' in 5 min.
Jul 23 20:57:51 node-2 anacron[8591]: Will run job `cron.weekly' in 10 min.
Jul 23 20:57:51 node-2 anacron[8591]: Will run job `cron.monthly' in 15 min.
Jul 23 20:57:51 node-2 anacron[8591]: Jobs will be executed sequentially
Jul 23 20:57:51 node-2 cron[8592]: (CRON) INFO (Running @reboot jobs)
Jul 23 20:57:51 node-2 multipathd: path checkers start up
Jul 23 20:57:52 node-2 postfix/master[8734]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 23 20:57:55 node-2 puppet-agent[8918]: Reopening log files
Jul 23 20:57:55 node-2 puppet-agent[8918]: Could not request certificate: Connection refused - connect(2)
Jul 23 20:58:01 node-2 CRON[8949]: (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")
Jul 23 20:58:06 node-2 puppet-user[9008]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 23 20:58:06 node-2 puppet-user[9008]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 23 20:58:07 node-2 puppet-user[9008]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 23 20:58:07 node-2 puppet-user[9008]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 23 20:58:07 node-2 puppet-user[9008]: Finished catalog run in 0.61 seconds
Jul 23 20:58:08 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 20:58:08 node-2 nailgun-agent: D, [2016-07-23T20:58:01.602044 #8952] DEBUG -- : Sleep for 7 seconds before sending request
Jul 23 20:58:08 node-2 nailgun-agent: I, [2016-07-23T20:58:08.635680 #8952]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 23 20:58:09 node-2 multipathd: uevent trigger error
Jul 23 20:58:09 node-2 puppet-user[9433]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 23 20:58:09 node-2 puppet-user[9433]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Jul 23 20:58:09 node-2 nailgun-agent: D, [2016-07-23T20:58:09.408038 #8952] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 23 20:58:09 node-2 puppet-user[9433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 23 20:58:09 node-2 puppet-user[9433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 23 20:58:09 node-2 puppet-user[9433]: (/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"]'
Jul 23 20:58:09 node-2 puppet-user[9433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 23 20:58:09 node-2 puppet-user[9433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 23 20:58:09 node-2 puppet-user[9433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 23 20:58:09 node-2 puppet-user[9433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 23 20:58:09 node-2 puppet-user[9433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 23 20:58:09 node-2 puppet-user[9433]: Finished catalog run in 0.05 seconds
Jul 23 20:58:10 node-2 puppet-user[10020]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 23 20:58:10 node-2 puppet-user[10020]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 23 20:58:10 node-2 puppet-user[10020]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 23 20:58:10 node-2 puppet-user[10020]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 23 20:58:10 node-2 puppet-user[10020]: Finished catalog run in 0.03 seconds
Jul 23 20:58:12 node-2 puppet-user[10607]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 23 20:58:12 node-2 puppet-user[10607]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 23 20:58:12 node-2 puppet-user[10607]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 23 20:58:12 node-2 puppet-user[10607]: Finished catalog run in 0.04 seconds
Jul 23 20:58:14 node-2 puppet-user[11067]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 23 20:58:15 node-2 puppet-user[11067]: Compiled catalog for node-2.domain.tld in environment production in 0.36 seconds
Jul 23 20:58:15 node-2 puppet-user[11067]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 23 20:58:15 node-2 kernel: [   66.019202] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 23 20:58:15 node-2 kernel: [   66.019254] 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.
Jul 23 20:58:15 node-2 puppet-user[11067]: (/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'
Jul 23 20:58:15 node-2 puppet-user[11067]: Finished catalog run in 0.05 seconds
Jul 23 20:58:16 node-2 puppet-user[11528]: (Scope(Class[main])) MODULAR: sync_time
Jul 23 20:58:17 node-2 puppet-user[11528]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 23 20:58:17 node-2 ntpdate[11948]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.546706 #8952] DEBUG -- : Trying to find block devices
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.546809 #8952] DEBUG -- : Found block device: sda
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.546849 #8952] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.546873 #8952] DEBUG -- : Trying to get list of physical devices
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.547054 #8952] DEBUG -- : Getting udev properties for device: sda
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.548771 #8952] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Jul 23 20:58:21 node-2 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65471", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.548799 #8952] DEBUG -- : Trying to find out if device sda is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.548885 #8952] DEBUG -- : Device sda removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.548903 #8952] DEBUG -- : Device sda seems to be appropriate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.549340 #8952] DEBUG -- : Getting udev properties for device: dm-0
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.551012 #8952] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-8TYLUuxZhJJ9zDiiPFkQ30gL3OWl8BewCu4aSJpIvVRK4qzqusqv960WZl9uhR9R /dev/disk/by-uuid/10206109-ba2f-424c-a44d-686171708197 /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-8TYLUuxZhJJ9zDiiPFkQ30gL3OWl8BewCu4aSJpIvVRK4qzqusqv960WZl9uhR9R", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"10206109-ba2f-424c-a44d-686171708197", "ID_FS_UUID_ENC"=>"10206109-ba2f-424c-a44d-686171708197", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3812", "nomdmonddf"=>"1", "nomdm
Jul 23 20:58:21 node-2 nailgun-agent: onisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.551052 #8952] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.551084 #8952] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.551098 #8952] DEBUG -- : Device dm-0 seems to be appropriate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.551128 #8952] DEBUG -- : Getting udev properties for device: dm-1
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.552717 #8952] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-tHzanP3Vh6X21G19jeTJYeVwsqWvkdWjC3C8Ro5GYX8mUS2KJGsop01lxs4hsae7 /dev/disk/by-uuid/082cd384-1ba5-4759-ad75-df5da6c80d57 /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-tHzanP3Vh6X21G19jeTJYeVwsqWvkdWjC3C8Ro5GYX8mUS2KJGsop01lxs4hsae7", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"082cd384-1ba5-4759-ad75-df5da6c80d57", "ID_FS_UUID_ENC"=>"082cd384-1ba5-4759-ad75-df5da6c80d57", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52
Jul 23 20:58:21 node-2 nailgun-agent: 083", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.552746 #8952] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.552816 #8952] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.552830 #8952] DEBUG -- : Device dm-1 seems to be appropriate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.552845 #8952] DEBUG -- : Getting udev properties for device: dm-2
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.554392 #8952] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-MY7FeJKYsiPqMTNeEcJJ1JWqDqInxmOhGd8lZ0IORgLMrDTqoOap8IWfz5Iw7xLk /dev/disk/by-uuid/76987255-99a5-465b-81e4-45c01657c0e7 /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-MY7FeJKYsiPqMTNeEcJJ1JWqDqInxmOhGd8lZ0IORgLMrDTqoOap8IWfz5Iw7xLk", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"76987255-99a5-465b-81e4-45c01657c0e7", "ID_FS_UUID_ENC"=>"76987255-99a5-465b-81e4-45c01657c0e7", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59303", "nomdmond
Jul 23 20:58:21 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.554451 #8952] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.554484 #8952] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.554498 #8952] DEBUG -- : Device dm-2 seems to be appropriate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.554513 #8952] DEBUG -- : Getting udev properties for device: dm-3
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.556110 #8952] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Zt5fYnxAFzhaQBt3i08hwigHhXJT5f159gHSI1hF6egw2QTyStyvkj7sG4YCVw7g /dev/disk/by-uuid/ba8d96fd-8b58-44ce-ba8e-aef1c432892b /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-Zt5fYnxAFzhaQBt3i08hwigHhXJT5f159gHSI1hF6egw2QTyStyvkj7sG4YCVw7g", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ba8d96fd-8b58-44ce-ba8e-aef1c432892b", "ID_FS_UUID_ENC"=>"ba8d96fd-8b58-44ce-ba8e-aef1c432892b", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71169", "nomdmonddf"=>"1", 
Jul 23 20:58:21 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.556149 #8952] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.556181 #8952] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.556195 #8952] DEBUG -- : Device dm-3 seems to be appropriate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.556209 #8952] DEBUG -- : Getting udev properties for device: dm-4
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.557750 #8952] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-VPjMPArUZL3wAf7LctuOVbUQdMA3Oqce4uIvsh4dr1bzoeLDMM4AkTrlhkPVOvyU /dev/disk/by-uuid/54f94713-5f25-4270-9e18-e1ed37a23278 /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-VPjMPArUZL3wAf7LctuOVbUQdMA3Oqce4uIvsh4dr1bzoeLDMM4AkTrlhkPVOvyU", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"54f94713-5f25-4270-9e18-e1ed37a23278", "ID_FS_UUID_ENC"=>"54f94713-5f25-4270-9e18-e1ed37a23278", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79621", "nomdmonddf"=>"1", "nomd
Jul 23 20:58:21 node-2 nailgun-agent: monisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.557820 #8952] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.557853 #8952] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.557868 #8952] DEBUG -- : Device dm-4 seems to be appropriate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.557883 #8952] DEBUG -- : Getting udev properties for device: dm-5
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.559456 #8952] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-VPjMPArUZL3wAf7LctuOVbUQdMA3OqcewNQRmJq40ToqHcIVZFbTdjdQkOquS1M7 /dev/disk/by-uuid/ef8391d8-3a57-4263-9241-d08556d90d33 /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-VPjMPArUZL3wAf7LctuOVbUQdMA3OqcewNQRmJq40ToqHcIVZFbTdjdQkOquS1M7", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"ef8391d8-3a57-4263-9241-d08556d90d33", "ID_FS_UUID_ENC"=>"ef8391d8-3a57-4263-9241-d08556d90d33", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80023", "nomdmonddf"=>"1", "nomdmonisw"
Jul 23 20:58:21 node-2 nailgun-agent: =>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.559495 #8952] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.559532 #8952] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.559558 #8952] DEBUG -- : Device dm-5 seems to be appropriate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.559573 #8952] DEBUG -- : Getting udev properties for device: ram0
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.561012 #8952] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65131", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.561041 #8952] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.561100 #8952] DEBUG -- : Device ram0 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.561121 #8952] DEBUG -- : Getting udev properties for device: ram1
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.562559 #8952] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65144", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.562584 #8952] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.562621 #8952] DEBUG -- : Device ram1 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.562654 #8952] DEBUG -- : Getting udev properties for device: ram2
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.564020 #8952] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65336", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.564047 #8952] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.564109 #8952] DEBUG -- : Device ram2 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.564129 #8952] DEBUG -- : Getting udev properties for device: ram3
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.565501 #8952] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65351", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.565548 #8952] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.565591 #8952] DEBUG -- : Device ram3 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.565612 #8952] DEBUG -- : Getting udev properties for device: ram4
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.566975 #8952] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65367", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.567001 #8952] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.567035 #8952] DEBUG -- : Device ram4 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.567055 #8952] DEBUG -- : Getting udev properties for device: ram5
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.568447 #8952] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65382", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.568497 #8952] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.568535 #8952] DEBUG -- : Device ram5 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.568555 #8952] DEBUG -- : Getting udev properties for device: ram6
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.569915 #8952] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65494", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.569941 #8952] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.569988 #8952] DEBUG -- : Device ram6 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.570009 #8952] DEBUG -- : Getting udev properties for device: ram7
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.571387 #8952] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65513", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.571413 #8952] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.571449 #8952] DEBUG -- : Device ram7 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.571470 #8952] DEBUG -- : Getting udev properties for device: ram8
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.572863 #8952] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65528", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.572891 #8952] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.572933 #8952] DEBUG -- : Device ram8 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.572954 #8952] DEBUG -- : Getting udev properties for device: ram9
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.574318 #8952] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65671", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.574344 #8952] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.574380 #8952] DEBUG -- : Device ram9 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.574417 #8952] DEBUG -- : Getting udev properties for device: loop0
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.575818 #8952] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65028", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.575844 #8952] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.575887 #8952] DEBUG -- : Device loop0 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.575907 #8952] DEBUG -- : Getting udev properties for device: loop1
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.577273 #8952] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65045", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.577313 #8952] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.577347 #8952] DEBUG -- : Device loop1 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.577367 #8952] DEBUG -- : Getting udev properties for device: loop2
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.578713 #8952] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65057", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.578739 #8952] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.578774 #8952] DEBUG -- : Device loop2 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.578804 #8952] DEBUG -- : Getting udev properties for device: loop3
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.580214 #8952] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65071", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.580241 #8952] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.580313 #8952] DEBUG -- : Device loop3 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.580333 #8952] DEBUG -- : Getting udev properties for device: loop4
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.581749 #8952] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65081", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.581793 #8952] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.581829 #8952] DEBUG -- : Device loop4 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.581861 #8952] DEBUG -- : Getting udev properties for device: loop5
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.583253 #8952] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65093", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.583299 #8952] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.583337 #8952] DEBUG -- : Device loop5 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.583356 #8952] DEBUG -- : Getting udev properties for device: loop6
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.584751 #8952] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65107", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.584777 #8952] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.584821 #8952] DEBUG -- : Device loop6 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.584856 #8952] DEBUG -- : Getting udev properties for device: loop7
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.586212 #8952] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65119", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.586249 #8952] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.586282 #8952] DEBUG -- : Device loop7 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.586321 #8952] DEBUG -- : Getting udev properties for device: ram10
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.587701 #8952] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65156", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.594874 #8952] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.594940 #8952] DEBUG -- : Device ram10 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.594962 #8952] DEBUG -- : Getting udev properties for device: ram11
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.596622 #8952] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65168", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.596650 #8952] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.596681 #8952] DEBUG -- : Device ram11 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.596745 #8952] DEBUG -- : Getting udev properties for device: ram12
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.598146 #8952] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65179", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.598172 #8952] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.598205 #8952] DEBUG -- : Device ram12 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.598226 #8952] DEBUG -- : Getting udev properties for device: ram13
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.599667 #8952] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65191", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.599694 #8952] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.599725 #8952] DEBUG -- : Device ram13 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.599744 #8952] DEBUG -- : Getting udev properties for device: ram14
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.601121 #8952] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65312", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.601147 #8952] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.601182 #8952] DEBUG -- : Device ram14 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.601202 #8952] DEBUG -- : Getting udev properties for device: ram15
Jul 23 20:58:21 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602591 #8952] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65325", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602617 #8952] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602653 #8952] DEBUG -- : Device ram15 removable parameter: "0"
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602691 #8952] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602706 #8952] DEBUG -- : Block device seems to be physical data storage: sda
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602759 #8952] DEBUG -- : Found block device: dm-0
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602774 #8952] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602789 #8952] DEBUG -- : Found block device: dm-1
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602837 #8952] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602847 #8952] DEBUG -- : Found block device: dm-2
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602858 #8952] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602867 #8952] DEBUG -- : Found block device: dm-3
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602879 #8952] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602888 #8952] DEBUG -- : Found block device: dm-4
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602900 #8952] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602908 #8952] DEBUG -- : Found block device: dm-5
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602918 #8952] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602928 #8952] DEBUG -- : Found block device: ram0
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602972 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602982 #8952] DEBUG -- : Found block device: ram1
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.602992 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603001 #8952] DEBUG -- : Found block device: ram2
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603012 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603021 #8952] DEBUG -- : Found block device: ram3
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603032 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603040 #8952] DEBUG -- : Found block device: ram4
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603051 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603060 #8952] DEBUG -- : Found block device: ram5
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603072 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603124 #8952] DEBUG -- : Found block device: ram6
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603135 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603144 #8952] DEBUG -- : Found block device: ram7
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603162 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603172 #8952] DEBUG -- : Found block device: ram8
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603182 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603190 #8952] DEBUG -- : Found block device: ram9
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603200 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603208 #8952] DEBUG -- : Found block device: loop0
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603217 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603283 #8952] DEBUG -- : Found block device: loop1
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603293 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603303 #8952] DEBUG -- : Found block device: loop2
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603313 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603321 #8952] DEBUG -- : Found block device: loop3
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603332 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603341 #8952] DEBUG -- : Found block device: loop4
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603353 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603362 #8952] DEBUG -- : Found block device: loop5
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603429 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603439 #8952] DEBUG -- : Found block device: loop6
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603449 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603457 #8952] DEBUG -- : Found block device: loop7
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603467 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603475 #8952] DEBUG -- : Found block device: ram10
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603485 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603494 #8952] DEBUG -- : Found block device: ram11
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603504 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603562 #8952] DEBUG -- : Found block device: ram12
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603574 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603583 #8952] DEBUG -- : Found block device: ram13
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603594 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603603 #8952] DEBUG -- : Found block device: ram14
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603614 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603623 #8952] DEBUG -- : Found block device: ram15
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603634 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.603667 #8952] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.661559 #8952] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 23 20:58:21 node-2 nailgun-agent: D, [2016-07-23T20:58:21.661601 #8952] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 23 20:58:23 node-2 ntpdate[11948]: adjust time server 10.20.0.2 offset 0.000521 sec
Jul 23 20:58:23 node-2 puppet-user[11528]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 23 20:58:23 node-2 puppet-user[11528]: Finished catalog run in 6.19 seconds
Jul 23 20:58:29 node-2 puppet-user[12495]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 23 20:58:29 node-2 puppet-user[12495]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Jul 23 20:58:29 node-2 puppet-user[12495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 23 20:58:29 node-2 puppet-user[12495]: Finished catalog run in 0.09 seconds
Jul 23 20:58:31 node-2 puppet-user[12947]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 23 20:58:32 node-2 puppet-user[12947]: Compiled catalog for node-2.domain.tld in environment production in 1.35 seconds
Jul 23 20:58:32 node-2 puppet-user[12947]: (/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
Jul 23 20:58:32 node-2 puppet-user[12947]: (/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
Jul 23 20:58:32 node-2 puppet-user[12947]: (/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
Jul 23 20:58:32 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 23 20:58:32 node-2 puppet-user[12947]: (/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
Jul 23 20:58:32 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 23 20:58:32 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 23 20:58:32 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 23 20:58:32 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 23 20:58:33 node-2 puppet-user[12947]: (/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
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 23 20:58:33 node-2 puppet-user[12947]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 23 20:58:33 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887443 #8952] DEBUG -- : Trying to find block devices
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887512 #8952] DEBUG -- : Found block device: sda
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887540 #8952] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887558 #8952] DEBUG -- : Block device seems to be physical data storage: sda
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887581 #8952] DEBUG -- : Found block device: dm-0
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887594 #8952] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887606 #8952] DEBUG -- : Found block device: dm-1
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887633 #8952] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887642 #8952] DEBUG -- : Found block device: dm-2
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887652 #8952] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887662 #8952] DEBUG -- : Found block device: dm-3
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887672 #8952] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887682 #8952] DEBUG -- : Found block device: dm-4
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887693 #8952] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887713 #8952] DEBUG -- : Found block device: dm-5
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887746 #8952] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887755 #8952] DEBUG -- : Found block device: ram0
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887767 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887776 #8952] DEBUG -- : Found block device: ram1
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887786 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887795 #8952] DEBUG -- : Found block device: ram2
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887805 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887814 #8952] DEBUG -- : Found block device: ram3
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887824 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887833 #8952] DEBUG -- : Found block device: ram4
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887861 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887870 #8952] DEBUG -- : Found block device: ram5
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887880 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887889 #8952] DEBUG -- : Found block device: ram6
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887899 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887907 #8952] DEBUG -- : Found block device: ram7
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887916 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887925 #8952] DEBUG -- : Found block device: ram8
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887935 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887943 #8952] DEBUG -- : Found block device: ram9
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887966 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887975 #8952] DEBUG -- : Found block device: loop0
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887985 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.887994 #8952] DEBUG -- : Found block device: loop1
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888003 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888012 #8952] DEBUG -- : Found block device: loop2
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888021 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888038 #8952] DEBUG -- : Found block device: loop3
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888048 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888057 #8952] DEBUG -- : Found block device: loop4
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888076 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888085 #8952] DEBUG -- : Found block device: loop5
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888094 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888104 #8952] DEBUG -- : Found block device: loop6
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888126 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888135 #8952] DEBUG -- : Found block device: loop7
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888144 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888152 #8952] DEBUG -- : Found block device: ram10
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888178 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888188 #8952] DEBUG -- : Found block device: ram11
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888197 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888206 #8952] DEBUG -- : Found block device: ram12
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888228 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888237 #8952] DEBUG -- : Found block device: ram13
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888247 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888255 #8952] DEBUG -- : Found block device: ram14
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888280 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888290 #8952] DEBUG -- : Found block device: ram15
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888299 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:33.888346 #8952] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 23 20:58:34 node-2 nailgun-agent: D, [2016-07-23T20:58:34.076898 #8952] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 23 20:58:34 node-2 nailgun-agent: I, [2016-07-23T20:58:34.077050 #8952]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 23 20:58:35 node-2 kernel: [   86.274963] init: plymouth-upstart-bridge main process ended, respawning
Jul 23 20:58:35 node-2 puppet-agent[8918]: Could not run: SIGTERM
Jul 23 20:58:35 node-2 kernel: [   86.527108] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 23 20:58:35 node-2 ec2: 
Jul 23 20:58:35 node-2 ec2: #############################################################
Jul 23 20:58:35 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 23 20:58:35 node-2 ec2: 1024 77:e5:ab:49:31:bc:80:43:e9:a2:4d:e2:66:96:b4:a4  root@node-2.domain.tld (DSA)
Jul 23 20:58:35 node-2 ec2: 256 6a:44:ac:89:1a:d8:0d:52:d9:d7:96:0c:fd:2b:e0:59  root@node-2.domain.tld (ECDSA)
Jul 23 20:58:35 node-2 ec2: 256 bf:83:83:71:49:5f:16:7c:2f:55:cf:0a:88:9a:b8:ae  root@node-2.domain.tld (ED25519)
Jul 23 20:58:35 node-2 ec2: 2048 a8:f1:2b:ea:51:9d:91:2b:c0:40:cc:d8:fd:c3:6d:8c  root@node-2.domain.tld (RSA)
Jul 23 20:58:35 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 23 20:58:35 node-2 ec2: #############################################################
Jul 23 20:58:41 node-2 puppet-user[12947]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 23 20:58:41 node-2 puppet-user[12947]: Finished catalog run in 9.06 seconds
Jul 23 20:58:43 node-2 puppet-user[14065]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 23 20:58:43 node-2 puppet-user[14065]: Compiled catalog for node-2.domain.tld in environment production in 0.12 seconds
Jul 23 20:58:48 node-2 puppet-user[14065]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 23 20:59:01 node-2 CRON[16048]: (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")
Jul 23 20:59:19 node-2 puppet-user[14065]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 23 20:59:19 node-2 puppet-user[14065]: Finished catalog run in 35.56 seconds
Jul 23 20:59:20 node-2 puppet-user[16975]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 23 20:59:21 node-2 puppet-user[16975]: Compiled catalog for node-2.domain.tld in environment production in 0.59 seconds
Jul 23 20:59:21 node-2 puppet-user[16975]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 23 20:59:21 node-2 puppet-user[16975]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 23 20:59:21 node-2 puppet-user[16975]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 23 20:59:21 node-2 puppet-user[16975]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 23 20:59:21 node-2 puppet-user[16975]: Finished catalog run in 0.08 seconds
Jul 23 20:59:23 node-2 puppet-user[17429]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 23 20:59:24 node-2 puppet-user[17429]: Compiled catalog for node-2.domain.tld in environment production in 0.89 seconds
Jul 23 20:59:24 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 23 20:59:24 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 23 20:59:24 node-2 crontab[17865]: (root) LIST (root)
Jul 23 20:59:24 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 23 20:59:24 node-2 crontab[17866]: (root) REPLACE (root)
Jul 23 20:59:26 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/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
Jul 23 20:59:28 node-2 puppet-user[17429]: (/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
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/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
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/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
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/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
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 23 20:59:28 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 23 20:59:29 node-2 puppet-user[17429]: (/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
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 23 20:59:29 node-2 puppet-user[17429]: (/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
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 23 20:59:29 node-2 puppet-user[17429]: (/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
Jul 23 20:59:29 node-2 puppet-user[17429]: (/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
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 23 20:59:29 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 23 20:59:29 node-2 nailgun-agent: I, [2016-07-23T20:59:29.261659 #16051]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 23 20:59:29 node-2 puppet-user[17429]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 23 20:59:29 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 20:59:29 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 23 20:59:31 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:31 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:31 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:31 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:31 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:50 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:50 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:50 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:50 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:50 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:50 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:52 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:52 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:52 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:52 node-2 multipathd: uevent trigger error
<27>Jul 23 20:59:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:00:52 node-2 ntpdate[29368]: no servers can be used, exiting
<27>Jul 23 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:43 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:43 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:43 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:43 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:43 node-2 multipathd: uevent trigger error
<27>Jul 23 21:01:43 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:02:53 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 23 21:02:53 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 23 21:02:59 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 23 21:02:59 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 23 21:03:05 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 23 21:03:10 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 23 21:03:10 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 23 21:03:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:31 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:31 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:31 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:31 node-2 multipathd: uevent trigger error
<129>Jul 23 21:03:33 node-2 haproxy[17621]: 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>Jul 23 21:03:34 node-2 haproxy[17627]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:34 node-2 haproxy[17627]: 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>Jul 23 21:03:34 node-2 haproxy[17627]: proxy mysqld has no server available!
<27>Jul 23 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:37 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:37 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:40 node-2 multipathd: uevent trigger error
<129>Jul 23 21:03:42 node-2 haproxy[20224]: 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>Jul 23 21:03:43 node-2 haproxy[20233]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:43 node-2 haproxy[20233]: 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>Jul 23 21:03:43 node-2 haproxy[20233]: proxy mysqld has no server available!
<129>Jul 23 21:03:43 node-2 haproxy[20233]: 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>Jul 23 21:03:44 node-2 haproxy[20233]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:44 node-2 haproxy[20233]: 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>Jul 23 21:03:44 node-2 haproxy[20233]: proxy object-storage has no server available!
<27>Jul 23 21:03:46 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:46 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:46 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:46 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:46 node-2 multipathd: uevent trigger error
<129>Jul 23 21:03:48 node-2 haproxy[21605]: 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>Jul 23 21:03:48 node-2 haproxy[21605]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:48 node-2 haproxy[21605]: 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>Jul 23 21:03:48 node-2 haproxy[21605]: proxy neutron has no server available!
<129>Jul 23 21:03:48 node-2 haproxy[21605]: 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>Jul 23 21:03:49 node-2 haproxy[21609]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:49 node-2 haproxy[21609]: 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>Jul 23 21:03:49 node-2 haproxy[21609]: proxy mysqld has no server available!
<129>Jul 23 21:03:49 node-2 haproxy[21609]: 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>Jul 23 21:03:49 node-2 haproxy[21609]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:49 node-2 haproxy[21609]: 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>Jul 23 21:03:49 node-2 haproxy[21609]: proxy object-storage has no server available!
<27>Jul 23 21:03:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:51 node-2 multipathd: uevent trigger error
<129>Jul 23 21:03:53 node-2 haproxy[23018]: 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>Jul 23 21:03:53 node-2 haproxy[23018]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:54 node-2 haproxy[23022]: 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>Jul 23 21:03:54 node-2 haproxy[23022]: proxy keystone-1 has no server available!
<129>Jul 23 21:03:54 node-2 haproxy[23022]: 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>Jul 23 21:03:54 node-2 haproxy[23022]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:54 node-2 haproxy[23022]: 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>Jul 23 21:03:54 node-2 haproxy[23022]: proxy keystone-2 has no server available!
<129>Jul 23 21:03:54 node-2 haproxy[23022]: 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>Jul 23 21:03:54 node-2 haproxy[23022]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:54 node-2 haproxy[23022]: 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>Jul 23 21:03:54 node-2 haproxy[23022]: proxy neutron has no server available!
<129>Jul 23 21:03:55 node-2 haproxy[23022]: 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>Jul 23 21:03:55 node-2 haproxy[23022]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:55 node-2 haproxy[23022]: 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>Jul 23 21:03:55 node-2 haproxy[23022]: proxy mysqld has no server available!
<129>Jul 23 21:03:55 node-2 haproxy[23022]: 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>Jul 23 21:03:55 node-2 haproxy[23022]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:55 node-2 haproxy[23022]: 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>Jul 23 21:03:55 node-2 haproxy[23022]: proxy object-storage has no server available!
<27>Jul 23 21:03:56 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:56 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:56 node-2 multipathd: uevent trigger error
<27>Jul 23 21:03:56 node-2 multipathd: uevent trigger error
<129>Jul 23 21:03:59 node-2 haproxy[24344]: 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>Jul 23 21:03:59 node-2 haproxy[24344]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:59 node-2 haproxy[24344]: 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>Jul 23 21:03:59 node-2 haproxy[24344]: proxy keystone-1 has no server available!
<129>Jul 23 21:03:59 node-2 haproxy[24344]: 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>Jul 23 21:03:59 node-2 haproxy[24344]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:59 node-2 haproxy[24344]: 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>Jul 23 21:03:59 node-2 haproxy[24344]: proxy keystone-2 has no server available!
<129>Jul 23 21:03:59 node-2 haproxy[24344]: 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>Jul 23 21:03:59 node-2 haproxy[24344]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:03:59 node-2 haproxy[24344]: 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>Jul 23 21:03:59 node-2 haproxy[24344]: proxy neutron has no server available!
<129>Jul 23 21:04:00 node-2 haproxy[24348]: 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>Jul 23 21:04:00 node-2 haproxy[24348]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:00 node-2 haproxy[24348]: 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>Jul 23 21:04:00 node-2 haproxy[24348]: proxy mysqld has no server available!
<129>Jul 23 21:04:00 node-2 haproxy[24348]: 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>Jul 23 21:04:00 node-2 haproxy[24348]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:00 node-2 haproxy[24348]: 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>Jul 23 21:04:00 node-2 haproxy[24348]: proxy object-storage has no server available!
<129>Jul 23 21:04:00 node-2 haproxy[24348]: 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>Jul 23 21:04:00 node-2 haproxy[24348]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:00 node-2 haproxy[24348]: 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>Jul 23 21:04:00 node-2 haproxy[24348]: proxy aodh has no server available!
<27>Jul 23 21:04:02 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:02 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:02 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:02 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:02 node-2 multipathd: uevent trigger error
<129>Jul 23 21:04:04 node-2 haproxy[25867]: 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>Jul 23 21:04:04 node-2 haproxy[25867]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:04 node-2 haproxy[25867]: 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>Jul 23 21:04:04 node-2 haproxy[25867]: proxy keystone-1 has no server available!
<129>Jul 23 21:04:04 node-2 haproxy[25867]: 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>Jul 23 21:04:05 node-2 haproxy[25871]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:05 node-2 haproxy[25871]: 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>Jul 23 21:04:05 node-2 haproxy[25871]: proxy keystone-2 has no server available!
<129>Jul 23 21:04:05 node-2 haproxy[25871]: 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>Jul 23 21:04:05 node-2 haproxy[25871]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:05 node-2 haproxy[25871]: 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>Jul 23 21:04:05 node-2 haproxy[25871]: proxy neutron has no server available!
<129>Jul 23 21:04:05 node-2 haproxy[25871]: 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>Jul 23 21:04:05 node-2 haproxy[25871]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:05 node-2 haproxy[25871]: 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>Jul 23 21:04:05 node-2 haproxy[25871]: proxy mysqld has no server available!
<129>Jul 23 21:04:05 node-2 haproxy[25871]: 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>Jul 23 21:04:05 node-2 haproxy[25871]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:06 node-2 haproxy[25871]: 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>Jul 23 21:04:06 node-2 haproxy[25871]: proxy object-storage has no server available!
<129>Jul 23 21:04:06 node-2 haproxy[25871]: 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>Jul 23 21:04:06 node-2 haproxy[25871]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:06 node-2 haproxy[25871]: 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>Jul 23 21:04:06 node-2 haproxy[25871]: proxy aodh has no server available!
<129>Jul 23 21:04:06 node-2 haproxy[25871]: 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>Jul 23 21:04:06 node-2 haproxy[25871]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:06 node-2 haproxy[25871]: 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>Jul 23 21:04:06 node-2 haproxy[25871]: proxy ceilometer has no server available!
<27>Jul 23 21:04:08 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:08 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:08 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:08 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:08 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:08 node-2 multipathd: uevent trigger error
<129>Jul 23 21:04:10 node-2 haproxy[27204]: 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>Jul 23 21:04:10 node-2 haproxy[27204]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:10 node-2 haproxy[27204]: 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>Jul 23 21:04:10 node-2 haproxy[27204]: proxy keystone-1 has no server available!
<129>Jul 23 21:04:10 node-2 haproxy[27204]: 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>Jul 23 21:04:10 node-2 haproxy[27204]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:10 node-2 haproxy[27204]: 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>Jul 23 21:04:10 node-2 haproxy[27204]: proxy keystone-2 has no server available!
<129>Jul 23 21:04:10 node-2 haproxy[27204]: 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>Jul 23 21:04:10 node-2 haproxy[27204]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:10 node-2 haproxy[27204]: 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>Jul 23 21:04:10 node-2 haproxy[27204]: proxy neutron has no server available!
<129>Jul 23 21:04:10 node-2 haproxy[27204]: 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>Jul 23 21:04:11 node-2 haproxy[27208]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:11 node-2 haproxy[27208]: 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>Jul 23 21:04:11 node-2 haproxy[27208]: proxy mysqld has no server available!
<129>Jul 23 21:04:11 node-2 haproxy[27208]: 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>Jul 23 21:04:11 node-2 haproxy[27208]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:11 node-2 haproxy[27208]: 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>Jul 23 21:04:11 node-2 haproxy[27208]: proxy object-storage has no server available!
<129>Jul 23 21:04:11 node-2 haproxy[27208]: 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>Jul 23 21:04:11 node-2 haproxy[27208]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:11 node-2 haproxy[27208]: 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>Jul 23 21:04:11 node-2 haproxy[27208]: proxy aodh has no server available!
<129>Jul 23 21:04:11 node-2 haproxy[27208]: 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>Jul 23 21:04:11 node-2 haproxy[27208]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:12 node-2 haproxy[27208]: 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>Jul 23 21:04:12 node-2 haproxy[27208]: proxy ceilometer has no server available!
<27>Jul 23 21:04:13 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:13 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:13 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:13 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:13 node-2 multipathd: uevent trigger error
<129>Jul 23 21:04:15 node-2 haproxy[28574]: 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>Jul 23 21:04:15 node-2 haproxy[28574]: 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>Jul 23 21:04:15 node-2 haproxy[28574]: 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>Jul 23 21:04:15 node-2 haproxy[28574]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:15 node-2 haproxy[28574]: 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>Jul 23 21:04:15 node-2 haproxy[28574]: proxy keystone-1 has no server available!
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: proxy keystone-2 has no server available!
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: proxy neutron has no server available!
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: proxy mysqld has no server available!
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:16 node-2 haproxy[28588]: 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>Jul 23 21:04:16 node-2 haproxy[28588]: proxy object-storage has no server available!
<129>Jul 23 21:04:17 node-2 haproxy[28588]: 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>Jul 23 21:04:17 node-2 haproxy[28588]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:17 node-2 haproxy[28588]: 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>Jul 23 21:04:17 node-2 haproxy[28588]: proxy aodh has no server available!
<129>Jul 23 21:04:17 node-2 haproxy[28588]: 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>Jul 23 21:04:17 node-2 haproxy[28588]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:17 node-2 haproxy[28588]: 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>Jul 23 21:04:17 node-2 haproxy[28588]: proxy ceilometer has no server available!
<27>Jul 23 21:04:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:18 node-2 multipathd: uevent trigger error
<129>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: proxy keystone-1 has no server available!
<129>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: proxy keystone-2 has no server available!
<129>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:21 node-2 haproxy[30117]: 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>Jul 23 21:04:21 node-2 haproxy[30117]: proxy glance-api has no server available!
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: proxy glance-glare has no server available!
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: proxy neutron has no server available!
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: proxy glance-registry has no server available!
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: proxy mysqld has no server available!
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:22 node-2 haproxy[30128]: proxy object-storage has no server available!
<129>Jul 23 21:04:22 node-2 haproxy[30128]: 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>Jul 23 21:04:23 node-2 haproxy[30128]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:23 node-2 haproxy[30128]: 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>Jul 23 21:04:23 node-2 haproxy[30128]: proxy aodh has no server available!
<129>Jul 23 21:04:23 node-2 haproxy[30128]: 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>Jul 23 21:04:23 node-2 haproxy[30128]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:23 node-2 haproxy[30128]: 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>Jul 23 21:04:23 node-2 haproxy[30128]: proxy ceilometer has no server available!
<27>Jul 23 21:04:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:24 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:24 node-2 multipathd: uevent trigger error
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: proxy keystone-1 has no server available!
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: proxy keystone-2 has no server available!
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: proxy nova-api has no server available!
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: proxy nova-metadata-api has no server available!
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: proxy glance-api has no server available!
<129>Jul 23 21:04:27 node-2 haproxy[31529]: 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>Jul 23 21:04:27 node-2 haproxy[31529]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: proxy glance-glare has no server available!
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: proxy neutron has no server available!
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: proxy glance-registry has no server available!
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: proxy mysqld has no server available!
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: proxy object-storage has no server available!
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: proxy aodh has no server available!
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: proxy ceilometer has no server available!
<129>Jul 23 21:04:28 node-2 haproxy[31533]: 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>Jul 23 21:04:28 node-2 haproxy[31533]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:29 node-2 haproxy[31533]: 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>Jul 23 21:04:29 node-2 haproxy[31533]: proxy nova-novncproxy has no server available!
<27>Jul 23 21:04:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:30 node-2 multipathd: uevent trigger error
<129>Jul 23 21:04:32 node-2 haproxy[411]: 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>Jul 23 21:04:32 node-2 haproxy[411]: 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>Jul 23 21:04:32 node-2 haproxy[411]: 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>Jul 23 21:04:32 node-2 haproxy[411]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:32 node-2 haproxy[411]: 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>Jul 23 21:04:32 node-2 haproxy[411]: proxy keystone-1 has no server available!
<129>Jul 23 21:04:32 node-2 haproxy[411]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: proxy keystone-2 has no server available!
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: proxy nova-api has no server available!
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: proxy nova-metadata-api has no server available!
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: proxy cinder-api has no server available!
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: proxy glance-api has no server available!
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: proxy glance-glare has no server available!
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: proxy neutron has no server available!
<129>Jul 23 21:04:33 node-2 haproxy[415]: 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>Jul 23 21:04:33 node-2 haproxy[415]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: proxy glance-registry has no server available!
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: proxy mysqld has no server available!
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: proxy object-storage has no server available!
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: proxy aodh has no server available!
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: proxy ceilometer has no server available!
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:34 node-2 haproxy[415]: 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>Jul 23 21:04:34 node-2 haproxy[415]: proxy nova-novncproxy has no server available!
<27>Jul 23 21:04:35 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:35 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:35 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:35 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:35 node-2 multipathd: uevent trigger error
<129>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: proxy keystone-1 has no server available!
<129>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: proxy keystone-2 has no server available!
<129>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: proxy nova-api has no server available!
<129>Jul 23 21:04:38 node-2 haproxy[1854]: 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>Jul 23 21:04:38 node-2 haproxy[1854]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy nova-metadata-api has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy cinder-api has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy glance-api has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy glance-glare has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy neutron has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy glance-registry has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy mysqld has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy object-storage has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: proxy aodh has no server available!
<129>Jul 23 21:04:39 node-2 haproxy[1861]: 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>Jul 23 21:04:39 node-2 haproxy[1861]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: proxy ceilometer has no server available!
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: proxy heat-api has no server available!
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: proxy heat-api-cfn has no server available!
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: proxy heat-api-cloudwatch has no server available!
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 23 21:04:40 node-2 haproxy[1861]: 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>Jul 23 21:04:40 node-2 haproxy[1861]: proxy nova-novncproxy has no server available!
<27>Jul 23 21:04:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:04:56 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 23 21:05:21 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>Jul 23 21:05:23 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 23 21:05:50 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:05:57 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 23 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:10 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:10 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:10 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:10 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:10 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:10 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:10 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:17 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:17 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:17 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:17 node-2 multipathd: uevent trigger error
<43>Jul 23 21:08:30 node-2 apache2_error [Sat Jul 23 21:08:29.683116 2016] [mpm_event:notice] [pid 8436:tid 140571601135488] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 23 21:08:30 node-2 apache2_error [Sat Jul 23 21:08:29.683248 2016] [core:notice] [pid 8436:tid 140571601135488] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 21:08:38 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:38 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:38 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:38 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:38 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:38 node-2 multipathd: uevent trigger error
<43>Jul 23 21:08:40 node-2 apache2_error [Sat Jul 23 21:08:32.804334 2016] [mpm_event:notice] [pid 8436:tid 140571601135488] AH00491: caught SIGTERM, shutting down
<43>Jul 23 21:08:40 node-2 apache2_error [Sat Jul 23 21:08:33.898495 2016] [mpm_worker:notice] [pid 9029:tid 139926391977856] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 23 21:08:40 node-2 apache2_error [Sat Jul 23 21:08:33.898558 2016] [core:notice] [pid 9029:tid 139926391977856] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 21:08:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:41 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:42 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:08:57 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:09:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:28 node-2 multipathd: uevent trigger error
<43>Jul 23 21:09:30 node-2 apache2_error [Sat Jul 23 21:09:24.542647 2016] [mpm_worker:notice] [pid 9029:tid 139926391977856] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 21:09:30 node-2 apache2_error [Sat Jul 23 21:09:24.549604 2016] [mpm_worker:warn] [pid 9029:tid 139926391977856] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 21:09:30 node-2 apache2_error [Sat Jul 23 21:09:24.550354 2016] [mpm_worker:notice] [pid 9029:tid 139926391977856] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 23 21:09:30 node-2 apache2_error [Sat Jul 23 21:09:24.550367 2016] [core:notice] [pid 9029:tid 139926391977856] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:09:32 node-2 multipathd: uevent trigger error
<43>Jul 23 21:10:50 node-2 apache2_error [Sat Jul 23 21:10:42.044989 2016] [mpm_worker:notice] [pid 9029:tid 139926391977856] AH00295: caught SIGTERM, shutting down
<43>Jul 23 21:10:50 node-2 apache2_error [Sat Jul 23 21:10:42.807063 2016] [mpm_worker:notice] [pid 30303:tid 140487824009088] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 21:10:50 node-2 apache2_error [Sat Jul 23 21:10:42.807095 2016] [core:notice] [pid 30303:tid 140487824009088] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 23 21:11:30 node-2 apache2_error [Sat Jul 23 21:11:26.885344 2016] [mpm_worker:notice] [pid 30303:tid 140487824009088] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 21:11:30 node-2 apache2_error [Sat Jul 23 21:11:26.896826 2016] [mpm_worker:warn] [pid 30303:tid 140487824009088] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 21:11:30 node-2 apache2_error [Sat Jul 23 21:11:26.901630 2016] [mpm_worker:notice] [pid 30303:tid 140487824009088] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 21:11:30 node-2 apache2_error [Sat Jul 23 21:11:26.901652 2016] [core:notice] [pid 30303:tid 140487824009088] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 21:11:58 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:12:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:28 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:48 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:48 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:48 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:48 node-2 multipathd: uevent trigger error
<27>Jul 23 21:13:48 node-2 multipathd: uevent trigger error
<27>Jul 23 21:14:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:14:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:14:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:14:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:14:47 node-2 multipathd: uevent trigger error
<27>Jul 23 21:15:00 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:16:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:16:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:17:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:18:02 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:19:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:19:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:19:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:19:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:19:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:19:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:59 node-2 multipathd: uevent trigger error
<27>Jul 23 21:20:59 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:21:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:21:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 23 21:22:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 23 21:22:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 23 21:22:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 23 21:22:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 23 21:22:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:22:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:23:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:23:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:23:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:23:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:23:04 node-2 multipathd: uevent trigger error
<27>Jul 23 21:24:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:25:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:25:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:25:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:25:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:25:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:01 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:01 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:01 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:02 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:02 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:07 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:30 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:51 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:57 node-2 multipathd: uevent trigger error
<27>Jul 23 21:26:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:27:07 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 21:27:36 node-2 multipathd: uevent trigger error
<27>Jul 23 21:27:36 node-2 multipathd: uevent trigger error
<27>Jul 23 21:27:36 node-2 multipathd: uevent trigger error
<27>Jul 23 21:27:36 node-2 multipathd: uevent trigger error
<27>Jul 23 21:28:49 node-2 multipathd: uevent trigger error
<27>Jul 23 21:28:49 node-2 multipathd: uevent trigger error
<27>Jul 23 21:28:49 node-2 multipathd: uevent trigger error
<27>Jul 23 21:28:49 node-2 multipathd: uevent trigger error
<27>Jul 23 21:28:49 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:05 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:05 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:05 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:05 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:05 node-2 multipathd: uevent trigger error
<11>Jul 23 21:29:18 node-2 liberasurecode[22363]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:18 node-2 liberasurecode[22363]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:18 node-2 liberasurecode[22363]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:18 node-2 liberasurecode[22363]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:18 node-2 liberasurecode[22392]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:18 node-2 liberasurecode[22392]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:18 node-2 liberasurecode[22392]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:18 node-2 liberasurecode[22392]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:20 node-2 liberasurecode[23045]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:20 node-2 liberasurecode[23045]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:20 node-2 liberasurecode[23045]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:20 node-2 liberasurecode[23045]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25205]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25205]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25205]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25205]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25246]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25246]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25246]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25246]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25288]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25288]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25288]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25288]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25349]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25349]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25349]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25349]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25361]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25361]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25361]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:26 node-2 liberasurecode[25361]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25411]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25411]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25411]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25411]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25388]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25388]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25388]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:27 node-2 liberasurecode[25388]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:35 node-2 liberasurecode[25767]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:35 node-2 liberasurecode[25767]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:35 node-2 liberasurecode[25767]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:29:35 node-2 liberasurecode[25767]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 23 21:29:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:29:45 node-2 multipathd: uevent trigger error
<11>Jul 23 21:30:01 node-2 liberasurecode[30029]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:30:01 node-2 liberasurecode[30029]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:30:01 node-2 liberasurecode[30029]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:30:01 node-2 liberasurecode[30029]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 23 21:30:09 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 23 21:30:41 node-2 apache2_error [Sat Jul 23 21:30:32.819013 2016] [mpm_worker:notice] [pid 30303:tid 140487824009088] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 21:30:41 node-2 apache2_error [Sat Jul 23 21:30:33.205175 2016] [mpm_worker:warn] [pid 30303:tid 140487824009088] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 21:30:41 node-2 apache2_error [Sat Jul 23 21:30:33.209243 2016] [mpm_worker:notice] [pid 30303:tid 140487824009088] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 21:30:41 node-2 apache2_error [Sat Jul 23 21:30:33.209261 2016] [core:notice] [pid 30303:tid 140487824009088] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 23 21:31:11 node-2 apache2_error [Sat Jul 23 21:31:10.391795 2016] [mpm_worker:notice] [pid 30303:tid 140487824009088] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 21:31:11 node-2 apache2_error [Sat Jul 23 21:31:10.602977 2016] [mpm_worker:warn] [pid 30303:tid 140487824009088] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 21:31:11 node-2 apache2_error [Sat Jul 23 21:31:10.615050 2016] [mpm_worker:notice] [pid 30303:tid 140487824009088] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 21:31:11 node-2 apache2_error [Sat Jul 23 21:31:10.615093 2016] [core:notice] [pid 30303:tid 140487824009088] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 21:31:14 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:14 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:14 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:14 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:14 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:21 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:32 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:50 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:50 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:50 node-2 multipathd: uevent trigger error
<27>Jul 23 21:31:50 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:18 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:26 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 23 21:32:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:35 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:35 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:35 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:40 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:00 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:21 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 23 21:33:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:27 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:34 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:52 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:53 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:53 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:33:58 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:11 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:15 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:15 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:15 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:15 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:15 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:20 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:25 node-2 multipathd: uevent trigger error
<27>Jul 23 21:34:25 node-2 multipathd: uevent trigger error
<11>Jul 23 21:35:01 node-2 liberasurecode[809]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:35:01 node-2 liberasurecode[809]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:35:01 node-2 liberasurecode[809]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 21:35:01 node-2 liberasurecode[809]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
