Sep 26 05:27:36 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8429" x-info="http://www.rsyslog.com"] start
Sep 26 05:27:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 26 05:27:36 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep 26 05:27:36 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep 26 05:27:36 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 26 05:27:36 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 26 05:27:36 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 26 05:27:36 node-2 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Sep 26 05:27:36 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=2bea9d59-f45e-4348-9c6c-c77e145971e4 nomdmonddf nomdmonisw
Sep 26 05:27:36 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep 26 05:27:36 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep 26 05:27:36 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep 26 05:27:36 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep 26 05:27:36 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 26 05:27:36 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 26 05:27:36 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 26 05:27:36 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Sep 26 05:27:36 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 26 05:27:36 node-2 kernel: [    0.000000] No AGP bridge found
Sep 26 05:27:36 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 26 05:27:36 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep 26 05:27:36 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 26 05:27:36 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep 26 05:27:36 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 26 05:27:36 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 26 05:27:36 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 26 05:27:36 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 26 05:27:36 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 26 05:27:36 node-2 kernel: [    0.000000]   2 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000]   3 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000]   4 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000]   5 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000]   6 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000]   7 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000]   8 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000]   9 disabled
Sep 26 05:27:36 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 26 05:27:36 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 26 05:27:36 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 26 05:27:36 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 26 05:27:36 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 26 05:27:36 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 26 05:27:36 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 26 05:27:36 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 26 05:27:36 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 26 05:27:36 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 26 05:27:36 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 26 05:27:36 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 26 05:27:36 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 26 05:27:36 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 26 05:27:36 node-2 kernel: [    0.000000] Zone ranges:
Sep 26 05:27:36 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] Movable zone start for each node
Sep 26 05:27:36 node-2 kernel: [    0.000000] Early memory node ranges
Sep 26 05:27:36 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 26 05:27:36 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 26 05:27:36 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 26 05:27:36 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 26 05:27:36 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 26 05:27:36 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 26 05:27:36 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 26 05:27:36 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 26 05:27:36 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 26 05:27:36 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 26 05:27:36 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 26 05:27:36 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 26 05:27:36 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 26 05:27:36 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 26 05:27:36 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 26 05:27:36 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 26 05:27:36 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 26 05:27:36 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 26 05:27:36 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 26 05:27:36 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 26 05:27:36 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 26 05:27:36 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 26 05:27:36 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 26 05:27:36 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Sep 26 05:27:36 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 26 05:27:36 node-2 kernel: [    0.000000] Policy zone: Normal
Sep 26 05:27:36 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=2bea9d59-f45e-4348-9c6c-c77e145971e4 nomdmonddf nomdmonisw
Sep 26 05:27:36 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 26 05:27:36 node-2 kernel: [    0.000000] Checking aperture...
Sep 26 05:27:36 node-2 kernel: [    0.000000] No AGP bridge found
Sep 26 05:27:36 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 26 05:27:36 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 26 05:27:36 node-2 kernel: [    0.000000] Memory: 32653320K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep 26 05:27:36 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 26 05:27:36 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 26 05:27:36 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 26 05:27:36 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 26 05:27:36 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 26 05:27:36 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 26 05:27:36 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 26 05:27:36 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 26 05:27:36 node-2 kernel: [    0.000000] console [tty0] enabled
Sep 26 05:27:36 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 26 05:27:36 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 26 05:27:36 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 26 05:27:36 node-2 kernel: [    0.000000] hpet clockevent registered
Sep 26 05:27:36 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 26 05:27:36 node-2 kernel: [    0.004000] tsc: Detected 3491.699 MHz processor
Sep 26 05:27:36 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.39 BogoMIPS (lpj=13966796)
Sep 26 05:27:36 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 26 05:27:36 node-2 kernel: [    0.000047] Security Framework initialized
Sep 26 05:27:36 node-2 kernel: [    0.000064] AppArmor: AppArmor initialized
Sep 26 05:27:36 node-2 kernel: [    0.000066] Yama: becoming mindful.
Sep 26 05:27:36 node-2 kernel: [    0.001450] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.006354] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.008282] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.008309] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.008600] Initializing cgroup subsys memory
Sep 26 05:27:36 node-2 kernel: [    0.008608] Initializing cgroup subsys devices
Sep 26 05:27:36 node-2 kernel: [    0.008610] Initializing cgroup subsys freezer
Sep 26 05:27:36 node-2 kernel: [    0.008612] Initializing cgroup subsys blkio
Sep 26 05:27:36 node-2 kernel: [    0.008614] Initializing cgroup subsys perf_event
Sep 26 05:27:36 node-2 kernel: [    0.008616] Initializing cgroup subsys hugetlb
Sep 26 05:27:36 node-2 kernel: [    0.008635] CPU: Physical Processor ID: 0
Sep 26 05:27:36 node-2 kernel: [    0.008637] CPU: Processor Core ID: 0
Sep 26 05:27:36 node-2 kernel: [    0.008640] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 26 05:27:36 node-2 kernel: [    0.008640] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 26 05:27:36 node-2 kernel: [    0.009334] mce: CPU supports 22 MCE banks
Sep 26 05:27:36 node-2 kernel: [    0.009362] CPU0: Thermal monitoring enabled (TM1)
Sep 26 05:27:36 node-2 kernel: [    0.009382] process: using mwait in idle threads
Sep 26 05:27:36 node-2 kernel: [    0.009385] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 26 05:27:36 node-2 kernel: [    0.009385] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 26 05:27:36 node-2 kernel: [    0.009385] tlb_flushall_shift: 6
Sep 26 05:27:36 node-2 kernel: [    0.009473] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 26 05:27:36 node-2 kernel: [    0.010200] ACPI: Core revision 20131115
Sep 26 05:27:36 node-2 kernel: [    0.022866] ACPI: All ACPI Tables successfully acquired
Sep 26 05:27:36 node-2 kernel: [    0.023029] ftrace: allocating 28614 entries in 112 pages
Sep 26 05:27:36 node-2 kernel: [    0.031743] dmar: Host address width 46
Sep 26 05:27:36 node-2 kernel: [    0.031746] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 26 05:27:36 node-2 kernel: [    0.031751] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 26 05:27:36 node-2 kernel: [    0.031753] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 26 05:27:36 node-2 kernel: [    0.031757] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 26 05:27:36 node-2 kernel: [    0.031758] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 26 05:27:36 node-2 kernel: [    0.031760] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 26 05:27:36 node-2 kernel: [    0.031761] dmar: ATSR flags: 0x0
Sep 26 05:27:36 node-2 kernel: [    0.031762] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 26 05:27:36 node-2 kernel: [    0.031763] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 26 05:27:36 node-2 kernel: [    0.031879] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 26 05:27:36 node-2 kernel: [    0.031880] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 26 05:27:36 node-2 kernel: [    0.031881] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 26 05:27:36 node-2 kernel: [    0.031882] HPET id 0 under DRHD base 0xc7ffc000
Sep 26 05:27:36 node-2 kernel: [    0.031884] Your BIOS is broken and requested that x2apic be disabled.
Sep 26 05:27:36 node-2 kernel: [    0.031884] This will slightly decrease performance.
Sep 26 05:27:36 node-2 kernel: [    0.031884] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 26 05:27:36 node-2 kernel: [    0.032317] Enabled IRQ remapping in xapic mode
Sep 26 05:27:36 node-2 kernel: [    0.032318] x2apic not enabled, IRQ remapping is in xapic mode
Sep 26 05:27:36 node-2 kernel: [    0.032322] Switched APIC routing to physical flat.
Sep 26 05:27:36 node-2 kernel: [    0.032948] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 26 05:27:36 node-2 kernel: [    0.072595] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 26 05:27:36 node-2 kernel: [    0.072601] TSC deadline timer enabled
Sep 26 05:27:36 node-2 kernel: [    0.072609] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 26 05:27:36 node-2 kernel: [    0.072615] ... version:                3
Sep 26 05:27:36 node-2 kernel: [    0.072615] ... bit width:              48
Sep 26 05:27:36 node-2 kernel: [    0.072616] ... generic registers:      4
Sep 26 05:27:36 node-2 kernel: [    0.072617] ... value mask:             0000ffffffffffff
Sep 26 05:27:36 node-2 kernel: [    0.072618] ... max period:             0000ffffffffffff
Sep 26 05:27:36 node-2 kernel: [    0.072619] ... fixed-purpose events:   3
Sep 26 05:27:36 node-2 kernel: [    0.072620] ... event mask:             000000070000000f
Sep 26 05:27:36 node-2 kernel: [    0.074008] x86: Booting SMP configuration:
Sep 26 05:27:36 node-2 kernel: [    0.088111] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 26 05:27:36 node-2 kernel: [    0.074009] .... node  #0, CPUs:        #1  #2  #3
Sep 26 05:27:36 node-2 kernel: [    0.116016] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 26 05:27:36 node-2 kernel: [    0.270142] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 26 05:27:36 node-2 kernel: [    0.325775] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 26 05:27:36 node-2 kernel: [    0.382830] x86: Booted up 2 nodes, 16 CPUs
Sep 26 05:27:36 node-2 kernel: [    0.382833] smpboot: Total of 16 processors activated (111768.54 BogoMIPS)
Sep 26 05:27:36 node-2 kernel: [    0.407488] devtmpfs: initialized
Sep 26 05:27:36 node-2 kernel: [    0.409849] EVM: security.selinux
Sep 26 05:27:36 node-2 kernel: [    0.409851] EVM: security.SMACK64
Sep 26 05:27:36 node-2 kernel: [    0.409852] EVM: security.ima
Sep 26 05:27:36 node-2 kernel: [    0.409853] EVM: security.capability
Sep 26 05:27:36 node-2 kernel: [    0.409904] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.410563] pinctrl core: initialized pinctrl subsystem
Sep 26 05:27:36 node-2 kernel: [    0.410627] regulator-dummy: no parameters
Sep 26 05:27:36 node-2 kernel: [    0.410658] RTC time:  5:27:00, date: 09/26/16
Sep 26 05:27:36 node-2 kernel: [    0.410693] NET: Registered protocol family 16
Sep 26 05:27:36 node-2 kernel: [    0.410778] cpuidle: using governor ladder
Sep 26 05:27:36 node-2 kernel: [    0.410779] cpuidle: using governor menu
Sep 26 05:27:36 node-2 kernel: [    0.410816] ACPI: bus type PCI registered
Sep 26 05:27:36 node-2 kernel: [    0.410818] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 26 05:27:36 node-2 kernel: [    0.410866] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 26 05:27:36 node-2 kernel: [    0.410868] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 26 05:27:36 node-2 kernel: [    0.424629] PCI: Using configuration type 1 for base access
Sep 26 05:27:36 node-2 kernel: [    0.425629] bio: create slab <bio-0> at 0
Sep 26 05:27:36 node-2 kernel: [    0.425910] ACPI: Added _OSI(Module Device)
Sep 26 05:27:36 node-2 kernel: [    0.425911] ACPI: Added _OSI(Processor Device)
Sep 26 05:27:36 node-2 kernel: [    0.425913] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 26 05:27:36 node-2 kernel: [    0.425914] ACPI: Added _OSI(Processor Aggregator Device)
Sep 26 05:27:36 node-2 kernel: [    0.438701] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 26 05:27:36 node-2 kernel: [    0.449167] ACPI: Interpreter enabled
Sep 26 05:27:36 node-2 kernel: [    0.449172] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 26 05:27:36 node-2 kernel: [    0.449176] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 26 05:27:36 node-2 kernel: [    0.449179] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 26 05:27:36 node-2 kernel: [    0.449186] ACPI: (supports S0 S4 S5)
Sep 26 05:27:36 node-2 kernel: [    0.449188] ACPI: Using IOAPIC for interrupt routing
Sep 26 05:27:36 node-2 kernel: [    0.449229] HEST: Table parsing has been initialized.
Sep 26 05:27:36 node-2 kernel: [    0.449232] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 26 05:27:36 node-2 kernel: [    0.449807] ACPI: No dock devices found.
Sep 26 05:27:36 node-2 kernel: [    0.461987] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 26 05:27:36 node-2 kernel: [    0.461992] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 05:27:36 node-2 kernel: [    0.461995] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 26 05:27:36 node-2 kernel: [    0.462021] PCI host bridge to bus 0000:ff
Sep 26 05:27:36 node-2 kernel: [    0.462023] pci_bus 0000:ff: root bus resource [bus ff]
Sep 26 05:27:36 node-2 kernel: [    0.462032] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462070] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.462101] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462135] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462164] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.462193] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.462224] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462252] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462283] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462310] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462336] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462362] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462393] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462420] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462447] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462475] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462505] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462532] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462558] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.462586] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462612] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.462638] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462664] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462694] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.462728] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462759] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462789] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462820] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462850] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462881] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462914] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462946] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.462976] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463006] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463037] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463068] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463099] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463128] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463155] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463186] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463219] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463255] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463288] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463321] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463351] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463381] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463412] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463440] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463472] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463506] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463538] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463567] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463596] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463625] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463654] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463685] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463716] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463774] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 26 05:27:36 node-2 kernel: [    0.463777] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 05:27:36 node-2 kernel: [    0.463780] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 26 05:27:36 node-2 kernel: [    0.463797] PCI host bridge to bus 0000:7f
Sep 26 05:27:36 node-2 kernel: [    0.463799] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 26 05:27:36 node-2 kernel: [    0.463804] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463831] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.463859] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463889] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463910] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.463935] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.463960] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.463986] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464008] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464030] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464052] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464075] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464098] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464120] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464143] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464169] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464191] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464214] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464236] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.464260] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464282] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.464304] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464327] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464353] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 26 05:27:36 node-2 kernel: [    0.464385] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464411] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464438] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464464] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464489] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464515] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464541] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464568] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464594] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464622] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464649] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464677] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464705] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464731] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464755] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464783] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464808] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464834] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464862] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464888] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464912] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464937] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464962] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.464989] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465013] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465040] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465069] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465094] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465116] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465142] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465167] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465198] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.465223] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.466471] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 26 05:27:36 node-2 kernel: [    0.466474] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 05:27:36 node-2 kernel: [    0.467611] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 26 05:27:36 node-2 kernel: [    0.468121] PCI host bridge to bus 0000:00
Sep 26 05:27:36 node-2 kernel: [    0.468123] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 26 05:27:36 node-2 kernel: [    0.468125] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 26 05:27:36 node-2 kernel: [    0.468126] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 26 05:27:36 node-2 kernel: [    0.468127] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 26 05:27:36 node-2 kernel: [    0.468129] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 26 05:27:36 node-2 kernel: [    0.468130] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 26 05:27:36 node-2 kernel: [    0.468132] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 26 05:27:36 node-2 kernel: [    0.468137] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 26 05:27:36 node-2 kernel: [    0.468220] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.468251] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.468292] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 26 05:27:36 node-2 kernel: [    0.468311] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.468340] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.468381] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 26 05:27:36 node-2 kernel: [    0.468399] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.468429] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.468469] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 26 05:27:36 node-2 kernel: [    0.468486] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.468556] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.468634] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.468709] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 26 05:27:36 node-2 kernel: [    0.468714] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 26 05:27:36 node-2 kernel: [    0.468800] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 26 05:27:36 node-2 kernel: [    0.468950] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 26 05:27:36 node-2 kernel: [    0.468968] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 26 05:27:36 node-2 kernel: [    0.469046] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.469102] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 26 05:27:36 node-2 kernel: [    0.469124] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.469180] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.469223] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 26 05:27:36 node-2 kernel: [    0.469254] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.469310] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.469353] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 26 05:27:36 node-2 kernel: [    0.469379] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 26 05:27:36 node-2 kernel: [    0.469396] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 26 05:27:36 node-2 kernel: [    0.469475] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.469525] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 26 05:27:36 node-2 kernel: [    0.469551] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 26 05:27:36 node-2 kernel: [    0.469802] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 26 05:27:36 node-2 kernel: [    0.469808] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 26 05:27:36 node-2 kernel: [    0.469814] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.469820] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.469827] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 26 05:27:36 node-2 kernel: [    0.469857] pci 0000:01:00.0: supports D1 D2
Sep 26 05:27:36 node-2 kernel: [    0.479491] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 26 05:27:36 node-2 kernel: [    0.479497] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 26 05:27:36 node-2 kernel: [    0.479502] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 26 05:27:36 node-2 kernel: [    0.479758] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.479791] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 26 05:27:36 node-2 kernel: [    0.491485] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 26 05:27:36 node-2 kernel: [    0.491491] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.491495] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 05:27:36 node-2 kernel: [    0.491580] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.491653] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.491749] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.491832] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 26 05:27:36 node-2 kernel: [    0.491839] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.491843] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 05:27:36 node-2 kernel: [    0.491931] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.492058] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.492112] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 26 05:27:36 node-2 kernel: [    0.492115] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.492117] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.492166] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.492302] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.492343] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.492466] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.492502] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.492622] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.492659] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 26 05:27:36 node-2 kernel: [    0.492778] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 26 05:27:36 node-2 kernel: [    0.492823] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 26 05:27:36 node-2 kernel: [    0.492825] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.492827] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.492888] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 26 05:27:36 node-2 kernel: [    0.492953] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.493005] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.493046] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 26 05:27:36 node-2 kernel: [    0.493128] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 26 05:27:36 node-2 kernel: [    0.493234] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 26 05:27:36 node-2 kernel: [    0.493237] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.493239] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.493316] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 26 05:27:36 node-2 kernel: [    0.493374] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.493422] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.493637] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 26 05:27:36 node-2 kernel: [    0.493641] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 26 05:27:36 node-2 kernel: [    0.493706] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 26 05:27:36 node-2 kernel: [    0.493759] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.493808] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.494018] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 26 05:27:36 node-2 kernel: [    0.494021] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 26 05:27:36 node-2 kernel: [    0.494080] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 26 05:27:36 node-2 kernel: [    0.494140] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.494192] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 26 05:27:36 node-2 kernel: [    0.494443] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 26 05:27:36 node-2 kernel: [    0.494446] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 26 05:27:36 node-2 kernel: [    0.494626] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 26 05:27:36 node-2 kernel: [    0.494664] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 26 05:27:36 node-2 kernel: [    0.494740] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 26 05:27:36 node-2 kernel: [    0.494759] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 26 05:27:36 node-2 kernel: [    0.494772] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 26 05:27:36 node-2 kernel: [    0.494785] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 26 05:27:36 node-2 kernel: [    0.494836] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 26 05:27:36 node-2 kernel: [    0.503485] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 26 05:27:36 node-2 kernel: [    0.503490] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 26 05:27:36 node-2 kernel: [    0.503522] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 26 05:27:36 node-2 kernel: [    0.504017] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 26 05:27:36 node-2 kernel: [    0.504020] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 26 05:27:36 node-2 kernel: [    0.504140] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 26 05:27:36 node-2 kernel: [    0.504252] PCI host bridge to bus 0000:80
Sep 26 05:27:36 node-2 kernel: [    0.504254] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 26 05:27:36 node-2 kernel: [    0.504256] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 26 05:27:36 node-2 kernel: [    0.504257] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 26 05:27:36 node-2 kernel: [    0.504265] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.504329] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.504399] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 26 05:27:36 node-2 kernel: [    0.504464] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 26 05:27:36 node-2 kernel: [    0.504469] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 26 05:27:36 node-2 kernel: [    0.504540] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 26 05:27:36 node-2 kernel: [    0.504840] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 26 05:27:36 node-2 kernel: [    0.504872] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 26 05:27:36 node-2 kernel: [    0.504902] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 26 05:27:36 node-2 kernel: [    0.504931] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 26 05:27:36 node-2 kernel: [    0.504960] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 05:27:36 node-2 kernel: [    0.504990] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 05:27:36 node-2 kernel: [    0.505021] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 05:27:36 node-2 kernel: [    0.505050] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 26 05:27:36 node-2 kernel: [    0.505137] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 26 05:27:36 node-2 kernel: [    0.505141] ACPI: \_SB_.UNC1: notify handler is installed
Sep 26 05:27:36 node-2 kernel: [    0.505143] ACPI: \_SB_.UNC0: notify handler is installed
Sep 26 05:27:36 node-2 kernel: [    0.505158] ACPI: \_SB_.PCI0: notify handler is installed
Sep 26 05:27:36 node-2 kernel: [    0.505211] ACPI: \_SB_.PCI1: notify handler is installed
Sep 26 05:27:36 node-2 kernel: [    0.505291] Found 4 acpi root devices
Sep 26 05:27:36 node-2 kernel: [    0.505403] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 26 05:27:36 node-2 kernel: [    0.505405] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 26 05:27:36 node-2 kernel: [    0.505407] vgaarb: loaded
Sep 26 05:27:36 node-2 kernel: [    0.505408] vgaarb: bridge control possible 0000:0c:00.0
Sep 26 05:27:36 node-2 kernel: [    0.505528] SCSI subsystem initialized
Sep 26 05:27:36 node-2 kernel: [    0.505594] libata version 3.00 loaded.
Sep 26 05:27:36 node-2 kernel: [    0.505611] ACPI: bus type USB registered
Sep 26 05:27:36 node-2 kernel: [    0.505622] usbcore: registered new interface driver usbfs
Sep 26 05:27:36 node-2 kernel: [    0.505627] usbcore: registered new interface driver hub
Sep 26 05:27:36 node-2 kernel: [    0.505653] usbcore: registered new device driver usb
Sep 26 05:27:36 node-2 kernel: [    0.505822] PCI: Using ACPI for IRQ routing
Sep 26 05:27:36 node-2 kernel: [    0.509451] PCI: pci_cache_line_size set to 64 bytes
Sep 26 05:27:36 node-2 kernel: [    0.509660] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 26 05:27:36 node-2 kernel: [    0.509661] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 26 05:27:36 node-2 kernel: [    0.509662] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 26 05:27:36 node-2 kernel: [    0.509727] NetLabel: Initializing
Sep 26 05:27:36 node-2 kernel: [    0.509729] NetLabel:  domain hash size = 128
Sep 26 05:27:36 node-2 kernel: [    0.509730] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 26 05:27:36 node-2 kernel: [    0.509739] NetLabel:  unlabeled traffic allowed by default
Sep 26 05:27:36 node-2 kernel: [    0.509798] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 26 05:27:36 node-2 kernel: [    0.509802] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 26 05:27:36 node-2 kernel: [    0.511864] Switched to clocksource hpet
Sep 26 05:27:36 node-2 kernel: [    0.515805] AppArmor: AppArmor Filesystem Enabled
Sep 26 05:27:36 node-2 kernel: [    0.515826] pnp: PnP ACPI init
Sep 26 05:27:36 node-2 kernel: [    0.515833] ACPI: bus type PNP registered
Sep 26 05:27:36 node-2 kernel: [    0.515951] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 26 05:27:36 node-2 kernel: [    0.515960] pnp 00:01: [dma 4]
Sep 26 05:27:36 node-2 kernel: [    0.515971] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 26 05:27:36 node-2 kernel: [    0.515997] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516017] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516035] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516068] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516119] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516121] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 26 05:27:36 node-2 kernel: [    0.516123] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516124] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516126] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516130] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516132] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 26 05:27:36 node-2 kernel: [    0.516134] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516136] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516137] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516139] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516140] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516141] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 26 05:27:36 node-2 kernel: [    0.516144] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516228] pnp 00:07: [dma 0 disabled]
Sep 26 05:27:36 node-2 kernel: [    0.516256] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516331] pnp 00:08: [dma 0 disabled]
Sep 26 05:27:36 node-2 kernel: [    0.516361] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516411] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 26 05:27:36 node-2 kernel: [    0.516763] pnp: PnP ACPI: found 10 devices
Sep 26 05:27:36 node-2 kernel: [    0.516764] ACPI: bus type PNP unregistered
Sep 26 05:27:36 node-2 kernel: [    0.523097] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 26 05:27:36 node-2 kernel: [    0.523100] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 26 05:27:36 node-2 kernel: [    0.523103] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 26 05:27:36 node-2 kernel: [    0.523107] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 26 05:27:36 node-2 kernel: [    0.523109] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523124] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523153] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 26 05:27:36 node-2 kernel: [    0.523167] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523196] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 26 05:27:36 node-2 kernel: [    0.523211] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 26 05:27:36 node-2 kernel: [    0.523240] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 26 05:27:36 node-2 kernel: [    0.523268] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 26 05:27:36 node-2 kernel: [    0.523296] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 26 05:27:36 node-2 kernel: [    0.523298] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523313] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523342] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 26 05:27:36 node-2 kernel: [    0.523344] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523358] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523387] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 26 05:27:36 node-2 kernel: [    0.523389] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523392] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523396] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 26 05:27:36 node-2 kernel: [    0.523397] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523400] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523404] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 26 05:27:36 node-2 kernel: [    0.523408] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 26 05:27:36 node-2 kernel: [    0.523416] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 26 05:27:36 node-2 kernel: [    0.523420] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 26 05:27:36 node-2 kernel: [    0.523426] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 26 05:27:36 node-2 kernel: [    0.523427] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 26 05:27:36 node-2 kernel: [    0.523428] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 26 05:27:36 node-2 kernel: [    0.523429] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 26 05:27:36 node-2 kernel: [    0.523430] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 26 05:27:36 node-2 kernel: [    0.523431] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 26 05:27:36 node-2 kernel: [    0.523432] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 26 05:27:36 node-2 kernel: [    0.523432] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 26 05:27:36 node-2 kernel: [    0.523433] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523434] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523435] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523436] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523437] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523438] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523439] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523440] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523440] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 26 05:27:36 node-2 kernel: [    0.523441] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523442] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 26 05:27:36 node-2 kernel: [    0.523443] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 26 05:27:36 node-2 kernel: [    0.523444] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 26 05:27:36 node-2 kernel: [    0.523445] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 26 05:27:36 node-2 kernel: [    0.523447] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 26 05:27:36 node-2 kernel: [    0.523448] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 26 05:27:36 node-2 kernel: [    0.523485] NET: Registered protocol family 2
Sep 26 05:27:36 node-2 kernel: [    0.523747] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.524088] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.524235] TCP: Hash tables configured (established 262144 bind 65536)
Sep 26 05:27:36 node-2 kernel: [    0.524272] TCP: reno registered
Sep 26 05:27:36 node-2 kernel: [    0.524301] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.524398] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.524548] NET: Registered protocol family 1
Sep 26 05:27:36 node-2 kernel: [    0.563944] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 26 05:27:36 node-2 kernel: [    0.563951] PCI: CLS 64 bytes, default 64
Sep 26 05:27:36 node-2 kernel: [    0.563993] Trying to unpack rootfs image as initramfs...
Sep 26 05:27:36 node-2 kernel: [    0.783157] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep 26 05:27:36 node-2 kernel: [    0.783194] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 26 05:27:36 node-2 kernel: [    0.783196] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 26 05:27:36 node-2 kernel: [    0.783604] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783610] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783615] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783620] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783646] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783661] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783670] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783678] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783686] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783695] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783701] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783707] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783714] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783722] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783730] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783737] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 26 05:27:36 node-2 kernel: [    0.783817] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 26 05:27:36 node-2 kernel: [    0.783820] Scanning for low memory corruption every 60 seconds
Sep 26 05:27:36 node-2 kernel: [    0.784211] Initialise system trusted keyring
Sep 26 05:27:36 node-2 kernel: [    0.784266] audit: initializing netlink socket (disabled)
Sep 26 05:27:36 node-2 kernel: [    0.784282] type=2000 audit(1474867619.736:1): initialized
Sep 26 05:27:36 node-2 kernel: [    0.802041] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 26 05:27:36 node-2 kernel: [    0.803549] zbud: loaded
Sep 26 05:27:36 node-2 kernel: [    0.803691] VFS: Disk quotas dquot_6.5.2
Sep 26 05:27:36 node-2 kernel: [    0.803726] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 26 05:27:36 node-2 kernel: [    0.804102] fuse init (API version 7.22)
Sep 26 05:27:36 node-2 kernel: [    0.804156] msgmni has been set to 32768
Sep 26 05:27:36 node-2 kernel: [    0.804206] Key type big_key registered
Sep 26 05:27:36 node-2 kernel: [    0.804688] Key type asymmetric registered
Sep 26 05:27:36 node-2 kernel: [    0.804690] Asymmetric key parser 'x509' registered
Sep 26 05:27:36 node-2 kernel: [    0.804712] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 26 05:27:36 node-2 kernel: [    0.804778] io scheduler noop registered
Sep 26 05:27:36 node-2 kernel: [    0.804780] io scheduler deadline registered (default)
Sep 26 05:27:36 node-2 kernel: [    0.804799] io scheduler cfq registered
Sep 26 05:27:36 node-2 kernel: [    0.805314] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    0.805488] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    0.805616] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    0.805720] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    0.805830] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    0.805917] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    0.806270] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 26 05:27:36 node-2 kernel: [    0.806296] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 26 05:27:36 node-2 kernel: [    0.806312] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 26 05:27:36 node-2 kernel: [    0.806326] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806328] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806331] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 26 05:27:36 node-2 kernel: [    0.806336] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806337] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806339] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806340] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806342] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806343] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806345] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806346] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806348] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806349] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806351] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806352] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806354] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 26 05:27:36 node-2 kernel: [    0.806360] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806362] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 26 05:27:36 node-2 kernel: [    0.806373] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806376] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 26 05:27:36 node-2 kernel: [    0.806387] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806388] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 26 05:27:36 node-2 kernel: [    0.806391] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 26 05:27:36 node-2 kernel: [    0.806418] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 26 05:27:36 node-2 kernel: [    0.806424] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 26 05:27:36 node-2 kernel: [    0.806428] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 26 05:27:36 node-2 kernel: [    0.806446] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 26 05:27:36 node-2 kernel: [    0.806486] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 26 05:27:36 node-2 kernel: [    0.806487] vesafb: scrolling: redraw
Sep 26 05:27:36 node-2 kernel: [    0.806489] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 26 05:27:36 node-2 kernel: [    0.827234] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 26 05:27:36 node-2 kernel: [    0.835760] Console: switching to colour frame buffer device 80x30
Sep 26 05:27:36 node-2 kernel: [    0.844428] fb0: VESA VGA frame buffer device
Sep 26 05:27:36 node-2 kernel: [    0.844625] intel_idle: MWAIT substates: 0x2120
Sep 26 05:27:36 node-2 kernel: [    0.844626] intel_idle: v0.4 model 0x3F
Sep 26 05:27:36 node-2 kernel: [    0.844626] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 26 05:27:36 node-2 kernel: [    0.844860] ipmi message handler version 39.2
Sep 26 05:27:36 node-2 kernel: [    0.845134] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 26 05:27:36 node-2 kernel: [    0.845567] ACPI: AC Adapter [P111] (on-line)
Sep 26 05:27:36 node-2 kernel: [    0.850818] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 26 05:27:36 node-2 kernel: [    0.861825] ACPI: Power Button [PWRB]
Sep 26 05:27:36 node-2 kernel: [    0.867623] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 26 05:27:36 node-2 kernel: [    0.879249] ACPI: Power Button [PWRF]
Sep 26 05:27:36 node-2 kernel: [    0.901413] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 26 05:27:36 node-2 kernel: [    0.913064] pstore: Registered erst as persistent store backend
Sep 26 05:27:36 node-2 kernel: [    0.919257] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 26 05:27:36 node-2 kernel: [    0.931192] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 26 05:27:36 node-2 kernel: [    0.957945] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 26 05:27:36 node-2 kernel: [    0.991230] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 26 05:27:36 node-2 kernel: [    1.005294] Linux agpgart interface v0.103
Sep 26 05:27:36 node-2 kernel: [    1.012918] brd: module loaded
Sep 26 05:27:36 node-2 kernel: [    1.019988] loop: module loaded
Sep 26 05:27:36 node-2 kernel: [    1.026727] libphy: Fixed MDIO Bus: probed
Sep 26 05:27:36 node-2 kernel: [    1.033212] tun: Universal TUN/TAP device driver, 1.6
Sep 26 05:27:36 node-2 kernel: [    1.039719] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 26 05:27:36 node-2 kernel: [    1.046286] PPP generic driver version 2.4.2
Sep 26 05:27:36 node-2 kernel: [    1.052728] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 26 05:27:36 node-2 kernel: [    1.059248] ehci-pci: EHCI PCI platform driver
Sep 26 05:27:36 node-2 kernel: [    1.065835] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 26 05:27:36 node-2 kernel: [    1.072274] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 26 05:27:36 node-2 kernel: [    1.084953] ehci-pci 0000:00:1a.0: debug port 2
Sep 26 05:27:36 node-2 kernel: [    1.095211] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 26 05:27:36 node-2 kernel: [    1.095230] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 26 05:27:36 node-2 kernel: [    1.111360] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 26 05:27:36 node-2 kernel: [    1.117446] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 26 05:27:36 node-2 kernel: [    1.123605] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 26 05:27:36 node-2 kernel: [    1.135494] usb usb1: Product: EHCI Host Controller
Sep 26 05:27:36 node-2 kernel: [    1.141500] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 26 05:27:36 node-2 kernel: [    1.147536] usb usb1: SerialNumber: 0000:00:1a.0
Sep 26 05:27:36 node-2 kernel: [    1.153466] hub 1-0:1.0: USB hub found
Sep 26 05:27:36 node-2 kernel: [    1.159228] hub 1-0:1.0: 2 ports detected
Sep 26 05:27:36 node-2 kernel: [    1.164991] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 26 05:27:36 node-2 kernel: [    1.170563] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 26 05:27:36 node-2 kernel: [    1.181445] ehci-pci 0000:00:1d.0: debug port 2
Sep 26 05:27:36 node-2 kernel: [    1.190738] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 26 05:27:36 node-2 kernel: [    1.190741] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 26 05:27:36 node-2 kernel: [    1.207278] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 26 05:27:36 node-2 kernel: [    1.212475] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 26 05:27:36 node-2 kernel: [    1.217768] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 26 05:27:36 node-2 kernel: [    1.228347] usb usb2: Product: EHCI Host Controller
Sep 26 05:27:36 node-2 kernel: [    1.233819] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 26 05:27:36 node-2 kernel: [    1.239358] usb usb2: SerialNumber: 0000:00:1d.0
Sep 26 05:27:36 node-2 kernel: [    1.244886] hub 2-0:1.0: USB hub found
Sep 26 05:27:36 node-2 kernel: [    1.250244] hub 2-0:1.0: 2 ports detected
Sep 26 05:27:36 node-2 kernel: [    1.255549] ehci-platform: EHCI generic platform driver
Sep 26 05:27:36 node-2 kernel: [    1.260785] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 26 05:27:36 node-2 kernel: [    1.266101] ohci-pci: OHCI PCI platform driver
Sep 26 05:27:36 node-2 kernel: [    1.271396] ohci-platform: OHCI generic platform driver
Sep 26 05:27:36 node-2 kernel: [    1.276593] uhci_hcd: USB Universal Host Controller Interface driver
Sep 26 05:27:36 node-2 kernel: [    1.281938] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 26 05:27:36 node-2 kernel: [    1.479044] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 26 05:27:36 node-2 kernel: [    1.643312] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 26 05:27:36 node-2 kernel: [    1.648841] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 26 05:27:36 node-2 kernel: [    1.654580] hub 1-1:1.0: USB hub found
Sep 26 05:27:36 node-2 kernel: [    1.660047] hub 1-1:1.0: 6 ports detected
Sep 26 05:27:36 node-2 kernel: [    1.774794] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 26 05:27:36 node-2 kernel: [    1.779155] tsc: Refined TSC clocksource calibration: 3491.854 MHz
Sep 26 05:27:36 node-2 kernel: [    2.038975] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 26 05:27:36 node-2 kernel: [    2.044534] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 26 05:27:36 node-2 kernel: [    2.050367] hub 2-1:1.0: USB hub found
Sep 26 05:27:36 node-2 kernel: [    2.056087] hub 2-1:1.0: 8 ports detected
Sep 26 05:27:36 node-2 kernel: [    2.323995] i8042: No controller found
Sep 26 05:27:36 node-2 kernel: [    2.329426] mousedev: PS/2 mouse device common for all mice
Sep 26 05:27:36 node-2 kernel: [    2.334394] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 26 05:27:36 node-2 kernel: [    2.340650] rtc_cmos 00:02: RTC can wake from S4
Sep 26 05:27:36 node-2 kernel: [    2.346429] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 26 05:27:36 node-2 kernel: [    2.352051] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 26 05:27:36 node-2 kernel: [    2.363167] device-mapper: uevent: version 1.0.3
Sep 26 05:27:36 node-2 kernel: [    2.368819] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 26 05:27:36 node-2 kernel: [    2.380066] ledtrig-cpu: registered to indicate activity on CPUs
Sep 26 05:27:36 node-2 kernel: [    2.385993] TCP: cubic registered
Sep 26 05:27:36 node-2 kernel: [    2.391903] NET: Registered protocol family 10
Sep 26 05:27:36 node-2 kernel: [    2.397918] NET: Registered protocol family 17
Sep 26 05:27:36 node-2 kernel: [    2.403604] Key type dns_resolver registered
Sep 26 05:27:36 node-2 kernel: [    2.409565] Loading compiled-in X.509 certificates
Sep 26 05:27:36 node-2 kernel: [    2.415734] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Sep 26 05:27:36 node-2 kernel: [    2.427188] registered taskstats version 1
Sep 26 05:27:36 node-2 kernel: [    2.435195] Key type trusted registered
Sep 26 05:27:36 node-2 kernel: [    2.443180] Key type encrypted registered
Sep 26 05:27:36 node-2 kernel: [    2.448636] AppArmor: AppArmor sha1 policy hashing enabled
Sep 26 05:27:36 node-2 kernel: [    2.454115] IMA: No TPM chip found, activating TPM-bypass!
Sep 26 05:27:36 node-2 kernel: [    2.460308] regulator-dummy: disabling
Sep 26 05:27:36 node-2 kernel: [    2.465874]   Magic number: 0:427:467
Sep 26 05:27:36 node-2 kernel: [    2.471184] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 26 05:27:36 node-2 kernel: [    2.471185] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 26 05:27:36 node-2 kernel: [    2.471186] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 26 05:27:36 node-2 kernel: [    2.471187] usb 2-1.4: Manufacturer: Avocent
Sep 26 05:27:36 node-2 kernel: [    2.471188] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 26 05:27:36 node-2 kernel: [    2.504703] rtc_cmos 00:02: setting system clock to 2016-09-26 05:27:02 UTC (1474867622)
Sep 26 05:27:36 node-2 kernel: [    2.517241] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 26 05:27:36 node-2 kernel: [    2.522969] EDD information not available.
Sep 26 05:27:36 node-2 kernel: [    2.528644] PM: Hibernation image not present or could not be loaded.
Sep 26 05:27:36 node-2 kernel: [    2.529505] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 26 05:27:36 node-2 kernel: [    2.540934] Write protecting the kernel read-only data: 12288k
Sep 26 05:27:36 node-2 kernel: [    2.547241] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 26 05:27:36 node-2 kernel: [    2.559809] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 26 05:27:36 node-2 kernel: [    2.592255] device-mapper: multipath: version 1.6.0 loaded
Sep 26 05:27:36 node-2 kernel: [    2.600251] systemd-udevd[216]: starting version 204
Sep 26 05:27:36 node-2 kernel: [    2.625247] md: linear personality registered for level -1
Sep 26 05:27:36 node-2 kernel: [    2.640145] md: multipath personality registered for level -4
Sep 26 05:27:36 node-2 kernel: [    2.648103] md: raid0 personality registered for level 0
Sep 26 05:27:36 node-2 kernel: [    2.656239] md: raid1 personality registered for level 1
Sep 26 05:27:36 node-2 kernel: [    2.663849] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 26 05:27:36 node-2 kernel: [    2.670251] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 26 05:27:36 node-2 kernel: [    2.676632] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 26 05:27:36 node-2 kernel: [    2.677515] megasas: FW now in Ready state
Sep 26 05:27:36 node-2 kernel: [    2.677594] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677633] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677667] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677705] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677742] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677780] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677820] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677863] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677912] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.677947] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.678005] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.678297] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.678351] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.678390] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.678427] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.678478] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 26 05:27:36 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 26 05:27:36 node-2 kernel: [    2.678757] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 26 05:27:36 node-2 kernel: [    2.702177] hidraw: raw HID events driver (C) Jiri Kosina
Sep 26 05:27:36 node-2 kernel: [    2.710839] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 26 05:27:36 node-2 kernel: [    2.723880] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 26 05:27:36 node-2 kernel: [    2.737746] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 26 05:27:36 node-2 kernel: [    2.742263] raid6: sse2x1    2000 MB/s
Sep 26 05:27:36 node-2 kernel: [    2.751561] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.751565] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.751569] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.751573] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.751613] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.765803] usbcore: registered new interface driver usbhid
Sep 26 05:27:36 node-2 kernel: [    2.772703] usbhid: USB HID core driver
Sep 26 05:27:36 node-2 kernel: [    2.777855] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 26 05:27:36 node-2 kernel: [    2.777856] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 26 05:27:36 node-2 kernel: [    2.777857] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 26 05:27:36 node-2 kernel: [    2.777914] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.778003] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.778019] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.778026] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.778057] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.778091] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.778306] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 26 05:27:36 node-2 kernel: [    2.791213] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 26 05:27:36 node-2 kernel: [    2.791215] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 26 05:27:36 node-2 kernel: [    2.791216] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 26 05:27:36 node-2 kernel: [    2.810238] raid6: sse2x2    6930 MB/s
Sep 26 05:27:36 node-2 kernel: [    2.877871] raid6: sse2x4    9589 MB/s
Sep 26 05:27:36 node-2 kernel: [    2.949816] raid6: avx2x1   14934 MB/s
Sep 26 05:27:36 node-2 kernel: [    3.021752] raid6: avx2x2   18847 MB/s
Sep 26 05:27:36 node-2 kernel: [    3.093682] raid6: avx2x4   21196 MB/s
Sep 26 05:27:36 node-2 kernel: [    3.100232] raid6: using algorithm avx2x4 (21196 MB/s)
Sep 26 05:27:36 node-2 kernel: [    3.106718] raid6: using avx2x2 recovery algorithm
Sep 26 05:27:36 node-2 kernel: [    3.113093] megasas:IOC Init cmd success
Sep 26 05:27:36 node-2 kernel: [    3.113095] Switched to clocksource tsc
Sep 26 05:27:36 node-2 kernel: [    3.113246] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.113312] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.113457] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.113589] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.114256] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.129102] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 26 05:27:36 node-2 kernel: [    3.129151] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 26 05:27:36 node-2 kernel: [    3.129181] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 26 05:27:36 node-2 kernel: [    3.130009] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.130099] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.130248] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.130307] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.130447] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 26 05:27:36 node-2 kernel: [    3.180918] xor: automatically using best checksumming function:
Sep 26 05:27:36 node-2 kernel: [    3.187137] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 26 05:27:36 node-2 kernel: [    3.199290] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 26 05:27:36 node-2 kernel: [    3.201602] megasas: INIT adapter done
Sep 26 05:27:36 node-2 kernel: [    3.217995] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 26 05:27:36 node-2 kernel: [    3.225554]    avx       : 35764.000 MB/sec
Sep 26 05:27:36 node-2 kernel: [    3.236810] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 26 05:27:36 node-2 kernel: [    3.249318] async_tx: api initialized (async)
Sep 26 05:27:36 node-2 kernel: [    3.249342] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 26 05:27:36 node-2 kernel: [    3.249388] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 26 05:27:36 node-2 kernel: [    3.273831] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 26 05:27:36 node-2 kernel: [    3.275775] scsi0 : LSI SAS based MegaRAID driver
Sep 26 05:27:36 node-2 kernel: [    3.284074] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 26 05:27:36 node-2 kernel: [    3.316034] md: raid6 personality registered for level 6
Sep 26 05:27:36 node-2 kernel: [    3.322226] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 26 05:27:36 node-2 kernel: [    3.338300] md: raid5 personality registered for level 5
Sep 26 05:27:36 node-2 kernel: [    3.345576] md: raid4 personality registered for level 4
Sep 26 05:27:36 node-2 kernel: [    3.353504] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 26 05:27:36 node-2 kernel: [    3.353849] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 26 05:27:36 node-2 kernel: [    3.374722] md: raid10 personality registered for level 10
Sep 26 05:27:36 node-2 kernel: [    3.375139] sd 0:2:0:0: [sda] Write Protect is off
Sep 26 05:27:36 node-2 kernel: [    3.375158] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 26 05:27:36 node-2 kernel: [    3.375597] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 26 05:27:36 node-2 kernel: [    3.407857]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 26 05:27:36 node-2 kernel: [    3.416282] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 26 05:27:36 node-2 kernel: [    3.464676] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Sep 26 05:27:36 node-2 kernel: [    3.575193] random: lvm urandom read with 31 bits of entropy available
Sep 26 05:27:36 node-2 kernel: [    3.717025] bio: create slab <bio-1> at 1
Sep 26 05:27:36 node-2 kernel: [    4.523381] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 26 05:27:36 node-2 kernel: [    5.191689] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 26 05:27:36 node-2 kernel: [    5.247237] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 26 05:27:36 node-2 kernel: [    5.341329] random: nonblocking pool is initialized
Sep 26 05:27:36 node-2 kernel: [    5.367201] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 26 05:27:36 node-2 kernel: [    5.403112] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 26 05:27:36 node-2 kernel: [    5.490702] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 26 05:27:36 node-2 kernel: [    5.678761] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 26 05:27:36 node-2 kernel: [    5.707570] XFS (dm-1): Mounting Filesystem
Sep 26 05:27:36 node-2 kernel: [    6.043030] XFS (dm-1): Ending clean mount
Sep 26 05:27:36 node-2 kernel: [    6.089739] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 26 05:27:36 node-2 kernel: [    6.148771] XFS (dm-2): Mounting Filesystem
Sep 26 05:27:36 node-2 kernel: [    6.272222] XFS (dm-2): Ending clean mount
Sep 26 05:27:36 node-2 kernel: [    6.378117] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 26 05:27:36 node-2 kernel: [    8.006615] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 26 05:27:36 node-2 kernel: [    8.035224] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 26 05:27:36 node-2 kernel: [    8.189223] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 26 05:27:36 node-2 kernel: [    8.189234] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 26 05:27:36 node-2 kernel: [    8.189242] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 26 05:27:36 node-2 kernel: [    8.189261] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 26 05:27:36 node-2 kernel: [    8.254329] systemd-udevd[801]: starting version 204
Sep 26 05:27:36 node-2 kernel: [    8.418920] power_meter ACPI000D:00: Found ACPI power meter.
Sep 26 05:27:36 node-2 kernel: [    8.418960] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 26 05:27:36 node-2 kernel: [    8.435276] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 26 05:27:36 node-2 kernel: [    8.435282] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 26 05:27:36 node-2 kernel: [    8.435285] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 26 05:27:36 node-2 kernel: [    8.435287] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 26 05:27:36 node-2 kernel: [    8.435337] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 26 05:27:36 node-2 kernel: [    8.442404] IPMI System Interface driver.
Sep 26 05:27:36 node-2 kernel: [    8.442480] ipmi_si: probing via ACPI
Sep 26 05:27:36 node-2 kernel: [    8.442499] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 26 05:27:36 node-2 kernel: [    8.442500] ipmi_si: Adding ACPI-specified kcs state machine
Sep 26 05:27:36 node-2 kernel: [    8.442514] ipmi_si: probing via SMBIOS
Sep 26 05:27:36 node-2 kernel: [    8.442516] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 26 05:27:36 node-2 kernel: [    8.442517] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 26 05:27:36 node-2 kernel: [    8.442519] ipmi_si: probing via SPMI
Sep 26 05:27:36 node-2 kernel: [    8.442520] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 26 05:27:36 node-2 kernel: [    8.442521] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 26 05:27:36 node-2 kernel: [    8.442522] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 26 05:27:36 node-2 kernel: [    8.446760] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 26 05:27:36 node-2 kernel: [    8.458585] wmi: Mapper loaded
Sep 26 05:27:36 node-2 kernel: [    8.521487] systemd-udevd[830]: renamed network interface eth3 to enp9s0
Sep 26 05:27:36 node-2 kernel: [    8.553335] systemd-udevd[822]: renamed network interface eth1 to enp7s0
Sep 26 05:27:36 node-2 kernel: [    8.577340] systemd-udevd[842]: renamed network interface eth2 to enp8s0
Sep 26 05:27:36 node-2 kernel: [    8.591245] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 26 05:27:36 node-2 kernel: [    8.591251] ipmi_si 00:09: IPMI kcs interface initialized
Sep 26 05:27:36 node-2 kernel: [    8.605763] systemd-udevd[819]: renamed network interface eth0 to enp6s0
Sep 26 05:27:36 node-2 kernel: [    8.935573] type=1400 audit(1474867628.931:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1090 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.935730] type=1400 audit(1474867628.931:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1090 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.935861] type=1400 audit(1474867628.931:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1090 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.939030] type=1400 audit(1474867628.935:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1079 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.939167] type=1400 audit(1474867628.935:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1079 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.939284] type=1400 audit(1474867628.935:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1079 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.953056] type=1400 audit(1474867628.951:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1077 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.953223] type=1400 audit(1474867628.951:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1077 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.953352] type=1400 audit(1474867628.951:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1077 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    8.979920] type=1400 audit(1474867628.975:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1078 comm="apparmor_parser"
Sep 26 05:27:36 node-2 kernel: [    9.445537] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 26 05:27:36 node-2 kernel: [    9.446317] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 26 05:27:36 node-2 kernel: [    9.661721] enic 0000:06:00.0 enp6s0: Link UP
Sep 26 05:27:36 node-2 kernel: [    9.662248] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 26 05:27:36 node-2 kernel: [    9.662258] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 26 05:27:36 node-2 kernel: [   19.202051] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 26 05:27:37 node-2 failsafe: Failsafe of 120 seconds reached.
Sep 26 05:27:37 node-2 kernel: [   38.586067] init: failsafe main process (8456) killed by TERM signal
Sep 26 05:27:38 node-2 dbus[8498]: [system] AppArmor D-Bus mediation is enabled
Sep 26 05:27:38 node-2 kernel: [   38.841252] audit_printk_skb: 30 callbacks suppressed
Sep 26 05:27:38 node-2 kernel: [   38.841254] type=1400 audit(1474867658.238:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8583 comm="apparmor_parser"
Sep 26 05:27:38 node-2 kernel: [   38.841258] type=1400 audit(1474867658.238:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8583 comm="apparmor_parser"
Sep 26 05:27:38 node-2 kernel: [   38.841262] type=1400 audit(1474867658.238:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8583 comm="apparmor_parser"
Sep 26 05:27:38 node-2 kernel: [   38.841480] type=1400 audit(1474867658.238:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8583 comm="apparmor_parser"
Sep 26 05:27:38 node-2 kernel: [   38.841482] type=1400 audit(1474867658.238:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8583 comm="apparmor_parser"
Sep 26 05:27:38 node-2 kernel: [   38.841595] type=1400 audit(1474867658.238:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8583 comm="apparmor_parser"
Sep 26 05:27:38 node-2 kernel: [   38.846400] type=1400 audit(1474867658.246:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8584 comm="apparmor_parser"
Sep 26 05:27:38 node-2 kernel: [   38.907793] type=1400 audit(1474867658.306:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8586 comm="apparmor_parser"
Sep 26 05:27:38 node-2 anacron[8650]: Anacron 2.3 started on 2016-09-26
Sep 26 05:27:38 node-2 anacron[8650]: Will run job `cron.daily' in 5 min.
Sep 26 05:27:38 node-2 anacron[8650]: Will run job `cron.weekly' in 10 min.
Sep 26 05:27:38 node-2 anacron[8650]: Will run job `cron.monthly' in 15 min.
Sep 26 05:27:38 node-2 anacron[8650]: Jobs will be executed sequentially
Sep 26 05:27:38 node-2 cron[8615]: (CRON) INFO (pidfile fd = 3)
Sep 26 05:27:38 node-2 multipathd: path checkers start up
Sep 26 05:27:38 node-2 cron[8699]: (CRON) STARTUP (fork ok)
Sep 26 05:27:38 node-2 cron[8699]: (CRON) INFO (Running @reboot jobs)
Sep 26 05:27:38 node-2 postfix/master[8794]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 26 05:27:42 node-2 puppet-agent[8979]: Reopening log files
Sep 26 05:27:43 node-2 puppet-agent[8979]: Could not request certificate: Connection refused - connect(2)
Sep 26 05:27:55 node-2 puppet-user[9058]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 26 05:27:55 node-2 puppet-user[9058]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 26 05:27:56 node-2 puppet-user[9058]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 26 05:27:56 node-2 puppet-user[9058]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 26 05:27:56 node-2 puppet-user[9058]: Finished catalog run in 0.67 seconds
Sep 26 05:27:57 node-2 multipathd: uevent trigger error
Sep 26 05:27:58 node-2 puppet-user[9493]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 26 05:27:58 node-2 puppet-user[9493]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 26 05:27:58 node-2 puppet-user[9493]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 26 05:27:58 node-2 puppet-user[9493]: Finished catalog run in 0.08 seconds
Sep 26 05:27:59 node-2 puppet-user[9956]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 26 05:27:59 node-2 puppet-user[9956]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep 26 05:27:59 node-2 puppet-user[9956]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 26 05:27:59 node-2 puppet-user[9956]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 26 05:27:59 node-2 puppet-user[9956]: Finished catalog run in 0.04 seconds
Sep 26 05:28:01 node-2 CRON[10943]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 26 05:28:01 node-2 puppet-user[10550]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 26 05:28:01 node-2 puppet-user[10550]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 26 05:28:01 node-2 puppet-user[10550]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 26 05:28:01 node-2 puppet-user[10550]: Finished catalog run in 0.03 seconds
Sep 26 05:28:03 node-2 puppet-user[11020]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 26 05:28:03 node-2 puppet-user[11020]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Sep 26 05:28:03 node-2 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 26 05:28:03 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 26 05:28:03 node-2 nailgun-agent: D, [2016-09-26T05:28:01.769398 #10946] DEBUG -- : Sleep for 2 seconds before sending request
Sep 26 05:28:03 node-2 nailgun-agent: I, [2016-09-26T05:28:03.787108 #10946]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 26 05:28:03 node-2 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep 26 05:28:04 node-2 nailgun-agent: D, [2016-09-26T05:28:04.157740 #10946] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep 26 05:28:04 node-2 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 26 05:28:04 node-2 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Sep 26 05:28:04 node-2 puppet-user[11020]: Finished catalog run in 1.18 seconds
Sep 26 05:28:06 node-2 puppet-user[11691]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 26 05:28:06 node-2 puppet-user[11691]: Compiled catalog for node-2.domain.tld in environment production in 0.23 seconds
Sep 26 05:28:06 node-2 puppet-user[11691]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep 26 05:28:06 node-2 puppet-user[11691]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Sep 26 05:28:06 node-2 puppet-user[11691]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 26 05:28:06 node-2 puppet-user[11691]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 26 05:28:06 node-2 puppet-user[11691]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 26 05:28:06 node-2 puppet-user[11691]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 26 05:28:06 node-2 puppet-user[11691]: Finished catalog run in 0.42 seconds
Sep 26 05:28:08 node-2 puppet-user[12181]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 26 05:28:08 node-2 puppet-user[12181]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Sep 26 05:28:08 node-2 puppet-user[12181]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 26 05:28:08 node-2 kernel: [   69.365385] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 26 05:28:08 node-2 kernel: [   69.365432] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 26 05:28:08 node-2 puppet-user[12181]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 26 05:28:08 node-2 puppet-user[12181]: Finished catalog run in 0.09 seconds
Sep 26 05:28:10 node-2 puppet-user[12649]: (Scope(Class[main])) MODULAR: sync_time
Sep 26 05:28:10 node-2 puppet-user[12649]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 26 05:28:10 node-2 ntpdate[13081]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.321546 #10946] DEBUG -- : Trying to find block devices
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.321615 #10946] DEBUG -- : Found block device: sda
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.321651 #10946] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.321674 #10946] DEBUG -- : Trying to get list of physical devices
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.321812 #10946] DEBUG -- : Getting udev properties for device: sda
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.323546 #10946] 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"=>"0x618e72837273a8901cc788
Sep 26 05:28:16 node-2 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65964", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.323572 #10946] DEBUG -- : Trying to find out if device sda is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.323612 #10946] DEBUG -- : Device sda removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.323627 #10946] DEBUG -- : Device sda seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.324077 #10946] DEBUG -- : Getting udev properties for device: dm-0
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.325585 #10946] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-0YWVj1DU5XYspU6DoM4nuGFty0mVOi82mYXp599lXjBMFIvQ6sKoIsBUKR5c8qi1 /dev/disk/by-uuid/9f657659-00f9-49ad-a9fe-4aff40202b84 /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-0YWVj1DU5XYspU6DoM4nuGFty0mVOi82mYXp599lXjBMFIvQ6sKoIsBUKR5c8qi1", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9f657659-00f9-49ad-a9fe-4aff40202b84", "ID_FS_UUID_ENC"=>"9f657659-00f9-49ad-a9fe-4aff40202b84", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7
Sep 26 05:28:16 node-2 nailgun-agent: 1815", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.325611 #10946] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.325652 #10946] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.325665 #10946] DEBUG -- : Device dm-0 seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.325690 #10946] DEBUG -- : Getting udev properties for device: dm-1
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.327204 #10946] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-gpPuILeFdGFKvFzsk5PzLOKEnWWfmND5Y3ue7fDsZW3KxiSSVvJt7F43hpJE0ozC /dev/disk/by-uuid/83fdf349-7832-47f6-8fae-94f0dd0c18a3 /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-gpPuILeFdGFKvFzsk5PzLOKEnWWfmND5Y3ue7fDsZW3KxiSSVvJt7F43hpJE0ozC", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"83fdf349-7832-47f6-8fae-94f0dd0c18a3", "ID_FS_UUID_ENC"=>"83fdf349-7832-47f6-8fae-94f0dd0c18a3", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"361", "nomdmonddf"=>"1", "nomdm
Sep 26 05:28:16 node-2 nailgun-agent: onisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.327286 #10946] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.327316 #10946] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.327330 #10946] DEBUG -- : Device dm-1 seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.327345 #10946] DEBUG -- : Getting udev properties for device: dm-2
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.328871 #10946] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-vF7q3KBACsjG5LNUZGla151XiiKjX4bWxHneWftQZ4RkYSBc5qBCBsErb12PyqBs /dev/disk/by-uuid/2d510f10-5da8-4b01-94b3-9e4558a40645 /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-vF7q3KBACsjG5LNUZGla151XiiKjX4bWxHneWftQZ4RkYSBc5qBCBsErb12PyqBs", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2d510f10-5da8-4b01-94b3-9e4558a40645", "ID_FS_UUID_ENC"=>"2d510f10-5da8-4b01-94b3-9e4558a40645", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1
Sep 26 05:28:16 node-2 nailgun-agent: 5159", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.328897 #10946] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.328960 #10946] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.328974 #10946] DEBUG -- : Device dm-2 seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.328990 #10946] DEBUG -- : Getting udev properties for device: dm-3
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.330528 #10946] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-AkpWXtaIuZrX6WYCI99iUnUUfRlhs2QSO3eHooIcC2s4Jbx4206kUfzyLIP74hwP /dev/disk/by-uuid/ad7c47e3-6d7a-4cea-93d9-818a8ad5b97f /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-AkpWXtaIuZrX6WYCI99iUnUUfRlhs2QSO3eHooIcC2s4Jbx4206kUfzyLIP74hwP", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ad7c47e3-6d7a-4cea-93d9-818a8ad5b97f", "ID_FS_UUID_ENC"=>"ad7c47e3-6d7a-4cea-93d9-818a8ad5b97f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18309", "nomdmon
Sep 26 05:28:16 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.330566 #10946] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.330609 #10946] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.330622 #10946] DEBUG -- : Device dm-3 seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.330647 #10946] DEBUG -- : Getting udev properties for device: dm-4
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.332178 #10946] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-WNrtq7BuTuwskMGL8EXnoalVarOuYva0baVeZjgifXulDNluT3ILfxmwokKSGa6v /dev/disk/by-uuid/9b520e1b-acf7-46a5-bc27-83ae88f1d0f6 /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-WNrtq7BuTuwskMGL8EXnoalVarOuYva0baVeZjgifXulDNluT3ILfxmwokKSGa6v", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9b520e1b-acf7-46a5-bc27-83ae88f1d0f6", "ID_FS_UUID_ENC"=>"9b520e1b-acf7-46a5-bc27-83ae88f1d0f6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22566", "nomdmonddf"=>"1",
Sep 26 05:28:16 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.332211 #10946] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.332257 #10946] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.332270 #10946] DEBUG -- : Device dm-4 seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.332285 #10946] DEBUG -- : Getting udev properties for device: dm-5
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.333816 #10946] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-cnta1whBh6tDTfnjCCG4HV70rLyoR7rrBaofqGIPQMQi5362xmfmCpVnih0YOs5B /dev/disk/by-uuid/2bea9d59-f45e-4348-9c6c-c77e145971e4 /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-cnta1whBh6tDTfnjCCG4HV70rLyoR7rrBaofqGIPQMQi5362xmfmCpVnih0YOs5B", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2bea9d59-f45e-4348-9c6c-c77e145971e4", "ID_FS_UUID_ENC"=>"2bea9d59-f45e-4348-9c6c-c77e145971e4", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29927", "nomdmonddf"=>"1", "nom
Sep 26 05:28:16 node-2 nailgun-agent: dmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.333849 #10946] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.333875 #10946] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.333888 #10946] DEBUG -- : Device dm-5 seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.333917 #10946] DEBUG -- : Getting udev properties for device: dm-6
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.335401 #10946] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-cnta1whBh6tDTfnjCCG4HV70rLyoR7rrqeS7GQkaxRT64m8jwNA2dTenGhAU95iN /dev/disk/by-uuid/f54a6b1c-07c5-4a6e-add5-0a109901499b /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-cnta1whBh6tDTfnjCCG4HV70rLyoR7rrqeS7GQkaxRT64m8jwNA2dTenGhAU95iN", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"f54a6b1c-07c5-4a6e-add5-0a109901499b", "ID_FS_UUID_ENC"=>"f54a6b1c-07c5-4a6e-add5-0a109901499b", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30345", "nomdmonddf"=>"1", "nomdmonisw
Sep 26 05:28:16 node-2 nailgun-agent: "=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.335423 #10946] DEBUG -- : Trying to find out if device dm-6 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.335451 #10946] DEBUG -- : Device dm-6 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.335485 #10946] DEBUG -- : Device dm-6 seems to be appropriate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.335500 #10946] DEBUG -- : Getting udev properties for device: ram0
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.336894 #10946] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14958", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.336916 #10946] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.336954 #10946] DEBUG -- : Device ram0 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.336985 #10946] DEBUG -- : Getting udev properties for device: ram1
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.338427 #10946] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15167", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.338463 #10946] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.338508 #10946] DEBUG -- : Device ram1 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.338530 #10946] DEBUG -- : Getting udev properties for device: ram2
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.339930 #10946] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17575", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.339955 #10946] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.339991 #10946] DEBUG -- : Device ram2 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.340011 #10946] DEBUG -- : Getting udev properties for device: ram3
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.341404 #10946] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17748", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.341429 #10946] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.341482 #10946] DEBUG -- : Device ram3 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.341503 #10946] DEBUG -- : Getting udev properties for device: ram4
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.342873 #10946] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18001", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.342904 #10946] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.342943 #10946] DEBUG -- : Device ram4 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.342962 #10946] DEBUG -- : Getting udev properties for device: ram5
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.344359 #10946] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18261", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.344384 #10946] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.344418 #10946] DEBUG -- : Device ram5 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.344447 #10946] DEBUG -- : Getting udev properties for device: ram6
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.345841 #10946] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18391", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.345867 #10946] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.345925 #10946] DEBUG -- : Device ram6 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.345945 #10946] DEBUG -- : Getting udev properties for device: ram7
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.347311 #10946] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18749", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.347343 #10946] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.347381 #10946] DEBUG -- : Device ram7 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.347413 #10946] DEBUG -- : Getting udev properties for device: ram8
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.348839 #10946] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18894", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.348864 #10946] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.348901 #10946] DEBUG -- : Device ram8 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.348921 #10946] DEBUG -- : Getting udev properties for device: ram9
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.350315 #10946] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19094", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.350349 #10946] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.350382 #10946] DEBUG -- : Device ram9 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.350403 #10946] DEBUG -- : Getting udev properties for device: loop0
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.351787 #10946] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13527", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.351827 #10946] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.351866 #10946] DEBUG -- : Device loop0 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.351890 #10946] DEBUG -- : Getting udev properties for device: loop1
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.353311 #10946] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13686", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.353336 #10946] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.353372 #10946] DEBUG -- : Device loop1 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.353399 #10946] DEBUG -- : Getting udev properties for device: loop2
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.358973 #10946] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13826", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.359001 #10946] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.359038 #10946] DEBUG -- : Device loop2 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.359058 #10946] DEBUG -- : Getting udev properties for device: loop3
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.360649 #10946] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14016", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.360676 #10946] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.360715 #10946] DEBUG -- : Device loop3 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.360735 #10946] DEBUG -- : Getting udev properties for device: loop4
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.362138 #10946] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14200", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.362163 #10946] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.362204 #10946] DEBUG -- : Device loop4 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.362224 #10946] DEBUG -- : Getting udev properties for device: loop5
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.363615 #10946] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14368", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.363640 #10946] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.363676 #10946] DEBUG -- : Device loop5 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.363695 #10946] DEBUG -- : Getting udev properties for device: loop6
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.365044 #10946] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14523", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.365070 #10946] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.365138 #10946] DEBUG -- : Device loop6 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.365158 #10946] DEBUG -- : Getting udev properties for device: loop7
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.366511 #10946] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14731", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.366536 #10946] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.366572 #10946] DEBUG -- : Device loop7 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.366627 #10946] DEBUG -- : Getting udev properties for device: ram10
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.367980 #10946] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15576", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.368005 #10946] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.368038 #10946] DEBUG -- : Device ram10 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.368059 #10946] DEBUG -- : Getting udev properties for device: ram11
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.369425 #10946] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15801", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.369450 #10946] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.369481 #10946] DEBUG -- : Device ram11 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.369501 #10946] DEBUG -- : Getting udev properties for device: ram12
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.370876 #10946] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16248", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.370901 #10946] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.370933 #10946] DEBUG -- : Device ram12 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.370953 #10946] DEBUG -- : Getting udev properties for device: ram13
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.372403 #10946] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16525", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.372428 #10946] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.372466 #10946] DEBUG -- : Device ram13 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.372485 #10946] DEBUG -- : Getting udev properties for device: ram14
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.373857 #10946] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17007", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.373882 #10946] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.373919 #10946] DEBUG -- : Device ram14 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.373939 #10946] DEBUG -- : Getting udev properties for device: ram15
Sep 26 05:28:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375285 #10946] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17299", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375340 #10946] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375375 #10946] DEBUG -- : Device ram15 removable parameter: "0"
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375409 #10946] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375423 #10946] DEBUG -- : Block device seems to be physical data storage: sda
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375457 #10946] DEBUG -- : Found block device: dm-0
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375483 #10946] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375496 #10946] DEBUG -- : Found block device: dm-1
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375506 #10946] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375515 #10946] DEBUG -- : Found block device: dm-2
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375525 #10946] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375561 #10946] DEBUG -- : Found block device: dm-3
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375571 #10946] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375579 #10946] DEBUG -- : Found block device: dm-4
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375588 #10946] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375597 #10946] DEBUG -- : Found block device: dm-5
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375606 #10946] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375614 #10946] DEBUG -- : Found block device: dm-6
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375623 #10946] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375631 #10946] DEBUG -- : Found block device: ram0
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375640 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375677 #10946] DEBUG -- : Found block device: ram1
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375687 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375695 #10946] DEBUG -- : Found block device: ram2
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375704 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375712 #10946] DEBUG -- : Found block device: ram3
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375722 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375730 #10946] DEBUG -- : Found block device: ram4
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375740 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375749 #10946] DEBUG -- : Found block device: ram5
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375758 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375766 #10946] DEBUG -- : Found block device: ram6
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375808 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375817 #10946] DEBUG -- : Found block device: ram7
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375826 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375834 #10946] DEBUG -- : Found block device: ram8
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375843 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375851 #10946] DEBUG -- : Found block device: ram9
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375866 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375875 #10946] DEBUG -- : Found block device: loop0
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375900 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375958 #10946] DEBUG -- : Found block device: loop1
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375969 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375978 #10946] DEBUG -- : Found block device: loop2
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375987 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.375995 #10946] DEBUG -- : Found block device: loop3
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376006 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376015 #10946] DEBUG -- : Found block device: loop4
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376025 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376033 #10946] DEBUG -- : Found block device: loop5
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376076 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376085 #10946] DEBUG -- : Found block device: loop6
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376094 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376103 #10946] DEBUG -- : Found block device: loop7
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376112 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376120 #10946] DEBUG -- : Found block device: ram10
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376130 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376149 #10946] DEBUG -- : Found block device: ram11
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376158 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376204 #10946] DEBUG -- : Found block device: ram12
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376214 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376222 #10946] DEBUG -- : Found block device: ram13
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376232 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376240 #10946] DEBUG -- : Found block device: ram14
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376249 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376258 #10946] DEBUG -- : Found block device: ram15
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376267 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.376293 #10946] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.459924 #10946] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep 26 05:28:16 node-2 nailgun-agent: D, [2016-09-26T05:28:16.459981 #10946] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 26 05:28:16 node-2 ntpdate[13081]: adjust time server 10.20.0.2 offset 0.319812 sec
Sep 26 05:28:16 node-2 puppet-user[12649]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 26 05:28:16 node-2 puppet-user[12649]: Finished catalog run in 6.18 seconds
Sep 26 05:28:20 node-2 puppet-user[13657]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 26 05:28:20 node-2 puppet-user[13657]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Sep 26 05:28:20 node-2 puppet-user[13657]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 26 05:28:20 node-2 puppet-user[13657]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep 26 05:28:20 node-2 puppet-user[13657]: Finished catalog run in 0.07 seconds
Sep 26 05:28:22 node-2 puppet-user[14127]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 26 05:28:22 node-2 puppet-user[14127]: Compiled catalog for node-2.domain.tld in environment production in 0.52 seconds
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 26 05:28:22 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 26 05:28:23 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 26 05:28:23 node-2 puppet-user[14127]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 26 05:28:23 node-2 puppet-user[14127]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 26 05:28:23 node-2 puppet-user[14127]: Finished catalog run in 0.93 seconds
Sep 26 05:28:24 node-2 kernel: [   84.852926] init: plymouth-upstart-bridge main process ended, respawning
Sep 26 05:28:24 node-2 puppet-agent[8979]: Could not run: SIGTERM
Sep 26 05:28:24 node-2 kernel: [   85.187116] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 26 05:28:24 node-2 ec2: 
Sep 26 05:28:24 node-2 ec2: #############################################################
Sep 26 05:28:24 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 26 05:28:24 node-2 ec2: 1024 fc:45:46:bd:c5:36:5f:53:c0:92:60:8e:9f:d8:ae:b5  root@node-2.domain.tld (DSA)
Sep 26 05:28:24 node-2 ec2: 256 7f:28:5f:bc:b2:36:c9:b7:13:ab:32:3b:c5:a0:6e:b4  root@node-2.domain.tld (ECDSA)
Sep 26 05:28:24 node-2 ec2: 256 cd:06:ed:65:0d:c8:dd:57:48:e7:0b:48:88:7b:c3:d1  root@node-2.domain.tld (ED25519)
Sep 26 05:28:24 node-2 ec2: 2048 97:db:7d:c8:fd:ef:67:4b:7b:dd:e1:2b:12:1e:a7:9d  root@node-2.domain.tld (RSA)
Sep 26 05:28:24 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 26 05:28:24 node-2 ec2: #############################################################
Sep 26 05:28:25 node-2 puppet-user[14775]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 26 05:28:25 node-2 puppet-user[14775]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Sep 26 05:28:28 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476599 #10946] DEBUG -- : Trying to find block devices
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476696 #10946] DEBUG -- : Found block device: sda
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476723 #10946] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476742 #10946] DEBUG -- : Block device seems to be physical data storage: sda
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476762 #10946] DEBUG -- : Found block device: dm-0
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476775 #10946] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476786 #10946] DEBUG -- : Found block device: dm-1
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476797 #10946] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476807 #10946] DEBUG -- : Found block device: dm-2
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476841 #10946] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476850 #10946] DEBUG -- : Found block device: dm-3
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476860 #10946] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476869 #10946] DEBUG -- : Found block device: dm-4
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476877 #10946] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476887 #10946] DEBUG -- : Found block device: dm-5
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476896 #10946] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476904 #10946] DEBUG -- : Found block device: dm-6
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476914 #10946] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476944 #10946] DEBUG -- : Found block device: ram0
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476954 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476963 #10946] DEBUG -- : Found block device: ram1
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476973 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476981 #10946] DEBUG -- : Found block device: ram2
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476990 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.476998 #10946] DEBUG -- : Found block device: ram3
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477008 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477016 #10946] DEBUG -- : Found block device: ram4
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477025 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477069 #10946] DEBUG -- : Found block device: ram5
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477079 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477087 #10946] DEBUG -- : Found block device: ram6
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477096 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477104 #10946] DEBUG -- : Found block device: ram7
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477113 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477121 #10946] DEBUG -- : Found block device: ram8
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477130 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477148 #10946] DEBUG -- : Found block device: ram9
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477187 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477196 #10946] DEBUG -- : Found block device: loop0
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477205 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477213 #10946] DEBUG -- : Found block device: loop1
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477223 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477231 #10946] DEBUG -- : Found block device: loop2
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477240 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477247 #10946] DEBUG -- : Found block device: loop3
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477256 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477293 #10946] DEBUG -- : Found block device: loop4
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477303 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477311 #10946] DEBUG -- : Found block device: loop5
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477319 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477327 #10946] DEBUG -- : Found block device: loop6
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477337 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477344 #10946] DEBUG -- : Found block device: loop7
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477353 #10946] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477360 #10946] DEBUG -- : Found block device: ram10
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477369 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477408 #10946] DEBUG -- : Found block device: ram11
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477417 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477425 #10946] DEBUG -- : Found block device: ram12
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477434 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477442 #10946] DEBUG -- : Found block device: ram13
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477451 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477458 #10946] DEBUG -- : Found block device: ram14
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477467 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477474 #10946] DEBUG -- : Found block device: ram15
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477483 #10946] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.477541 #10946] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Sep 26 05:28:28 node-2 nailgun-agent: D, [2016-09-26T05:28:28.628624 #10946] DEBUG -- : Response: status: 200 body: {"id": 2}
Sep 26 05:28:28 node-2 nailgun-agent: I, [2016-09-26T05:28:28.628797 #10946]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep 26 05:28:29 node-2 puppet-user[14775]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 26 05:29:00 node-2 puppet-user[14775]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 26 05:29:01 node-2 puppet-user[14775]: Finished catalog run in 35.19 seconds
Sep 26 05:29:01 node-2 CRON[17465]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 26 05:29:02 node-2 puppet-user[17457]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 26 05:29:03 node-2 puppet-user[17457]: Compiled catalog for node-2.domain.tld in environment production in 0.63 seconds
Sep 26 05:29:03 node-2 puppet-user[17457]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 26 05:29:03 node-2 puppet-user[17457]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 26 05:29:03 node-2 puppet-user[17457]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 26 05:29:03 node-2 puppet-user[17457]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 26 05:29:03 node-2 puppet-user[17457]: Finished catalog run in 0.10 seconds
Sep 26 05:29:05 node-2 puppet-user[17938]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 26 05:29:06 node-2 puppet-user[17938]: Compiled catalog for node-2.domain.tld in environment production in 0.97 seconds
Sep 26 05:29:06 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 26 05:29:06 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 26 05:29:06 node-2 crontab[18365]: (root) LIST (root)
Sep 26 05:29:06 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 26 05:29:06 node-2 crontab[18369]: (root) REPLACE (root)
Sep 26 05:29:07 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 26 05:29:08 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 26 05:29:09 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 26 05:29:09 node-2 nailgun-agent: I, [2016-09-26T05:29:09.802502 #17468]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 26 05:29:09 node-2 puppet-user[17938]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 26 05:29:09 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8429" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 26 05:29:09 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 26 05:29:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:25 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:25 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:25 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:25 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:25 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:27 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:27 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:27 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:27 node-2 multipathd: uevent trigger error
<27>Sep 26 05:29:27 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:23 node-2 ntpdate[28254]: no servers can be used, exiting
<27>Sep 26 05:30:54 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:54 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:54 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:54 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:54 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:30:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:31:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:08 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:19 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 05:32:19 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 05:32:25 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 05:32:25 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 05:32:30 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 05:32:36 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 05:32:36 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 26 05:32:43 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:43 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:43 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:43 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:43 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:43 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:32:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:01 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:03 node-2 haproxy[16371]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:04 node-2 haproxy[16378]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:04 node-2 haproxy[16378]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:04 node-2 haproxy[16378]: proxy mysqld has no server available!
<27>Sep 26 05:33:06 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:06 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:06 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:06 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:06 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:10 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:12 node-2 haproxy[18758]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:13 node-2 haproxy[18762]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:13 node-2 haproxy[18762]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:13 node-2 haproxy[18762]: proxy mysqld has no server available!
<129>Sep 26 05:33:13 node-2 haproxy[18762]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:13 node-2 haproxy[18762]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:14 node-2 haproxy[18762]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:14 node-2 haproxy[18762]: proxy object-storage has no server available!
<27>Sep 26 05:33:15 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:15 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:15 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:15 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:15 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:18 node-2 haproxy[20168]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:18 node-2 haproxy[20168]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:18 node-2 haproxy[20168]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:18 node-2 haproxy[20168]: proxy neutron has no server available!
<129>Sep 26 05:33:18 node-2 haproxy[20168]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:18 node-2 haproxy[20168]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:19 node-2 haproxy[20172]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:19 node-2 haproxy[20172]: proxy mysqld has no server available!
<129>Sep 26 05:33:19 node-2 haproxy[20172]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:19 node-2 haproxy[20172]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:19 node-2 haproxy[20172]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:19 node-2 haproxy[20172]: proxy object-storage has no server available!
<27>Sep 26 05:33:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:20 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:23 node-2 haproxy[21443]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:23 node-2 haproxy[21443]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:23 node-2 haproxy[21443]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:23 node-2 haproxy[21443]: proxy keystone-1 has no server available!
<129>Sep 26 05:33:23 node-2 haproxy[21443]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:23 node-2 haproxy[21443]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:23 node-2 haproxy[21443]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:23 node-2 haproxy[21443]: proxy keystone-2 has no server available!
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:24 node-2 haproxy[21449]: proxy neutron has no server available!
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:24 node-2 haproxy[21449]: proxy mysqld has no server available!
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:24 node-2 haproxy[21449]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:24 node-2 haproxy[21449]: proxy object-storage has no server available!
<27>Sep 26 05:33:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:26 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:28 node-2 haproxy[22681]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:28 node-2 haproxy[22681]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:28 node-2 haproxy[22681]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:28 node-2 haproxy[22681]: proxy keystone-1 has no server available!
<129>Sep 26 05:33:28 node-2 haproxy[22681]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:28 node-2 haproxy[22681]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:28 node-2 haproxy[22681]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:28 node-2 haproxy[22681]: proxy keystone-2 has no server available!
<129>Sep 26 05:33:28 node-2 haproxy[22681]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:29 node-2 haproxy[22685]: proxy neutron has no server available!
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:29 node-2 haproxy[22685]: proxy mysqld has no server available!
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:29 node-2 haproxy[22685]: proxy object-storage has no server available!
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:29 node-2 haproxy[22685]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:30 node-2 haproxy[22685]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:30 node-2 haproxy[22685]: proxy aodh has no server available!
<27>Sep 26 05:33:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:31 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:33 node-2 haproxy[24089]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:33 node-2 haproxy[24089]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:33 node-2 haproxy[24089]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:33 node-2 haproxy[24089]: proxy keystone-1 has no server available!
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:34 node-2 haproxy[24093]: proxy keystone-2 has no server available!
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:34 node-2 haproxy[24093]: proxy neutron has no server available!
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:34 node-2 haproxy[24093]: proxy mysqld has no server available!
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:34 node-2 haproxy[24093]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:34 node-2 haproxy[24093]: proxy object-storage has no server available!
<129>Sep 26 05:33:35 node-2 haproxy[24093]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:35 node-2 haproxy[24093]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:35 node-2 haproxy[24093]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:35 node-2 haproxy[24093]: proxy aodh has no server available!
<129>Sep 26 05:33:35 node-2 haproxy[24093]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:35 node-2 haproxy[24093]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:35 node-2 haproxy[24093]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:35 node-2 haproxy[24093]: proxy ceilometer has no server available!
<27>Sep 26 05:33:36 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:36 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:36 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:36 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:37 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:39 node-2 haproxy[25315]: proxy keystone-1 has no server available!
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:39 node-2 haproxy[25315]: proxy keystone-2 has no server available!
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:39 node-2 haproxy[25315]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:39 node-2 haproxy[25315]: proxy neutron has no server available!
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:40 node-2 haproxy[25319]: proxy mysqld has no server available!
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:40 node-2 haproxy[25319]: proxy object-storage has no server available!
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:40 node-2 haproxy[25319]: proxy aodh has no server available!
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:40 node-2 haproxy[25319]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:41 node-2 haproxy[25319]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:41 node-2 haproxy[25319]: proxy ceilometer has no server available!
<27>Sep 26 05:33:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:42 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:44 node-2 haproxy[26578]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:44 node-2 haproxy[26578]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:44 node-2 haproxy[26578]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:44 node-2 haproxy[26578]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:44 node-2 haproxy[26578]: proxy keystone-1 has no server available!
<129>Sep 26 05:33:44 node-2 haproxy[26578]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:45 node-2 haproxy[26582]: proxy keystone-2 has no server available!
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:45 node-2 haproxy[26582]: proxy neutron has no server available!
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:45 node-2 haproxy[26582]: proxy mysqld has no server available!
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:45 node-2 haproxy[26582]: proxy object-storage has no server available!
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:45 node-2 haproxy[26582]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:46 node-2 haproxy[26582]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:46 node-2 haproxy[26582]: proxy aodh has no server available!
<129>Sep 26 05:33:46 node-2 haproxy[26582]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:46 node-2 haproxy[26582]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:46 node-2 haproxy[26582]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:46 node-2 haproxy[26582]: proxy ceilometer has no server available!
<27>Sep 26 05:33:47 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:47 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:47 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:47 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:47 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:50 node-2 haproxy[27866]: proxy keystone-1 has no server available!
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:50 node-2 haproxy[27866]: proxy keystone-2 has no server available!
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:50 node-2 haproxy[27866]: proxy glance-api has no server available!
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:50 node-2 haproxy[27866]: proxy glance-glare has no server available!
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:50 node-2 haproxy[27866]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:51 node-2 haproxy[27870]: proxy neutron has no server available!
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:51 node-2 haproxy[27870]: proxy glance-registry has no server available!
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:51 node-2 haproxy[27870]: proxy mysqld has no server available!
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:51 node-2 haproxy[27870]: proxy object-storage has no server available!
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:51 node-2 haproxy[27870]: proxy aodh has no server available!
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:51 node-2 haproxy[27870]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:51 node-2 haproxy[27870]: proxy ceilometer has no server available!
<27>Sep 26 05:33:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:52 node-2 multipathd: uevent trigger error
<129>Sep 26 05:33:55 node-2 haproxy[29128]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:55 node-2 haproxy[29128]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:55 node-2 haproxy[29128]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:55 node-2 haproxy[29128]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:55 node-2 haproxy[29128]: proxy keystone-1 has no server available!
<129>Sep 26 05:33:55 node-2 haproxy[29128]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:55 node-2 haproxy[29128]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:55 node-2 haproxy[29128]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:55 node-2 haproxy[29128]: proxy keystone-2 has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:56 node-2 haproxy[29132]: proxy nova-api has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:56 node-2 haproxy[29132]: proxy nova-metadata-api has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:56 node-2 haproxy[29132]: proxy glance-api has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:56 node-2 haproxy[29132]: proxy glance-glare has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:56 node-2 haproxy[29132]: proxy neutron has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:56 node-2 haproxy[29132]: proxy glance-registry has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:56 node-2 haproxy[29132]: proxy mysqld has no server available!
<129>Sep 26 05:33:56 node-2 haproxy[29132]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:57 node-2 haproxy[29132]: proxy object-storage has no server available!
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:57 node-2 haproxy[29132]: proxy aodh has no server available!
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:57 node-2 haproxy[29132]: proxy ceilometer has no server available!
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:33:57 node-2 haproxy[29132]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:33:57 node-2 haproxy[29132]: proxy nova-novncproxy has no server available!
<27>Sep 26 05:33:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:33:58 node-2 multipathd: uevent trigger error
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:01 node-2 haproxy[30342]: proxy keystone-1 has no server available!
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:01 node-2 haproxy[30342]: proxy keystone-2 has no server available!
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:01 node-2 haproxy[30342]: proxy nova-api has no server available!
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:01 node-2 haproxy[30342]: proxy nova-metadata-api has no server available!
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:01 node-2 haproxy[30342]: proxy cinder-api has no server available!
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:01 node-2 haproxy[30342]: proxy glance-api has no server available!
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:01 node-2 haproxy[30342]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:01 node-2 haproxy[30342]: proxy glance-glare has no server available!
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:02 node-2 haproxy[30346]: proxy neutron has no server available!
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:02 node-2 haproxy[30346]: proxy glance-registry has no server available!
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:02 node-2 haproxy[30346]: proxy mysqld has no server available!
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:02 node-2 haproxy[30346]: proxy object-storage has no server available!
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:02 node-2 haproxy[30346]: proxy aodh has no server available!
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:02 node-2 haproxy[30346]: proxy ceilometer has no server available!
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:02 node-2 haproxy[30346]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:02 node-2 haproxy[30346]: proxy nova-novncproxy has no server available!
<27>Sep 26 05:34:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:04 node-2 multipathd: uevent trigger error
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy keystone-1 has no server available!
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy keystone-2 has no server available!
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy nova-api has no server available!
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy nova-metadata-api has no server available!
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy cinder-api has no server available!
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy glance-api has no server available!
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy glance-glare has no server available!
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:07 node-2 haproxy[31621]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:07 node-2 haproxy[31621]: proxy neutron has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy glance-registry has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy mysqld has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy object-storage has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy aodh has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy ceilometer has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy heat-api has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy heat-api-cfn has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy heat-api-cloudwatch has no server available!
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 26 05:34:08 node-2 haproxy[31626]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 26 05:34:08 node-2 haproxy[31626]: proxy nova-novncproxy has no server available!
<27>Sep 26 05:34:09 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:09 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:09 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:09 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:09 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:34:20 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 26 05:34:40 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:34:46 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Sep 26 05:34:48 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 26 05:35:18 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 05:35:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:35:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:35:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:35:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:35:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:37:44 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:37:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:37:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:37:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:37:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:37:55 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:01 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:01 node-2 multipathd: uevent trigger error
<43>Sep 26 05:38:21 node-2 apache2_error [Mon Sep 26 05:38:13.170018 2016] [mpm_event:notice] [pid 7970:tid 139788140369792] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 26 05:38:21 node-2 apache2_error [Mon Sep 26 05:38:13.170090 2016] [core:notice] [pid 7970:tid 139788140369792] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 26 05:38:21 node-2 apache2_error [Mon Sep 26 05:38:16.244642 2016] [mpm_event:notice] [pid 7970:tid 139788140369792] AH00491: caught SIGTERM, shutting down
<43>Sep 26 05:38:21 node-2 apache2_error [Mon Sep 26 05:38:17.326036 2016] [mpm_worker:notice] [pid 8877:tid 140006798133120] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 26 05:38:21 node-2 apache2_error [Mon Sep 26 05:38:17.326093 2016] [core:notice] [pid 8877:tid 140006798133120] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 05:38:21 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:21 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:21 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:21 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:21 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:26 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:29 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:29 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:29 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:29 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:29 node-2 multipathd: uevent trigger error
<27>Sep 26 05:38:29 node-2 multipathd: uevent trigger error
<43>Sep 26 05:39:41 node-2 apache2_error [Mon Sep 26 05:39:39.144885 2016] [mpm_worker:notice] [pid 8877:tid 140006798133120] AH00295: caught SIGTERM, shutting down
<43>Sep 26 05:39:41 node-2 apache2_error [Mon Sep 26 05:39:39.914417 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 05:39:41 node-2 apache2_error [Mon Sep 26 05:39:39.914452 2016] [core:notice] [pid 22785:tid 140181652379520] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 26 05:40:31 node-2 apache2_error [Mon Sep 26 05:40:25.787128 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 26 05:40:31 node-2 apache2_error [Mon Sep 26 05:40:25.980247 2016] [mpm_worker:warn] [pid 22785:tid 140181652379520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 05:40:31 node-2 apache2_error [Mon Sep 26 05:40:25.983144 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 05:40:31 node-2 apache2_error [Mon Sep 26 05:40:25.983159 2016] [core:notice] [pid 22785:tid 140181652379520] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 05:40:44 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:41:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:11 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:15 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:15 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:16 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:31 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:41:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:42 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:42:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:43:45 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:43:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:43:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:43:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:43:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:43:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:43:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:44:59 node-2 multipathd: uevent trigger error
<27>Sep 26 05:44:59 node-2 multipathd: uevent trigger error
<27>Sep 26 05:44:59 node-2 multipathd: uevent trigger error
<27>Sep 26 05:44:59 node-2 multipathd: uevent trigger error
<27>Sep 26 05:44:59 node-2 multipathd: uevent trigger error
<27>Sep 26 05:44:59 node-2 multipathd: uevent trigger error
<27>Sep 26 05:44:59 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:00 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:00 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:00 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:00 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:00 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:22 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:22 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:22 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:22 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:22 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:22 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:28 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:28 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:28 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:28 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:28 node-2 multipathd: uevent trigger error
<27>Sep 26 05:46:47 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:48:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:48:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:48:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:48:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:48:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:13 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:19 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:19 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:19 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:19 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:19 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:49 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:49 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:49 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:49 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:49:49 node-2 multipathd: uevent trigger error
<27>Sep 26 05:49:49 node-2 multipathd: uevent trigger error
<27>Sep 26 05:50:33 node-2 multipathd: uevent trigger error
<27>Sep 26 05:50:33 node-2 multipathd: uevent trigger error
<27>Sep 26 05:50:33 node-2 multipathd: uevent trigger error
<27>Sep 26 05:50:33 node-2 multipathd: uevent trigger error
<27>Sep 26 05:50:33 node-2 multipathd: uevent trigger error
<27>Sep 26 05:50:33 node-2 multipathd: uevent trigger error
<27>Sep 26 05:50:33 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:24 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:51:57 node-2 multipathd: uevent trigger error
<27>Sep 26 05:52:51 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:54:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:20 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:54:58 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:44 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:48 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:52 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 26 05:55:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:55:52 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:04 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:10 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:40 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:40 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:40 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:40 node-2 multipathd: uevent trigger error
<27>Sep 26 05:56:40 node-2 multipathd: uevent trigger error
<27>Sep 26 05:57:46 node-2 multipathd: uevent trigger error
<27>Sep 26 05:57:46 node-2 multipathd: uevent trigger error
<27>Sep 26 05:57:46 node-2 multipathd: uevent trigger error
<27>Sep 26 05:57:46 node-2 multipathd: uevent trigger error
<27>Sep 26 05:57:46 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:03 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:03 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:03 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:03 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:03 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:03 node-2 multipathd: uevent trigger error
<11>Sep 26 05:58:15 node-2 liberasurecode[8226]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:15 node-2 liberasurecode[8226]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:15 node-2 liberasurecode[8226]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:15 node-2 liberasurecode[8226]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:15 node-2 liberasurecode[8255]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:15 node-2 liberasurecode[8255]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:15 node-2 liberasurecode[8255]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:15 node-2 liberasurecode[8255]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:17 node-2 liberasurecode[8732]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:17 node-2 liberasurecode[8732]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:17 node-2 liberasurecode[8732]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:17 node-2 liberasurecode[8732]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9377]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9377]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9377]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9377]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9444]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9444]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9444]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9444]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9576]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9576]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9576]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9576]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9590]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9590]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9590]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9590]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9605]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9605]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9605]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9605]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9622]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9622]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9622]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:22 node-2 liberasurecode[9622]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:31 node-2 liberasurecode[10215]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:31 node-2 liberasurecode[10215]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:31 node-2 liberasurecode[10215]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 05:58:31 node-2 liberasurecode[10215]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 26 05:58:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:39 node-2 multipathd: uevent trigger error
<27>Sep 26 05:58:54 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 26 05:59:33 node-2 apache2_error [Mon Sep 26 05:59:25.640827 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 26 05:59:33 node-2 apache2_error [Mon Sep 26 05:59:26.025211 2016] [mpm_worker:warn] [pid 22785:tid 140181652379520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 05:59:33 node-2 apache2_error [Mon Sep 26 05:59:26.031895 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 05:59:33 node-2 apache2_error [Mon Sep 26 05:59:26.031934 2016] [core:notice] [pid 22785:tid 140181652379520] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 26 06:00:02 node-2 liberasurecode[22711]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 06:00:02 node-2 liberasurecode[22711]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 06:00:02 node-2 liberasurecode[22711]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 06:00:02 node-2 liberasurecode[22711]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Sep 26 06:00:03 node-2 apache2_error [Mon Sep 26 06:00:02.718236 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Sep 26 06:00:06 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:06 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:06 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:06 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:06 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:06 node-2 multipathd: uevent trigger error
<43>Sep 26 06:00:13 node-2 apache2_error [Mon Sep 26 06:00:04.229762 2016] [mpm_worker:warn] [pid 22785:tid 140181652379520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 06:00:13 node-2 apache2_error [Mon Sep 26 06:00:04.243902 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 06:00:13 node-2 apache2_error [Mon Sep 26 06:00:04.243947 2016] [core:notice] [pid 22785:tid 140181652379520] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 06:00:13 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:13 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:13 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:13 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:13 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:51 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:51 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:51 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:51 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:51 node-2 multipathd: uevent trigger error
<43>Sep 26 06:00:53 node-2 apache2_error [Mon Sep 26 06:00:47.847614 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 26 06:00:53 node-2 apache2_error [Mon Sep 26 06:00:48.232057 2016] [mpm_worker:warn] [pid 22785:tid 140181652379520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 26 06:00:53 node-2 apache2_error [Mon Sep 26 06:00:48.240304 2016] [mpm_worker:notice] [pid 22785:tid 140181652379520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 26 06:00:53 node-2 apache2_error [Mon Sep 26 06:00:48.240336 2016] [core:notice] [pid 22785:tid 140181652379520] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 26 06:00:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:00:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:04 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:04 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:04 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:04 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:04 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:43 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:01:55 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 26 06:02:05 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:05 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:05 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:05 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:05 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:05 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:20 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:31 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:31 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:31 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:31 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:31 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:32 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 26 06:02:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:02:58 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:03 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:03 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:03 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:03 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:03 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:16 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:16 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:16 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:16 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:16 node-2 multipathd: uevent trigger error
<129>Sep 26 06:03:18 node-2 haproxy[31626]: 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.
<27>Sep 26 06:03:23 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:23 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:23 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:23 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:23 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:28 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:28 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:28 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:28 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:28 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:03:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:10 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:15 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:19 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:19 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:19 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:19 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:19 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:19 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:26 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:26 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:26 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:26 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:26 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:26 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:30 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:30 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:30 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:30 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:30 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:31 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:36 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:36 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:36 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:36 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:36 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:40 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:45 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:45 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:45 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:45 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:45 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:45 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:49 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:50 node-2 multipathd: uevent trigger error
<27>Sep 26 06:04:58 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:04:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:04:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:04:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:04:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:04:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:04:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:04:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<11>Sep 26 06:05:02 node-2 liberasurecode[5779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 06:05:02 node-2 liberasurecode[5779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 06:05:02 node-2 liberasurecode[5779]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 26 06:05:02 node-2 liberasurecode[5779]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 26 06:05:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:12 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:05:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:24 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:05:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:36 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:05:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:48 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:05:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:05:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:01 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:06:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:13 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:06:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:25 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:06:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:37 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:06:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:49 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:06:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:06:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:01 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 26 06:07:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
<27>Sep 26 06:07:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-0e168cf6-55" in table Interface
