Jul 30 20:35:52 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8393" x-info="http://www.rsyslog.com"] start
Jul 30 20:35:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 30 20:35:52 node-3 rsyslogd: rsyslogd's groupid changed to 104
Jul 30 20:35:52 node-3 rsyslogd: rsyslogd's userid changed to 101
Jul 30 20:35:52 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 30 20:35:52 node-3 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 30 20:35:52 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 30 20:35:52 node-3 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 30 20:35:52 node-3 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=ca26f6af-2f05-437d-b34b-d9e008c02ce6 nomdmonddf nomdmonisw
Jul 30 20:35:52 node-3 kernel: [    0.000000] KERNEL supported cpus:
Jul 30 20:35:52 node-3 kernel: [    0.000000]   Intel GenuineIntel
Jul 30 20:35:52 node-3 kernel: [    0.000000]   AMD AuthenticAMD
Jul 30 20:35:52 node-3 kernel: [    0.000000]   Centaur CentaurHauls
Jul 30 20:35:52 node-3 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 30 20:35:52 node-3 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 30 20:35:52 node-3 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 30 20:35:52 node-3 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 30 20:35:52 node-3 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 30 20:35:52 node-3 kernel: [    0.000000] No AGP bridge found
Jul 30 20:35:52 node-3 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 30 20:35:52 node-3 kernel: [    0.000000] MTRR default type: write-back
Jul 30 20:35:52 node-3 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 30 20:35:52 node-3 kernel: [    0.000000]   00000-9FFFF write-back
Jul 30 20:35:52 node-3 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 30 20:35:52 node-3 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 30 20:35:52 node-3 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 30 20:35:52 node-3 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 30 20:35:52 node-3 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 30 20:35:52 node-3 kernel: [    0.000000]   2 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000]   3 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000]   4 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000]   5 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000]   6 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000]   7 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000]   8 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000]   9 disabled
Jul 30 20:35:52 node-3 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 30 20:35:52 node-3 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 30 20:35:52 node-3 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 30 20:35:52 node-3 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 30 20:35:52 node-3 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 30 20:35:52 node-3 kernel: [    0.000000] Using GB pages for direct mapping
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 30 20:35:52 node-3 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 30 20:35:52 node-3 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 30 20:35:52 node-3 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 30 20:35:52 node-3 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 30 20:35:52 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 30 20:35:52 node-3 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 30 20:35:52 node-3 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 30 20:35:52 node-3 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 30 20:35:52 node-3 kernel: [    0.000000] Zone ranges:
Jul 30 20:35:52 node-3 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] Movable zone start for each node
Jul 30 20:35:52 node-3 kernel: [    0.000000] Early memory node ranges
Jul 30 20:35:52 node-3 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 30 20:35:52 node-3 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 30 20:35:52 node-3 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 30 20:35:52 node-3 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 30 20:35:52 node-3 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 30 20:35:52 node-3 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 30 20:35:52 node-3 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 30 20:35:52 node-3 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 30 20:35:52 node-3 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 30 20:35:52 node-3 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 30 20:35:52 node-3 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 30 20:35:52 node-3 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 30 20:35:52 node-3 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 30 20:35:52 node-3 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 30 20:35:52 node-3 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 30 20:35:52 node-3 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 30 20:35:52 node-3 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 30 20:35:52 node-3 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 30 20:35:52 node-3 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 30 20:35:52 node-3 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 30 20:35:52 node-3 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 30 20:35:52 node-3 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 30 20:35:52 node-3 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 30 20:35:52 node-3 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 30 20:35:52 node-3 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 30 20:35:52 node-3 kernel: [    0.000000] Policy zone: Normal
Jul 30 20:35:52 node-3 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=ca26f6af-2f05-437d-b34b-d9e008c02ce6 nomdmonddf nomdmonisw
Jul 30 20:35:52 node-3 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 30 20:35:52 node-3 kernel: [    0.000000] Checking aperture...
Jul 30 20:35:52 node-3 kernel: [    0.000000] No AGP bridge found
Jul 30 20:35:52 node-3 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 30 20:35:52 node-3 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 30 20:35:52 node-3 kernel: [    0.000000] Memory: 32653324K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Jul 30 20:35:52 node-3 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 30 20:35:52 node-3 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 30 20:35:52 node-3 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 30 20:35:52 node-3 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 30 20:35:52 node-3 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 30 20:35:52 node-3 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 30 20:35:52 node-3 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 30 20:35:52 node-3 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 30 20:35:52 node-3 kernel: [    0.000000] console [tty0] enabled
Jul 30 20:35:52 node-3 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 30 20:35:52 node-3 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 30 20:35:52 node-3 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 30 20:35:52 node-3 kernel: [    0.000000] hpet clockevent registered
Jul 30 20:35:52 node-3 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 30 20:35:52 node-3 kernel: [    0.004000] tsc: Detected 3492.155 MHz processor
Jul 30 20:35:52 node-3 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.31 BogoMIPS (lpj=13968620)
Jul 30 20:35:52 node-3 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 30 20:35:52 node-3 kernel: [    0.000043] Security Framework initialized
Jul 30 20:35:52 node-3 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 30 20:35:52 node-3 kernel: [    0.000063] Yama: becoming mindful.
Jul 30 20:35:52 node-3 kernel: [    0.001466] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.006419] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.008348] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.008377] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.008669] Initializing cgroup subsys memory
Jul 30 20:35:52 node-3 kernel: [    0.008677] Initializing cgroup subsys devices
Jul 30 20:35:52 node-3 kernel: [    0.008679] Initializing cgroup subsys freezer
Jul 30 20:35:52 node-3 kernel: [    0.008681] Initializing cgroup subsys blkio
Jul 30 20:35:52 node-3 kernel: [    0.008682] Initializing cgroup subsys perf_event
Jul 30 20:35:52 node-3 kernel: [    0.008685] Initializing cgroup subsys hugetlb
Jul 30 20:35:52 node-3 kernel: [    0.008704] CPU: Physical Processor ID: 0
Jul 30 20:35:52 node-3 kernel: [    0.008706] CPU: Processor Core ID: 0
Jul 30 20:35:52 node-3 kernel: [    0.008709] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 30 20:35:52 node-3 kernel: [    0.008709] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 30 20:35:52 node-3 kernel: [    0.009403] mce: CPU supports 22 MCE banks
Jul 30 20:35:52 node-3 kernel: [    0.009431] CPU0: Thermal monitoring enabled (TM1)
Jul 30 20:35:52 node-3 kernel: [    0.009451] process: using mwait in idle threads
Jul 30 20:35:52 node-3 kernel: [    0.009454] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 30 20:35:52 node-3 kernel: [    0.009454] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 30 20:35:52 node-3 kernel: [    0.009454] tlb_flushall_shift: 6
Jul 30 20:35:52 node-3 kernel: [    0.009543] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 30 20:35:52 node-3 kernel: [    0.010268] ACPI: Core revision 20131115
Jul 30 20:35:52 node-3 kernel: [    0.022926] ACPI: All ACPI Tables successfully acquired
Jul 30 20:35:52 node-3 kernel: [    0.023085] ftrace: allocating 28617 entries in 112 pages
Jul 30 20:35:52 node-3 kernel: [    0.031889] dmar: Host address width 46
Jul 30 20:35:52 node-3 kernel: [    0.031891] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 30 20:35:52 node-3 kernel: [    0.031897] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 30 20:35:52 node-3 kernel: [    0.031899] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 30 20:35:52 node-3 kernel: [    0.031903] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 30 20:35:52 node-3 kernel: [    0.031904] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 30 20:35:52 node-3 kernel: [    0.031906] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 30 20:35:52 node-3 kernel: [    0.031907] dmar: ATSR flags: 0x0
Jul 30 20:35:52 node-3 kernel: [    0.031908] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 30 20:35:52 node-3 kernel: [    0.031909] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 30 20:35:52 node-3 kernel: [    0.032025] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 30 20:35:52 node-3 kernel: [    0.032026] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 30 20:35:52 node-3 kernel: [    0.032027] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 30 20:35:52 node-3 kernel: [    0.032028] HPET id 0 under DRHD base 0xc7ffc000
Jul 30 20:35:52 node-3 kernel: [    0.032029] Your BIOS is broken and requested that x2apic be disabled.
Jul 30 20:35:52 node-3 kernel: [    0.032029] This will slightly decrease performance.
Jul 30 20:35:52 node-3 kernel: [    0.032029] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 30 20:35:52 node-3 kernel: [    0.032460] Enabled IRQ remapping in xapic mode
Jul 30 20:35:52 node-3 kernel: [    0.032461] x2apic not enabled, IRQ remapping is in xapic mode
Jul 30 20:35:52 node-3 kernel: [    0.032465] Switched APIC routing to physical flat.
Jul 30 20:35:52 node-3 kernel: [    0.033087] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 30 20:35:52 node-3 kernel: [    0.072740] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 30 20:35:52 node-3 kernel: [    0.072745] TSC deadline timer enabled
Jul 30 20:35:52 node-3 kernel: [    0.072753] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 30 20:35:52 node-3 kernel: [    0.072759] ... version:                3
Jul 30 20:35:52 node-3 kernel: [    0.072760] ... bit width:              48
Jul 30 20:35:52 node-3 kernel: [    0.072761] ... generic registers:      4
Jul 30 20:35:52 node-3 kernel: [    0.072762] ... value mask:             0000ffffffffffff
Jul 30 20:35:52 node-3 kernel: [    0.072763] ... max period:             0000ffffffffffff
Jul 30 20:35:52 node-3 kernel: [    0.072764] ... fixed-purpose events:   3
Jul 30 20:35:52 node-3 kernel: [    0.072765] ... event mask:             000000070000000f
Jul 30 20:35:52 node-3 kernel: [    0.074185] x86: Booting SMP configuration:
Jul 30 20:35:52 node-3 kernel: [    0.088291] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 30 20:35:52 node-3 kernel: [    0.074187] .... node  #0, CPUs:        #1  #2  #3
Jul 30 20:35:52 node-3 kernel: [    0.116199] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 30 20:35:52 node-3 kernel: [    0.270356] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 30 20:35:52 node-3 kernel: [    0.325975] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 30 20:35:52 node-3 kernel: [    0.383036] x86: Booted up 2 nodes, 16 CPUs
Jul 30 20:35:52 node-3 kernel: [    0.383039] smpboot: Total of 16 processors activated (111760.89 BogoMIPS)
Jul 30 20:35:52 node-3 kernel: [    0.407259] devtmpfs: initialized
Jul 30 20:35:52 node-3 kernel: [    0.410357] EVM: security.selinux
Jul 30 20:35:52 node-3 kernel: [    0.410359] EVM: security.SMACK64
Jul 30 20:35:52 node-3 kernel: [    0.410360] EVM: security.ima
Jul 30 20:35:52 node-3 kernel: [    0.410361] EVM: security.capability
Jul 30 20:35:52 node-3 kernel: [    0.410412] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.411092] pinctrl core: initialized pinctrl subsystem
Jul 30 20:35:52 node-3 kernel: [    0.411153] regulator-dummy: no parameters
Jul 30 20:35:52 node-3 kernel: [    0.411184] RTC time: 20:35:16, date: 07/30/16
Jul 30 20:35:52 node-3 kernel: [    0.411216] NET: Registered protocol family 16
Jul 30 20:35:52 node-3 kernel: [    0.411301] cpuidle: using governor ladder
Jul 30 20:35:52 node-3 kernel: [    0.411303] cpuidle: using governor menu
Jul 30 20:35:52 node-3 kernel: [    0.411337] ACPI: bus type PCI registered
Jul 30 20:35:52 node-3 kernel: [    0.411339] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 30 20:35:52 node-3 kernel: [    0.411385] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 30 20:35:52 node-3 kernel: [    0.411388] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 30 20:35:52 node-3 kernel: [    0.425123] PCI: Using configuration type 1 for base access
Jul 30 20:35:52 node-3 kernel: [    0.426116] bio: create slab <bio-0> at 0
Jul 30 20:35:52 node-3 kernel: [    0.426394] ACPI: Added _OSI(Module Device)
Jul 30 20:35:52 node-3 kernel: [    0.426396] ACPI: Added _OSI(Processor Device)
Jul 30 20:35:52 node-3 kernel: [    0.426397] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 30 20:35:52 node-3 kernel: [    0.426398] ACPI: Added _OSI(Processor Aggregator Device)
Jul 30 20:35:52 node-3 kernel: [    0.439060] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 30 20:35:52 node-3 kernel: [    0.449709] ACPI: Interpreter enabled
Jul 30 20:35:52 node-3 kernel: [    0.449715] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 30 20:35:52 node-3 kernel: [    0.449718] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 30 20:35:52 node-3 kernel: [    0.449721] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 30 20:35:52 node-3 kernel: [    0.449728] ACPI: (supports S0 S4 S5)
Jul 30 20:35:52 node-3 kernel: [    0.449729] ACPI: Using IOAPIC for interrupt routing
Jul 30 20:35:52 node-3 kernel: [    0.449769] HEST: Table parsing has been initialized.
Jul 30 20:35:52 node-3 kernel: [    0.449772] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 30 20:35:52 node-3 kernel: [    0.450322] ACPI: No dock devices found.
Jul 30 20:35:52 node-3 kernel: [    0.461930] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 30 20:35:52 node-3 kernel: [    0.461935] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-3 kernel: [    0.461938] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 30 20:35:52 node-3 kernel: [    0.461966] PCI host bridge to bus 0000:ff
Jul 30 20:35:52 node-3 kernel: [    0.461969] pci_bus 0000:ff: root bus resource [bus ff]
Jul 30 20:35:52 node-3 kernel: [    0.461977] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462016] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.462047] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462082] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462112] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.462142] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.462174] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462203] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462234] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462263] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462290] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462317] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462346] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462372] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462400] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462427] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462455] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462483] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462510] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.462538] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462564] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.462591] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462619] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462651] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.462687] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462718] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462749] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462780] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462811] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462842] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462872] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462903] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462933] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462964] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.462996] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463029] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463060] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463089] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463117] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463148] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463182] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463222] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463258] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463289] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463318] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463350] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463380] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463409] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463442] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463474] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463506] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463535] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463564] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463594] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463624] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463655] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463689] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463746] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 30 20:35:52 node-3 kernel: [    0.463749] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-3 kernel: [    0.463752] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 30 20:35:52 node-3 kernel: [    0.463770] PCI host bridge to bus 0000:7f
Jul 30 20:35:52 node-3 kernel: [    0.463771] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 30 20:35:52 node-3 kernel: [    0.463776] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463804] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.463831] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463864] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463886] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.463911] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.463938] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463965] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.463990] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464012] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464035] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464058] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464082] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464104] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464130] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464155] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464177] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464199] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464222] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.464245] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464267] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.464289] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464311] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464337] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 30 20:35:52 node-3 kernel: [    0.464369] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464395] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464421] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464448] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464473] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464501] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464528] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464555] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464580] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464606] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464632] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464659] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464687] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464711] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464736] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464763] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464788] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464814] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464843] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464870] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464896] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464921] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464947] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464973] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.464999] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465025] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465053] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465077] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465099] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465124] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465148] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465176] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.465202] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.466443] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 30 20:35:52 node-3 kernel: [    0.466447] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-3 kernel: [    0.467565] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 30 20:35:52 node-3 kernel: [    0.468076] PCI host bridge to bus 0000:00
Jul 30 20:35:52 node-3 kernel: [    0.468079] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 30 20:35:52 node-3 kernel: [    0.468080] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 30 20:35:52 node-3 kernel: [    0.468082] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 30 20:35:52 node-3 kernel: [    0.468083] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 30 20:35:52 node-3 kernel: [    0.468084] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 30 20:35:52 node-3 kernel: [    0.468086] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 30 20:35:52 node-3 kernel: [    0.468087] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 30 20:35:52 node-3 kernel: [    0.468093] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 30 20:35:52 node-3 kernel: [    0.468175] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.468206] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.468247] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-3 kernel: [    0.468267] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.468296] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.468336] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-3 kernel: [    0.468355] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.468385] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.468428] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-3 kernel: [    0.468446] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.468516] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.468592] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.468670] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 30 20:35:52 node-3 kernel: [    0.468675] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 30 20:35:52 node-3 kernel: [    0.468759] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 30 20:35:52 node-3 kernel: [    0.468898] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 30 20:35:52 node-3 kernel: [    0.468915] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 30 20:35:52 node-3 kernel: [    0.468992] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.469046] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-3 kernel: [    0.469068] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.469123] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.469166] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-3 kernel: [    0.469194] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.469250] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.469293] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 30 20:35:52 node-3 kernel: [    0.469318] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 30 20:35:52 node-3 kernel: [    0.469335] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 30 20:35:52 node-3 kernel: [    0.469413] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.469462] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-3 kernel: [    0.469489] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 30 20:35:52 node-3 kernel: [    0.469738] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 30 20:35:52 node-3 kernel: [    0.469743] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 30 20:35:52 node-3 kernel: [    0.469749] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.469755] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.469762] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 30 20:35:52 node-3 kernel: [    0.469793] pci 0000:01:00.0: supports D1 D2
Jul 30 20:35:52 node-3 kernel: [    0.479867] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 30 20:35:52 node-3 kernel: [    0.479874] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 30 20:35:52 node-3 kernel: [    0.479893] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 30 20:35:52 node-3 kernel: [    0.480001] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.480034] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 30 20:35:52 node-3 kernel: [    0.487865] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 30 20:35:52 node-3 kernel: [    0.487867] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.487869] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-3 kernel: [    0.487924] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.487992] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.488068] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.488114] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 30 20:35:52 node-3 kernel: [    0.488117] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.488119] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-3 kernel: [    0.488172] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.488298] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.488352] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 30 20:35:52 node-3 kernel: [    0.488355] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.488357] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.488406] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.488541] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.488586] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.488706] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.488743] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.488863] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.488899] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-3 kernel: [    0.489017] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-3 kernel: [    0.489058] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 30 20:35:52 node-3 kernel: [    0.489060] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.489062] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.489124] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-3 kernel: [    0.489187] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.489241] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.489282] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 30 20:35:52 node-3 kernel: [    0.489364] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 30 20:35:52 node-3 kernel: [    0.489487] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 30 20:35:52 node-3 kernel: [    0.489490] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.489492] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.489548] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-3 kernel: [    0.489605] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.489654] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.489869] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 30 20:35:52 node-3 kernel: [    0.489873] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 30 20:35:52 node-3 kernel: [    0.489936] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-3 kernel: [    0.489989] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.490037] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.490248] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 30 20:35:52 node-3 kernel: [    0.490252] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 30 20:35:52 node-3 kernel: [    0.490310] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-3 kernel: [    0.490370] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.490446] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 30 20:35:52 node-3 kernel: [    0.490667] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 30 20:35:52 node-3 kernel: [    0.490670] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 30 20:35:52 node-3 kernel: [    0.490844] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 30 20:35:52 node-3 kernel: [    0.490881] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 30 20:35:52 node-3 kernel: [    0.490955] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 30 20:35:52 node-3 kernel: [    0.490974] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 30 20:35:52 node-3 kernel: [    0.490987] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 30 20:35:52 node-3 kernel: [    0.491000] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 30 20:35:52 node-3 kernel: [    0.491050] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 30 20:35:52 node-3 kernel: [    0.495871] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 30 20:35:52 node-3 kernel: [    0.495876] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 30 20:35:52 node-3 kernel: [    0.495908] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 30 20:35:52 node-3 kernel: [    0.496397] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 30 20:35:52 node-3 kernel: [    0.496400] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-3 kernel: [    0.496523] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 30 20:35:52 node-3 kernel: [    0.496628] PCI host bridge to bus 0000:80
Jul 30 20:35:52 node-3 kernel: [    0.496630] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 30 20:35:52 node-3 kernel: [    0.496631] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 30 20:35:52 node-3 kernel: [    0.496633] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 30 20:35:52 node-3 kernel: [    0.496641] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.496703] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.496771] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 30 20:35:52 node-3 kernel: [    0.496832] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 30 20:35:52 node-3 kernel: [    0.496838] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 30 20:35:52 node-3 kernel: [    0.496909] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 30 20:35:52 node-3 kernel: [    0.497209] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 30 20:35:52 node-3 kernel: [    0.497240] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 30 20:35:52 node-3 kernel: [    0.497269] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 30 20:35:52 node-3 kernel: [    0.497298] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 30 20:35:52 node-3 kernel: [    0.497327] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-3 kernel: [    0.497357] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-3 kernel: [    0.497387] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-3 kernel: [    0.497416] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-3 kernel: [    0.497501] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 30 20:35:52 node-3 kernel: [    0.497505] ACPI: \_SB_.UNC1: notify handler is installed
Jul 30 20:35:52 node-3 kernel: [    0.497506] ACPI: \_SB_.UNC0: notify handler is installed
Jul 30 20:35:52 node-3 kernel: [    0.497521] ACPI: \_SB_.PCI0: notify handler is installed
Jul 30 20:35:52 node-3 kernel: [    0.497575] ACPI: \_SB_.PCI1: notify handler is installed
Jul 30 20:35:52 node-3 kernel: [    0.497655] Found 4 acpi root devices
Jul 30 20:35:52 node-3 kernel: [    0.497762] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 30 20:35:52 node-3 kernel: [    0.497764] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 30 20:35:52 node-3 kernel: [    0.497766] vgaarb: loaded
Jul 30 20:35:52 node-3 kernel: [    0.497767] vgaarb: bridge control possible 0000:0c:00.0
Jul 30 20:35:52 node-3 kernel: [    0.497881] SCSI subsystem initialized
Jul 30 20:35:52 node-3 kernel: [    0.497946] libata version 3.00 loaded.
Jul 30 20:35:52 node-3 kernel: [    0.497961] ACPI: bus type USB registered
Jul 30 20:35:52 node-3 kernel: [    0.497971] usbcore: registered new interface driver usbfs
Jul 30 20:35:52 node-3 kernel: [    0.497976] usbcore: registered new interface driver hub
Jul 30 20:35:52 node-3 kernel: [    0.497999] usbcore: registered new device driver usb
Jul 30 20:35:52 node-3 kernel: [    0.498163] PCI: Using ACPI for IRQ routing
Jul 30 20:35:52 node-3 kernel: [    0.501778] PCI: pci_cache_line_size set to 64 bytes
Jul 30 20:35:52 node-3 kernel: [    0.501985] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 30 20:35:52 node-3 kernel: [    0.501986] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 30 20:35:52 node-3 kernel: [    0.501987] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 30 20:35:52 node-3 kernel: [    0.502052] NetLabel: Initializing
Jul 30 20:35:52 node-3 kernel: [    0.502053] NetLabel:  domain hash size = 128
Jul 30 20:35:52 node-3 kernel: [    0.502054] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 30 20:35:52 node-3 kernel: [    0.502063] NetLabel:  unlabeled traffic allowed by default
Jul 30 20:35:52 node-3 kernel: [    0.502122] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 30 20:35:52 node-3 kernel: [    0.502126] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 30 20:35:52 node-3 kernel: [    0.504182] Switched to clocksource hpet
Jul 30 20:35:52 node-3 kernel: [    0.508069] AppArmor: AppArmor Filesystem Enabled
Jul 30 20:35:52 node-3 kernel: [    0.508083] pnp: PnP ACPI init
Jul 30 20:35:52 node-3 kernel: [    0.508090] ACPI: bus type PNP registered
Jul 30 20:35:52 node-3 kernel: [    0.508215] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508222] pnp 00:01: [dma 4]
Jul 30 20:35:52 node-3 kernel: [    0.508234] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508260] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508280] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508297] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508329] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508382] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508384] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 30 20:35:52 node-3 kernel: [    0.508386] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508387] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508389] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508394] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508396] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 30 20:35:52 node-3 kernel: [    0.508397] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508399] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508400] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508402] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508403] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508405] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 30 20:35:52 node-3 kernel: [    0.508407] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508490] pnp 00:07: [dma 0 disabled]
Jul 30 20:35:52 node-3 kernel: [    0.508518] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508593] pnp 00:08: [dma 0 disabled]
Jul 30 20:35:52 node-3 kernel: [    0.508626] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 30 20:35:52 node-3 kernel: [    0.508676] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 30 20:35:52 node-3 kernel: [    0.509020] pnp: PnP ACPI: found 10 devices
Jul 30 20:35:52 node-3 kernel: [    0.509022] ACPI: bus type PNP unregistered
Jul 30 20:35:52 node-3 kernel: [    0.515330] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 30 20:35:52 node-3 kernel: [    0.515333] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 30 20:35:52 node-3 kernel: [    0.515335] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 30 20:35:52 node-3 kernel: [    0.515340] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 30 20:35:52 node-3 kernel: [    0.515342] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515356] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515389] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 30 20:35:52 node-3 kernel: [    0.515426] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515454] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 30 20:35:52 node-3 kernel: [    0.515468] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 30 20:35:52 node-3 kernel: [    0.515498] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 30 20:35:52 node-3 kernel: [    0.515512] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 30 20:35:52 node-3 kernel: [    0.515541] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 30 20:35:52 node-3 kernel: [    0.515542] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515559] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515587] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 30 20:35:52 node-3 kernel: [    0.515589] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515604] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515632] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 30 20:35:52 node-3 kernel: [    0.515634] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515637] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515641] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 30 20:35:52 node-3 kernel: [    0.515642] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515645] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515649] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 30 20:35:52 node-3 kernel: [    0.515653] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 30 20:35:52 node-3 kernel: [    0.515661] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 30 20:35:52 node-3 kernel: [    0.515665] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 30 20:35:52 node-3 kernel: [    0.515671] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 30 20:35:52 node-3 kernel: [    0.515672] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 30 20:35:52 node-3 kernel: [    0.515673] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 30 20:35:52 node-3 kernel: [    0.515674] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 30 20:35:52 node-3 kernel: [    0.515675] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 30 20:35:52 node-3 kernel: [    0.515676] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 30 20:35:52 node-3 kernel: [    0.515676] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 30 20:35:52 node-3 kernel: [    0.515677] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 30 20:35:52 node-3 kernel: [    0.515678] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515679] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515680] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515681] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515682] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515683] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515683] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515684] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515685] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-3 kernel: [    0.515686] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515687] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 30 20:35:52 node-3 kernel: [    0.515688] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 30 20:35:52 node-3 kernel: [    0.515689] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 30 20:35:52 node-3 kernel: [    0.515690] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 30 20:35:52 node-3 kernel: [    0.515692] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 30 20:35:52 node-3 kernel: [    0.515693] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 30 20:35:52 node-3 kernel: [    0.515731] NET: Registered protocol family 2
Jul 30 20:35:52 node-3 kernel: [    0.515987] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.516321] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.516463] TCP: Hash tables configured (established 262144 bind 65536)
Jul 30 20:35:52 node-3 kernel: [    0.516507] TCP: reno registered
Jul 30 20:35:52 node-3 kernel: [    0.516537] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.516630] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.516778] NET: Registered protocol family 1
Jul 30 20:35:52 node-3 kernel: [    0.556278] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 30 20:35:52 node-3 kernel: [    0.556292] PCI: CLS 64 bytes, default 64
Jul 30 20:35:52 node-3 kernel: [    0.556367] Trying to unpack rootfs image as initramfs...
Jul 30 20:35:52 node-3 kernel: [    0.775513] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Jul 30 20:35:52 node-3 kernel: [    0.775549] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 30 20:35:52 node-3 kernel: [    0.775551] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 30 20:35:52 node-3 kernel: [    0.775971] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.775977] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.775982] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.775987] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776000] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776017] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776032] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776048] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776059] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776069] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776075] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776081] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776090] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776102] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776115] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776128] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-3 kernel: [    0.776241] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 30 20:35:52 node-3 kernel: [    0.776244] Scanning for low memory corruption every 60 seconds
Jul 30 20:35:52 node-3 kernel: [    0.776635] Initialise system trusted keyring
Jul 30 20:35:52 node-3 kernel: [    0.776689] audit: initializing netlink socket (disabled)
Jul 30 20:35:52 node-3 kernel: [    0.776706] type=2000 audit(1469910915.732:1): initialized
Jul 30 20:35:52 node-3 kernel: [    0.794594] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 30 20:35:52 node-3 kernel: [    0.796106] zbud: loaded
Jul 30 20:35:52 node-3 kernel: [    0.796235] VFS: Disk quotas dquot_6.5.2
Jul 30 20:35:52 node-3 kernel: [    0.796271] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 30 20:35:52 node-3 kernel: [    0.796641] fuse init (API version 7.22)
Jul 30 20:35:52 node-3 kernel: [    0.796697] msgmni has been set to 32768
Jul 30 20:35:52 node-3 kernel: [    0.796749] Key type big_key registered
Jul 30 20:35:52 node-3 kernel: [    0.797370] Key type asymmetric registered
Jul 30 20:35:52 node-3 kernel: [    0.797374] Asymmetric key parser 'x509' registered
Jul 30 20:35:52 node-3 kernel: [    0.797420] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 30 20:35:52 node-3 kernel: [    0.797486] io scheduler noop registered
Jul 30 20:35:52 node-3 kernel: [    0.797488] io scheduler deadline registered (default)
Jul 30 20:35:52 node-3 kernel: [    0.797506] io scheduler cfq registered
Jul 30 20:35:52 node-3 kernel: [    0.798036] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    0.798214] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    0.798331] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    0.798442] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    0.798557] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    0.798660] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    0.799019] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 30 20:35:52 node-3 kernel: [    0.799044] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 30 20:35:52 node-3 kernel: [    0.799060] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 30 20:35:52 node-3 kernel: [    0.799073] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799075] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799078] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-3 kernel: [    0.799083] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799084] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799086] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799087] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799089] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799090] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799092] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799093] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799094] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799096] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799097] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799099] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799101] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-3 kernel: [    0.799106] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799108] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-3 kernel: [    0.799120] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799123] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-3 kernel: [    0.799134] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799135] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-3 kernel: [    0.799138] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-3 kernel: [    0.799166] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 30 20:35:52 node-3 kernel: [    0.799172] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 30 20:35:52 node-3 kernel: [    0.799176] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 30 20:35:52 node-3 kernel: [    0.799192] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 30 20:35:52 node-3 kernel: [    0.799231] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 30 20:35:52 node-3 kernel: [    0.799233] vesafb: scrolling: redraw
Jul 30 20:35:52 node-3 kernel: [    0.799235] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 30 20:35:52 node-3 kernel: [    0.819702] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 30 20:35:52 node-3 kernel: [    0.828405] Console: switching to colour frame buffer device 80x30
Jul 30 20:35:52 node-3 kernel: [    0.837268] fb0: VESA VGA frame buffer device
Jul 30 20:35:52 node-3 kernel: [    0.837469] intel_idle: MWAIT substates: 0x2120
Jul 30 20:35:52 node-3 kernel: [    0.837470] intel_idle: v0.4 model 0x3F
Jul 30 20:35:52 node-3 kernel: [    0.837471] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 30 20:35:52 node-3 kernel: [    0.837696] ipmi message handler version 39.2
Jul 30 20:35:52 node-3 kernel: [    0.837969] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 30 20:35:52 node-3 kernel: [    0.838405] ACPI: AC Adapter [P111] (on-line)
Jul 30 20:35:52 node-3 kernel: [    0.843693] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 30 20:35:52 node-3 kernel: [    0.854800] ACPI: Power Button [PWRB]
Jul 30 20:35:52 node-3 kernel: [    0.860558] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 30 20:35:52 node-3 kernel: [    0.872180] ACPI: Power Button [PWRF]
Jul 30 20:35:52 node-3 kernel: [    0.897708] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 30 20:35:52 node-3 kernel: [    0.909364] pstore: Registered erst as persistent store backend
Jul 30 20:35:52 node-3 kernel: [    0.915558] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 30 20:35:52 node-3 kernel: [    0.927498] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 30 20:35:52 node-3 kernel: [    0.954248] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 30 20:35:52 node-3 kernel: [    0.987541] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 30 20:35:52 node-3 kernel: [    1.001602] Linux agpgart interface v0.103
Jul 30 20:35:52 node-3 kernel: [    1.009233] brd: module loaded
Jul 30 20:35:52 node-3 kernel: [    1.016264] loop: module loaded
Jul 30 20:35:52 node-3 kernel: [    1.022965] libphy: Fixed MDIO Bus: probed
Jul 30 20:35:52 node-3 kernel: [    1.029413] tun: Universal TUN/TAP device driver, 1.6
Jul 30 20:35:52 node-3 kernel: [    1.035870] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 30 20:35:52 node-3 kernel: [    1.042389] PPP generic driver version 2.4.2
Jul 30 20:35:52 node-3 kernel: [    1.048770] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 30 20:35:52 node-3 kernel: [    1.055205] ehci-pci: EHCI PCI platform driver
Jul 30 20:35:52 node-3 kernel: [    1.061695] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 30 20:35:52 node-3 kernel: [    1.068091] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 30 20:35:52 node-3 kernel: [    1.080590] ehci-pci 0000:00:1a.0: debug port 2
Jul 30 20:35:52 node-3 kernel: [    1.090774] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 30 20:35:52 node-3 kernel: [    1.090791] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 30 20:35:52 node-3 kernel: [    1.107675] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 30 20:35:52 node-3 kernel: [    1.113740] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 30 20:35:52 node-3 kernel: [    1.119897] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 30 20:35:52 node-3 kernel: [    1.131767] usb usb1: Product: EHCI Host Controller
Jul 30 20:35:52 node-3 kernel: [    1.137774] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 30 20:35:52 node-3 kernel: [    1.143821] usb usb1: SerialNumber: 0000:00:1a.0
Jul 30 20:35:52 node-3 kernel: [    1.149759] hub 1-0:1.0: USB hub found
Jul 30 20:35:52 node-3 kernel: [    1.155512] hub 1-0:1.0: 2 ports detected
Jul 30 20:35:52 node-3 kernel: [    1.161273] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 30 20:35:52 node-3 kernel: [    1.166850] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 30 20:35:52 node-3 kernel: [    1.177715] ehci-pci 0000:00:1d.0: debug port 2
Jul 30 20:35:52 node-3 kernel: [    1.187000] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 30 20:35:52 node-3 kernel: [    1.187003] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 30 20:35:52 node-3 kernel: [    1.203594] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 30 20:35:52 node-3 kernel: [    1.208788] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 30 20:35:52 node-3 kernel: [    1.214076] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 30 20:35:52 node-3 kernel: [    1.224644] usb usb2: Product: EHCI Host Controller
Jul 30 20:35:52 node-3 kernel: [    1.230115] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 30 20:35:52 node-3 kernel: [    1.235672] usb usb2: SerialNumber: 0000:00:1d.0
Jul 30 20:35:52 node-3 kernel: [    1.241191] hub 2-0:1.0: USB hub found
Jul 30 20:35:52 node-3 kernel: [    1.246540] hub 2-0:1.0: 2 ports detected
Jul 30 20:35:52 node-3 kernel: [    1.251838] ehci-platform: EHCI generic platform driver
Jul 30 20:35:52 node-3 kernel: [    1.257066] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 30 20:35:52 node-3 kernel: [    1.262381] ohci-pci: OHCI PCI platform driver
Jul 30 20:35:52 node-3 kernel: [    1.267681] ohci-platform: OHCI generic platform driver
Jul 30 20:35:52 node-3 kernel: [    1.272884] uhci_hcd: USB Universal Host Controller Interface driver
Jul 30 20:35:52 node-3 kernel: [    1.278224] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 30 20:35:52 node-3 kernel: [    1.471373] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 30 20:35:52 node-3 kernel: [    1.771168] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 30 20:35:52 node-3 kernel: [    1.787420] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 30 20:35:52 node-3 kernel: [    1.793050] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 30 20:35:52 node-3 kernel: [    1.798814] hub 1-1:1.0: USB hub found
Jul 30 20:35:52 node-3 kernel: [    1.804406] hub 1-1:1.0: 6 ports detected
Jul 30 20:35:52 node-3 kernel: [    1.919014] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 30 20:35:52 node-3 kernel: [    2.317096] i8042: No controller found
Jul 30 20:35:52 node-3 kernel: [    2.322617] mousedev: PS/2 mouse device common for all mice
Jul 30 20:35:52 node-3 kernel: [    2.328336] rtc_cmos 00:02: RTC can wake from S4
Jul 30 20:35:52 node-3 kernel: [    2.331528] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 30 20:35:52 node-3 kernel: [    2.331529] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 30 20:35:52 node-3 kernel: [    2.332169] hub 2-1:1.0: USB hub found
Jul 30 20:35:52 node-3 kernel: [    2.332404] hub 2-1:1.0: 8 ports detected
Jul 30 20:35:52 node-3 kernel: [    2.356737] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 30 20:35:52 node-3 kernel: [    2.362483] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 30 20:35:52 node-3 kernel: [    2.373878] device-mapper: uevent: version 1.0.3
Jul 30 20:35:52 node-3 kernel: [    2.379679] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 30 20:35:52 node-3 kernel: [    2.391021] ledtrig-cpu: registered to indicate activity on CPUs
Jul 30 20:35:52 node-3 kernel: [    2.396977] TCP: cubic registered
Jul 30 20:35:52 node-3 kernel: [    2.402826] NET: Registered protocol family 10
Jul 30 20:35:52 node-3 kernel: [    2.408868] NET: Registered protocol family 17
Jul 30 20:35:52 node-3 kernel: [    2.414628] Key type dns_resolver registered
Jul 30 20:35:52 node-3 kernel: [    2.420672] Loading compiled-in X.509 certificates
Jul 30 20:35:52 node-3 kernel: [    2.426847] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 30 20:35:52 node-3 kernel: [    2.438437] registered taskstats version 1
Jul 30 20:35:52 node-3 kernel: [    2.446459] Key type trusted registered
Jul 30 20:35:52 node-3 kernel: [    2.454053] Key type encrypted registered
Jul 30 20:35:52 node-3 kernel: [    2.459542] AppArmor: AppArmor sha1 policy hashing enabled
Jul 30 20:35:52 node-3 kernel: [    2.465041] IMA: No TPM chip found, activating TPM-bypass!
Jul 30 20:35:52 node-3 kernel: [    2.471118] regulator-dummy: disabling
Jul 30 20:35:52 node-3 kernel: [    2.476610]   Magic number: 8:413:600
Jul 30 20:35:52 node-3 kernel: [    2.482343] rtc_cmos 00:02: setting system clock to 2016-07-30 20:35:18 UTC (1469910918)
Jul 30 20:35:52 node-3 kernel: [    2.494921] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 30 20:35:52 node-3 kernel: [    2.500583] EDD information not available.
Jul 30 20:35:52 node-3 kernel: [    2.506232] PM: Hibernation image not present or could not be loaded.
Jul 30 20:35:52 node-3 kernel: [    2.507102] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 30 20:35:52 node-3 kernel: [    2.518438] Write protecting the kernel read-only data: 12288k
Jul 30 20:35:52 node-3 kernel: [    2.524742] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 30 20:35:52 node-3 kernel: [    2.537685] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 30 20:35:52 node-3 kernel: [    2.570129] device-mapper: multipath: version 1.6.0 loaded
Jul 30 20:35:52 node-3 kernel: [    2.578096] systemd-udevd[215]: starting version 204
Jul 30 20:35:52 node-3 kernel: [    2.602895] md: linear personality registered for level -1
Jul 30 20:35:52 node-3 kernel: [    2.606524] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 30 20:35:52 node-3 kernel: [    2.624498] md: multipath personality registered for level -4
Jul 30 20:35:52 node-3 kernel: [    2.632635] md: raid0 personality registered for level 0
Jul 30 20:35:52 node-3 kernel: [    2.641396] md: raid1 personality registered for level 1
Jul 30 20:35:52 node-3 kernel: [    2.647815] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 30 20:35:52 node-3 kernel: [    2.654310] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 30 20:35:52 node-3 kernel: [    2.660653] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 30 20:35:52 node-3 kernel: [    2.665973] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-3 kernel: [    2.665994] 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 30 20:35:52 node-3 kernel: [    2.666018] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-3 kernel: [    2.666312] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.666559] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.666671] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.666918] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.667240] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.683867] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-3 kernel: [    2.683884] 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 30 20:35:52 node-3 kernel: [    2.683885] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-3 kernel: [    2.684197] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.684324] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.684463] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.684567] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.684772] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.700888] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-3 kernel: [    2.700890] 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 30 20:35:52 node-3 kernel: [    2.700917] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-3 kernel: [    2.701303] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.701362] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.701490] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.701613] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.701960] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.717324] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-3 kernel: [    2.717337] 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 30 20:35:52 node-3 kernel: [    2.717338] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-3 kernel: [    2.717549] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.717698] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.717799] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.717894] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.718169] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.743100] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 30 20:35:52 node-3 kernel: [    2.743101] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 30 20:35:52 node-3 kernel: [    2.743117] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 30 20:35:52 node-3 kernel: [    2.743133] usb 2-1.4: Manufacturer: Avocent
Jul 30 20:35:52 node-3 kernel: [    2.743134] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 30 20:35:52 node-3 kernel: [    2.896666] Switched to clocksource tsc
Jul 30 20:35:52 node-3 kernel: [    2.897609] megasas: FW now in Ready state
Jul 30 20:35:52 node-3 kernel: [    2.898080] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.898325] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.898452] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.898563] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.898652] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.898798] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.898956] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899047] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899148] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899302] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899399] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899483] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899629] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899781] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899872] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.899938] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 30 20:35:52 node-3 kernel: [    2.900465] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 30 20:35:52 node-3 kernel: [    2.937171] hidraw: raw HID events driver (C) Jiri Kosina
Jul 30 20:35:52 node-3 kernel: [    2.946616] usbcore: registered new interface driver usbhid
Jul 30 20:35:52 node-3 kernel: [    2.953059] usbhid: USB HID core driver
Jul 30 20:35:52 node-3 kernel: [    2.960293] 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 30 20:35:52 node-3 kernel: [    2.967633] raid6: sse2x1   10184 MB/s
Jul 30 20:35:52 node-3 kernel: [    2.980031] 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 30 20:35:52 node-3 kernel: [    2.993188] 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 30 20:35:52 node-3 kernel: [    3.006324] 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 30 20:35:52 node-3 kernel: [    3.020027] 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 30 20:35:52 node-3 kernel: [    3.033748] 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 30 20:35:52 node-3 kernel: [    3.038158] raid6: sse2x2     795 MB/s
Jul 30 20:35:52 node-3 kernel: [    3.105970] raid6: sse2x4   13800 MB/s
Jul 30 20:35:52 node-3 kernel: [    3.177908] raid6: avx2x1   22377 MB/s
Jul 30 20:35:52 node-3 kernel: [    3.237860] megasas:IOC Init cmd success
Jul 30 20:35:52 node-3 kernel: [    3.249847] raid6: avx2x2   25771 MB/s
Jul 30 20:35:52 node-3 kernel: [    3.289822] megasas: INIT adapter done
Jul 30 20:35:52 node-3 kernel: [    3.321787] raid6: avx2x4   30232 MB/s
Jul 30 20:35:52 node-3 kernel: [    3.327976] raid6: using algorithm avx2x4 (30232 MB/s)
Jul 30 20:35:52 node-3 kernel: [    3.334229] raid6: using avx2x2 recovery algorithm
Jul 30 20:35:52 node-3 kernel: [    3.341182] xor: automatically using best checksumming function:
Jul 30 20:35:52 node-3 kernel: [    3.365753] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 30 20:35:52 node-3 kernel: [    3.372226] scsi0 : LSI SAS based MegaRAID driver
Jul 30 20:35:52 node-3 kernel: [    3.379714] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 30 20:35:52 node-3 kernel: [    3.385730]    avx       : 35730.000 MB/sec
Jul 30 20:35:52 node-3 kernel: [    3.399125] async_tx: api initialized (async)
Jul 30 20:35:52 node-3 kernel: [    3.407266] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 30 20:35:52 node-3 kernel: [    3.420811] md: raid6 personality registered for level 6
Jul 30 20:35:52 node-3 kernel: [    3.422021] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 30 20:35:52 node-3 kernel: [    3.422116] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 30 20:35:52 node-3 kernel: [    3.422431] sd 0:2:0:0: [sda] Write Protect is off
Jul 30 20:35:52 node-3 kernel: [    3.422432] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 30 20:35:52 node-3 kernel: [    3.422502] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 30 20:35:52 node-3 kernel: [    3.451346]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 30 20:35:52 node-3 kernel: [    3.451900] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 30 20:35:52 node-3 kernel: [    3.473305] md: raid5 personality registered for level 5
Jul 30 20:35:52 node-3 kernel: [    3.478783] md: raid4 personality registered for level 4
Jul 30 20:35:52 node-3 kernel: [    3.487425] md: raid10 personality registered for level 10
Jul 30 20:35:52 node-3 kernel: [    3.534112] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 30 20:35:52 node-3 kernel: [    3.619223] random: lvm urandom read with 30 bits of entropy available
Jul 30 20:35:52 node-3 kernel: [    3.744939] bio: create slab <bio-1> at 1
Jul 30 20:35:52 node-3 kernel: [    4.528405] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 20:35:52 node-3 kernel: [    5.279106] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 30 20:35:52 node-3 kernel: [    5.300559] random: nonblocking pool is initialized
Jul 30 20:35:52 node-3 kernel: [    5.318606] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 30 20:35:52 node-3 kernel: [    5.431016] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 30 20:35:52 node-3 kernel: [    5.466960] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 30 20:35:52 node-3 kernel: [    5.524600] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 20:35:52 node-3 kernel: [    5.672930] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 30 20:35:52 node-3 kernel: [    5.704459] XFS (dm-1): Mounting Filesystem
Jul 30 20:35:52 node-3 kernel: [    5.921368] XFS (dm-1): Ending clean mount
Jul 30 20:35:52 node-3 kernel: [    6.021614] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 20:35:52 node-3 kernel: [    6.055903] XFS (dm-2): Mounting Filesystem
Jul 30 20:35:52 node-3 kernel: [    6.180454] XFS (dm-2): Ending clean mount
Jul 30 20:35:52 node-3 kernel: [    6.300356] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 20:35:52 node-3 kernel: [    8.156073] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 30 20:35:52 node-3 kernel: [    8.170740] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 30 20:35:52 node-3 kernel: [    8.294522] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 30 20:35:52 node-3 kernel: [    8.294533] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 30 20:35:52 node-3 kernel: [    8.294542] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 30 20:35:52 node-3 kernel: [    8.294550] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 30 20:35:52 node-3 kernel: [    8.344347] systemd-udevd[797]: starting version 204
Jul 30 20:35:52 node-3 kernel: [    8.565978] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 30 20:35:52 node-3 kernel: [    8.565984] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 30 20:35:52 node-3 kernel: [    8.565986] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 30 20:35:52 node-3 kernel: [    8.565988] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 30 20:35:52 node-3 kernel: [    8.566040] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 30 20:35:52 node-3 kernel: [    8.571021] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 30 20:35:52 node-3 kernel: [    8.571612] power_meter ACPI000D:00: Found ACPI power meter.
Jul 30 20:35:52 node-3 kernel: [    8.571633] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 30 20:35:52 node-3 kernel: [    8.583253] wmi: Mapper loaded
Jul 30 20:35:52 node-3 kernel: [    8.587572] IPMI System Interface driver.
Jul 30 20:35:52 node-3 kernel: [    8.587644] ipmi_si: probing via ACPI
Jul 30 20:35:52 node-3 kernel: [    8.587658] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 30 20:35:52 node-3 kernel: [    8.587659] ipmi_si: Adding ACPI-specified kcs state machine
Jul 30 20:35:52 node-3 kernel: [    8.587670] ipmi_si: probing via SMBIOS
Jul 30 20:35:52 node-3 kernel: [    8.587671] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 30 20:35:52 node-3 kernel: [    8.587672] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 30 20:35:52 node-3 kernel: [    8.587673] ipmi_si: probing via SPMI
Jul 30 20:35:52 node-3 kernel: [    8.587675] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 30 20:35:52 node-3 kernel: [    8.587675] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 30 20:35:52 node-3 kernel: [    8.587677] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 30 20:35:52 node-3 kernel: [    8.637787] systemd-udevd[838]: renamed network interface eth3 to enp9s0
Jul 30 20:35:52 node-3 kernel: [    8.665734] systemd-udevd[836]: renamed network interface eth2 to enp8s0
Jul 30 20:35:52 node-3 kernel: [    8.693765] systemd-udevd[833]: renamed network interface eth1 to enp7s0
Jul 30 20:35:52 node-3 kernel: [    8.725625] systemd-udevd[832]: renamed network interface eth0 to enp6s0
Jul 30 20:35:52 node-3 kernel: [    8.743750] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 30 20:35:52 node-3 kernel: [    8.743757] ipmi_si 00:09: IPMI kcs interface initialized
Jul 30 20:35:52 node-3 kernel: [    9.069307] type=1400 audit(1469910925.088:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.069460] type=1400 audit(1469910925.088:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1057 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.069587] type=1400 audit(1469910925.088:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1057 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.079108] type=1400 audit(1469910925.096:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1073 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.079354] type=1400 audit(1469910925.096:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1073 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.079575] type=1400 audit(1469910925.096:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1073 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.088058] type=1400 audit(1469910925.104:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1074 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.088206] type=1400 audit(1469910925.104:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1074 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.088331] type=1400 audit(1469910925.104:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1074 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.098143] type=1400 audit(1469910925.116:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Jul 30 20:35:52 node-3 kernel: [    9.617785] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 30 20:35:52 node-3 kernel: [    9.618890] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 30 20:35:52 node-3 kernel: [    9.808250] enic 0000:06:00.0 enp6s0: Link UP
Jul 30 20:35:52 node-3 kernel: [    9.808807] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 30 20:35:52 node-3 kernel: [    9.808814] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 30 20:35:52 node-3 kernel: [   19.612536] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 30 20:35:52 node-3 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 30 20:35:53 node-3 failsafe: Failsafe of 120 seconds reached.
Jul 30 20:35:53 node-3 kernel: [   38.313990] init: failsafe main process (8420) killed by TERM signal
Jul 30 20:35:54 node-3 dbus[8449]: [system] AppArmor D-Bus mediation is enabled
Jul 30 20:35:54 node-3 kernel: [   38.617395] audit_printk_skb: 30 callbacks suppressed
Jul 30 20:35:54 node-3 kernel: [   38.617397] type=1400 audit(1469910954.203:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8547 comm="apparmor_parser"
Jul 30 20:35:54 node-3 kernel: [   38.617676] type=1400 audit(1469910954.203:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8546 comm="apparmor_parser"
Jul 30 20:35:54 node-3 kernel: [   38.617680] type=1400 audit(1469910954.203:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8546 comm="apparmor_parser"
Jul 30 20:35:54 node-3 kernel: [   38.617683] type=1400 audit(1469910954.203:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8546 comm="apparmor_parser"
Jul 30 20:35:54 node-3 kernel: [   38.617918] type=1400 audit(1469910954.203:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8546 comm="apparmor_parser"
Jul 30 20:35:54 node-3 kernel: [   38.617919] type=1400 audit(1469910954.203:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8546 comm="apparmor_parser"
Jul 30 20:35:54 node-3 kernel: [   38.618031] type=1400 audit(1469910954.203:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8546 comm="apparmor_parser"
Jul 30 20:35:54 node-3 kernel: [   38.707307] type=1400 audit(1469910954.295:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8549 comm="apparmor_parser"
Jul 30 20:35:54 node-3 anacron[8603]: Anacron 2.3 started on 2016-07-30
Jul 30 20:35:54 node-3 anacron[8603]: Will run job `cron.daily' in 5 min.
Jul 30 20:35:54 node-3 anacron[8603]: Will run job `cron.weekly' in 10 min.
Jul 30 20:35:54 node-3 anacron[8603]: Will run job `cron.monthly' in 15 min.
Jul 30 20:35:54 node-3 anacron[8603]: Jobs will be executed sequentially
Jul 30 20:35:54 node-3 cron[8579]: (CRON) INFO (pidfile fd = 3)
Jul 30 20:35:54 node-3 cron[8624]: (CRON) STARTUP (fork ok)
Jul 30 20:35:54 node-3 multipathd: path checkers start up
Jul 30 20:35:54 node-3 cron[8624]: (CRON) INFO (Running @reboot jobs)
Jul 30 20:35:54 node-3 postfix/master[8758]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 30 20:35:58 node-3 puppet-agent[8942]: Reopening log files
Jul 30 20:35:59 node-3 puppet-agent[8942]: Could not request certificate: Connection refused - connect(2)
Jul 30 20:36:01 node-3 CRON[8973]: (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 30 20:36:11 node-3 puppet-user[9032]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 30 20:36:11 node-3 puppet-user[9032]: Compiled catalog for node-3.domain.tld in environment production in 0.03 seconds
Jul 30 20:36:12 node-3 puppet-user[9032]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 30 20:36:12 node-3 puppet-user[9032]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 30 20:36:12 node-3 puppet-user[9032]: Finished catalog run in 0.83 seconds
Jul 30 20:36:14 node-3 multipathd: uevent trigger error
Jul 30 20:36:14 node-3 puppet-user[9495]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 30 20:36:14 node-3 puppet-user[9495]: Compiled catalog for node-3.domain.tld in environment production in 0.10 seconds
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 30 20:36:14 node-3 puppet-user[9495]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 30 20:36:14 node-3 puppet-user[9495]: Finished catalog run in 0.07 seconds
Jul 30 20:36:15 node-3 puppet-user[10064]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 30 20:36:15 node-3 puppet-user[10064]: Compiled catalog for node-3.domain.tld in environment production in 0.07 seconds
Jul 30 20:36:15 node-3 puppet-user[10064]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 30 20:36:15 node-3 puppet-user[10064]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 30 20:36:15 node-3 puppet-user[10064]: Finished catalog run in 0.03 seconds
Jul 30 20:36:17 node-3 puppet-user[10529]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 30 20:36:17 node-3 puppet-user[10529]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 30 20:36:17 node-3 puppet-user[10529]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 30 20:36:17 node-3 puppet-user[10529]: Finished catalog run in 0.03 seconds
Jul 30 20:36:18 node-3 puppet-user[10978]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 30 20:36:18 node-3 puppet-user[10978]: Compiled catalog for node-3.domain.tld in environment production in 0.18 seconds
Jul 30 20:36:18 node-3 puppet-user[10978]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 30 20:36:19 node-3 puppet-user[10978]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 30 20:36:19 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:36:19 node-3 nailgun-agent: D, [2016-07-30T20:36:01.651599 #8976] DEBUG -- : Sleep for 18 seconds before sending request
Jul 30 20:36:19 node-3 nailgun-agent: I, [2016-07-30T20:36:19.665648 #8976]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 30 20:36:19 node-3 puppet-user[10978]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 30 20:36:19 node-3 puppet-user[10978]: Finished catalog run in 0.80 seconds
Jul 30 20:36:20 node-3 nailgun-agent: D, [2016-07-30T20:36:20.048981 #8976] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 30 20:36:20 node-3 puppet-user[11607]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 30 20:36:21 node-3 puppet-user[11607]: Compiled catalog for node-3.domain.tld in environment production in 0.22 seconds
Jul 30 20:36:21 node-3 puppet-user[11607]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 30 20:36:21 node-3 puppet-user[11607]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 30 20:36:21 node-3 puppet-user[11607]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 30 20:36:21 node-3 puppet-user[11607]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 30 20:36:21 node-3 puppet-user[11607]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 30 20:36:21 node-3 puppet-user[11607]: Finished catalog run in 0.35 seconds
Jul 30 20:36:22 node-3 puppet-user[12101]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 30 20:36:23 node-3 puppet-user[12101]: Compiled catalog for node-3.domain.tld in environment production in 0.16 seconds
Jul 30 20:36:23 node-3 puppet-user[12101]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 30 20:36:23 node-3 kernel: [   67.627205] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 30 20:36:23 node-3 kernel: [   67.627252] 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 30 20:36:23 node-3 puppet-user[12101]: (/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 30 20:36:23 node-3 puppet-user[12101]: Finished catalog run in 0.05 seconds
Jul 30 20:36:24 node-3 puppet-user[12570]: (Scope(Class[main])) MODULAR: sync_time
Jul 30 20:36:24 node-3 puppet-user[12570]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 30 20:36:25 node-3 ntpdate[12988]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 30 20:36:31 node-3 ntpdate[12988]: adjust time server 10.20.0.2 offset 0.232445 sec
Jul 30 20:36:31 node-3 puppet-user[12570]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 30 20:36:31 node-3 puppet-user[12570]: Finished catalog run in 6.17 seconds
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.134943 #8976] DEBUG -- : Trying to find block devices
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.135033 #8976] DEBUG -- : Found block device: sda
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.135077 #8976] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.135118 #8976] DEBUG -- : Trying to get list of physical devices
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.135265 #8976] DEBUG -- : Getting udev properties for device: sda
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.136996 #8976] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc7884
Jul 30 20:36:32 node-3 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9873", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.137022 #8976] DEBUG -- : Trying to find out if device sda is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.137083 #8976] DEBUG -- : Device sda removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.137098 #8976] DEBUG -- : Device sda seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.137574 #8976] DEBUG -- : Getting udev properties for device: dm-0
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.139074 #8976] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-i9T98p1S2alLfVzPpE6flfiyd0Mctwr1C0wfhbCsJPnVQDmqd651pozQgL29vP22 /dev/disk/by-uuid/fdf88864-64d5-4dd0-99b6-190e249cf1cb /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-i9T98p1S2alLfVzPpE6flfiyd0Mctwr1C0wfhbCsJPnVQDmqd651pozQgL29vP22", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"fdf88864-64d5-4dd0-99b6-190e249cf1cb", "ID_FS_UUID_ENC"=>"fdf88864-64d5-4dd0-99b6-190e249cf1cb", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34
Jul 30 20:36:32 node-3 nailgun-agent: 27", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.139114 #8976] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.139145 #8976] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.139169 #8976] DEBUG -- : Device dm-0 seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.139196 #8976] DEBUG -- : Getting udev properties for device: dm-1
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.140882 #8976] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-MvRFf7aStdoctm2yvZEcwbUqoZdXqdfQs3GY8XeUBLLV9uM5i2H40fHrWboKx6Oc /dev/disk/by-uuid/646e22ab-e282-4d3b-9cf6-ae1659ad8e3c /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-MvRFf7aStdoctm2yvZEcwbUqoZdXqdfQs3GY8XeUBLLV9uM5i2H40fHrWboKx6Oc", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"646e22ab-e282-4d3b-9cf6-ae1659ad8e3c", "ID_FS_UUID_ENC"=>"646e22ab-e282-4d3b-9cf6-ae1659ad8e3c", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"20112", "nomdmonddf"=>"1", "nomd
Jul 30 20:36:32 node-3 nailgun-agent: monisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.140908 #8976] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.140946 #8976] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.140958 #8976] DEBUG -- : Device dm-1 seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.140985 #8976] DEBUG -- : Getting udev properties for device: dm-2
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.142550 #8976] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-tscrNZuroqEKDONyqPx8Y0E7gzrPwo7QQcicj2tg1Q4oFiRfWj5FTuLmW8JeLPdz /dev/disk/by-uuid/47092972-a4c0-475f-9566-7b83405d7f1b /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-tscrNZuroqEKDONyqPx8Y0E7gzrPwo7QQcicj2tg1Q4oFiRfWj5FTuLmW8JeLPdz", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"47092972-a4c0-475f-9566-7b83405d7f1b", "ID_FS_UUID_ENC"=>"47092972-a4c0-475f-9566-7b83405d7f1b", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34
Jul 30 20:36:32 node-3 nailgun-agent: 790", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.142599 #8976] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.142637 #8976] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.142649 #8976] DEBUG -- : Device dm-2 seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.142662 #8976] DEBUG -- : Getting udev properties for device: dm-3
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.144191 #8976] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-36gXqaDqe7W7vV3iDdH3EQ7eOppuqkB1u7s14NF85UXkSxvREExscNHRNeQEuP5X /dev/disk/by-uuid/3160bf0c-81a3-4051-8ea6-5210a582af82 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-36gXqaDqe7W7vV3iDdH3EQ7eOppuqkB1u7s14NF85UXkSxvREExscNHRNeQEuP5X", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3160bf0c-81a3-4051-8ea6-5210a582af82", "ID_FS_UUID_ENC"=>"3160bf0c-81a3-4051-8ea6-5210a582af82", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44707", "nomdmond
Jul 30 20:36:32 node-3 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.144213 #8976] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.144251 #8976] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.144280 #8976] DEBUG -- : Device dm-3 seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.144292 #8976] DEBUG -- : Getting udev properties for device: dm-4
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.146125 #8976] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-O63jbvWOTFZoi3qMTx2vugeiCWs038XyVoOXhXvCBxvnmcHEdmmloEN9aCxJwtGn /dev/disk/by-uuid/2d2bf45f-b74c-4135-acf7-7b4089b3c9a3 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-O63jbvWOTFZoi3qMTx2vugeiCWs038XyVoOXhXvCBxvnmcHEdmmloEN9aCxJwtGn", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2d2bf45f-b74c-4135-acf7-7b4089b3c9a3", "ID_FS_UUID_ENC"=>"2d2bf45f-b74c-4135-acf7-7b4089b3c9a3", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60884", "nomdmonddf"=>"1", 
Jul 30 20:36:32 node-3 nailgun-agent: "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.146158 #8976] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.146186 #8976] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.146200 #8976] DEBUG -- : Device dm-4 seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.146214 #8976] DEBUG -- : Getting udev properties for device: dm-5
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.147888 #8976] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-pn38m3ImJgqEd5U0IEv7mhhW2fLLetqasrVaxnI9vn4aoZ7Ik78CqY8tdyyHtASj /dev/disk/by-uuid/ca26f6af-2f05-437d-b34b-d9e008c02ce6 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-pn38m3ImJgqEd5U0IEv7mhhW2fLLetqasrVaxnI9vn4aoZ7Ik78CqY8tdyyHtASj", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ca26f6af-2f05-437d-b34b-d9e008c02ce6", "ID_FS_UUID_ENC"=>"ca26f6af-2f05-437d-b34b-d9e008c02ce6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"68102", "nomdmonddf"=>"1", "nomd
Jul 30 20:36:32 node-3 nailgun-agent: monisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.147915 #8976] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.147945 #8976] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.147959 #8976] DEBUG -- : Device dm-5 seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.147985 #8976] DEBUG -- : Getting udev properties for device: dm-6
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.149574 #8976] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-pn38m3ImJgqEd5U0IEv7mhhW2fLLetqaNrFXW100VpMaDnspDgFxoQrRoYwj5nBk /dev/disk/by-uuid/d9453411-e4ee-4e7b-b49c-a5beb4db3a36 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-pn38m3ImJgqEd5U0IEv7mhhW2fLLetqaNrFXW100VpMaDnspDgFxoQrRoYwj5nBk", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"d9453411-e4ee-4e7b-b49c-a5beb4db3a36", "ID_FS_UUID_ENC"=>"d9453411-e4ee-4e7b-b49c-a5beb4db3a36", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"68502", "nomdmonddf"=>"1", "nomdmonisw"
Jul 30 20:36:32 node-3 nailgun-agent: =>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.149612 #8976] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.149641 #8976] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.149654 #8976] DEBUG -- : Device dm-6 seems to be appropriate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.149669 #8976] DEBUG -- : Getting udev properties for device: ram0
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.151113 #8976] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86216", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.151150 #8976] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.151186 #8976] DEBUG -- : Device ram0 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.151216 #8976] DEBUG -- : Getting udev properties for device: ram1
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.152611 #8976] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86223", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.152646 #8976] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.152706 #8976] DEBUG -- : Device ram1 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.152727 #8976] DEBUG -- : Getting udev properties for device: ram2
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.154189 #8976] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86357", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.154232 #8976] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.154267 #8976] DEBUG -- : Device ram2 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.154287 #8976] DEBUG -- : Getting udev properties for device: ram3
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.155680 #8976] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86369", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.155718 #8976] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.155759 #8976] DEBUG -- : Device ram3 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.155794 #8976] DEBUG -- : Getting udev properties for device: ram4
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.157245 #8976] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86376", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.157270 #8976] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.157301 #8976] DEBUG -- : Device ram4 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.157337 #8976] DEBUG -- : Getting udev properties for device: ram5
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.158730 #8976] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86384", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.158767 #8976] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.158804 #8976] DEBUG -- : Device ram5 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.158824 #8976] DEBUG -- : Getting udev properties for device: ram6
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.160209 #8976] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86393", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.160241 #8976] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.160288 #8976] DEBUG -- : Device ram6 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.160328 #8976] DEBUG -- : Getting udev properties for device: ram7
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.161718 #8976] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86405", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.161750 #8976] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.161785 #8976] DEBUG -- : Device ram7 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.161812 #8976] DEBUG -- : Getting udev properties for device: ram8
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.163245 #8976] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86418", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.163283 #8976] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.163317 #8976] DEBUG -- : Device ram8 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.163354 #8976] DEBUG -- : Getting udev properties for device: ram9
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.164723 #8976] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86431", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.164748 #8976] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.164794 #8976] DEBUG -- : Device ram9 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.164826 #8976] DEBUG -- : Getting udev properties for device: loop0
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.166216 #8976] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86156", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.166263 #8976] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.166301 #8976] DEBUG -- : Device loop0 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.166320 #8976] DEBUG -- : Getting udev properties for device: loop1
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.167701 #8976] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86164", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.167744 #8976] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.167781 #8976] DEBUG -- : Device loop1 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.167800 #8976] DEBUG -- : Getting udev properties for device: loop2
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.169223 #8976] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86174", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.169248 #8976] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.169295 #8976] DEBUG -- : Device loop2 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.169327 #8976] DEBUG -- : Getting udev properties for device: loop3
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.170720 #8976] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86182", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.170761 #8976] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.170798 #8976] DEBUG -- : Device loop3 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.170817 #8976] DEBUG -- : Getting udev properties for device: loop4
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.172210 #8976] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86189", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.172245 #8976] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.172293 #8976] DEBUG -- : Device loop4 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.172313 #8976] DEBUG -- : Getting udev properties for device: loop5
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.173693 #8976] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86196", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.173719 #8976] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.173769 #8976] DEBUG -- : Device loop5 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.173788 #8976] DEBUG -- : Getting udev properties for device: loop6
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.175143 #8976] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86203", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.175167 #8976] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.175201 #8976] DEBUG -- : Device loop6 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.175236 #8976] DEBUG -- : Getting udev properties for device: loop7
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.176600 #8976] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86209", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.176631 #8976] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.176673 #8976] DEBUG -- : Device loop7 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.176691 #8976] DEBUG -- : Getting udev properties for device: ram10
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.183062 #8976] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86231", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.183090 #8976] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.183124 #8976] DEBUG -- : Device ram10 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.183144 #8976] DEBUG -- : Getting udev properties for device: ram11
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.184551 #8976] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86238", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.184576 #8976] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.184610 #8976] DEBUG -- : Device ram11 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.184630 #8976] DEBUG -- : Getting udev properties for device: ram12
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.186046 #8976] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86246", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.186071 #8976] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.186114 #8976] DEBUG -- : Device ram12 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.186133 #8976] DEBUG -- : Getting udev properties for device: ram13
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.187539 #8976] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86256", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.187563 #8976] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.187606 #8976] DEBUG -- : Device ram13 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.187625 #8976] DEBUG -- : Getting udev properties for device: ram14
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.189033 #8976] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86268", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.189059 #8976] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.189102 #8976] DEBUG -- : Device ram14 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.189120 #8976] DEBUG -- : Getting udev properties for device: ram15
Jul 30 20:36:32 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190499 #8976] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86280", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190523 #8976] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190568 #8976] DEBUG -- : Device ram15 removable parameter: "0"
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190602 #8976] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190616 #8976] DEBUG -- : Block device seems to be physical data storage: sda
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190663 #8976] DEBUG -- : Found block device: dm-0
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190725 #8976] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190738 #8976] DEBUG -- : Found block device: dm-1
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190748 #8976] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190757 #8976] DEBUG -- : Found block device: dm-2
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190767 #8976] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190775 #8976] DEBUG -- : Found block device: dm-3
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190783 #8976] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190792 #8976] DEBUG -- : Found block device: dm-4
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190852 #8976] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190861 #8976] DEBUG -- : Found block device: dm-5
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190871 #8976] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190879 #8976] DEBUG -- : Found block device: dm-6
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190890 #8976] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190897 #8976] DEBUG -- : Found block device: ram0
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190906 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190915 #8976] DEBUG -- : Found block device: ram1
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190924 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190972 #8976] DEBUG -- : Found block device: ram2
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190982 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.190990 #8976] DEBUG -- : Found block device: ram3
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191002 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191010 #8976] DEBUG -- : Found block device: ram4
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191020 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191029 #8976] DEBUG -- : Found block device: ram5
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191039 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191047 #8976] DEBUG -- : Found block device: ram6
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191084 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191092 #8976] DEBUG -- : Found block device: ram7
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191101 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191109 #8976] DEBUG -- : Found block device: ram8
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191119 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191127 #8976] DEBUG -- : Found block device: ram9
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191136 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191144 #8976] DEBUG -- : Found block device: loop0
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191153 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191190 #8976] DEBUG -- : Found block device: loop1
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191199 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191207 #8976] DEBUG -- : Found block device: loop2
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191217 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191225 #8976] DEBUG -- : Found block device: loop3
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191234 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191242 #8976] DEBUG -- : Found block device: loop4
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191250 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191258 #8976] DEBUG -- : Found block device: loop5
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191267 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191305 #8976] DEBUG -- : Found block device: loop6
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191314 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191321 #8976] DEBUG -- : Found block device: loop7
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191330 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191338 #8976] DEBUG -- : Found block device: ram10
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191347 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191355 #8976] DEBUG -- : Found block device: ram11
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191364 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191373 #8976] DEBUG -- : Found block device: ram12
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191409 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191417 #8976] DEBUG -- : Found block device: ram13
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191427 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191435 #8976] DEBUG -- : Found block device: ram14
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191444 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191453 #8976] DEBUG -- : Found block device: ram15
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191463 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.191491 #8976] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.283374 #8976] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 30 20:36:32 node-3 nailgun-agent: D, [2016-07-30T20:36:32.283454 #8976] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 30 20:36:38 node-3 kernel: [   82.583307] init: plymouth-upstart-bridge main process ended, respawning
Jul 30 20:36:38 node-3 puppet-agent[8942]: Could not run: SIGTERM
Jul 30 20:36:38 node-3 kernel: [   82.852768] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 30 20:36:38 node-3 ec2: 
Jul 30 20:36:38 node-3 ec2: #############################################################
Jul 30 20:36:38 node-3 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 30 20:36:38 node-3 ec2: 1024 db:d8:01:23:4d:e4:ed:00:14:91:a3:06:96:01:13:e3  root@node-3.domain.tld (DSA)
Jul 30 20:36:38 node-3 ec2: 256 30:ab:8e:5e:94:47:65:52:86:0f:f9:cf:e3:78:05:60  root@node-3.domain.tld (ECDSA)
Jul 30 20:36:38 node-3 ec2: 256 69:eb:57:bb:e0:7b:dd:15:7f:e2:f5:4b:cc:9b:fd:97  root@node-3.domain.tld (ED25519)
Jul 30 20:36:38 node-3 ec2: 2048 60:4a:28:2e:bd:65:86:0b:ab:6f:72:9c:23:d5:07:c8  root@node-3.domain.tld (RSA)
Jul 30 20:36:38 node-3 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 30 20:36:38 node-3 ec2: #############################################################
Jul 30 20:36:44 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307562 #8976] DEBUG -- : Trying to find block devices
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307676 #8976] DEBUG -- : Found block device: sda
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307706 #8976] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307724 #8976] DEBUG -- : Block device seems to be physical data storage: sda
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307747 #8976] DEBUG -- : Found block device: dm-0
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307787 #8976] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307799 #8976] DEBUG -- : Found block device: dm-1
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307811 #8976] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307821 #8976] DEBUG -- : Found block device: dm-2
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307831 #8976] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307840 #8976] DEBUG -- : Found block device: dm-3
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307850 #8976] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307859 #8976] DEBUG -- : Found block device: dm-4
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307868 #8976] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307876 #8976] DEBUG -- : Found block device: dm-5
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307885 #8976] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307914 #8976] DEBUG -- : Found block device: dm-6
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307925 #8976] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307933 #8976] DEBUG -- : Found block device: ram0
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307942 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307951 #8976] DEBUG -- : Found block device: ram1
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307961 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307969 #8976] DEBUG -- : Found block device: ram2
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307978 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307986 #8976] DEBUG -- : Found block device: ram3
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.307996 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308028 #8976] DEBUG -- : Found block device: ram4
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308038 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308047 #8976] DEBUG -- : Found block device: ram5
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308058 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308066 #8976] DEBUG -- : Found block device: ram6
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308076 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308084 #8976] DEBUG -- : Found block device: ram7
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308093 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308102 #8976] DEBUG -- : Found block device: ram8
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308111 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308119 #8976] DEBUG -- : Found block device: ram9
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308149 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308159 #8976] DEBUG -- : Found block device: loop0
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308169 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308176 #8976] DEBUG -- : Found block device: loop1
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308185 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308194 #8976] DEBUG -- : Found block device: loop2
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308203 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308211 #8976] DEBUG -- : Found block device: loop3
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308221 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308230 #8976] DEBUG -- : Found block device: loop4
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308240 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308273 #8976] DEBUG -- : Found block device: loop5
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308283 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308292 #8976] DEBUG -- : Found block device: loop6
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308302 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308310 #8976] DEBUG -- : Found block device: loop7
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308319 #8976] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308327 #8976] DEBUG -- : Found block device: ram10
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308336 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308344 #8976] DEBUG -- : Found block device: ram11
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308354 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308377 #8976] DEBUG -- : Found block device: ram12
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308387 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308395 #8976] DEBUG -- : Found block device: ram13
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308404 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308412 #8976] DEBUG -- : Found block device: ram14
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308422 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308430 #8976] DEBUG -- : Found block device: ram15
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308458 #8976] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.308490 #8976] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 30 20:36:44 node-3 nailgun-agent: D, [2016-07-30T20:36:44.492203 #8976] DEBUG -- : Response: status: 200 body: {"id": 3}
Jul 30 20:36:44 node-3 nailgun-agent: I, [2016-07-30T20:36:44.492413 #8976]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 30 20:37:01 node-3 CRON[13833]: (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 30 20:37:15 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:37:15 node-3 nailgun-agent: I, [2016-07-30T20:37:15.669843 #13836]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 30 20:37:19 node-3 puppet-user[13992]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 30 20:37:19 node-3 puppet-user[13992]: Compiled catalog for node-3.domain.tld in environment production in 0.10 seconds
Jul 30 20:37:19 node-3 puppet-user[13992]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 30 20:37:19 node-3 puppet-user[13992]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 30 20:37:19 node-3 puppet-user[13992]: Finished catalog run in 0.08 seconds
Jul 30 20:37:21 node-3 puppet-user[14455]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 30 20:37:22 node-3 puppet-user[14455]: Compiled catalog for node-3.domain.tld in environment production in 1.08 seconds
Jul 30 20:37:22 node-3 puppet-user[14455]: (/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 30 20:37:22 node-3 puppet-user[14455]: (/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 30 20:37:22 node-3 puppet-user[14455]: (/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 30 20:37:22 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:23 node-3 puppet-user[14455]: (/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 30 20:37:28 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:37:28 node-3 nailgun-agent: I, [2016-07-30T20:37:28.723415 #13836]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 30 20:37:39 node-3 puppet-user[14455]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 30 20:37:39 node-3 puppet-user[14455]: Finished catalog run in 16.26 seconds
Jul 30 20:37:41 node-3 puppet-user[15528]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 30 20:37:41 node-3 puppet-user[15528]: Compiled catalog for node-3.domain.tld in environment production in 0.15 seconds
Jul 30 20:37:46 node-3 puppet-user[15528]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 30 20:38:01 node-3 CRON[17125]: (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 30 20:38:04 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:38:04 node-3 nailgun-agent: I, [2016-07-30T20:38:04.908846 #17128]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 30 20:38:17 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:38:18 node-3 nailgun-agent: I, [2016-07-30T20:38:18.041009 #17128]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 30 20:38:20 node-3 puppet-user[15528]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 30 20:38:20 node-3 puppet-user[15528]: Finished catalog run in 38.72 seconds
Jul 30 20:38:22 node-3 puppet-user[18385]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 30 20:38:22 node-3 puppet-user[18385]: Compiled catalog for node-3.domain.tld in environment production in 0.58 seconds
Jul 30 20:38:22 node-3 puppet-user[18385]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 30 20:38:22 node-3 puppet-user[18385]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 30 20:38:22 node-3 puppet-user[18385]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 30 20:38:22 node-3 puppet-user[18385]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 30 20:38:22 node-3 puppet-user[18385]: Finished catalog run in 0.10 seconds
Jul 30 20:38:24 node-3 puppet-user[18850]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 30 20:38:25 node-3 puppet-user[18850]: Compiled catalog for node-3.domain.tld in environment production in 0.99 seconds
Jul 30 20:38:25 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 30 20:38:25 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 30 20:38:25 node-3 crontab[19298]: (root) LIST (root)
Jul 30 20:38:25 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 30 20:38:25 node-3 crontab[19299]: (root) REPLACE (root)
Jul 30 20:38:28 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 30 20:38:30 node-3 puppet-user[18850]: (/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 30 20:38:30 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8393" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:31 node-3 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 30 20:38:33 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:33 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:33 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:33 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:33 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-3 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-3 multipathd: uevent trigger error
<27>Jul 30 20:39:57 node-3 ntpdate[30293]: no servers can be used, exiting
<27>Jul 30 20:40:28 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:47 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:47 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:47 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:47 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:47 node-3 multipathd: uevent trigger error
<27>Jul 30 20:40:47 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:41:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:02 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 20:42:02 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 30 20:42:08 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 20:42:08 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 30 20:42:14 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 30 20:42:19 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 20:42:19 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 30 20:42:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:39 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:39 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:39 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:39 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:39 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:39 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:39 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:45 node-3 multipathd: uevent trigger error
<129>Jul 30 20:42:47 node-3 haproxy[19967]: Server mysqld/node-3 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 30 20:42:47 node-3 haproxy[19967]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:42:48 node-3 haproxy[19978]: 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 30 20:42:48 node-3 haproxy[19978]: proxy mysqld has no server available!
<27>Jul 30 20:42:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:54 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:54 node-3 multipathd: uevent trigger error
<129>Jul 30 20:42:56 node-3 haproxy[22587]: Server mysqld/node-3 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 30 20:42:56 node-3 haproxy[22587]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:42:56 node-3 haproxy[22587]: 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 30 20:42:56 node-3 haproxy[22587]: proxy mysqld has no server available!
<129>Jul 30 20:42:57 node-3 haproxy[22591]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:42:57 node-3 haproxy[22591]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:42:57 node-3 haproxy[22591]: 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 30 20:42:57 node-3 haproxy[22591]: proxy object-storage has no server available!
<27>Jul 30 20:42:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:01 node-3 haproxy[24065]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:02 node-3 haproxy[24069]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:02 node-3 haproxy[24069]: 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 30 20:43:02 node-3 haproxy[24069]: proxy neutron has no server available!
<129>Jul 30 20:43:02 node-3 haproxy[24069]: Server mysqld/node-3 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 30 20:43:02 node-3 haproxy[24069]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:02 node-3 haproxy[24069]: 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 30 20:43:02 node-3 haproxy[24069]: proxy mysqld has no server available!
<129>Jul 30 20:43:02 node-3 haproxy[24069]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:03 node-3 haproxy[24069]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:03 node-3 haproxy[24069]: 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 30 20:43:03 node-3 haproxy[24069]: proxy object-storage has no server available!
<27>Jul 30 20:43:04 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:05 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:05 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:05 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:05 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:07 node-3 haproxy[25672]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:07 node-3 haproxy[25672]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:07 node-3 haproxy[25672]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:07 node-3 haproxy[25672]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:07 node-3 haproxy[25672]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:07 node-3 haproxy[25672]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:08 node-3 haproxy[25676]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:08 node-3 haproxy[25676]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:08 node-3 haproxy[25676]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:08 node-3 haproxy[25676]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:08 node-3 haproxy[25676]: 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 30 20:43:08 node-3 haproxy[25676]: proxy neutron has no server available!
<129>Jul 30 20:43:08 node-3 haproxy[25676]: Server mysqld/node-3 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 30 20:43:08 node-3 haproxy[25676]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:08 node-3 haproxy[25676]: 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 30 20:43:08 node-3 haproxy[25676]: proxy mysqld has no server available!
<129>Jul 30 20:43:08 node-3 haproxy[25676]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:08 node-3 haproxy[25676]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:09 node-3 haproxy[25676]: 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 30 20:43:09 node-3 haproxy[25676]: proxy object-storage has no server available!
<27>Jul 30 20:43:10 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:10 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:10 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:10 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:10 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:10 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:12 node-3 haproxy[27070]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:12 node-3 haproxy[27070]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:12 node-3 haproxy[27070]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:12 node-3 haproxy[27070]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:13 node-3 haproxy[27076]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:13 node-3 haproxy[27076]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:13 node-3 haproxy[27076]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:13 node-3 haproxy[27076]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:13 node-3 haproxy[27076]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:13 node-3 haproxy[27076]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:13 node-3 haproxy[27076]: 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 30 20:43:13 node-3 haproxy[27076]: proxy neutron has no server available!
<129>Jul 30 20:43:13 node-3 haproxy[27076]: Server mysqld/node-3 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 30 20:43:13 node-3 haproxy[27076]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:13 node-3 haproxy[27076]: 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 30 20:43:13 node-3 haproxy[27076]: proxy mysqld has no server available!
<129>Jul 30 20:43:13 node-3 haproxy[27076]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:14 node-3 haproxy[27076]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:14 node-3 haproxy[27076]: 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 30 20:43:14 node-3 haproxy[27076]: proxy object-storage has no server available!
<129>Jul 30 20:43:14 node-3 haproxy[27076]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:14 node-3 haproxy[27076]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:14 node-3 haproxy[27076]: 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 30 20:43:14 node-3 haproxy[27076]: proxy aodh has no server available!
<27>Jul 30 20:43:15 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:15 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:16 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:16 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:16 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:18 node-3 haproxy[28478]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:18 node-3 haproxy[28478]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:18 node-3 haproxy[28478]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:18 node-3 haproxy[28478]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:18 node-3 haproxy[28478]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:18 node-3 haproxy[28478]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:18 node-3 haproxy[28478]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:18 node-3 haproxy[28478]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:18 node-3 haproxy[28478]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:18 node-3 haproxy[28478]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:18 node-3 haproxy[28478]: 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 30 20:43:18 node-3 haproxy[28478]: proxy neutron has no server available!
<129>Jul 30 20:43:18 node-3 haproxy[28478]: Server mysqld/node-3 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 30 20:43:18 node-3 haproxy[28478]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:18 node-3 haproxy[28478]: 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 30 20:43:18 node-3 haproxy[28478]: proxy mysqld has no server available!
<129>Jul 30 20:43:19 node-3 haproxy[28482]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:19 node-3 haproxy[28482]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:19 node-3 haproxy[28482]: 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 30 20:43:19 node-3 haproxy[28482]: proxy object-storage has no server available!
<129>Jul 30 20:43:19 node-3 haproxy[28482]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:19 node-3 haproxy[28482]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:19 node-3 haproxy[28482]: 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 30 20:43:19 node-3 haproxy[28482]: proxy aodh has no server available!
<129>Jul 30 20:43:19 node-3 haproxy[28482]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:19 node-3 haproxy[28482]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:19 node-3 haproxy[28482]: 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 30 20:43:19 node-3 haproxy[28482]: proxy ceilometer has no server available!
<27>Jul 30 20:43:21 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:23 node-3 haproxy[30077]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:23 node-3 haproxy[30077]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:23 node-3 haproxy[30077]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:23 node-3 haproxy[30077]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:23 node-3 haproxy[30077]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:23 node-3 haproxy[30077]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:23 node-3 haproxy[30077]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:23 node-3 haproxy[30077]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:23 node-3 haproxy[30077]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:24 node-3 haproxy[30091]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:24 node-3 haproxy[30091]: 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 30 20:43:24 node-3 haproxy[30091]: proxy neutron has no server available!
<129>Jul 30 20:43:24 node-3 haproxy[30091]: Server mysqld/node-3 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 30 20:43:24 node-3 haproxy[30091]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:24 node-3 haproxy[30091]: 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 30 20:43:24 node-3 haproxy[30091]: proxy mysqld has no server available!
<129>Jul 30 20:43:24 node-3 haproxy[30091]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:24 node-3 haproxy[30091]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:24 node-3 haproxy[30091]: 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 30 20:43:24 node-3 haproxy[30091]: proxy object-storage has no server available!
<129>Jul 30 20:43:24 node-3 haproxy[30091]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:24 node-3 haproxy[30091]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:24 node-3 haproxy[30091]: 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 30 20:43:24 node-3 haproxy[30091]: proxy aodh has no server available!
<129>Jul 30 20:43:25 node-3 haproxy[30091]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:25 node-3 haproxy[30091]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:25 node-3 haproxy[30091]: 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 30 20:43:25 node-3 haproxy[30091]: proxy ceilometer has no server available!
<27>Jul 30 20:43:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:28 node-3 haproxy[31511]: Server horizon/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:29 node-3 haproxy[31520]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:29 node-3 haproxy[31520]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:29 node-3 haproxy[31520]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:29 node-3 haproxy[31520]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:29 node-3 haproxy[31520]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:29 node-3 haproxy[31520]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:29 node-3 haproxy[31520]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:29 node-3 haproxy[31520]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:29 node-3 haproxy[31520]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:29 node-3 haproxy[31520]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:29 node-3 haproxy[31520]: 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 30 20:43:29 node-3 haproxy[31520]: proxy neutron has no server available!
<129>Jul 30 20:43:29 node-3 haproxy[31520]: Server mysqld/node-3 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 30 20:43:29 node-3 haproxy[31520]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:29 node-3 haproxy[31520]: 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 30 20:43:29 node-3 haproxy[31520]: proxy mysqld has no server available!
<129>Jul 30 20:43:30 node-3 haproxy[31520]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:30 node-3 haproxy[31520]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:30 node-3 haproxy[31520]: 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 30 20:43:30 node-3 haproxy[31520]: proxy object-storage has no server available!
<129>Jul 30 20:43:30 node-3 haproxy[31520]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:30 node-3 haproxy[31520]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:30 node-3 haproxy[31520]: 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 30 20:43:30 node-3 haproxy[31520]: proxy aodh has no server available!
<129>Jul 30 20:43:30 node-3 haproxy[31520]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:30 node-3 haproxy[31520]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:30 node-3 haproxy[31520]: 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 30 20:43:30 node-3 haproxy[31520]: proxy ceilometer has no server available!
<27>Jul 30 20:43:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:32 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:32 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:34 node-3 haproxy[555]: Server horizon/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:35 node-3 haproxy[559]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:35 node-3 haproxy[559]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:35 node-3 haproxy[559]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:35 node-3 haproxy[559]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:35 node-3 haproxy[559]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:35 node-3 haproxy[559]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:35 node-3 haproxy[559]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:35 node-3 haproxy[559]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:35 node-3 haproxy[559]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:35 node-3 haproxy[559]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:35 node-3 haproxy[559]: 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 30 20:43:35 node-3 haproxy[559]: proxy glance-api has no server available!
<129>Jul 30 20:43:35 node-3 haproxy[559]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:35 node-3 haproxy[559]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:35 node-3 haproxy[559]: 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 30 20:43:35 node-3 haproxy[559]: proxy glance-glare has no server available!
<129>Jul 30 20:43:35 node-3 haproxy[559]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:35 node-3 haproxy[559]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:35 node-3 haproxy[559]: 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 30 20:43:35 node-3 haproxy[559]: proxy neutron has no server available!
<129>Jul 30 20:43:35 node-3 haproxy[559]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:36 node-3 haproxy[559]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:36 node-3 haproxy[559]: 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 30 20:43:36 node-3 haproxy[559]: proxy glance-registry has no server available!
<129>Jul 30 20:43:36 node-3 haproxy[559]: Server mysqld/node-3 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 30 20:43:36 node-3 haproxy[559]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:36 node-3 haproxy[559]: 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 30 20:43:36 node-3 haproxy[559]: proxy mysqld has no server available!
<129>Jul 30 20:43:36 node-3 haproxy[559]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:36 node-3 haproxy[559]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:36 node-3 haproxy[559]: 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 30 20:43:36 node-3 haproxy[559]: proxy object-storage has no server available!
<129>Jul 30 20:43:36 node-3 haproxy[559]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:36 node-3 haproxy[559]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:36 node-3 haproxy[559]: 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 30 20:43:36 node-3 haproxy[559]: proxy aodh has no server available!
<129>Jul 30 20:43:36 node-3 haproxy[559]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:36 node-3 haproxy[559]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:36 node-3 haproxy[559]: 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 30 20:43:36 node-3 haproxy[559]: proxy ceilometer has no server available!
<27>Jul 30 20:43:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:38 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:40 node-3 haproxy[2041]: Server horizon/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:40 node-3 haproxy[2041]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:41 node-3 haproxy[2048]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:41 node-3 haproxy[2048]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server nova-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:41 node-3 haproxy[2048]: 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 30 20:43:41 node-3 haproxy[2048]: proxy nova-api has no server available!
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:41 node-3 haproxy[2048]: 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 30 20:43:41 node-3 haproxy[2048]: proxy nova-metadata-api has no server available!
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:41 node-3 haproxy[2048]: 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 30 20:43:41 node-3 haproxy[2048]: proxy glance-api has no server available!
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:41 node-3 haproxy[2048]: 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 30 20:43:41 node-3 haproxy[2048]: proxy glance-glare has no server available!
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:41 node-3 haproxy[2048]: 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 30 20:43:41 node-3 haproxy[2048]: proxy neutron has no server available!
<129>Jul 30 20:43:41 node-3 haproxy[2048]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:41 node-3 haproxy[2048]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:42 node-3 haproxy[2048]: 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 30 20:43:42 node-3 haproxy[2048]: proxy glance-registry has no server available!
<129>Jul 30 20:43:42 node-3 haproxy[2048]: Server mysqld/node-3 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 30 20:43:42 node-3 haproxy[2048]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:42 node-3 haproxy[2048]: 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 30 20:43:42 node-3 haproxy[2048]: proxy mysqld has no server available!
<129>Jul 30 20:43:42 node-3 haproxy[2048]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:42 node-3 haproxy[2048]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:42 node-3 haproxy[2048]: 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 30 20:43:42 node-3 haproxy[2048]: proxy object-storage has no server available!
<129>Jul 30 20:43:42 node-3 haproxy[2048]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:42 node-3 haproxy[2048]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:42 node-3 haproxy[2048]: 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 30 20:43:42 node-3 haproxy[2048]: proxy aodh has no server available!
<129>Jul 30 20:43:42 node-3 haproxy[2048]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:42 node-3 haproxy[2048]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:42 node-3 haproxy[2048]: 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 30 20:43:42 node-3 haproxy[2048]: proxy ceilometer has no server available!
<129>Jul 30 20:43:42 node-3 haproxy[2048]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:42 node-3 haproxy[2048]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:42 node-3 haproxy[2048]: 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 30 20:43:42 node-3 haproxy[2048]: proxy nova-novncproxy has no server available!
<27>Jul 30 20:43:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:44 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:44 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:46 node-3 haproxy[3482]: Server horizon/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:46 node-3 haproxy[3482]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:46 node-3 haproxy[3482]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:46 node-3 haproxy[3482]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:46 node-3 haproxy[3482]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:46 node-3 haproxy[3482]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:46 node-3 haproxy[3482]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:46 node-3 haproxy[3482]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:46 node-3 haproxy[3482]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:46 node-3 haproxy[3482]: Server nova-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:46 node-3 haproxy[3482]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:46 node-3 haproxy[3482]: 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 30 20:43:46 node-3 haproxy[3482]: proxy nova-api has no server available!
<129>Jul 30 20:43:46 node-3 haproxy[3482]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:46 node-3 haproxy[3482]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy nova-metadata-api has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server cinder-api/node-3 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 30 20:43:47 node-3 haproxy[3486]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy cinder-api has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:47 node-3 haproxy[3486]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy glance-api has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:47 node-3 haproxy[3486]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy glance-glare has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:47 node-3 haproxy[3486]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy neutron has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:47 node-3 haproxy[3486]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy glance-registry has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server mysqld/node-3 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 30 20:43:47 node-3 haproxy[3486]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy mysqld has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:47 node-3 haproxy[3486]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:47 node-3 haproxy[3486]: 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 30 20:43:47 node-3 haproxy[3486]: proxy object-storage has no server available!
<129>Jul 30 20:43:47 node-3 haproxy[3486]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:47 node-3 haproxy[3486]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:48 node-3 haproxy[3486]: 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 30 20:43:48 node-3 haproxy[3486]: proxy aodh has no server available!
<129>Jul 30 20:43:48 node-3 haproxy[3486]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:48 node-3 haproxy[3486]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:48 node-3 haproxy[3486]: 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 30 20:43:48 node-3 haproxy[3486]: proxy ceilometer has no server available!
<129>Jul 30 20:43:48 node-3 haproxy[3486]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:48 node-3 haproxy[3486]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:48 node-3 haproxy[3486]: 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 30 20:43:48 node-3 haproxy[3486]: proxy nova-novncproxy has no server available!
<27>Jul 30 20:43:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:49 node-3 multipathd: uevent trigger error
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server horizon/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:52 node-3 haproxy[4993]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:52 node-3 haproxy[4993]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:52 node-3 haproxy[4993]: proxy keystone-1 has no server available!
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:52 node-3 haproxy[4993]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:52 node-3 haproxy[4993]: proxy keystone-2 has no server available!
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server nova-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:52 node-3 haproxy[4993]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:52 node-3 haproxy[4993]: 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 30 20:43:52 node-3 haproxy[4993]: proxy nova-api has no server available!
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:52 node-3 haproxy[4993]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:52 node-3 haproxy[4993]: 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 30 20:43:52 node-3 haproxy[4993]: proxy nova-metadata-api has no server available!
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server cinder-api/node-3 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 30 20:43:52 node-3 haproxy[4993]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:52 node-3 haproxy[4993]: 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 30 20:43:52 node-3 haproxy[4993]: proxy cinder-api has no server available!
<129>Jul 30 20:43:52 node-3 haproxy[4993]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy glance-api has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy glance-glare has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy neutron has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy glance-registry has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server mysqld/node-3 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 30 20:43:53 node-3 haproxy[5000]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy mysqld has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy object-storage has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy aodh has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy ceilometer has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server heat-api/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:53 node-3 haproxy[5000]: 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 30 20:43:53 node-3 haproxy[5000]: proxy heat-api has no server available!
<129>Jul 30 20:43:53 node-3 haproxy[5000]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:53 node-3 haproxy[5000]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:54 node-3 haproxy[5000]: 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 30 20:43:54 node-3 haproxy[5000]: proxy heat-api-cfn has no server available!
<129>Jul 30 20:43:54 node-3 haproxy[5000]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:54 node-3 haproxy[5000]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:54 node-3 haproxy[5000]: 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 30 20:43:54 node-3 haproxy[5000]: proxy heat-api-cloudwatch has no server available!
<129>Jul 30 20:43:54 node-3 haproxy[5000]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection 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 30 20:43:54 node-3 haproxy[5000]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:54 node-3 haproxy[5000]: 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 30 20:43:54 node-3 haproxy[5000]: proxy nova-novncproxy has no server available!
<27>Jul 30 20:43:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:43:59 node-3 multipathd: uevent trigger error
<27>Jul 30 20:44:10 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 30 20:44:36 node-3 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 30 20:44:38 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 30 20:45:07 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 20:45:10 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 20:45:42 node-3 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-3 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-3 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-3 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:09 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 20:48:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:12 node-3 multipathd: uevent trigger error
<43>Jul 30 20:48:32 node-3 apache2_error [Sat Jul 30 20:48:26.414179 2016] [mpm_event:notice] [pid 19543:tid 140133136578432] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 20:48:32 node-3 apache2_error [Sat Jul 30 20:48:26.414304 2016] [core:notice] [pid 19543:tid 140133136578432] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 20:48:32 node-3 apache2_error [Sat Jul 30 20:48:29.611676 2016] [mpm_event:notice] [pid 19543:tid 140133136578432] AH00491: caught SIGTERM, shutting down
<43>Jul 30 20:48:32 node-3 apache2_error [Sat Jul 30 20:48:30.698002 2016] [mpm_worker:notice] [pid 19909:tid 139942976944000] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 20:48:32 node-3 apache2_error [Sat Jul 30 20:48:30.698032 2016] [core:notice] [pid 19909:tid 139942976944000] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 20:48:35 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:35 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:35 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:35 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:35 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:38 node-3 multipathd: uevent trigger error
<27>Jul 30 20:48:38 node-3 multipathd: uevent trigger error
<43>Jul 30 20:50:02 node-3 apache2_error [Sat Jul 30 20:49:53.600256 2016] [mpm_worker:notice] [pid 19909:tid 139942976944000] AH00295: caught SIGTERM, shutting down
<43>Jul 30 20:50:02 node-3 apache2_error [Sat Jul 30 20:49:54.365402 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 20:50:02 node-3 apache2_error [Sat Jul 30 20:49:54.365446 2016] [core:notice] [pid 2434:tid 139676071655296] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 20:50:42 node-3 apache2_error [Sat Jul 30 20:50:40.215733 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 20:50:42 node-3 apache2_error [Sat Jul 30 20:50:40.410950 2016] [mpm_worker:warn] [pid 2434:tid 139676071655296] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 20:50:42 node-3 apache2_error [Sat Jul 30 20:50:40.414096 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 20:50:42 node-3 apache2_error [Sat Jul 30 20:50:40.414110 2016] [core:notice] [pid 2434:tid 139676071655296] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 20:51:11 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 20:51:24 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:45 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:46 node-3 multipathd: uevent trigger error
<27>Jul 30 20:51:46 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:07 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:52:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:00 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:19 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:19 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:19 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:19 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:19 node-3 multipathd: uevent trigger error
<27>Jul 30 20:53:19 node-3 multipathd: uevent trigger error
<27>Jul 30 20:54:12 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 20:54:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:54:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:54:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:54:12 node-3 multipathd: uevent trigger error
<27>Jul 30 20:54:13 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:55:27 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:29 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:51 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:57 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:57 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:57 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:57 node-3 multipathd: uevent trigger error
<27>Jul 30 20:56:57 node-3 multipathd: uevent trigger error
<27>Jul 30 20:57:14 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 20:59:34 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:34 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:34 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:34 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:34 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:34 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:49 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:50 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:55 node-3 multipathd: uevent trigger error
<27>Jul 30 20:59:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:16 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 21:00:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:00:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:01:11 node-3 multipathd: uevent trigger error
<27>Jul 30 21:01:11 node-3 multipathd: uevent trigger error
<27>Jul 30 21:01:11 node-3 multipathd: uevent trigger error
<27>Jul 30 21:01:11 node-3 multipathd: uevent trigger error
<27>Jul 30 21:01:11 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:16 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:16 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:16 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:16 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:16 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:02:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:03:17 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 21:05:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:44 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:44 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:44 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:44 node-3 multipathd: uevent trigger error
<27>Jul 30 21:05:44 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:19 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 21:06:34 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:34 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:34 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:34 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:34 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:54 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:54 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:54 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:55 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:55 node-3 multipathd: uevent trigger error
<27>Jul 30 21:06:55 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:01 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:07:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:54 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:54 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:54 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:54 node-3 multipathd: uevent trigger error
<27>Jul 30 21:08:54 node-3 multipathd: uevent trigger error
<11>Jul 30 21:09:08 node-3 liberasurecode[28899]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:08 node-3 liberasurecode[28899]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:08 node-3 liberasurecode[28899]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:08 node-3 liberasurecode[28899]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:08 node-3 liberasurecode[28929]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:08 node-3 liberasurecode[28929]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:08 node-3 liberasurecode[28929]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:08 node-3 liberasurecode[28929]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:10 node-3 liberasurecode[29405]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:10 node-3 liberasurecode[29405]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:10 node-3 liberasurecode[29405]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:10 node-3 liberasurecode[29405]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30225]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30225]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30225]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30225]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30266]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30266]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30266]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30266]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30306]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30306]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30306]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30306]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30373]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30373]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30373]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:16 node-3 liberasurecode[30373]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30387]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30387]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30387]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30387]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30400]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30400]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30400]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30400]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30430]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30430]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30430]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:17 node-3 liberasurecode[30430]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 21:09:20 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 30 21:09:33 node-3 liberasurecode[494]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:33 node-3 liberasurecode[494]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:33 node-3 liberasurecode[494]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:33 node-3 liberasurecode[494]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 21:09:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:09:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:09:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:09:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:09:42 node-3 multipathd: uevent trigger error
<27>Jul 30 21:09:42 node-3 multipathd: uevent trigger error
<11>Jul 30 21:10:01 node-3 liberasurecode[4855]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:10:01 node-3 liberasurecode[4855]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:10:01 node-3 liberasurecode[4855]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:10:01 node-3 liberasurecode[4855]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Jul 30 21:10:34 node-3 apache2_error [Sat Jul 30 21:10:29.233061 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 21:10:34 node-3 apache2_error [Sat Jul 30 21:10:29.616890 2016] [mpm_worker:warn] [pid 2434:tid 139676071655296] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 21:10:34 node-3 apache2_error [Sat Jul 30 21:10:29.623722 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 21:10:34 node-3 apache2_error [Sat Jul 30 21:10:29.623746 2016] [core:notice] [pid 2434:tid 139676071655296] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 21:11:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:10 node-3 multipathd: uevent trigger error
<43>Jul 30 21:11:14 node-3 apache2_error [Sat Jul 30 21:11:06.496839 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 21:11:14 node-3 apache2_error [Sat Jul 30 21:11:06.692506 2016] [mpm_worker:warn] [pid 2434:tid 139676071655296] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 21:11:14 node-3 apache2_error [Sat Jul 30 21:11:06.704019 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 21:11:14 node-3 apache2_error [Sat Jul 30 21:11:06.704049 2016] [core:notice] [pid 2434:tid 139676071655296] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 21:11:18 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:18 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:18 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:18 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:18 node-3 multipathd: uevent trigger error
<43>Jul 30 21:11:54 node-3 apache2_error [Sat Jul 30 21:11:52.242840 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 21:11:54 node-3 apache2_error [Sat Jul 30 21:11:52.442115 2016] [mpm_worker:warn] [pid 2434:tid 139676071655296] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 21:11:54 node-3 apache2_error [Sat Jul 30 21:11:52.454287 2016] [mpm_worker:notice] [pid 2434:tid 139676071655296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 21:11:54 node-3 apache2_error [Sat Jul 30 21:11:52.454318 2016] [core:notice] [pid 2434:tid 139676071655296] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 21:11:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:11:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:03 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:08 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:08 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:08 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:08 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:08 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:08 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:22 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 30 21:12:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:25 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:49 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:12:56 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:03 node-3 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 30 21:13:12 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:12 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:12 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:12 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:12 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:12 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:22 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:27 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:27 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:27 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:27 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:27 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:27 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:38 node-3 multipathd: uevent trigger error
<27>Jul 30 21:13:41 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 21:14:06 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:10 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:23 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:23 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:23 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:23 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:23 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:30 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:30 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:30 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:30 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:30 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:48 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:48 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:48 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:48 node-3 multipathd: uevent trigger error
<27>Jul 30 21:14:48 node-3 multipathd: uevent trigger error
<11>Jul 30 21:15:01 node-3 liberasurecode[9445]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:15:01 node-3 liberasurecode[9445]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:15:01 node-3 liberasurecode[9445]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:15:01 node-3 liberasurecode[9445]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 21:15:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:17 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:21 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:21 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:21 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:21 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:21 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:26 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:26 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:26 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:26 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:26 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:30 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:31 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:35 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:41 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:41 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:41 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:41 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:41 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:45 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:45 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:45 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:45 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:45 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:50 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:50 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:50 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:50 node-3 multipathd: uevent trigger error
<27>Jul 30 21:15:50 node-3 multipathd: uevent trigger error
