Oct 30 15:27:35 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8395" x-info="http://www.rsyslog.com"] start
Oct 30 15:27:35 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 30 15:27:35 node-2 rsyslogd: rsyslogd's groupid changed to 104
Oct 30 15:27:35 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct 30 15:27:35 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 30 15:27:35 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 30 15:27:35 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 30 15:27:35 node-2 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Oct 30 15:27:35 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=d0190e4f-9fd7-46e6-b01b-a6d011235260 nomdmonddf nomdmonisw
Oct 30 15:27:35 node-2 kernel: [    0.000000] KERNEL supported cpus:
Oct 30 15:27:35 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct 30 15:27:35 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct 30 15:27:35 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct 30 15:27:35 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 30 15:27:35 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 30 15:27:35 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 30 15:27:35 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
Oct 30 15:27:35 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 30 15:27:35 node-2 kernel: [    0.000000] No AGP bridge found
Oct 30 15:27:35 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 30 15:27:35 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct 30 15:27:35 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 30 15:27:35 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct 30 15:27:35 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 30 15:27:35 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 30 15:27:35 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 30 15:27:35 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 30 15:27:35 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 30 15:27:35 node-2 kernel: [    0.000000]   2 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000]   3 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000]   4 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000]   5 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000]   6 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000]   7 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000]   8 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000]   9 disabled
Oct 30 15:27:35 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 30 15:27:35 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 30 15:27:35 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 30 15:27:35 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 30 15:27:35 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 30 15:27:35 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 30 15:27:35 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 30 15:27:35 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 30 15:27:35 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 30 15:27:35 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 30 15:27:35 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 30 15:27:35 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 30 15:27:35 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 30 15:27:35 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 30 15:27:35 node-2 kernel: [    0.000000] Zone ranges:
Oct 30 15:27:35 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] Movable zone start for each node
Oct 30 15:27:35 node-2 kernel: [    0.000000] Early memory node ranges
Oct 30 15:27:35 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct 30 15:27:35 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 30 15:27:35 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 30 15:27:35 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 30 15:27:35 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct 30 15:27:35 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct 30 15:27:35 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 30 15:27:35 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 30 15:27:35 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 30 15:27:35 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 30 15:27:35 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 30 15:27:35 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 30 15:27:35 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 30 15:27:35 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 30 15:27:35 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 30 15:27:35 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 30 15:27:35 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 30 15:27:35 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 30 15:27:35 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 30 15:27:35 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 30 15:27:35 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 30 15:27:35 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 30 15:27:35 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 30 15:27:35 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 
Oct 30 15:27:35 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct 30 15:27:35 node-2 kernel: [    0.000000] Policy zone: Normal
Oct 30 15:27:35 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=d0190e4f-9fd7-46e6-b01b-a6d011235260 nomdmonddf nomdmonisw
Oct 30 15:27:35 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 30 15:27:35 node-2 kernel: [    0.000000] Checking aperture...
Oct 30 15:27:35 node-2 kernel: [    0.000000] No AGP bridge found
Oct 30 15:27:35 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 30 15:27:35 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 30 15:27:35 node-2 kernel: [    0.000000] Memory: 32653452K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct 30 15:27:35 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 30 15:27:35 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 30 15:27:35 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 30 15:27:35 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 30 15:27:35 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 30 15:27:35 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 30 15:27:35 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 30 15:27:35 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 30 15:27:35 node-2 kernel: [    0.000000] console [tty0] enabled
Oct 30 15:27:35 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 30 15:27:35 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 30 15:27:35 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 30 15:27:35 node-2 kernel: [    0.000000] hpet clockevent registered
Oct 30 15:27:35 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 30 15:27:35 node-2 kernel: [    0.004000] tsc: Detected 3492.069 MHz processor
Oct 30 15:27:35 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.13 BogoMIPS (lpj=13968276)
Oct 30 15:27:35 node-2 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 30 15:27:35 node-2 kernel: [    0.000049] Security Framework initialized
Oct 30 15:27:35 node-2 kernel: [    0.000067] AppArmor: AppArmor initialized
Oct 30 15:27:35 node-2 kernel: [    0.000068] Yama: becoming mindful.
Oct 30 15:27:35 node-2 kernel: [    0.001479] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.006366] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.008288] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.008316] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.008605] Initializing cgroup subsys memory
Oct 30 15:27:35 node-2 kernel: [    0.008613] Initializing cgroup subsys devices
Oct 30 15:27:35 node-2 kernel: [    0.008615] Initializing cgroup subsys freezer
Oct 30 15:27:35 node-2 kernel: [    0.008617] Initializing cgroup subsys blkio
Oct 30 15:27:35 node-2 kernel: [    0.008618] Initializing cgroup subsys perf_event
Oct 30 15:27:35 node-2 kernel: [    0.008621] Initializing cgroup subsys hugetlb
Oct 30 15:27:35 node-2 kernel: [    0.008640] CPU: Physical Processor ID: 0
Oct 30 15:27:35 node-2 kernel: [    0.008641] CPU: Processor Core ID: 0
Oct 30 15:27:35 node-2 kernel: [    0.008645] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 30 15:27:35 node-2 kernel: [    0.008645] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 30 15:27:35 node-2 kernel: [    0.009339] mce: CPU supports 22 MCE banks
Oct 30 15:27:35 node-2 kernel: [    0.009367] CPU0: Thermal monitoring enabled (TM1)
Oct 30 15:27:35 node-2 kernel: [    0.009388] process: using mwait in idle threads
Oct 30 15:27:35 node-2 kernel: [    0.009391] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 30 15:27:35 node-2 kernel: [    0.009391] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 30 15:27:35 node-2 kernel: [    0.009391] tlb_flushall_shift: 6
Oct 30 15:27:35 node-2 kernel: [    0.009478] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 30 15:27:35 node-2 kernel: [    0.010199] ACPI: Core revision 20131115
Oct 30 15:27:35 node-2 kernel: [    0.022999] ACPI: All ACPI Tables successfully acquired
Oct 30 15:27:35 node-2 kernel: [    0.023162] ftrace: allocating 28622 entries in 112 pages
Oct 30 15:27:35 node-2 kernel: [    0.031914] dmar: Host address width 46
Oct 30 15:27:35 node-2 kernel: [    0.031916] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 30 15:27:35 node-2 kernel: [    0.031922] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 30 15:27:35 node-2 kernel: [    0.031924] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 30 15:27:35 node-2 kernel: [    0.031928] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 30 15:27:35 node-2 kernel: [    0.031929] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 30 15:27:35 node-2 kernel: [    0.031931] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 30 15:27:35 node-2 kernel: [    0.031932] dmar: ATSR flags: 0x0
Oct 30 15:27:35 node-2 kernel: [    0.031933] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 30 15:27:35 node-2 kernel: [    0.031934] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 30 15:27:35 node-2 kernel: [    0.032050] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 30 15:27:35 node-2 kernel: [    0.032051] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 30 15:27:35 node-2 kernel: [    0.032052] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 30 15:27:35 node-2 kernel: [    0.032053] HPET id 0 under DRHD base 0xc7ffc000
Oct 30 15:27:35 node-2 kernel: [    0.032055] Your BIOS is broken and requested that x2apic be disabled.
Oct 30 15:27:35 node-2 kernel: [    0.032055] This will slightly decrease performance.
Oct 30 15:27:35 node-2 kernel: [    0.032055] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 30 15:27:35 node-2 kernel: [    0.032486] Enabled IRQ remapping in xapic mode
Oct 30 15:27:35 node-2 kernel: [    0.032487] x2apic not enabled, IRQ remapping is in xapic mode
Oct 30 15:27:35 node-2 kernel: [    0.032491] Switched APIC routing to physical flat.
Oct 30 15:27:35 node-2 kernel: [    0.033067] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 30 15:27:35 node-2 kernel: [    0.072718] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 30 15:27:35 node-2 kernel: [    0.072733] TSC deadline timer enabled
Oct 30 15:27:35 node-2 kernel: [    0.072741] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 30 15:27:35 node-2 kernel: [    0.072747] ... version:                3
Oct 30 15:27:35 node-2 kernel: [    0.072748] ... bit width:              48
Oct 30 15:27:35 node-2 kernel: [    0.072749] ... generic registers:      4
Oct 30 15:27:35 node-2 kernel: [    0.072750] ... value mask:             0000ffffffffffff
Oct 30 15:27:35 node-2 kernel: [    0.072751] ... max period:             0000ffffffffffff
Oct 30 15:27:35 node-2 kernel: [    0.072752] ... fixed-purpose events:   3
Oct 30 15:27:35 node-2 kernel: [    0.072753] ... event mask:             000000070000000f
Oct 30 15:27:35 node-2 kernel: [    0.074170] x86: Booting SMP configuration:
Oct 30 15:27:35 node-2 kernel: [    0.088276] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 30 15:27:35 node-2 kernel: [    0.074172] .... node  #0, CPUs:        #1  #2  #3
Oct 30 15:27:35 node-2 kernel: [    0.116188] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 30 15:27:35 node-2 kernel: [    0.270035] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 30 15:27:35 node-2 kernel: [    0.325649] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 30 15:27:35 node-2 kernel: [    0.382304] x86: Booted up 2 nodes, 16 CPUs
Oct 30 15:27:35 node-2 kernel: [    0.382308] smpboot: Total of 16 processors activated (111758.82 BogoMIPS)
Oct 30 15:27:35 node-2 kernel: [    0.406161] devtmpfs: initialized
Oct 30 15:27:35 node-2 kernel: [    0.408493] EVM: security.selinux
Oct 30 15:27:35 node-2 kernel: [    0.408495] EVM: security.SMACK64
Oct 30 15:27:35 node-2 kernel: [    0.408496] EVM: security.ima
Oct 30 15:27:35 node-2 kernel: [    0.408497] EVM: security.capability
Oct 30 15:27:35 node-2 kernel: [    0.408546] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.409204] pinctrl core: initialized pinctrl subsystem
Oct 30 15:27:35 node-2 kernel: [    0.409265] regulator-dummy: no parameters
Oct 30 15:27:35 node-2 kernel: [    0.409296] RTC time: 15:26:59, date: 10/30/16
Oct 30 15:27:35 node-2 kernel: [    0.409329] NET: Registered protocol family 16
Oct 30 15:27:35 node-2 kernel: [    0.409413] cpuidle: using governor ladder
Oct 30 15:27:35 node-2 kernel: [    0.409414] cpuidle: using governor menu
Oct 30 15:27:35 node-2 kernel: [    0.409447] ACPI: bus type PCI registered
Oct 30 15:27:35 node-2 kernel: [    0.409449] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 30 15:27:35 node-2 kernel: [    0.409495] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 30 15:27:35 node-2 kernel: [    0.409497] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 30 15:27:35 node-2 kernel: [    0.423241] PCI: Using configuration type 1 for base access
Oct 30 15:27:35 node-2 kernel: [    0.424233] bio: create slab <bio-0> at 0
Oct 30 15:27:35 node-2 kernel: [    0.424504] ACPI: Added _OSI(Module Device)
Oct 30 15:27:35 node-2 kernel: [    0.424505] ACPI: Added _OSI(Processor Device)
Oct 30 15:27:35 node-2 kernel: [    0.424506] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 30 15:27:35 node-2 kernel: [    0.424507] ACPI: Added _OSI(Processor Aggregator Device)
Oct 30 15:27:35 node-2 kernel: [    0.437142] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 30 15:27:35 node-2 kernel: [    0.451680] ACPI: Interpreter enabled
Oct 30 15:27:35 node-2 kernel: [    0.451685] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 30 15:27:35 node-2 kernel: [    0.451689] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 30 15:27:35 node-2 kernel: [    0.451692] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 30 15:27:35 node-2 kernel: [    0.451699] ACPI: (supports S0 S4 S5)
Oct 30 15:27:35 node-2 kernel: [    0.451700] ACPI: Using IOAPIC for interrupt routing
Oct 30 15:27:35 node-2 kernel: [    0.451740] HEST: Table parsing has been initialized.
Oct 30 15:27:35 node-2 kernel: [    0.451743] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 30 15:27:35 node-2 kernel: [    0.452294] ACPI: No dock devices found.
Oct 30 15:27:35 node-2 kernel: [    0.463798] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 30 15:27:35 node-2 kernel: [    0.463802] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 15:27:35 node-2 kernel: [    0.463806] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 30 15:27:35 node-2 kernel: [    0.463833] PCI host bridge to bus 0000:ff
Oct 30 15:27:35 node-2 kernel: [    0.463834] pci_bus 0000:ff: root bus resource [bus ff]
Oct 30 15:27:35 node-2 kernel: [    0.463842] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.463879] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.463909] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.463944] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.463972] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.464000] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.464029] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464057] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464086] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464113] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464139] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464165] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464193] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464219] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464245] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464271] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464299] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464326] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464352] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.464380] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464405] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.464430] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464456] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464485] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.464519] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464550] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464579] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464609] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464639] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464669] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464699] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464735] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464765] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464797] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464829] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464861] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464894] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464923] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464950] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.464982] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465017] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465056] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465090] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465122] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465150] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465180] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465210] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465240] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465271] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465301] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465332] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465361] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465389] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465418] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465448] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465479] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465510] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465567] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 30 15:27:35 node-2 kernel: [    0.465570] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 15:27:35 node-2 kernel: [    0.465573] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 30 15:27:35 node-2 kernel: [    0.465590] PCI host bridge to bus 0000:7f
Oct 30 15:27:35 node-2 kernel: [    0.465592] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 30 15:27:35 node-2 kernel: [    0.465597] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465624] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.465652] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465681] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465702] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.465726] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.465752] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465777] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465799] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465821] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465843] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465865] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465889] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465911] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465939] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465967] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.465989] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466013] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466037] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.466063] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466086] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.466109] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466133] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466161] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 30 15:27:35 node-2 kernel: [    0.466193] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466219] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466245] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466271] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466296] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466325] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466352] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466380] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466406] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466433] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466460] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466488] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466516] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466540] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466564] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466592] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466617] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466643] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466671] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466699] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466724] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466749] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466775] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466803] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466830] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466858] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466888] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466914] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466937] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466963] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.466989] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.467018] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.467044] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.468286] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 30 15:27:35 node-2 kernel: [    0.468290] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 15:27:35 node-2 kernel: [    0.469406] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 30 15:27:35 node-2 kernel: [    0.469910] PCI host bridge to bus 0000:00
Oct 30 15:27:35 node-2 kernel: [    0.469913] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 30 15:27:35 node-2 kernel: [    0.469914] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 30 15:27:35 node-2 kernel: [    0.469916] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 30 15:27:35 node-2 kernel: [    0.469920] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 30 15:27:35 node-2 kernel: [    0.469921] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 30 15:27:35 node-2 kernel: [    0.469923] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 30 15:27:35 node-2 kernel: [    0.469924] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 30 15:27:35 node-2 kernel: [    0.469930] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 30 15:27:35 node-2 kernel: [    0.470013] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.470043] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.470085] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 30 15:27:35 node-2 kernel: [    0.470104] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.470133] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.470173] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 30 15:27:35 node-2 kernel: [    0.470191] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.470221] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.470263] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 30 15:27:35 node-2 kernel: [    0.470279] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.470349] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.470426] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.470501] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 30 15:27:35 node-2 kernel: [    0.470506] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 30 15:27:35 node-2 kernel: [    0.470590] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 30 15:27:35 node-2 kernel: [    0.470739] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 30 15:27:35 node-2 kernel: [    0.470756] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 30 15:27:35 node-2 kernel: [    0.470834] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.470887] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 30 15:27:35 node-2 kernel: [    0.470909] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.470965] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.471008] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 30 15:27:35 node-2 kernel: [    0.471036] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.471092] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.471135] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 30 15:27:35 node-2 kernel: [    0.471160] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 30 15:27:35 node-2 kernel: [    0.471177] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 30 15:27:35 node-2 kernel: [    0.471255] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.471304] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 30 15:27:35 node-2 kernel: [    0.471331] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 30 15:27:35 node-2 kernel: [    0.471579] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 30 15:27:35 node-2 kernel: [    0.471584] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 30 15:27:35 node-2 kernel: [    0.471590] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.471596] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.471604] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 30 15:27:35 node-2 kernel: [    0.471634] pci 0000:01:00.0: supports D1 D2
Oct 30 15:27:35 node-2 kernel: [    0.481934] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 30 15:27:35 node-2 kernel: [    0.481940] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 30 15:27:35 node-2 kernel: [    0.481944] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 30 15:27:35 node-2 kernel: [    0.482205] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.482264] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 30 15:27:35 node-2 kernel: [    0.493930] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 30 15:27:35 node-2 kernel: [    0.493936] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.493940] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 15:27:35 node-2 kernel: [    0.494020] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.494088] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.494165] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.494210] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 30 15:27:35 node-2 kernel: [    0.494213] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.494215] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 15:27:35 node-2 kernel: [    0.494270] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.494392] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.494460] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 30 15:27:35 node-2 kernel: [    0.494463] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.494465] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.494515] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.494634] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.494676] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.494798] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.494834] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.494954] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.494989] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 30 15:27:35 node-2 kernel: [    0.495108] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 30 15:27:35 node-2 kernel: [    0.495149] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 30 15:27:35 node-2 kernel: [    0.495151] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.495153] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.495214] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 30 15:27:35 node-2 kernel: [    0.495277] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.495329] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.495371] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 30 15:27:35 node-2 kernel: [    0.495477] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 30 15:27:35 node-2 kernel: [    0.495585] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 30 15:27:35 node-2 kernel: [    0.495588] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.495590] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.495645] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 30 15:27:35 node-2 kernel: [    0.495700] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.495751] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.495962] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 30 15:27:35 node-2 kernel: [    0.495966] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 30 15:27:35 node-2 kernel: [    0.496032] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 30 15:27:35 node-2 kernel: [    0.496085] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.496133] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.496346] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 30 15:27:35 node-2 kernel: [    0.496349] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 30 15:27:35 node-2 kernel: [    0.496409] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 30 15:27:35 node-2 kernel: [    0.496485] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.496536] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 30 15:27:35 node-2 kernel: [    0.496757] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 30 15:27:35 node-2 kernel: [    0.496761] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 30 15:27:35 node-2 kernel: [    0.496936] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 30 15:27:35 node-2 kernel: [    0.496974] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 30 15:27:35 node-2 kernel: [    0.497050] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 30 15:27:35 node-2 kernel: [    0.497068] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 30 15:27:35 node-2 kernel: [    0.497082] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 30 15:27:35 node-2 kernel: [    0.497095] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 30 15:27:35 node-2 kernel: [    0.497145] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 30 15:27:35 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 30 15:27:35 node-2 kernel: [    0.501937] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 30 15:27:35 node-2 kernel: [    0.501946] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 30 15:27:35 node-2 kernel: [    0.501999] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 30 15:27:35 node-2 kernel: [    0.502576] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 30 15:27:35 node-2 kernel: [    0.502579] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 15:27:35 node-2 kernel: [    0.502704] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 30 15:27:35 node-2 kernel: [    0.502811] PCI host bridge to bus 0000:80
Oct 30 15:27:35 node-2 kernel: [    0.502813] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 30 15:27:35 node-2 kernel: [    0.502815] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 30 15:27:35 node-2 kernel: [    0.502816] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 30 15:27:35 node-2 kernel: [    0.502824] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.502888] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.502957] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 30 15:27:35 node-2 kernel: [    0.503019] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 30 15:27:35 node-2 kernel: [    0.503024] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 30 15:27:35 node-2 kernel: [    0.503097] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 30 15:27:35 node-2 kernel: [    0.503397] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 30 15:27:35 node-2 kernel: [    0.503428] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 30 15:27:35 node-2 kernel: [    0.503457] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 30 15:27:35 node-2 kernel: [    0.503487] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 30 15:27:35 node-2 kernel: [    0.503516] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 15:27:35 node-2 kernel: [    0.503546] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 15:27:35 node-2 kernel: [    0.503575] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 15:27:35 node-2 kernel: [    0.503605] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 15:27:35 node-2 kernel: [    0.503690] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 30 15:27:35 node-2 kernel: [    0.503695] ACPI: \_SB_.UNC1: notify handler is installed
Oct 30 15:27:35 node-2 kernel: [    0.503696] ACPI: \_SB_.UNC0: notify handler is installed
Oct 30 15:27:35 node-2 kernel: [    0.503711] ACPI: \_SB_.PCI0: notify handler is installed
Oct 30 15:27:35 node-2 kernel: [    0.503764] ACPI: \_SB_.PCI1: notify handler is installed
Oct 30 15:27:35 node-2 kernel: [    0.503843] Found 4 acpi root devices
Oct 30 15:27:35 node-2 kernel: [    0.503953] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 30 15:27:35 node-2 kernel: [    0.503955] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 30 15:27:35 node-2 kernel: [    0.503956] vgaarb: loaded
Oct 30 15:27:35 node-2 kernel: [    0.503957] vgaarb: bridge control possible 0000:0c:00.0
Oct 30 15:27:35 node-2 kernel: [    0.504081] SCSI subsystem initialized
Oct 30 15:27:35 node-2 kernel: [    0.504146] libata version 3.00 loaded.
Oct 30 15:27:35 node-2 kernel: [    0.504164] ACPI: bus type USB registered
Oct 30 15:27:35 node-2 kernel: [    0.504175] usbcore: registered new interface driver usbfs
Oct 30 15:27:35 node-2 kernel: [    0.504180] usbcore: registered new interface driver hub
Oct 30 15:27:35 node-2 kernel: [    0.504205] usbcore: registered new device driver usb
Oct 30 15:27:35 node-2 kernel: [    0.504371] PCI: Using ACPI for IRQ routing
Oct 30 15:27:35 node-2 kernel: [    0.507986] PCI: pci_cache_line_size set to 64 bytes
Oct 30 15:27:35 node-2 kernel: [    0.508194] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 30 15:27:35 node-2 kernel: [    0.508195] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct 30 15:27:35 node-2 kernel: [    0.508196] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 30 15:27:35 node-2 kernel: [    0.508261] NetLabel: Initializing
Oct 30 15:27:35 node-2 kernel: [    0.508262] NetLabel:  domain hash size = 128
Oct 30 15:27:35 node-2 kernel: [    0.508263] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 30 15:27:35 node-2 kernel: [    0.508273] NetLabel:  unlabeled traffic allowed by default
Oct 30 15:27:35 node-2 kernel: [    0.508329] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 30 15:27:35 node-2 kernel: [    0.508333] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 30 15:27:35 node-2 kernel: [    0.510405] Switched to clocksource hpet
Oct 30 15:27:35 node-2 kernel: [    0.514912] AppArmor: AppArmor Filesystem Enabled
Oct 30 15:27:35 node-2 kernel: [    0.514950] pnp: PnP ACPI init
Oct 30 15:27:35 node-2 kernel: [    0.514962] ACPI: bus type PNP registered
Oct 30 15:27:35 node-2 kernel: [    0.515144] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515155] pnp 00:01: [dma 4]
Oct 30 15:27:35 node-2 kernel: [    0.515173] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515207] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515232] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515253] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515299] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515412] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515414] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 30 15:27:35 node-2 kernel: [    0.515416] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515418] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515419] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515421] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515424] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 30 15:27:35 node-2 kernel: [    0.515426] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515427] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515429] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515430] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515432] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515433] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 30 15:27:35 node-2 kernel: [    0.515436] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515536] pnp 00:07: [dma 0 disabled]
Oct 30 15:27:35 node-2 kernel: [    0.515568] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515649] pnp 00:08: [dma 0 disabled]
Oct 30 15:27:35 node-2 kernel: [    0.515685] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 30 15:27:35 node-2 kernel: [    0.515743] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 30 15:27:35 node-2 kernel: [    0.516183] pnp: PnP ACPI: found 10 devices
Oct 30 15:27:35 node-2 kernel: [    0.516185] ACPI: bus type PNP unregistered
Oct 30 15:27:35 node-2 kernel: [    0.522164] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 30 15:27:35 node-2 kernel: [    0.522168] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 30 15:27:35 node-2 kernel: [    0.522171] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 30 15:27:35 node-2 kernel: [    0.522176] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 30 15:27:35 node-2 kernel: [    0.522178] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522192] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522221] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 30 15:27:35 node-2 kernel: [    0.522236] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522265] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 30 15:27:35 node-2 kernel: [    0.522279] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 30 15:27:35 node-2 kernel: [    0.522308] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 30 15:27:35 node-2 kernel: [    0.522323] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 30 15:27:35 node-2 kernel: [    0.522352] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 30 15:27:35 node-2 kernel: [    0.522354] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522369] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522416] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 30 15:27:35 node-2 kernel: [    0.522418] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522433] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522462] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 30 15:27:35 node-2 kernel: [    0.522463] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522467] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522471] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 30 15:27:35 node-2 kernel: [    0.522473] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522476] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522481] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 30 15:27:35 node-2 kernel: [    0.522487] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 30 15:27:35 node-2 kernel: [    0.522496] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 30 15:27:35 node-2 kernel: [    0.522499] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 30 15:27:35 node-2 kernel: [    0.522507] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 30 15:27:35 node-2 kernel: [    0.522508] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 30 15:27:35 node-2 kernel: [    0.522508] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 30 15:27:35 node-2 kernel: [    0.522509] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 30 15:27:35 node-2 kernel: [    0.522510] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 30 15:27:35 node-2 kernel: [    0.522511] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 30 15:27:35 node-2 kernel: [    0.522512] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 30 15:27:35 node-2 kernel: [    0.522513] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 30 15:27:35 node-2 kernel: [    0.522514] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522515] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522516] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522517] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522518] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522519] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522520] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522521] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522522] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 30 15:27:35 node-2 kernel: [    0.522523] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522524] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 30 15:27:35 node-2 kernel: [    0.522525] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 30 15:27:35 node-2 kernel: [    0.522527] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 30 15:27:35 node-2 kernel: [    0.522528] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 30 15:27:35 node-2 kernel: [    0.522530] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 30 15:27:35 node-2 kernel: [    0.522531] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 30 15:27:35 node-2 kernel: [    0.522571] NET: Registered protocol family 2
Oct 30 15:27:35 node-2 kernel: [    0.522870] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.523245] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.523412] TCP: Hash tables configured (established 262144 bind 65536)
Oct 30 15:27:35 node-2 kernel: [    0.523454] TCP: reno registered
Oct 30 15:27:35 node-2 kernel: [    0.523485] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.523601] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.523762] NET: Registered protocol family 1
Oct 30 15:27:35 node-2 kernel: [    0.558431] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 30 15:27:35 node-2 kernel: [    0.558438] PCI: CLS 64 bytes, default 64
Oct 30 15:27:35 node-2 kernel: [    0.558482] Trying to unpack rootfs image as initramfs...
Oct 30 15:27:35 node-2 kernel: [    0.780443] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct 30 15:27:35 node-2 kernel: [    0.780487] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 30 15:27:35 node-2 kernel: [    0.780490] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct 30 15:27:35 node-2 kernel: [    0.780940] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.780954] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.780969] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.780981] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.780994] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781002] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781007] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781013] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781022] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781033] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781050] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781062] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781073] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781080] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781086] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781092] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 15:27:35 node-2 kernel: [    0.781140] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 30 15:27:35 node-2 kernel: [    0.781142] Scanning for low memory corruption every 60 seconds
Oct 30 15:27:35 node-2 kernel: [    0.781471] Initialise system trusted keyring
Oct 30 15:27:35 node-2 kernel: [    0.781518] audit: initializing netlink socket (disabled)
Oct 30 15:27:35 node-2 kernel: [    0.781529] type=2000 audit(1477841219.724:1): initialized
Oct 30 15:27:35 node-2 kernel: [    0.799291] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 30 15:27:35 node-2 kernel: [    0.800753] zbud: loaded
Oct 30 15:27:35 node-2 kernel: [    0.800872] VFS: Disk quotas dquot_6.5.2
Oct 30 15:27:35 node-2 kernel: [    0.800914] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 30 15:27:35 node-2 kernel: [    0.801252] fuse init (API version 7.22)
Oct 30 15:27:35 node-2 kernel: [    0.801308] msgmni has been set to 32768
Oct 30 15:27:35 node-2 kernel: [    0.801354] Key type big_key registered
Oct 30 15:27:35 node-2 kernel: [    0.801933] Key type asymmetric registered
Oct 30 15:27:35 node-2 kernel: [    0.801937] Asymmetric key parser 'x509' registered
Oct 30 15:27:35 node-2 kernel: [    0.801986] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 30 15:27:35 node-2 kernel: [    0.802068] io scheduler noop registered
Oct 30 15:27:35 node-2 kernel: [    0.802071] io scheduler deadline registered (default)
Oct 30 15:27:35 node-2 kernel: [    0.802113] io scheduler cfq registered
Oct 30 15:27:35 node-2 kernel: [    0.802640] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    0.802859] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    0.802977] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    0.803092] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    0.803210] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    0.803303] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    0.803714] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 30 15:27:35 node-2 kernel: [    0.803753] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 30 15:27:35 node-2 kernel: [    0.803783] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 30 15:27:35 node-2 kernel: [    0.803796] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803798] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803801] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 30 15:27:35 node-2 kernel: [    0.803806] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803807] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803809] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803810] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803812] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803821] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803823] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803824] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803825] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803827] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803828] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803830] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803832] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 30 15:27:35 node-2 kernel: [    0.803845] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803848] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 30 15:27:35 node-2 kernel: [    0.803859] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803862] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 30 15:27:35 node-2 kernel: [    0.803873] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803875] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 30 15:27:35 node-2 kernel: [    0.803878] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 30 15:27:35 node-2 kernel: [    0.803907] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 30 15:27:35 node-2 kernel: [    0.803912] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 30 15:27:35 node-2 kernel: [    0.803916] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 30 15:27:35 node-2 kernel: [    0.803924] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 30 15:27:35 node-2 kernel: [    0.803962] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 30 15:27:35 node-2 kernel: [    0.803964] vesafb: scrolling: redraw
Oct 30 15:27:35 node-2 kernel: [    0.803965] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 30 15:27:35 node-2 kernel: [    0.824364] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 30 15:27:35 node-2 kernel: [    0.832862] Console: switching to colour frame buffer device 80x30
Oct 30 15:27:35 node-2 kernel: [    0.841524] fb0: VESA VGA frame buffer device
Oct 30 15:27:35 node-2 kernel: [    0.841725] intel_idle: MWAIT substates: 0x2120
Oct 30 15:27:35 node-2 kernel: [    0.841726] intel_idle: v0.4 model 0x3F
Oct 30 15:27:35 node-2 kernel: [    0.841727] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 30 15:27:35 node-2 kernel: [    0.841971] ipmi message handler version 39.2
Oct 30 15:27:35 node-2 kernel: [    0.842260] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 30 15:27:35 node-2 kernel: [    0.842692] ACPI: AC Adapter [P111] (on-line)
Oct 30 15:27:35 node-2 kernel: [    0.847925] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 30 15:27:35 node-2 kernel: [    0.858935] ACPI: Power Button [PWRB]
Oct 30 15:27:35 node-2 kernel: [    0.864744] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 30 15:27:35 node-2 kernel: [    0.876387] ACPI: Power Button [PWRF]
Oct 30 15:27:35 node-2 kernel: [    0.895973] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 30 15:27:35 node-2 kernel: [    0.907637] pstore: Registered erst as persistent store backend
Oct 30 15:27:35 node-2 kernel: [    0.913837] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 30 15:27:35 node-2 kernel: [    0.925762] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 30 15:27:35 node-2 kernel: [    0.952498] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 30 15:27:35 node-2 kernel: [    0.985872] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 30 15:27:35 node-2 kernel: [    0.999892] Linux agpgart interface v0.103
Oct 30 15:27:35 node-2 kernel: [    1.007600] brd: module loaded
Oct 30 15:27:35 node-2 kernel: [    1.014633] loop: module loaded
Oct 30 15:27:35 node-2 kernel: [    1.021338] libphy: Fixed MDIO Bus: probed
Oct 30 15:27:35 node-2 kernel: [    1.027802] tun: Universal TUN/TAP device driver, 1.6
Oct 30 15:27:35 node-2 kernel: [    1.034262] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 30 15:27:35 node-2 kernel: [    1.040784] PPP generic driver version 2.4.2
Oct 30 15:27:35 node-2 kernel: [    1.047179] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 30 15:27:35 node-2 kernel: [    1.053609] ehci-pci: EHCI PCI platform driver
Oct 30 15:27:35 node-2 kernel: [    1.060115] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 30 15:27:35 node-2 kernel: [    1.066506] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 30 15:27:35 node-2 kernel: [    1.079010] ehci-pci 0000:00:1a.0: debug port 2
Oct 30 15:27:35 node-2 kernel: [    1.089189] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 30 15:27:35 node-2 kernel: [    1.089207] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 30 15:27:35 node-2 kernel: [    1.105892] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 30 15:27:35 node-2 kernel: [    1.111962] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 30 15:27:35 node-2 kernel: [    1.118119] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 30 15:27:35 node-2 kernel: [    1.129999] usb usb1: Product: EHCI Host Controller
Oct 30 15:27:35 node-2 kernel: [    1.136013] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 30 15:27:35 node-2 kernel: [    1.142052] usb usb1: SerialNumber: 0000:00:1a.0
Oct 30 15:27:35 node-2 kernel: [    1.147998] hub 1-0:1.0: USB hub found
Oct 30 15:27:35 node-2 kernel: [    1.153762] hub 1-0:1.0: 2 ports detected
Oct 30 15:27:35 node-2 kernel: [    1.159544] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 30 15:27:35 node-2 kernel: [    1.165126] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 30 15:27:35 node-2 kernel: [    1.176020] ehci-pci 0000:00:1d.0: debug port 2
Oct 30 15:27:35 node-2 kernel: [    1.185327] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 30 15:27:35 node-2 kernel: [    1.185330] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 30 15:27:35 node-2 kernel: [    1.201810] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 30 15:27:35 node-2 kernel: [    1.207007] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 30 15:27:35 node-2 kernel: [    1.212320] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 30 15:27:35 node-2 kernel: [    1.222894] usb usb2: Product: EHCI Host Controller
Oct 30 15:27:35 node-2 kernel: [    1.228364] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 30 15:27:35 node-2 kernel: [    1.233921] usb usb2: SerialNumber: 0000:00:1d.0
Oct 30 15:27:35 node-2 kernel: [    1.239442] hub 2-0:1.0: USB hub found
Oct 30 15:27:35 node-2 kernel: [    1.244803] hub 2-0:1.0: 2 ports detected
Oct 30 15:27:35 node-2 kernel: [    1.250146] ehci-platform: EHCI generic platform driver
Oct 30 15:27:35 node-2 kernel: [    1.255387] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 30 15:27:35 node-2 kernel: [    1.260718] ohci-pci: OHCI PCI platform driver
Oct 30 15:27:35 node-2 kernel: [    1.266033] ohci-platform: OHCI generic platform driver
Oct 30 15:27:35 node-2 kernel: [    1.271243] uhci_hcd: USB Universal Host Controller Interface driver
Oct 30 15:27:35 node-2 kernel: [    1.276594] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 30 15:27:35 node-2 kernel: [    1.469591] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 30 15:27:35 node-2 kernel: [    1.641844] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 30 15:27:35 node-2 kernel: [    1.647389] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 30 15:27:35 node-2 kernel: [    1.653113] hub 1-1:1.0: USB hub found
Oct 30 15:27:35 node-2 kernel: [    1.658580] hub 1-1:1.0: 6 ports detected
Oct 30 15:27:35 node-2 kernel: [    1.773324] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 30 15:27:35 node-2 kernel: [    2.041504] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 30 15:27:35 node-2 kernel: [    2.046978] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 30 15:27:35 node-2 kernel: [    2.052643] hub 2-1:1.0: USB hub found
Oct 30 15:27:35 node-2 kernel: [    2.058241] hub 2-1:1.0: 8 ports detected
Oct 30 15:27:35 node-2 kernel: [    2.317549] i8042: No controller found
Oct 30 15:27:35 node-2 kernel: [    2.322901] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 30 15:27:35 node-2 kernel: [    2.324155] mousedev: PS/2 mouse device common for all mice
Oct 30 15:27:35 node-2 kernel: [    2.326287] rtc_cmos 00:02: RTC can wake from S4
Oct 30 15:27:35 node-2 kernel: [    2.328150] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 30 15:27:35 node-2 kernel: [    2.328557] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 30 15:27:35 node-2 kernel: [    2.329573] device-mapper: uevent: version 1.0.3
Oct 30 15:27:35 node-2 kernel: [    2.330699] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 30 15:27:35 node-2 kernel: [    2.330892] ledtrig-cpu: registered to indicate activity on CPUs
Oct 30 15:27:35 node-2 kernel: [    2.332779] TCP: cubic registered
Oct 30 15:27:35 node-2 kernel: [    2.332934] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 30 15:27:35 node-2 kernel: [    2.333849] NET: Registered protocol family 10
Oct 30 15:27:35 node-2 kernel: [    2.336415] NET: Registered protocol family 17
Oct 30 15:27:35 node-2 kernel: [    2.336558] Key type dns_resolver registered
Oct 30 15:27:35 node-2 kernel: [    2.343070] Loading compiled-in X.509 certificates
Oct 30 15:27:35 node-2 kernel: [    2.345124] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 30 15:27:35 node-2 kernel: [    2.345423] registered taskstats version 1
Oct 30 15:27:35 node-2 kernel: [    2.384736] Key type trusted registered
Oct 30 15:27:35 node-2 kernel: [    2.404957] Key type encrypted registered
Oct 30 15:27:35 node-2 kernel: [    2.405006] AppArmor: AppArmor sha1 policy hashing enabled
Oct 30 15:27:35 node-2 kernel: [    2.405043] IMA: No TPM chip found, activating TPM-bypass!
Oct 30 15:27:35 node-2 kernel: [    2.414042] regulator-dummy: disabling
Oct 30 15:27:35 node-2 kernel: [    2.414779]   Magic number: 4:246:438
Oct 30 15:27:35 node-2 kernel: [    2.461577] rtc_cmos 00:02: setting system clock to 2016-10-30 15:27:01 UTC (1477841221)
Oct 30 15:27:35 node-2 kernel: [    2.474067] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 30 15:27:35 node-2 kernel: [    2.479852] EDD information not available.
Oct 30 15:27:35 node-2 kernel: [    2.485626] PM: Hibernation image not present or could not be loaded.
Oct 30 15:27:35 node-2 kernel: [    2.486501] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 30 15:27:35 node-2 kernel: [    2.498118] Write protecting the kernel read-only data: 12288k
Oct 30 15:27:35 node-2 kernel: [    2.504581] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 30 15:27:35 node-2 kernel: [    2.517728] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 30 15:27:35 node-2 kernel: [    2.521800] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 30 15:27:35 node-2 kernel: [    2.521801] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 30 15:27:35 node-2 kernel: [    2.521801] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 30 15:27:35 node-2 kernel: [    2.521802] usb 2-1.4: Manufacturer: Avocent
Oct 30 15:27:35 node-2 kernel: [    2.521803] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 30 15:27:35 node-2 kernel: [    2.587238] device-mapper: multipath: version 1.6.0 loaded
Oct 30 15:27:35 node-2 kernel: [    2.595415] systemd-udevd[217]: starting version 204
Oct 30 15:27:35 node-2 kernel: [    2.620360] md: linear personality registered for level -1
Oct 30 15:27:35 node-2 kernel: [    2.635465] md: multipath personality registered for level -4
Oct 30 15:27:35 node-2 kernel: [    2.643526] md: raid0 personality registered for level 0
Oct 30 15:27:35 node-2 kernel: [    2.651874] md: raid1 personality registered for level 1
Oct 30 15:27:35 node-2 kernel: [    2.661539] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 30 15:27:35 node-2 kernel: [    2.668035] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 30 15:27:35 node-2 kernel: [    2.668375] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 30 15:27:35 node-2 kernel: [    2.681070] hidraw: raw HID events driver (C) Jiri Kosina
Oct 30 15:27:35 node-2 kernel: [    2.681411] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct 30 15:27:35 node-2 kernel: [    2.681413] 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
Oct 30 15:27:35 node-2 kernel: [    2.681416] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 15:27:35 node-2 kernel: [    2.681419] megasas: FW now in Ready state
Oct 30 15:27:35 node-2 kernel: [    2.681540] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681561] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681578] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681597] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681634] enic 0000:06:00.0: irq 100 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681650] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681667] enic 0000:06:00.0: irq 102 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681789] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681855] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681893] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681930] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681950] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.681987] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682033] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682083] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682126] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682172] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682352] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682413] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682469] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682511] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.682854] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 30 15:27:35 node-2 kernel: [    2.693189] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct 30 15:27:35 node-2 kernel: [    2.693191] 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
Oct 30 15:27:35 node-2 kernel: [    2.693196] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 30 15:27:35 node-2 kernel: [    2.693336] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.693383] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.693430] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.693463] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.693499] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.693533] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.693709] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.703099] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct 30 15:27:35 node-2 kernel: [    2.703107] 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
Oct 30 15:27:35 node-2 kernel: [    2.703108] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 15:27:35 node-2 kernel: [    2.703200] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.703235] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.703273] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.703329] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.703455] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.714992] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct 30 15:27:35 node-2 kernel: [    2.715000] 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
Oct 30 15:27:35 node-2 kernel: [    2.715008] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 15:27:35 node-2 kernel: [    2.715086] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.715142] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.715186] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.715230] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.715349] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 15:27:35 node-2 kernel: [    2.724796] raid6: sse2x1    3838 MB/s
Oct 30 15:27:35 node-2 kernel: [    2.804625] raid6: sse2x2    1046 MB/s
Oct 30 15:27:35 node-2 kernel: [    2.876483] raid6: sse2x4    1365 MB/s
Oct 30 15:27:35 node-2 kernel: [    2.922555] usbcore: registered new interface driver usbhid
Oct 30 15:27:35 node-2 kernel: [    2.929207] usbhid: USB HID core driver
Oct 30 15:27:35 node-2 kernel: [    2.936817] 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
Oct 30 15:27:35 node-2 kernel: [    2.944376] raid6: avx2x1    9480 MB/s
Oct 30 15:27:35 node-2 kernel: [    2.956591] 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
Oct 30 15:27:35 node-2 kernel: [    2.969771] 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
Oct 30 15:27:35 node-2 kernel: [    2.982899] 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
Oct 30 15:27:35 node-2 kernel: [    2.996368] 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
Oct 30 15:27:35 node-2 kernel: [    3.010128] 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
Oct 30 15:27:35 node-2 kernel: [    3.012346] raid6: avx2x2    5229 MB/s
Oct 30 15:27:35 node-2 kernel: [    3.020394] megasas:IOC Init cmd success
Oct 30 15:27:35 node-2 kernel: [    3.044272] megasas: INIT adapter done
Oct 30 15:27:35 node-2 kernel: [    3.080208] raid6: avx2x4   20841 MB/s
Oct 30 15:27:35 node-2 kernel: [    3.086715] raid6: using algorithm avx2x4 (20841 MB/s)
Oct 30 15:27:35 node-2 kernel: [    3.093153] raid6: using avx2x2 recovery algorithm
Oct 30 15:27:35 node-2 kernel: [    3.100291] xor: automatically using best checksumming function:
Oct 30 15:27:35 node-2 kernel: [    3.144155]    avx       : 35530.000 MB/sec
Oct 30 15:27:35 node-2 kernel: [    3.144184] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 30 15:27:35 node-2 kernel: [    3.144521] scsi0 : LSI SAS based MegaRAID driver
Oct 30 15:27:35 node-2 kernel: [    3.151653] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 30 15:27:35 node-2 kernel: [    3.167089] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 30 15:27:35 node-2 kernel: [    3.172496] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 30 15:27:35 node-2 kernel: [    3.173148] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 30 15:27:35 node-2 kernel: [    3.173543] sd 0:2:0:0: [sda] Write Protect is off
Oct 30 15:27:35 node-2 kernel: [    3.173544] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 30 15:27:35 node-2 kernel: [    3.173637] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 30 15:27:35 node-2 kernel: [    3.203643]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 30 15:27:35 node-2 kernel: [    3.206290] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 30 15:27:35 node-2 kernel: [    3.241262] async_tx: api initialized (async)
Oct 30 15:27:35 node-2 kernel: [    3.251765] md: raid6 personality registered for level 6
Oct 30 15:27:35 node-2 kernel: [    3.258109] md: raid5 personality registered for level 5
Oct 30 15:27:35 node-2 kernel: [    3.264096] md: raid4 personality registered for level 4
Oct 30 15:27:35 node-2 kernel: [    3.272974] md: raid10 personality registered for level 10
Oct 30 15:27:35 node-2 kernel: [    3.320489] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Oct 30 15:27:35 node-2 kernel: [    3.373881] random: lvm urandom read with 30 bits of entropy available
Oct 30 15:27:35 node-2 kernel: [    3.460105] Switched to clocksource tsc
Oct 30 15:27:35 node-2 kernel: [    3.614014] bio: create slab <bio-1> at 1
Oct 30 15:27:35 node-2 kernel: [    4.307145] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 15:27:35 node-2 kernel: [    4.864524] init: plymouth-upstart-bridge main process (549) terminated with status 1
Oct 30 15:27:35 node-2 kernel: [    4.876418] init: plymouth-upstart-bridge main process ended, respawning
Oct 30 15:27:35 node-2 kernel: [    4.886904] init: plymouth-upstart-bridge main process (560) terminated with status 1
Oct 30 15:27:35 node-2 kernel: [    4.898934] init: plymouth-upstart-bridge main process ended, respawning
Oct 30 15:27:35 node-2 kernel: [    4.959963] random: nonblocking pool is initialized
Oct 30 15:27:35 node-2 kernel: [    5.023260] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 30 15:27:35 node-2 kernel: [    5.061812] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 30 15:27:35 node-2 kernel: [    5.230104] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 30 15:27:35 node-2 kernel: [    5.278083] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 30 15:27:35 node-2 kernel: [    5.371103] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 15:27:35 node-2 kernel: [    5.522957] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 30 15:27:35 node-2 kernel: [    5.580925] XFS (dm-0): Mounting Filesystem
Oct 30 15:27:35 node-2 kernel: [    5.908374] XFS (dm-0): Ending clean mount
Oct 30 15:27:35 node-2 kernel: [    5.999851] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 15:27:35 node-2 kernel: [    6.023728] XFS (dm-1): Mounting Filesystem
Oct 30 15:27:35 node-2 kernel: [    6.107850] XFS (dm-1): Ending clean mount
Oct 30 15:27:35 node-2 kernel: [    7.971576] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 30 15:27:35 node-2 kernel: [    7.997356] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 30 15:27:35 node-2 kernel: [    8.229804] systemd-udevd[777]: starting version 204
Oct 30 15:27:35 node-2 kernel: [    8.427085] wmi: Mapper loaded
Oct 30 15:27:35 node-2 kernel: [    8.428491] power_meter ACPI000D:00: Found ACPI power meter.
Oct 30 15:27:35 node-2 kernel: [    8.428512] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 30 15:27:35 node-2 kernel: [    8.436676] IPMI System Interface driver.
Oct 30 15:27:35 node-2 kernel: [    8.436734] ipmi_si: probing via ACPI
Oct 30 15:27:35 node-2 kernel: [    8.436748] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 30 15:27:35 node-2 kernel: [    8.436749] ipmi_si: Adding ACPI-specified kcs state machine
Oct 30 15:27:35 node-2 kernel: [    8.436759] ipmi_si: probing via SMBIOS
Oct 30 15:27:35 node-2 kernel: [    8.436760] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 30 15:27:35 node-2 kernel: [    8.436761] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 30 15:27:35 node-2 kernel: [    8.436763] ipmi_si: probing via SPMI
Oct 30 15:27:35 node-2 kernel: [    8.436765] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 30 15:27:35 node-2 kernel: [    8.436766] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 30 15:27:35 node-2 kernel: [    8.436767] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 30 15:27:35 node-2 kernel: [    8.438275] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 30 15:27:35 node-2 kernel: [    8.438280] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 30 15:27:35 node-2 kernel: [    8.438285] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 30 15:27:35 node-2 kernel: [    8.438288] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 30 15:27:35 node-2 kernel: [    8.438314] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 30 15:27:35 node-2 kernel: [    8.448998] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 30 15:27:35 node-2 kernel: [    8.520105] systemd-udevd[820]: renamed network interface eth0 to enp6s0
Oct 30 15:27:35 node-2 kernel: [    8.544117] systemd-udevd[828]: renamed network interface eth2 to enp8s0
Oct 30 15:27:35 node-2 kernel: [    8.572103] systemd-udevd[821]: renamed network interface eth1 to enp7s0
Oct 30 15:27:35 node-2 kernel: [    8.583089] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 30 15:27:35 node-2 kernel: [    8.583095] ipmi_si 00:09: IPMI kcs interface initialized
Oct 30 15:27:35 node-2 kernel: [    8.595929] systemd-udevd[795]: renamed network interface eth3 to enp9s0
Oct 30 15:27:35 node-2 kernel: [    8.861553] type=1400 audit(1477841227.943:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1030 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.861710] type=1400 audit(1477841227.943:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1030 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.861839] type=1400 audit(1477841227.943:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1030 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.872108] type=1400 audit(1477841227.955:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1025 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.872254] type=1400 audit(1477841227.955:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1025 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.872374] type=1400 audit(1477841227.955:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1025 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.883631] type=1400 audit(1477841227.967:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1020 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.883871] type=1400 audit(1477841227.967:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1020 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.884070] type=1400 audit(1477841227.967:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1020 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    8.889089] type=1400 audit(1477841227.971:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1031 comm="apparmor_parser"
Oct 30 15:27:35 node-2 kernel: [    9.562944] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 30 15:27:35 node-2 kernel: [    9.563682] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 30 15:27:35 node-2 kernel: [    9.742243] enic 0000:06:00.0 enp6s0: Link UP
Oct 30 15:27:35 node-2 kernel: [    9.742673] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 30 15:27:35 node-2 kernel: [    9.742680] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 30 15:27:35 node-2 kernel: [   18.750610] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 30 15:27:36 node-2 failsafe: Failsafe of 120 seconds reached.
Oct 30 15:27:36 node-2 kernel: [   37.676826] init: failsafe main process (8423) killed by TERM signal
Oct 30 15:27:37 node-2 dbus[8458]: [system] AppArmor D-Bus mediation is enabled
Oct 30 15:27:37 node-2 kernel: [   37.927795] audit_printk_skb: 30 callbacks suppressed
Oct 30 15:27:37 node-2 kernel: [   37.927796] type=1400 audit(1477841257.218:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8548 comm="apparmor_parser"
Oct 30 15:27:37 node-2 kernel: [   37.927800] type=1400 audit(1477841257.218:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8548 comm="apparmor_parser"
Oct 30 15:27:37 node-2 kernel: [   37.927803] type=1400 audit(1477841257.218:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Oct 30 15:27:37 node-2 kernel: [   37.928020] type=1400 audit(1477841257.218:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8548 comm="apparmor_parser"
Oct 30 15:27:37 node-2 kernel: [   37.928022] type=1400 audit(1477841257.218:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Oct 30 15:27:37 node-2 kernel: [   37.928133] type=1400 audit(1477841257.218:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Oct 30 15:27:37 node-2 kernel: [   37.930714] type=1400 audit(1477841257.222:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8549 comm="apparmor_parser"
Oct 30 15:27:37 node-2 kernel: [   38.004819] type=1400 audit(1477841257.294:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8551 comm="apparmor_parser"
Oct 30 15:27:37 node-2 anacron[8616]: Anacron 2.3 started on 2016-10-30
Oct 30 15:27:37 node-2 anacron[8616]: Will run job `cron.daily' in 5 min.
Oct 30 15:27:37 node-2 anacron[8616]: Will run job `cron.weekly' in 10 min.
Oct 30 15:27:37 node-2 anacron[8616]: Will run job `cron.monthly' in 15 min.
Oct 30 15:27:37 node-2 anacron[8616]: Jobs will be executed sequentially
Oct 30 15:27:37 node-2 cron[8581]: (CRON) INFO (pidfile fd = 3)
Oct 30 15:27:37 node-2 cron[8623]: (CRON) STARTUP (fork ok)
Oct 30 15:27:37 node-2 multipathd: path checkers start up
Oct 30 15:27:37 node-2 cron[8623]: (CRON) INFO (Running @reboot jobs)
Oct 30 15:27:37 node-2 postfix/master[8760]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 30 15:27:41 node-2 puppet-agent[8944]: Reopening log files
Oct 30 15:27:42 node-2 puppet-agent[8944]: Could not request certificate: Connection refused - connect(2)
Oct 30 15:27:55 node-2 puppet-user[9023]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 30 15:27:55 node-2 puppet-user[9023]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 30 15:27:56 node-2 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 30 15:27:56 node-2 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 30 15:27:56 node-2 puppet-user[9023]: Finished catalog run in 0.88 seconds
Oct 30 15:27:57 node-2 multipathd: uevent trigger error
Oct 30 15:27:57 node-2 puppet-user[9582]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 30 15:27:57 node-2 puppet-user[9582]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Oct 30 15:27:57 node-2 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 30 15:27:57 node-2 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 30 15:27:57 node-2 puppet-user[9582]: (/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"]'
Oct 30 15:27:57 node-2 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 30 15:27:57 node-2 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 30 15:27:57 node-2 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 30 15:27:57 node-2 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 30 15:27:57 node-2 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 30 15:27:57 node-2 puppet-user[9582]: Finished catalog run in 0.07 seconds
Oct 30 15:27:59 node-2 puppet-user[10043]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 30 15:27:59 node-2 puppet-user[10043]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Oct 30 15:27:59 node-2 puppet-user[10043]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 30 15:27:59 node-2 puppet-user[10043]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 30 15:27:59 node-2 puppet-user[10043]: Finished catalog run in 0.03 seconds
Oct 30 15:28:00 node-2 puppet-user[10505]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 30 15:28:00 node-2 puppet-user[10505]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 30 15:28:00 node-2 puppet-user[10505]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 30 15:28:00 node-2 puppet-user[10505]: Finished catalog run in 0.05 seconds
Oct 30 15:28:01 node-2 CRON[10969]: (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")
Oct 30 15:28:02 node-2 puppet-user[10961]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 30 15:28:02 node-2 puppet-user[10961]: Compiled catalog for node-2.domain.tld in environment production in 0.17 seconds
Oct 30 15:28:02 node-2 puppet-user[10961]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 30 15:28:02 node-2 puppet-user[10961]: (/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
Oct 30 15:28:03 node-2 puppet-user[10961]: (/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
Oct 30 15:28:03 node-2 puppet-user[10961]: (/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
Oct 30 15:28:03 node-2 puppet-user[10961]: Finished catalog run in 1.22 seconds
Oct 30 15:28:04 node-2 puppet-user[11506]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 30 15:28:05 node-2 puppet-user[11506]: Compiled catalog for node-2.domain.tld in environment production in 0.29 seconds
Oct 30 15:28:05 node-2 puppet-user[11506]: (/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
Oct 30 15:28:05 node-2 puppet-user[11506]: (/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
Oct 30 15:28:05 node-2 puppet-user[11506]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 30 15:28:05 node-2 puppet-user[11506]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 30 15:28:05 node-2 puppet-user[11506]: (/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
Oct 30 15:28:05 node-2 puppet-user[11506]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 30 15:28:05 node-2 puppet-user[11506]: Finished catalog run in 0.38 seconds
Oct 30 15:28:07 node-2 puppet-user[11996]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 30 15:28:07 node-2 puppet-user[11996]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Oct 30 15:28:07 node-2 puppet-user[11996]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 30 15:28:07 node-2 kernel: [   68.019978] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 30 15:28:07 node-2 kernel: [   68.020028] 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.
Oct 30 15:28:07 node-2 puppet-user[11996]: (/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'
Oct 30 15:28:07 node-2 puppet-user[11996]: Finished catalog run in 0.06 seconds
Oct 30 15:28:09 node-2 puppet-user[12646]: (Scope(Class[main])) MODULAR: sync_time
Oct 30 15:28:09 node-2 puppet-user[12646]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 30 15:28:09 node-2 ntpdate[13061]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 30 15:28:15 node-2 ntpdate[13061]: adjust time server 10.20.0.2 offset -0.086862 sec
Oct 30 15:28:15 node-2 puppet-user[12646]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 30 15:28:15 node-2 puppet-user[12646]: Finished catalog run in 6.17 seconds
Oct 30 15:28:19 node-2 puppet-user[13258]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 30 15:28:19 node-2 puppet-user[13258]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Oct 30 15:28:19 node-2 puppet-user[13258]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 30 15:28:19 node-2 puppet-user[13258]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Oct 30 15:28:19 node-2 puppet-user[13258]: Finished catalog run in 0.07 seconds
Oct 30 15:28:20 node-2 kernel: [   81.020560] init: plymouth-upstart-bridge main process ended, respawning
Oct 30 15:28:20 node-2 puppet-agent[8944]: Could not run: SIGTERM
Oct 30 15:28:20 node-2 kernel: [   81.250090] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 30 15:28:20 node-2 ec2: 
Oct 30 15:28:20 node-2 ec2: #############################################################
Oct 30 15:28:20 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 30 15:28:20 node-2 ec2: 1024 3a:2b:a4:b4:e7:bf:35:2b:5e:6d:9a:2e:50:59:7c:cd  root@node-2.domain.tld (DSA)
Oct 30 15:28:20 node-2 ec2: 256 4c:75:29:04:4f:a3:da:a4:13:34:03:f2:2e:a3:1f:06  root@node-2.domain.tld (ECDSA)
Oct 30 15:28:20 node-2 ec2: 256 42:03:fb:bd:27:5f:ce:43:92:5e:0b:a9:c3:68:fd:04  root@node-2.domain.tld (ED25519)
Oct 30 15:28:20 node-2 ec2: 2048 db:dd:49:a7:3d:77:91:c2:39:db:9c:d9:9e:68:86:64  root@node-2.domain.tld (RSA)
Oct 30 15:28:20 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 30 15:28:20 node-2 ec2: #############################################################
Oct 30 15:28:21 node-2 puppet-user[13737]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 30 15:28:21 node-2 puppet-user[13737]: Compiled catalog for node-2.domain.tld in environment production in 0.48 seconds
Oct 30 15:28:21 node-2 puppet-user[13737]: (/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
Oct 30 15:28:21 node-2 puppet-user[13737]: (/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
Oct 30 15:28:21 node-2 puppet-user[13737]: (/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
Oct 30 15:28:21 node-2 puppet-user[13737]: (/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
Oct 30 15:28:21 node-2 puppet-user[13737]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 30 15:28:21 node-2 puppet-user[13737]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 30 15:28:21 node-2 puppet-user[13737]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 30 15:28:21 node-2 puppet-user[13737]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 30 15:28:21 node-2 puppet-user[13737]: (/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
Oct 30 15:28:21 node-2 puppet-user[13737]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 30 15:28:22 node-2 puppet-user[13737]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 30 15:28:22 node-2 puppet-user[13737]: Finished catalog run in 0.94 seconds
Oct 30 15:28:24 node-2 puppet-user[14394]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 30 15:28:24 node-2 puppet-user[14394]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Oct 30 15:28:25 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 15:28:25 node-2 nailgun-agent: D, [2016-10-30T15:28:01.684947 #10972] DEBUG -- : Sleep for 24 seconds before sending request
Oct 30 15:28:25 node-2 nailgun-agent: I, [2016-10-30T15:28:25.697507 #10972]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 30 15:28:26 node-2 nailgun-agent: D, [2016-10-30T15:28:26.235098 #10972] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 30 15:28:27 node-2 puppet-user[14394]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.341600 #10972] DEBUG -- : Trying to find block devices
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.341730 #10972] DEBUG -- : Found block device: sda
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.341914 #10972] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.341975 #10972] DEBUG -- : Trying to get list of physical devices
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.342383 #10972] DEBUG -- : Getting udev properties for device: sda
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.345543 #10972] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc788
Oct 30 15:28:38 node-2 nailgun-agent: 6005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53627", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.345596 #10972] DEBUG -- : Trying to find out if device sda is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.345720 #10972] DEBUG -- : Device sda removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.345751 #10972] DEBUG -- : Device sda seems to be appropriate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.346471 #10972] DEBUG -- : Getting udev properties for device: dm-0
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.349286 #10972] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-nBGoSV3Q0HQaP0Hz3qwn2djU9DDj58PXHoWwYpicbuJfdm4aREXsPYmKuw4NU7zR /dev/disk/by-uuid/55c34687-a2ca-4c60-8502-3aa9142d7c48 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-nBGoSV3Q0HQaP0Hz3qwn2djU9DDj58PXHoWwYpicbuJfdm4aREXsPYmKuw4NU7zR", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"55c34687-a2ca-4c60-8502-3aa9142d7c48", "ID_FS_UUID_ENC"=>"55c34687-a2ca-4c60-8502-3aa9142d7c48", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62160", "nomdmonddf"=>"1", "nom
Oct 30 15:28:38 node-2 nailgun-agent: dmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.349336 #10972] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.349395 #10972] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.349443 #10972] DEBUG -- : Device dm-0 seems to be appropriate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.349472 #10972] DEBUG -- : Getting udev properties for device: dm-1
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.358399 #10972] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-0HNZ0bRB9har682L70vvDvVkO10RV2GLjGQCqwfO7MT3js8BcW2EPWmTWtXX6T79 /dev/disk/by-uuid/be34c1b1-5fd6-4cde-a7e2-7d74465dccf0 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-0HNZ0bRB9har682L70vvDvVkO10RV2GLjGQCqwfO7MT3js8BcW2EPWmTWtXX6T79", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"be34c1b1-5fd6-4cde-a7e2-7d74465dccf0", "ID_FS_UUID_ENC"=>"be34c1b1-5fd6-4cde-a7e2-7d74465dccf0", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9
Oct 30 15:28:38 node-2 nailgun-agent: 7949", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.358487 #10972] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.358583 #10972] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.358623 #10972] DEBUG -- : Device dm-1 seems to be appropriate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.358668 #10972] DEBUG -- : Getting udev properties for device: dm-2
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.362922 #10972] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-71fEC4B58xzLCS0clC8UFQPZwZbtC0273Pq1fL3yrwQWXDzPXylTxzEAajr9lLoj /dev/disk/by-uuid/5dd58fb5-cc57-40e2-8814-a20f31f80f6c /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-71fEC4B58xzLCS0clC8UFQPZwZbtC0273Pq1fL3yrwQWXDzPXylTxzEAajr9lLoj", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"5dd58fb5-cc57-40e2-8814-a20f31f80f6c", "ID_FS_UUID_ENC"=>"5dd58fb5-cc57-40e2-8814-a20f31f80f6c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8606", "nomdmond
Oct 30 15:28:38 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.362991 #10972] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.363078 #10972] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.363153 #10972] DEBUG -- : Device dm-2 seems to be appropriate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.363194 #10972] DEBUG -- : Getting udev properties for device: dm-3
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.367086 #10972] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-rPDuUYdanvoTwMg4GV2xVBNIS91fx7zOcWdxsPSYqTOJBW2BpSltrxRewRB9u1U9 /dev/disk/by-uuid/b747823b-0991-447b-b63a-6682af8e8349 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-rPDuUYdanvoTwMg4GV2xVBNIS91fx7zOcWdxsPSYqTOJBW2BpSltrxRewRB9u1U9", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b747823b-0991-447b-b63a-6682af8e8349", "ID_FS_UUID_ENC"=>"b747823b-0991-447b-b63a-6682af8e8349", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13157", "nomdmonddf"=>"1",
Oct 30 15:28:38 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.367158 #10972] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.367248 #10972] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.367291 #10972] DEBUG -- : Device dm-3 seems to be appropriate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.367352 #10972] DEBUG -- : Getting udev properties for device: dm-4
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.370228 #10972] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-K2z2E5dS4eMpYxndhihwqJBqtOxoakqxdbgAWypSwmERYwJqtcaXruMbfbHIVOgC /dev/disk/by-uuid/d0190e4f-9fd7-46e6-b01b-a6d011235260 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-K2z2E5dS4eMpYxndhihwqJBqtOxoakqxdbgAWypSwmERYwJqtcaXruMbfbHIVOgC", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d0190e4f-9fd7-46e6-b01b-a6d011235260", "ID_FS_UUID_ENC"=>"d0190e4f-9fd7-46e6-b01b-a6d011235260", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15414", "nomdmonddf"=>"1", "nom
Oct 30 15:28:38 node-2 nailgun-agent: dmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.370301 #10972] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.370387 #10972] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.370426 #10972] DEBUG -- : Device dm-4 seems to be appropriate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.370465 #10972] DEBUG -- : Getting udev properties for device: dm-5
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.374785 #10972] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-K2z2E5dS4eMpYxndhihwqJBqtOxoakqx9CvAlKP40uUoniG5Me7LLfcQu52uCsOx /dev/disk/by-uuid/933c7ccb-2327-4d0a-a5f8-46f1ffb9bf34 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-K2z2E5dS4eMpYxndhihwqJBqtOxoakqx9CvAlKP40uUoniG5Me7LLfcQu52uCsOx", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"933c7ccb-2327-4d0a-a5f8-46f1ffb9bf34", "ID_FS_UUID_ENC"=>"933c7ccb-2327-4d0a-a5f8-46f1ffb9bf34", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15849", "nomdmonddf"=>"1", "nomdmonisw
Oct 30 15:28:38 node-2 nailgun-agent: "=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.374939 #10972] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.375011 #10972] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.375043 #10972] DEBUG -- : Device dm-5 seems to be appropriate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.375077 #10972] DEBUG -- : Getting udev properties for device: ram0
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.377800 #10972] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82567", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.377847 #10972] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.377908 #10972] DEBUG -- : Device ram0 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.377968 #10972] DEBUG -- : Getting udev properties for device: ram1
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.381846 #10972] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82695", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.381902 #10972] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.382011 #10972] DEBUG -- : Device ram1 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.382056 #10972] DEBUG -- : Getting udev properties for device: ram2
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.385179 #10972] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83338", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.385235 #10972] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.385399 #10972] DEBUG -- : Device ram2 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.385446 #10972] DEBUG -- : Getting udev properties for device: ram3
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.389167 #10972] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83419", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.389222 #10972] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.389300 #10972] DEBUG -- : Device ram3 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.389345 #10972] DEBUG -- : Getting udev properties for device: ram4
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.391957 #10972] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83489", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.392006 #10972] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.392070 #10972] DEBUG -- : Device ram4 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.392108 #10972] DEBUG -- : Getting udev properties for device: ram5
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.395429 #10972] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83571", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.395487 #10972] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.395564 #10972] DEBUG -- : Device ram5 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.395675 #10972] DEBUG -- : Getting udev properties for device: ram6
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.397994 #10972] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83630", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.398041 #10972] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.398118 #10972] DEBUG -- : Device ram6 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.398185 #10972] DEBUG -- : Getting udev properties for device: ram7
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.400689 #10972] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83743", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.400746 #10972] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.400856 #10972] DEBUG -- : Device ram7 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.400902 #10972] DEBUG -- : Getting udev properties for device: ram8
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.403475 #10972] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83810", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.403567 #10972] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.403643 #10972] DEBUG -- : Device ram8 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.403689 #10972] DEBUG -- : Getting udev properties for device: ram9
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.406265 #10972] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83875", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.406321 #10972] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.406464 #10972] DEBUG -- : Device ram9 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.406534 #10972] DEBUG -- : Getting udev properties for device: loop0
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.410506 #10972] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81866", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.410573 #10972] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.410716 #10972] DEBUG -- : Device loop0 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.410770 #10972] DEBUG -- : Getting udev properties for device: loop1
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.414275 #10972] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81959", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.414344 #10972] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.414457 #10972] DEBUG -- : Device loop1 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.414512 #10972] DEBUG -- : Getting udev properties for device: loop2
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.417320 #10972] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82047", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.417392 #10972] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.417452 #10972] DEBUG -- : Device loop2 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.417519 #10972] DEBUG -- : Getting udev properties for device: loop3
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.420735 #10972] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82133", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.420804 #10972] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.420909 #10972] DEBUG -- : Device loop3 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.420965 #10972] DEBUG -- : Getting udev properties for device: loop4
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.423972 #10972] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82210", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.424074 #10972] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.424208 #10972] DEBUG -- : Device loop4 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.424289 #10972] DEBUG -- : Getting udev properties for device: loop5
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.427565 #10972] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82288", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.427633 #10972] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.427732 #10972] DEBUG -- : Device loop5 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.427816 #10972] DEBUG -- : Getting udev properties for device: loop6
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.431570 #10972] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82367", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.431642 #10972] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.431708 #10972] DEBUG -- : Device loop6 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.431760 #10972] DEBUG -- : Getting udev properties for device: loop7
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.434366 #10972] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82446", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.434416 #10972] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.434520 #10972] DEBUG -- : Device loop7 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.434558 #10972] DEBUG -- : Getting udev properties for device: ram10
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.437746 #10972] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82811", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.437795 #10972] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.437881 #10972] DEBUG -- : Device ram10 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.437937 #10972] DEBUG -- : Getting udev properties for device: ram11
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.440893 #10972] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82894", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.440942 #10972] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.441052 #10972] DEBUG -- : Device ram11 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.441114 #10972] DEBUG -- : Getting udev properties for device: ram12
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.452897 #10972] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82997", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.452970 #10972] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.453066 #10972] DEBUG -- : Device ram12 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.453119 #10972] DEBUG -- : Getting udev properties for device: ram13
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.457389 #10972] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83092", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.457458 #10972] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.457554 #10972] DEBUG -- : Device ram13 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.457609 #10972] DEBUG -- : Getting udev properties for device: ram14
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.461778 #10972] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83169", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.461849 #10972] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.461960 #10972] DEBUG -- : Device ram14 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.462016 #10972] DEBUG -- : Getting udev properties for device: ram15
Oct 30 15:28:38 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.465766 #10972] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83280", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.465925 #10972] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466049 #10972] DEBUG -- : Device ram15 removable parameter: "0"
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466143 #10972] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466182 #10972] DEBUG -- : Block device seems to be physical data storage: sda
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466272 #10972] DEBUG -- : Found block device: dm-0
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466312 #10972] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466347 #10972] DEBUG -- : Found block device: dm-1
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466378 #10972] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466405 #10972] DEBUG -- : Found block device: dm-2
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466433 #10972] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466535 #10972] DEBUG -- : Found block device: dm-3
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466575 #10972] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466601 #10972] DEBUG -- : Found block device: dm-4
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466629 #10972] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466657 #10972] DEBUG -- : Found block device: dm-5
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466688 #10972] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466714 #10972] DEBUG -- : Found block device: ram0
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466742 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466765 #10972] DEBUG -- : Found block device: ram1
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466793 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.466971 #10972] DEBUG -- : Found block device: ram2
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467009 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467036 #10972] DEBUG -- : Found block device: ram3
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467062 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467087 #10972] DEBUG -- : Found block device: ram4
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467114 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467137 #10972] DEBUG -- : Found block device: ram5
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467164 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467190 #10972] DEBUG -- : Found block device: ram6
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467221 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467357 #10972] DEBUG -- : Found block device: ram7
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467384 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467409 #10972] DEBUG -- : Found block device: ram8
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467438 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467464 #10972] DEBUG -- : Found block device: ram9
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467491 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467517 #10972] DEBUG -- : Found block device: loop0
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467545 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467570 #10972] DEBUG -- : Found block device: loop1
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467685 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467711 #10972] DEBUG -- : Found block device: loop2
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467740 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467764 #10972] DEBUG -- : Found block device: loop3
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467795 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467821 #10972] DEBUG -- : Found block device: loop4
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467849 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467874 #10972] DEBUG -- : Found block device: loop5
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.467902 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468016 #10972] DEBUG -- : Found block device: loop6
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468046 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468072 #10972] DEBUG -- : Found block device: loop7
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468099 #10972] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468122 #10972] DEBUG -- : Found block device: ram10
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468151 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468177 #10972] DEBUG -- : Found block device: ram11
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468203 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468229 #10972] DEBUG -- : Found block device: ram12
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468258 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468384 #10972] DEBUG -- : Found block device: ram13
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468414 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468441 #10972] DEBUG -- : Found block device: ram14
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468467 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468492 #10972] DEBUG -- : Found block device: ram15
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468518 #10972] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.468593 #10972] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct 30 15:28:38 node-2 nailgun-agent: D, [2016-10-30T15:28:38.737059 #10972] DEBUG -- : Response: status: 200 body: {"id": 2}
Oct 30 15:28:38 node-2 nailgun-agent: I, [2016-10-30T15:28:38.740406 #10972]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 30 15:28:53 node-2 puppet-user[14394]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 30 15:28:53 node-2 puppet-user[14394]: Finished catalog run in 29.15 seconds
Oct 30 15:28:55 node-2 puppet-user[17143]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 30 15:28:55 node-2 puppet-user[17143]: Compiled catalog for node-2.domain.tld in environment production in 0.56 seconds
Oct 30 15:28:56 node-2 puppet-user[17143]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 30 15:28:56 node-2 puppet-user[17143]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 30 15:28:56 node-2 puppet-user[17143]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 30 15:28:56 node-2 puppet-user[17143]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 30 15:28:56 node-2 puppet-user[17143]: Finished catalog run in 0.09 seconds
Oct 30 15:28:57 node-2 puppet-user[17605]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 30 15:28:58 node-2 puppet-user[17605]: Compiled catalog for node-2.domain.tld in environment production in 0.87 seconds
Oct 30 15:28:59 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 30 15:28:59 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 30 15:28:59 node-2 crontab[18045]: (root) LIST (root)
Oct 30 15:28:59 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 30 15:28:59 node-2 crontab[18046]: (root) REPLACE (root)
Oct 30 15:29:00 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/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
Oct 30 15:29:01 node-2 puppet-user[17605]: (/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
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/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
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/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
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/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
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 30 15:29:01 node-2 CRON[18201]: (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")
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/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
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 30 15:29:01 node-2 puppet-user[17605]: (/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
Oct 30 15:29:02 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 30 15:29:02 node-2 puppet-user[17605]: (/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
Oct 30 15:29:02 node-2 puppet-user[17605]: (/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
Oct 30 15:29:02 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 30 15:29:02 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 30 15:29:02 node-2 puppet-user[17605]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 30 15:29:02 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8395" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 15:29:02 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 30 15:29:04 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:04 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:04 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:04 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:04 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:17 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:17 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:17 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:17 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:17 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:17 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:17 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:29:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:16 node-2 ntpdate[28456]: no servers can be used, exiting
<27>Oct 30 15:30:16 node-2 ntpdate[28628]: no servers can be used, exiting
<27>Oct 30 15:30:47 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:47 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:47 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:47 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:47 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:47 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:50 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:50 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:50 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:50 node-2 multipathd: uevent trigger error
<27>Oct 30 15:30:50 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:01 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:01 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:01 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:01 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:01 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:03 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:03 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:03 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:04 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:04 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:31:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:08 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 15:32:08 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 15:32:14 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 15:32:14 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 15:32:20 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 15:32:25 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 15:32:25 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 15:32:32 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:32 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:32 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:32 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:32 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:54 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:54 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:54 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:54 node-2 multipathd: uevent trigger error
<27>Oct 30 15:32:54 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:00 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:02 node-2 haproxy[18272]: 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>Oct 30 15:33:02 node-2 haproxy[18272]: 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>Oct 30 15:33:03 node-2 haproxy[18279]: 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>Oct 30 15:33:03 node-2 haproxy[18279]: proxy mysqld has no server available!
<27>Oct 30 15:33:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:09 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:09 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:09 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:09 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:09 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:11 node-2 haproxy[20738]: 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>Oct 30 15:33:11 node-2 haproxy[20738]: 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>Oct 30 15:33:12 node-2 haproxy[20742]: 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>Oct 30 15:33:12 node-2 haproxy[20742]: proxy mysqld has no server available!
<129>Oct 30 15:33:12 node-2 haproxy[20742]: 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>Oct 30 15:33:12 node-2 haproxy[20742]: 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>Oct 30 15:33:12 node-2 haproxy[20742]: 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>Oct 30 15:33:12 node-2 haproxy[20742]: proxy object-storage has no server available!
<27>Oct 30 15:33:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:14 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:16 node-2 haproxy[21961]: 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>Oct 30 15:33:16 node-2 haproxy[21961]: 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>Oct 30 15:33:16 node-2 haproxy[21961]: 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>Oct 30 15:33:16 node-2 haproxy[21961]: proxy neutron has no server available!
<129>Oct 30 15:33:17 node-2 haproxy[21972]: 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>Oct 30 15:33:17 node-2 haproxy[21972]: 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>Oct 30 15:33:17 node-2 haproxy[21972]: 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>Oct 30 15:33:17 node-2 haproxy[21972]: proxy mysqld has no server available!
<129>Oct 30 15:33:17 node-2 haproxy[21972]: 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>Oct 30 15:33:17 node-2 haproxy[21972]: 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>Oct 30 15:33:18 node-2 haproxy[21972]: 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>Oct 30 15:33:18 node-2 haproxy[21972]: proxy object-storage has no server available!
<27>Oct 30 15:33:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:19 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:19 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:21 node-2 haproxy[23419]: 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>Oct 30 15:33:21 node-2 haproxy[23419]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: proxy keystone-1 has no server available!
<129>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: proxy keystone-2 has no server available!
<129>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:22 node-2 haproxy[23423]: proxy neutron has no server available!
<129>Oct 30 15:33:22 node-2 haproxy[23423]: 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>Oct 30 15:33:23 node-2 haproxy[23423]: 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>Oct 30 15:33:23 node-2 haproxy[23423]: 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>Oct 30 15:33:23 node-2 haproxy[23423]: proxy mysqld has no server available!
<129>Oct 30 15:33:23 node-2 haproxy[23423]: 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>Oct 30 15:33:23 node-2 haproxy[23423]: 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>Oct 30 15:33:23 node-2 haproxy[23423]: 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>Oct 30 15:33:23 node-2 haproxy[23423]: proxy object-storage has no server available!
<27>Oct 30 15:33:24 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:24 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:24 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:24 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:24 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:26 node-2 haproxy[24614]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: proxy keystone-1 has no server available!
<129>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: proxy keystone-2 has no server available!
<129>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: proxy neutron has no server available!
<129>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:27 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: proxy mysqld has no server available!
<129>Oct 30 15:33:28 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: proxy object-storage has no server available!
<129>Oct 30 15:33:28 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: 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>Oct 30 15:33:28 node-2 haproxy[24621]: proxy aodh has no server available!
<27>Oct 30 15:33:30 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:30 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:30 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:30 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:30 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:30 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:32 node-2 haproxy[25866]: proxy keystone-1 has no server available!
<129>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:32 node-2 haproxy[25866]: proxy keystone-2 has no server available!
<129>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:32 node-2 haproxy[25866]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: proxy neutron has no server available!
<129>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: proxy mysqld has no server available!
<129>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: proxy object-storage has no server available!
<129>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: proxy aodh has no server available!
<129>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:33 node-2 haproxy[25872]: 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>Oct 30 15:33:34 node-2 haproxy[25872]: 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>Oct 30 15:33:34 node-2 haproxy[25872]: proxy ceilometer has no server available!
<27>Oct 30 15:33:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:35 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:37 node-2 haproxy[27076]: 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>Oct 30 15:33:37 node-2 haproxy[27076]: 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>Oct 30 15:33:37 node-2 haproxy[27076]: 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>Oct 30 15:33:37 node-2 haproxy[27076]: proxy keystone-1 has no server available!
<129>Oct 30 15:33:37 node-2 haproxy[27076]: 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>Oct 30 15:33:37 node-2 haproxy[27076]: 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>Oct 30 15:33:37 node-2 haproxy[27076]: 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>Oct 30 15:33:37 node-2 haproxy[27076]: proxy keystone-2 has no server available!
<129>Oct 30 15:33:37 node-2 haproxy[27076]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: proxy neutron has no server available!
<129>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: proxy mysqld has no server available!
<129>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: proxy object-storage has no server available!
<129>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:38 node-2 haproxy[27080]: proxy aodh has no server available!
<129>Oct 30 15:33:38 node-2 haproxy[27080]: 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>Oct 30 15:33:39 node-2 haproxy[27080]: 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>Oct 30 15:33:39 node-2 haproxy[27080]: 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>Oct 30 15:33:39 node-2 haproxy[27080]: proxy ceilometer has no server available!
<27>Oct 30 15:33:40 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:40 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:40 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:40 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:40 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:42 node-2 haproxy[28308]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: proxy keystone-1 has no server available!
<129>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: proxy keystone-2 has no server available!
<129>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: proxy neutron has no server available!
<129>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:43 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: proxy mysqld has no server available!
<129>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: proxy object-storage has no server available!
<129>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: proxy aodh has no server available!
<129>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: 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>Oct 30 15:33:44 node-2 haproxy[28312]: proxy ceilometer has no server available!
<27>Oct 30 15:33:45 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:45 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:46 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:48 node-2 haproxy[29597]: 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>Oct 30 15:33:48 node-2 haproxy[29597]: 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>Oct 30 15:33:48 node-2 haproxy[29597]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: proxy keystone-1 has no server available!
<129>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: proxy keystone-2 has no server available!
<129>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: proxy glance-api has no server available!
<129>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: proxy glance-glare has no server available!
<129>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: proxy neutron has no server available!
<129>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: proxy glance-registry has no server available!
<129>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:49 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: proxy mysqld has no server available!
<129>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: proxy object-storage has no server available!
<129>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: proxy aodh has no server available!
<129>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: 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>Oct 30 15:33:50 node-2 haproxy[29601]: proxy ceilometer has no server available!
<27>Oct 30 15:33:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:51 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: proxy keystone-1 has no server available!
<129>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: proxy keystone-2 has no server available!
<129>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: 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>Oct 30 15:33:54 node-2 haproxy[30897]: proxy nova-api has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: proxy nova-metadata-api has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: proxy glance-api has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: proxy glance-glare has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: proxy neutron has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: proxy glance-registry has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: proxy mysqld has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:55 node-2 haproxy[30904]: proxy object-storage has no server available!
<129>Oct 30 15:33:55 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: proxy aodh has no server available!
<129>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: proxy ceilometer has no server available!
<129>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: 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>Oct 30 15:33:56 node-2 haproxy[30904]: proxy nova-novncproxy has no server available!
<27>Oct 30 15:33:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:57 node-2 multipathd: uevent trigger error
<27>Oct 30 15:33:57 node-2 multipathd: uevent trigger error
<129>Oct 30 15:33:59 node-2 haproxy[32142]: 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>Oct 30 15:33:59 node-2 haproxy[32142]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy keystone-1 has no server available!
<129>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy keystone-2 has no server available!
<129>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy nova-api has no server available!
<129>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy nova-metadata-api has no server available!
<129>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy cinder-api has no server available!
<129>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy glance-api has no server available!
<129>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy glance-glare has no server available!
<129>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: 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>Oct 30 15:34:00 node-2 haproxy[32152]: proxy neutron has no server available!
<129>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: proxy glance-registry has no server available!
<129>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: proxy mysqld has no server available!
<129>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: proxy object-storage has no server available!
<129>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: proxy aodh has no server available!
<129>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: proxy ceilometer has no server available!
<129>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: 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>Oct 30 15:34:01 node-2 haproxy[32152]: proxy nova-novncproxy has no server available!
<27>Oct 30 15:34:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:02 node-2 multipathd: uevent trigger error
<129>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: proxy keystone-1 has no server available!
<129>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: proxy keystone-2 has no server available!
<129>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: proxy nova-api has no server available!
<129>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:05 node-2 haproxy[1025]: proxy nova-metadata-api has no server available!
<129>Oct 30 15:34:05 node-2 haproxy[1025]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy cinder-api has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy glance-api has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy glance-glare has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy neutron has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy glance-registry has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy mysqld has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy object-storage has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy aodh has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: proxy ceilometer has no server available!
<129>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:06 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: proxy heat-api has no server available!
<129>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: proxy heat-api-cfn has no server available!
<129>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: proxy heat-api-cloudwatch has no server available!
<129>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: 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>Oct 30 15:34:07 node-2 haproxy[1029]: proxy nova-novncproxy has no server available!
<27>Oct 30 15:34:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:11 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:11 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:11 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:11 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:11 node-2 multipathd: uevent trigger error
<27>Oct 30 15:34:19 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 30 15:34:43 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>Oct 30 15:34:45 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 30 15:35:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 15:35:21 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 15:35:41 node-2 multipathd: uevent trigger error
<27>Oct 30 15:35:41 node-2 multipathd: uevent trigger error
<27>Oct 30 15:35:41 node-2 multipathd: uevent trigger error
<27>Oct 30 15:35:41 node-2 multipathd: uevent trigger error
<27>Oct 30 15:35:41 node-2 multipathd: uevent trigger error
<27>Oct 30 15:37:59 node-2 multipathd: uevent trigger error
<27>Oct 30 15:37:59 node-2 multipathd: uevent trigger error
<27>Oct 30 15:37:59 node-2 multipathd: uevent trigger error
<27>Oct 30 15:37:59 node-2 multipathd: uevent trigger error
<27>Oct 30 15:37:59 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:14 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 30 15:38:22 node-2 apache2_error [Sun Oct 30 15:38:20.943555 2016] [mpm_event:notice] [pid 11421:tid 140293074347904] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 30 15:38:22 node-2 apache2_error [Sun Oct 30 15:38:20.943695 2016] [core:notice] [pid 11421:tid 140293074347904] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 15:38:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:38:31 node-2 multipathd: uevent trigger error
<43>Oct 30 15:38:33 node-2 apache2_error [Sun Oct 30 15:38:23.778458 2016] [mpm_event:notice] [pid 11421:tid 140293074347904] AH00491: caught SIGTERM, shutting down
<43>Oct 30 15:38:33 node-2 apache2_error [Sun Oct 30 15:38:24.847101 2016] [mpm_worker:notice] [pid 11813:tid 140237970974592] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 30 15:38:33 node-2 apache2_error [Sun Oct 30 15:38:24.847116 2016] [core:notice] [pid 11813:tid 140237970974592] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 30 15:39:33 node-2 apache2_error [Sun Oct 30 15:39:32.839438 2016] [mpm_worker:notice] [pid 11813:tid 140237970974592] AH00295: caught SIGTERM, shutting down
<43>Oct 30 15:39:43 node-2 apache2_error [Sun Oct 30 15:39:33.582654 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 15:39:43 node-2 apache2_error [Sun Oct 30 15:39:33.582679 2016] [core:notice] [pid 23385:tid 140481232717696] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 30 15:40:23 node-2 apache2_error [Sun Oct 30 15:40:17.332371 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 15:40:23 node-2 apache2_error [Sun Oct 30 15:40:17.524680 2016] [mpm_worker:warn] [pid 23385:tid 140481232717696] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 15:40:23 node-2 apache2_error [Sun Oct 30 15:40:17.528344 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 15:40:23 node-2 apache2_error [Sun Oct 30 15:40:17.528371 2016] [core:notice] [pid 23385:tid 140481232717696] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 15:41:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 15:41:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:21 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:39 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:39 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:39 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:39 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:39 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:39 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:43 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:43 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:43 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:43 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:43 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:58 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:58 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:58 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:58 node-2 multipathd: uevent trigger error
<27>Oct 30 15:41:58 node-2 multipathd: uevent trigger error
<27>Oct 30 15:42:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:42:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:42:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:42:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:42:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:43:52 node-2 multipathd: uevent trigger error
<27>Oct 30 15:43:52 node-2 multipathd: uevent trigger error
<27>Oct 30 15:43:52 node-2 multipathd: uevent trigger error
<27>Oct 30 15:43:52 node-2 multipathd: uevent trigger error
<27>Oct 30 15:43:52 node-2 multipathd: uevent trigger error
<27>Oct 30 15:44:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 15:44:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:44:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:44:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:44:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:44:46 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:08 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:45:14 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 15:47:34 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:34 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:34 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:34 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:34 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:34 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:49 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:49 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:49 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:49 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:49 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:50 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:47:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:48:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:07 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:07 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:07 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:07 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:07 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:49:51 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 15:50:23 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:23 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:23 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:23 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:23 node-2 multipathd: uevent trigger error
<27>Oct 30 15:50:23 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:42 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:54 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:52:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:13 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:13 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:13 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:13 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:13 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:15 node-2 multipathd: uevent trigger error
<27>Oct 30 15:53:16 node-2 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct 30 15:53:22 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 15:54:30 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:31 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:54:35 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:02 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:06 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:10 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:22 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:22 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:22 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:22 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:22 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:55:55 node-2 multipathd: uevent trigger error
<27>Oct 30 15:56:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 15:57:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:16 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:16 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:16 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:16 node-2 multipathd: uevent trigger error
<27>Oct 30 15:57:16 node-2 multipathd: uevent trigger error
<11>Oct 30 15:57:28 node-2 liberasurecode[92907]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:28 node-2 liberasurecode[92907]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:28 node-2 liberasurecode[92907]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:28 node-2 liberasurecode[92907]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:28 node-2 liberasurecode[92934]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:28 node-2 liberasurecode[92934]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:28 node-2 liberasurecode[92934]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:28 node-2 liberasurecode[92934]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:30 node-2 liberasurecode[93359]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:30 node-2 liberasurecode[93359]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:30 node-2 liberasurecode[93359]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:30 node-2 liberasurecode[93359]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93926]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93926]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93967]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:34 node-2 liberasurecode[93967]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94010]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94010]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94010]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94010]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94073]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94073]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94073]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94073]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94087]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94087]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94087]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94087]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94099]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94099]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94099]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94099]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94112]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94112]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94112]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:35 node-2 liberasurecode[94112]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:52 node-2 liberasurecode[96524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:52 node-2 liberasurecode[96524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:52 node-2 liberasurecode[96524]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 15:57:52 node-2 liberasurecode[96524]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 30 15:58:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:58:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:58:00 node-2 multipathd: uevent trigger error
<27>Oct 30 15:58:00 node-2 multipathd: uevent trigger error
<43>Oct 30 15:58:54 node-2 apache2_error [Sun Oct 30 15:58:45.252568 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 15:58:54 node-2 apache2_error [Sun Oct 30 15:58:45.637218 2016] [mpm_worker:warn] [pid 23385:tid 140481232717696] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 15:58:54 node-2 apache2_error [Sun Oct 30 15:58:45.642385 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 15:58:54 node-2 apache2_error [Sun Oct 30 15:58:45.642402 2016] [core:notice] [pid 23385:tid 140481232717696] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 15:59:24 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 30 15:59:24 node-2 apache2_error [Sun Oct 30 15:59:22.176588 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 15:59:24 node-2 apache2_error [Sun Oct 30 15:59:22.560345 2016] [mpm_worker:warn] [pid 23385:tid 140481232717696] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 15:59:24 node-2 apache2_error [Sun Oct 30 15:59:22.566914 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 15:59:24 node-2 apache2_error [Sun Oct 30 15:59:22.566933 2016] [core:notice] [pid 23385:tid 140481232717696] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 15:59:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:25 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:33 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:33 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:33 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:33 node-2 multipathd: uevent trigger error
<27>Oct 30 15:59:33 node-2 multipathd: uevent trigger error
<11>Oct 30 16:00:01 node-2 liberasurecode[115409]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 16:00:01 node-2 liberasurecode[115409]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 16:00:01 node-2 liberasurecode[115409]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 16:00:01 node-2 liberasurecode[115409]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 30 16:00:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:11 node-2 multipathd: uevent trigger error
<43>Oct 30 16:00:14 node-2 apache2_error [Sun Oct 30 16:00:07.787087 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 16:00:14 node-2 apache2_error [Sun Oct 30 16:00:07.982518 2016] [mpm_worker:warn] [pid 23385:tid 140481232717696] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 16:00:14 node-2 apache2_error [Sun Oct 30 16:00:07.988312 2016] [mpm_worker:notice] [pid 23385:tid 140481232717696] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 16:00:14 node-2 apache2_error [Sun Oct 30 16:00:07.988327 2016] [core:notice] [pid 23385:tid 140481232717696] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 16:00:17 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:17 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:17 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:17 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:17 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:21 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:21 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:21 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:21 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:21 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:27 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:27 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:27 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:27 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:27 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:43 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:43 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:43 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:43 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:43 node-2 multipathd: uevent trigger error
<27>Oct 30 16:00:43 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:04 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:11 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:17 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 30 16:01:26 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:26 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:26 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:26 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:26 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:39 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:39 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:39 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:39 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:39 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:58 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:58 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:58 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:58 node-2 multipathd: uevent trigger error
<27>Oct 30 16:01:58 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:25 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:25 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:25 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:25 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:25 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:25 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:25 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:29 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:29 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:29 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:29 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:29 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:42 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:42 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:42 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:42 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:42 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:42 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:47 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:47 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:47 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:47 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:47 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:59 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:59 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:59 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:59 node-2 multipathd: uevent trigger error
<27>Oct 30 16:02:59 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:14 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:14 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:14 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:14 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:14 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:18 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:18 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:18 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:18 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:18 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:23 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:23 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:23 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:23 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:23 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:30 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:30 node-2 multipathd: uevent trigger error
<129>Oct 30 16:03:31 node-2 haproxy[1029]: 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.
<27>Oct 30 16:03:35 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:35 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:35 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:35 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:35 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:40 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:40 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:40 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:40 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:40 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:44 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:49 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:49 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:49 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:49 node-2 multipathd: uevent trigger error
<27>Oct 30 16:03:49 node-2 multipathd: uevent trigger error
<11>Oct 30 16:05:01 node-2 liberasurecode[185439]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 16:05:01 node-2 liberasurecode[185439]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 16:05:01 node-2 liberasurecode[185439]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 16:05:01 node-2 liberasurecode[185439]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
