Nov  9 00:00:23 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8399" x-info="http://www.rsyslog.com"] start
Nov  9 00:00:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  9 00:00:23 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov  9 00:00:23 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov  9 00:00:23 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  9 00:00:23 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  9 00:00:23 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  9 00:00:23 node-1 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)
Nov  9 00:00:23 node-1 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=064ad23f-0acc-456f-b2bf-1143226f2a1f nomdmonddf nomdmonisw
Nov  9 00:00:23 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov  9 00:00:23 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov  9 00:00:23 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov  9 00:00:23 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov  9 00:00:23 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov  9 00:00:23 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  9 00:00:23 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  9 00:00:23 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Nov  9 00:00:23 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  9 00:00:23 node-1 kernel: [    0.000000] No AGP bridge found
Nov  9 00:00:23 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov  9 00:00:23 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov  9 00:00:23 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  9 00:00:23 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov  9 00:00:23 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  9 00:00:23 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov  9 00:00:23 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  9 00:00:23 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  9 00:00:23 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov  9 00:00:23 node-1 kernel: [    0.000000]   2 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000]   3 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000]   4 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000]   5 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000]   6 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000]   7 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000]   8 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000]   9 disabled
Nov  9 00:00:23 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  9 00:00:23 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov  9 00:00:23 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov  9 00:00:23 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  9 00:00:23 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov  9 00:00:23 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  9 00:00:23 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  9 00:00:23 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  9 00:00:23 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov  9 00:00:23 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov  9 00:00:23 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov  9 00:00:23 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  9 00:00:23 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov  9 00:00:23 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov  9 00:00:23 node-1 kernel: [    0.000000] Zone ranges:
Nov  9 00:00:23 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] Movable zone start for each node
Nov  9 00:00:23 node-1 kernel: [    0.000000] Early memory node ranges
Nov  9 00:00:23 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Nov  9 00:00:23 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  9 00:00:23 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  9 00:00:23 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov  9 00:00:23 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Nov  9 00:00:23 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Nov  9 00:00:23 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov  9 00:00:23 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov  9 00:00:23 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov  9 00:00:23 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov  9 00:00:23 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  9 00:00:23 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  9 00:00:23 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  9 00:00:23 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  9 00:00:23 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  9 00:00:23 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  9 00:00:23 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov  9 00:00:23 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov  9 00:00:23 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov  9 00:00:23 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  9 00:00:23 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov  9 00:00:23 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov  9 00:00:23 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov  9 00:00:23 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Nov  9 00:00:23 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Nov  9 00:00:23 node-1 kernel: [    0.000000] Policy zone: Normal
Nov  9 00:00:23 node-1 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=064ad23f-0acc-456f-b2bf-1143226f2a1f nomdmonddf nomdmonisw
Nov  9 00:00:23 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  9 00:00:23 node-1 kernel: [    0.000000] Checking aperture...
Nov  9 00:00:23 node-1 kernel: [    0.000000] No AGP bridge found
Nov  9 00:00:23 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  9 00:00:23 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  9 00:00:23 node-1 kernel: [    0.000000] Memory: 32653456K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627180K reserved)
Nov  9 00:00:23 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov  9 00:00:23 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  9 00:00:23 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  9 00:00:23 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov  9 00:00:23 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  9 00:00:23 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov  9 00:00:23 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov  9 00:00:23 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  9 00:00:23 node-1 kernel: [    0.000000] console [tty0] enabled
Nov  9 00:00:23 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov  9 00:00:23 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  9 00:00:23 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  9 00:00:23 node-1 kernel: [    0.000000] hpet clockevent registered
Nov  9 00:00:23 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  9 00:00:23 node-1 kernel: [    0.004000] tsc: Detected 3491.550 MHz processor
Nov  9 00:00:23 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.10 BogoMIPS (lpj=13966200)
Nov  9 00:00:23 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov  9 00:00:23 node-1 kernel: [    0.000042] Security Framework initialized
Nov  9 00:00:23 node-1 kernel: [    0.000068] AppArmor: AppArmor initialized
Nov  9 00:00:23 node-1 kernel: [    0.000070] Yama: becoming mindful.
Nov  9 00:00:23 node-1 kernel: [    0.001471] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.006353] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.008275] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.008303] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.008594] Initializing cgroup subsys memory
Nov  9 00:00:23 node-1 kernel: [    0.008603] Initializing cgroup subsys devices
Nov  9 00:00:23 node-1 kernel: [    0.008604] Initializing cgroup subsys freezer
Nov  9 00:00:23 node-1 kernel: [    0.008606] Initializing cgroup subsys blkio
Nov  9 00:00:23 node-1 kernel: [    0.008608] Initializing cgroup subsys perf_event
Nov  9 00:00:23 node-1 kernel: [    0.008610] Initializing cgroup subsys hugetlb
Nov  9 00:00:23 node-1 kernel: [    0.008629] CPU: Physical Processor ID: 0
Nov  9 00:00:23 node-1 kernel: [    0.008630] CPU: Processor Core ID: 0
Nov  9 00:00:23 node-1 kernel: [    0.008634] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov  9 00:00:23 node-1 kernel: [    0.008634] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov  9 00:00:23 node-1 kernel: [    0.009328] mce: CPU supports 22 MCE banks
Nov  9 00:00:23 node-1 kernel: [    0.009355] CPU0: Thermal monitoring enabled (TM1)
Nov  9 00:00:23 node-1 kernel: [    0.009376] process: using mwait in idle threads
Nov  9 00:00:23 node-1 kernel: [    0.009379] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  9 00:00:23 node-1 kernel: [    0.009379] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  9 00:00:23 node-1 kernel: [    0.009379] tlb_flushall_shift: 6
Nov  9 00:00:23 node-1 kernel: [    0.009467] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  9 00:00:23 node-1 kernel: [    0.010191] ACPI: Core revision 20131115
Nov  9 00:00:23 node-1 kernel: [    0.022985] ACPI: All ACPI Tables successfully acquired
Nov  9 00:00:23 node-1 kernel: [    0.023147] ftrace: allocating 28622 entries in 112 pages
Nov  9 00:00:23 node-1 kernel: [    0.031894] dmar: Host address width 46
Nov  9 00:00:23 node-1 kernel: [    0.031896] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  9 00:00:23 node-1 kernel: [    0.031902] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  9 00:00:23 node-1 kernel: [    0.031904] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  9 00:00:23 node-1 kernel: [    0.031908] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  9 00:00:23 node-1 kernel: [    0.031910] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov  9 00:00:23 node-1 kernel: [    0.031911] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov  9 00:00:23 node-1 kernel: [    0.031912] dmar: ATSR flags: 0x0
Nov  9 00:00:23 node-1 kernel: [    0.031913] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov  9 00:00:23 node-1 kernel: [    0.031914] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov  9 00:00:23 node-1 kernel: [    0.032030] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  9 00:00:23 node-1 kernel: [    0.032031] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  9 00:00:23 node-1 kernel: [    0.032032] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  9 00:00:23 node-1 kernel: [    0.032033] HPET id 0 under DRHD base 0xc7ffc000
Nov  9 00:00:23 node-1 kernel: [    0.032034] Your BIOS is broken and requested that x2apic be disabled.
Nov  9 00:00:23 node-1 kernel: [    0.032034] This will slightly decrease performance.
Nov  9 00:00:23 node-1 kernel: [    0.032034] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov  9 00:00:23 node-1 kernel: [    0.032467] Enabled IRQ remapping in xapic mode
Nov  9 00:00:23 node-1 kernel: [    0.032468] x2apic not enabled, IRQ remapping is in xapic mode
Nov  9 00:00:23 node-1 kernel: [    0.032472] Switched APIC routing to physical flat.
Nov  9 00:00:23 node-1 kernel: [    0.033047] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  9 00:00:23 node-1 kernel: [    0.072692] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  9 00:00:23 node-1 kernel: [    0.072697] TSC deadline timer enabled
Nov  9 00:00:23 node-1 kernel: [    0.072705] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov  9 00:00:23 node-1 kernel: [    0.072711] ... version:                3
Nov  9 00:00:23 node-1 kernel: [    0.072712] ... bit width:              48
Nov  9 00:00:23 node-1 kernel: [    0.072713] ... generic registers:      4
Nov  9 00:00:23 node-1 kernel: [    0.072714] ... value mask:             0000ffffffffffff
Nov  9 00:00:23 node-1 kernel: [    0.072715] ... max period:             0000ffffffffffff
Nov  9 00:00:23 node-1 kernel: [    0.072716] ... fixed-purpose events:   3
Nov  9 00:00:23 node-1 kernel: [    0.072717] ... event mask:             000000070000000f
Nov  9 00:00:23 node-1 kernel: [    0.074131] x86: Booting SMP configuration:
Nov  9 00:00:23 node-1 kernel: [    0.088256] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  9 00:00:23 node-1 kernel: [    0.074133] .... node  #0, CPUs:        #1  #2  #3
Nov  9 00:00:23 node-1 kernel: [    0.116168] .... node  #1, CPUs:    #4  #5  #6  #7
Nov  9 00:00:23 node-1 kernel: [    0.270000] .... node  #0, CPUs:    #8  #9 #10 #11
Nov  9 00:00:23 node-1 kernel: [    0.325607] .... node  #1, CPUs:   #12 #13 #14 #15
Nov  9 00:00:23 node-1 kernel: [    0.382450] x86: Booted up 2 nodes, 16 CPUs
Nov  9 00:00:23 node-1 kernel: [    0.382453] smpboot: Total of 16 processors activated (111742.04 BogoMIPS)
Nov  9 00:00:23 node-1 kernel: [    0.406766] devtmpfs: initialized
Nov  9 00:00:23 node-1 kernel: [    0.409099] EVM: security.selinux
Nov  9 00:00:23 node-1 kernel: [    0.409100] EVM: security.SMACK64
Nov  9 00:00:23 node-1 kernel: [    0.409101] EVM: security.ima
Nov  9 00:00:23 node-1 kernel: [    0.409102] EVM: security.capability
Nov  9 00:00:23 node-1 kernel: [    0.409153] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.409806] pinctrl core: initialized pinctrl subsystem
Nov  9 00:00:23 node-1 kernel: [    0.409866] regulator-dummy: no parameters
Nov  9 00:00:23 node-1 kernel: [    0.409897] RTC time: 23:59:46, date: 11/08/16
Nov  9 00:00:23 node-1 kernel: [    0.409931] NET: Registered protocol family 16
Nov  9 00:00:23 node-1 kernel: [    0.410016] cpuidle: using governor ladder
Nov  9 00:00:23 node-1 kernel: [    0.410017] cpuidle: using governor menu
Nov  9 00:00:23 node-1 kernel: [    0.410051] ACPI: bus type PCI registered
Nov  9 00:00:23 node-1 kernel: [    0.410053] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  9 00:00:23 node-1 kernel: [    0.410097] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  9 00:00:23 node-1 kernel: [    0.410099] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  9 00:00:23 node-1 kernel: [    0.423839] PCI: Using configuration type 1 for base access
Nov  9 00:00:23 node-1 kernel: [    0.424829] bio: create slab <bio-0> at 0
Nov  9 00:00:23 node-1 kernel: [    0.425093] ACPI: Added _OSI(Module Device)
Nov  9 00:00:23 node-1 kernel: [    0.425094] ACPI: Added _OSI(Processor Device)
Nov  9 00:00:23 node-1 kernel: [    0.425095] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  9 00:00:23 node-1 kernel: [    0.425097] ACPI: Added _OSI(Processor Aggregator Device)
Nov  9 00:00:23 node-1 kernel: [    0.437751] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov  9 00:00:23 node-1 kernel: [    0.448257] ACPI: Interpreter enabled
Nov  9 00:00:23 node-1 kernel: [    0.448263] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  9 00:00:23 node-1 kernel: [    0.448267] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  9 00:00:23 node-1 kernel: [    0.448270] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  9 00:00:23 node-1 kernel: [    0.448276] ACPI: (supports S0 S4 S5)
Nov  9 00:00:23 node-1 kernel: [    0.448278] ACPI: Using IOAPIC for interrupt routing
Nov  9 00:00:23 node-1 kernel: [    0.448319] HEST: Table parsing has been initialized.
Nov  9 00:00:23 node-1 kernel: [    0.448322] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  9 00:00:23 node-1 kernel: [    0.448894] ACPI: No dock devices found.
Nov  9 00:00:23 node-1 kernel: [    0.460859] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  9 00:00:23 node-1 kernel: [    0.460864] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 00:00:23 node-1 kernel: [    0.460868] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  9 00:00:23 node-1 kernel: [    0.460895] PCI host bridge to bus 0000:ff
Nov  9 00:00:23 node-1 kernel: [    0.460897] pci_bus 0000:ff: root bus resource [bus ff]
Nov  9 00:00:23 node-1 kernel: [    0.460905] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.460945] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.460975] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461010] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461039] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.461068] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.461098] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461127] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461157] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461185] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461211] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461237] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461265] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461291] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461318] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461344] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461373] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461400] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461426] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.461454] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461480] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.461505] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461531] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461561] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.461595] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461626] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461656] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461686] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461717] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461748] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461778] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461808] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461838] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461869] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461899] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461930] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461963] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.461992] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462020] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462053] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462085] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462121] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462155] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462188] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462217] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462247] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462277] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462306] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462336] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462365] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462395] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462424] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462453] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462479] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462508] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462543] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462575] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462632] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  9 00:00:23 node-1 kernel: [    0.462635] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 00:00:23 node-1 kernel: [    0.462638] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  9 00:00:23 node-1 kernel: [    0.462656] PCI host bridge to bus 0000:7f
Nov  9 00:00:23 node-1 kernel: [    0.462658] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  9 00:00:23 node-1 kernel: [    0.462663] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462690] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.462718] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462747] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462769] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.462794] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.462820] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462847] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462869] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462892] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462914] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462937] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462961] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.462983] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463006] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463032] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463054] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463077] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463100] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.463124] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463146] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.463168] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463191] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463217] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  9 00:00:23 node-1 kernel: [    0.463249] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463277] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463304] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463331] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463356] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463382] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463408] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463435] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463460] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463487] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463515] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463543] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463571] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463595] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463620] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463648] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463673] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463699] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463727] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463755] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463779] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463803] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463828] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463856] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463883] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463909] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463938] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463963] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.463985] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.464010] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.464034] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.464063] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.464089] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.465330] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  9 00:00:23 node-1 kernel: [    0.465333] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 00:00:23 node-1 kernel: [    0.466461] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  9 00:00:23 node-1 kernel: [    0.466972] PCI host bridge to bus 0000:00
Nov  9 00:00:23 node-1 kernel: [    0.466974] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  9 00:00:23 node-1 kernel: [    0.466976] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  9 00:00:23 node-1 kernel: [    0.466977] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  9 00:00:23 node-1 kernel: [    0.466978] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov  9 00:00:23 node-1 kernel: [    0.466980] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov  9 00:00:23 node-1 kernel: [    0.466981] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  9 00:00:23 node-1 kernel: [    0.466983] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  9 00:00:23 node-1 kernel: [    0.466988] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  9 00:00:23 node-1 kernel: [    0.467071] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.467101] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.467143] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  9 00:00:23 node-1 kernel: [    0.467162] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.467192] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.467232] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  9 00:00:23 node-1 kernel: [    0.467251] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.467280] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.467323] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  9 00:00:23 node-1 kernel: [    0.467339] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.467409] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.467487] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.467564] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  9 00:00:23 node-1 kernel: [    0.467569] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov  9 00:00:23 node-1 kernel: [    0.467655] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  9 00:00:23 node-1 kernel: [    0.467798] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  9 00:00:23 node-1 kernel: [    0.467815] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov  9 00:00:23 node-1 kernel: [    0.467893] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.467946] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov  9 00:00:23 node-1 kernel: [    0.467969] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.468024] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.468067] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov  9 00:00:23 node-1 kernel: [    0.468096] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.468152] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.468195] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov  9 00:00:23 node-1 kernel: [    0.468220] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  9 00:00:23 node-1 kernel: [    0.468238] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov  9 00:00:23 node-1 kernel: [    0.468315] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.468365] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov  9 00:00:23 node-1 kernel: [    0.468393] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  9 00:00:23 node-1 kernel: [    0.468641] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov  9 00:00:23 node-1 kernel: [    0.468647] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov  9 00:00:23 node-1 kernel: [    0.468653] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.468659] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.468666] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov  9 00:00:23 node-1 kernel: [    0.468696] pci 0000:01:00.0: supports D1 D2
Nov  9 00:00:23 node-1 kernel: [    0.478539] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  9 00:00:23 node-1 kernel: [    0.478546] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  9 00:00:23 node-1 kernel: [    0.478550] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  9 00:00:23 node-1 kernel: [    0.478827] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.478861] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov  9 00:00:23 node-1 kernel: [    0.486535] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  9 00:00:23 node-1 kernel: [    0.486542] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.486546] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 00:00:23 node-1 kernel: [    0.486630] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.486703] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.486797] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.486880] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  9 00:00:23 node-1 kernel: [    0.486887] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.486892] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 00:00:23 node-1 kernel: [    0.486978] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.487101] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.487155] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  9 00:00:23 node-1 kernel: [    0.487157] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.487159] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.487208] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.487327] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.487369] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.487491] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.487529] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.487648] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.487684] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov  9 00:00:23 node-1 kernel: [    0.487803] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov  9 00:00:23 node-1 kernel: [    0.487844] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  9 00:00:23 node-1 kernel: [    0.487846] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.487848] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.487909] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov  9 00:00:23 node-1 kernel: [    0.487992] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.488043] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.488084] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov  9 00:00:23 node-1 kernel: [    0.488163] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov  9 00:00:23 node-1 kernel: [    0.488271] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  9 00:00:23 node-1 kernel: [    0.488273] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.488275] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.488331] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov  9 00:00:23 node-1 kernel: [    0.488385] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.488437] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.488650] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  9 00:00:23 node-1 kernel: [    0.488654] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  9 00:00:23 node-1 kernel: [    0.488719] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov  9 00:00:23 node-1 kernel: [    0.488772] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.488820] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.489054] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  9 00:00:23 node-1 kernel: [    0.489058] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  9 00:00:23 node-1 kernel: [    0.489117] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov  9 00:00:23 node-1 kernel: [    0.489180] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.489232] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov  9 00:00:23 node-1 kernel: [    0.489455] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  9 00:00:23 node-1 kernel: [    0.489458] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  9 00:00:23 node-1 kernel: [    0.489632] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  9 00:00:23 node-1 kernel: [    0.489671] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  9 00:00:23 node-1 kernel: [    0.489746] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov  9 00:00:23 node-1 kernel: [    0.489764] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov  9 00:00:23 node-1 kernel: [    0.489778] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov  9 00:00:23 node-1 kernel: [    0.489791] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov  9 00:00:23 node-1 kernel: [    0.489841] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov  9 00:00:23 node-1 kernel: [    0.494542] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  9 00:00:23 node-1 kernel: [    0.494550] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  9 00:00:23 node-1 kernel: [    0.494603] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  9 00:00:23 node-1 kernel: [    0.495337] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  9 00:00:23 node-1 kernel: [    0.495340] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 00:00:23 node-1 kernel: [    0.495465] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  9 00:00:23 node-1 kernel: [    0.495573] PCI host bridge to bus 0000:80
Nov  9 00:00:23 node-1 kernel: [    0.495575] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  9 00:00:23 node-1 kernel: [    0.495577] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov  9 00:00:23 node-1 kernel: [    0.495578] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  9 00:00:23 node-1 kernel: [    0.495586] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.495650] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.495718] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  9 00:00:23 node-1 kernel: [    0.495781] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  9 00:00:23 node-1 kernel: [    0.495786] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov  9 00:00:23 node-1 kernel: [    0.495858] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  9 00:00:23 node-1 kernel: [    0.496157] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov  9 00:00:23 node-1 kernel: [    0.496188] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov  9 00:00:23 node-1 kernel: [    0.496218] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov  9 00:00:23 node-1 kernel: [    0.496247] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov  9 00:00:23 node-1 kernel: [    0.496276] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 00:00:23 node-1 kernel: [    0.496306] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 00:00:23 node-1 kernel: [    0.496336] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 00:00:23 node-1 kernel: [    0.496365] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 00:00:23 node-1 kernel: [    0.496451] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov  9 00:00:23 node-1 kernel: [    0.496455] ACPI: \_SB_.UNC1: notify handler is installed
Nov  9 00:00:23 node-1 kernel: [    0.496457] ACPI: \_SB_.UNC0: notify handler is installed
Nov  9 00:00:23 node-1 kernel: [    0.496472] ACPI: \_SB_.PCI0: notify handler is installed
Nov  9 00:00:23 node-1 kernel: [    0.496524] ACPI: \_SB_.PCI1: notify handler is installed
Nov  9 00:00:23 node-1 kernel: [    0.496604] Found 4 acpi root devices
Nov  9 00:00:23 node-1 kernel: [    0.496715] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov  9 00:00:23 node-1 kernel: [    0.496717] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov  9 00:00:23 node-1 kernel: [    0.496719] vgaarb: loaded
Nov  9 00:00:23 node-1 kernel: [    0.496720] vgaarb: bridge control possible 0000:0c:00.0
Nov  9 00:00:23 node-1 kernel: [    0.496843] SCSI subsystem initialized
Nov  9 00:00:23 node-1 kernel: [    0.496907] libata version 3.00 loaded.
Nov  9 00:00:23 node-1 kernel: [    0.496923] ACPI: bus type USB registered
Nov  9 00:00:23 node-1 kernel: [    0.496933] usbcore: registered new interface driver usbfs
Nov  9 00:00:23 node-1 kernel: [    0.496938] usbcore: registered new interface driver hub
Nov  9 00:00:23 node-1 kernel: [    0.496962] usbcore: registered new device driver usb
Nov  9 00:00:23 node-1 kernel: [    0.497133] PCI: Using ACPI for IRQ routing
Nov  9 00:00:23 node-1 kernel: [    0.500746] PCI: pci_cache_line_size set to 64 bytes
Nov  9 00:00:23 node-1 kernel: [    0.500968] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov  9 00:00:23 node-1 kernel: [    0.500969] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Nov  9 00:00:23 node-1 kernel: [    0.500970] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov  9 00:00:23 node-1 kernel: [    0.501035] NetLabel: Initializing
Nov  9 00:00:23 node-1 kernel: [    0.501036] NetLabel:  domain hash size = 128
Nov  9 00:00:23 node-1 kernel: [    0.501037] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  9 00:00:23 node-1 kernel: [    0.501047] NetLabel:  unlabeled traffic allowed by default
Nov  9 00:00:23 node-1 kernel: [    0.501117] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  9 00:00:23 node-1 kernel: [    0.501121] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  9 00:00:23 node-1 kernel: [    0.503198] Switched to clocksource hpet
Nov  9 00:00:23 node-1 kernel: [    0.507591] AppArmor: AppArmor Filesystem Enabled
Nov  9 00:00:23 node-1 kernel: [    0.507630] pnp: PnP ACPI init
Nov  9 00:00:23 node-1 kernel: [    0.507642] ACPI: bus type PNP registered
Nov  9 00:00:23 node-1 kernel: [    0.507823] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  9 00:00:23 node-1 kernel: [    0.507835] pnp 00:01: [dma 4]
Nov  9 00:00:23 node-1 kernel: [    0.507853] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  9 00:00:23 node-1 kernel: [    0.507887] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  9 00:00:23 node-1 kernel: [    0.507912] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  9 00:00:23 node-1 kernel: [    0.507933] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  9 00:00:23 node-1 kernel: [    0.507981] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  9 00:00:23 node-1 kernel: [    0.508094] system 00:06: [io  0x0500-0x057f] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508097] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov  9 00:00:23 node-1 kernel: [    0.508098] system 00:06: [io  0x0580-0x059f] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508100] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508101] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508103] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508106] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov  9 00:00:23 node-1 kernel: [    0.508108] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508109] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508111] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508112] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508114] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508115] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  9 00:00:23 node-1 kernel: [    0.508118] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  9 00:00:23 node-1 kernel: [    0.508219] pnp 00:07: [dma 0 disabled]
Nov  9 00:00:23 node-1 kernel: [    0.508252] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  9 00:00:23 node-1 kernel: [    0.508333] pnp 00:08: [dma 0 disabled]
Nov  9 00:00:23 node-1 kernel: [    0.508372] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  9 00:00:23 node-1 kernel: [    0.508431] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  9 00:00:23 node-1 kernel: [    0.508869] pnp: PnP ACPI: found 10 devices
Nov  9 00:00:23 node-1 kernel: [    0.508871] ACPI: bus type PNP unregistered
Nov  9 00:00:23 node-1 kernel: [    0.514824] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  9 00:00:23 node-1 kernel: [    0.514828] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  9 00:00:23 node-1 kernel: [    0.514831] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  9 00:00:23 node-1 kernel: [    0.514836] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  9 00:00:23 node-1 kernel: [    0.514838] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.514853] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.514882] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  9 00:00:23 node-1 kernel: [    0.514897] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  9 00:00:23 node-1 kernel: [    0.514925] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  9 00:00:23 node-1 kernel: [    0.514954] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  9 00:00:23 node-1 kernel: [    0.514983] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  9 00:00:23 node-1 kernel: [    0.514997] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  9 00:00:23 node-1 kernel: [    0.515026] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  9 00:00:23 node-1 kernel: [    0.515028] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515043] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515072] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  9 00:00:23 node-1 kernel: [    0.515074] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515088] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515117] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  9 00:00:23 node-1 kernel: [    0.515119] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515122] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515127] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  9 00:00:23 node-1 kernel: [    0.515129] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515131] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515136] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  9 00:00:23 node-1 kernel: [    0.515142] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  9 00:00:23 node-1 kernel: [    0.515150] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  9 00:00:23 node-1 kernel: [    0.515154] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  9 00:00:23 node-1 kernel: [    0.515161] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  9 00:00:23 node-1 kernel: [    0.515167] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  9 00:00:23 node-1 kernel: [    0.515168] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov  9 00:00:23 node-1 kernel: [    0.515169] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov  9 00:00:23 node-1 kernel: [    0.515170] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  9 00:00:23 node-1 kernel: [    0.515170] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov  9 00:00:23 node-1 kernel: [    0.515172] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov  9 00:00:23 node-1 kernel: [    0.515172] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov  9 00:00:23 node-1 kernel: [    0.515174] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515174] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515176] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515177] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515178] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515179] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515180] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515181] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515182] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov  9 00:00:23 node-1 kernel: [    0.515183] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515184] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov  9 00:00:23 node-1 kernel: [    0.515186] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov  9 00:00:23 node-1 kernel: [    0.515187] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov  9 00:00:23 node-1 kernel: [    0.515188] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov  9 00:00:23 node-1 kernel: [    0.515191] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov  9 00:00:23 node-1 kernel: [    0.515192] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  9 00:00:23 node-1 kernel: [    0.515234] NET: Registered protocol family 2
Nov  9 00:00:23 node-1 kernel: [    0.515545] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.515916] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.516084] TCP: Hash tables configured (established 262144 bind 65536)
Nov  9 00:00:23 node-1 kernel: [    0.516126] TCP: reno registered
Nov  9 00:00:23 node-1 kernel: [    0.516159] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.516267] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.516436] NET: Registered protocol family 1
Nov  9 00:00:23 node-1 kernel: [    0.555277] pci 0000:0c:00.0: Video device with shadowed ROM
Nov  9 00:00:23 node-1 kernel: [    0.555291] PCI: CLS 64 bytes, default 64
Nov  9 00:00:23 node-1 kernel: [    0.555377] Trying to unpack rootfs image as initramfs...
Nov  9 00:00:23 node-1 kernel: [    0.777671] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Nov  9 00:00:23 node-1 kernel: [    0.777709] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  9 00:00:23 node-1 kernel: [    0.777712] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Nov  9 00:00:23 node-1 kernel: [    0.778152] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778166] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778180] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778193] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778206] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778214] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778221] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778225] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778233] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778245] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778261] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778274] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778284] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778291] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778296] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778302] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 00:00:23 node-1 kernel: [    0.778353] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  9 00:00:23 node-1 kernel: [    0.778355] Scanning for low memory corruption every 60 seconds
Nov  9 00:00:23 node-1 kernel: [    0.778667] Initialise system trusted keyring
Nov  9 00:00:23 node-1 kernel: [    0.778716] audit: initializing netlink socket (disabled)
Nov  9 00:00:23 node-1 kernel: [    0.778734] type=2000 audit(1478649585.720:1): initialized
Nov  9 00:00:23 node-1 kernel: [    0.796555] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  9 00:00:23 node-1 kernel: [    0.798251] zbud: loaded
Nov  9 00:00:23 node-1 kernel: [    0.798373] VFS: Disk quotas dquot_6.5.2
Nov  9 00:00:23 node-1 kernel: [    0.798411] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  9 00:00:23 node-1 kernel: [    0.798761] fuse init (API version 7.22)
Nov  9 00:00:23 node-1 kernel: [    0.798813] msgmni has been set to 32768
Nov  9 00:00:23 node-1 kernel: [    0.798863] Key type big_key registered
Nov  9 00:00:23 node-1 kernel: [    0.799361] Key type asymmetric registered
Nov  9 00:00:23 node-1 kernel: [    0.799363] Asymmetric key parser 'x509' registered
Nov  9 00:00:23 node-1 kernel: [    0.799387] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  9 00:00:23 node-1 kernel: [    0.799468] io scheduler noop registered
Nov  9 00:00:23 node-1 kernel: [    0.799470] io scheduler deadline registered (default)
Nov  9 00:00:23 node-1 kernel: [    0.799492] io scheduler cfq registered
Nov  9 00:00:23 node-1 kernel: [    0.799886] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    0.800049] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    0.800179] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    0.800291] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    0.800407] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    0.800499] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    0.800879] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov  9 00:00:23 node-1 kernel: [    0.800905] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov  9 00:00:23 node-1 kernel: [    0.800923] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov  9 00:00:23 node-1 kernel: [    0.800937] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800939] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800941] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  9 00:00:23 node-1 kernel: [    0.800947] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800949] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800950] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800952] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800954] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800955] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800957] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800959] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800960] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800961] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800963] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800964] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800967] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  9 00:00:23 node-1 kernel: [    0.800981] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800983] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  9 00:00:23 node-1 kernel: [    0.800995] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.800998] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  9 00:00:23 node-1 kernel: [    0.801011] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.801012] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov  9 00:00:23 node-1 kernel: [    0.801016] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  9 00:00:23 node-1 kernel: [    0.801044] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  9 00:00:23 node-1 kernel: [    0.801050] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  9 00:00:23 node-1 kernel: [    0.801053] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  9 00:00:23 node-1 kernel: [    0.801062] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  9 00:00:23 node-1 kernel: [    0.801100] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  9 00:00:23 node-1 kernel: [    0.801101] vesafb: scrolling: redraw
Nov  9 00:00:23 node-1 kernel: [    0.801103] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  9 00:00:23 node-1 kernel: [    0.821551] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov  9 00:00:23 node-1 kernel: [    0.830049] Console: switching to colour frame buffer device 80x30
Nov  9 00:00:23 node-1 kernel: [    0.838715] fb0: VESA VGA frame buffer device
Nov  9 00:00:23 node-1 kernel: [    0.838928] intel_idle: MWAIT substates: 0x2120
Nov  9 00:00:23 node-1 kernel: [    0.838929] intel_idle: v0.4 model 0x3F
Nov  9 00:00:23 node-1 kernel: [    0.838930] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  9 00:00:23 node-1 kernel: [    0.839170] ipmi message handler version 39.2
Nov  9 00:00:23 node-1 kernel: [    0.839450] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov  9 00:00:23 node-1 kernel: [    0.839883] ACPI: AC Adapter [P111] (on-line)
Nov  9 00:00:23 node-1 kernel: [    0.845149] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov  9 00:00:23 node-1 kernel: [    0.856238] ACPI: Power Button [PWRB]
Nov  9 00:00:23 node-1 kernel: [    0.862114] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov  9 00:00:23 node-1 kernel: [    0.873862] ACPI: Power Button [PWRF]
Nov  9 00:00:23 node-1 kernel: [    0.896761] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  9 00:00:23 node-1 kernel: [    0.908534] pstore: Registered erst as persistent store backend
Nov  9 00:00:23 node-1 kernel: [    0.914791] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov  9 00:00:23 node-1 kernel: [    0.926920] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  9 00:00:23 node-1 kernel: [    0.953765] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  9 00:00:23 node-1 kernel: [    0.987215] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  9 00:00:23 node-1 kernel: [    1.001276] Linux agpgart interface v0.103
Nov  9 00:00:23 node-1 kernel: [    1.008881] brd: module loaded
Nov  9 00:00:23 node-1 kernel: [    1.015871] loop: module loaded
Nov  9 00:00:23 node-1 kernel: [    1.022579] libphy: Fixed MDIO Bus: probed
Nov  9 00:00:23 node-1 kernel: [    1.029033] tun: Universal TUN/TAP device driver, 1.6
Nov  9 00:00:23 node-1 kernel: [    1.035482] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  9 00:00:23 node-1 kernel: [    1.041982] PPP generic driver version 2.4.2
Nov  9 00:00:23 node-1 kernel: [    1.048342] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  9 00:00:23 node-1 kernel: [    1.054750] ehci-pci: EHCI PCI platform driver
Nov  9 00:00:23 node-1 kernel: [    1.061250] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  9 00:00:23 node-1 kernel: [    1.067625] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  9 00:00:23 node-1 kernel: [    1.080113] ehci-pci 0000:00:1a.0: debug port 2
Nov  9 00:00:23 node-1 kernel: [    1.090279] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  9 00:00:23 node-1 kernel: [    1.090298] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov  9 00:00:23 node-1 kernel: [    1.106669] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  9 00:00:23 node-1 kernel: [    1.112720] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  9 00:00:23 node-1 kernel: [    1.118862] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 00:00:23 node-1 kernel: [    1.130701] usb usb1: Product: EHCI Host Controller
Nov  9 00:00:23 node-1 kernel: [    1.136691] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  9 00:00:23 node-1 kernel: [    1.142717] usb usb1: SerialNumber: 0000:00:1a.0
Nov  9 00:00:23 node-1 kernel: [    1.148652] hub 1-0:1.0: USB hub found
Nov  9 00:00:23 node-1 kernel: [    1.154389] hub 1-0:1.0: 2 ports detected
Nov  9 00:00:23 node-1 kernel: [    1.160167] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  9 00:00:23 node-1 kernel: [    1.165728] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  9 00:00:23 node-1 kernel: [    1.176586] ehci-pci 0000:00:1d.0: debug port 2
Nov  9 00:00:23 node-1 kernel: [    1.185869] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  9 00:00:23 node-1 kernel: [    1.185872] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov  9 00:00:23 node-1 kernel: [    1.202588] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  9 00:00:23 node-1 kernel: [    1.207774] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  9 00:00:23 node-1 kernel: [    1.213062] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 00:00:23 node-1 kernel: [    1.223635] usb usb2: Product: EHCI Host Controller
Nov  9 00:00:23 node-1 kernel: [    1.229100] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  9 00:00:23 node-1 kernel: [    1.234662] usb usb2: SerialNumber: 0000:00:1d.0
Nov  9 00:00:23 node-1 kernel: [    1.240258] hub 2-0:1.0: USB hub found
Nov  9 00:00:23 node-1 kernel: [    1.245713] hub 2-0:1.0: 2 ports detected
Nov  9 00:00:23 node-1 kernel: [    1.251050] ehci-platform: EHCI generic platform driver
Nov  9 00:00:23 node-1 kernel: [    1.256300] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  9 00:00:23 node-1 kernel: [    1.261630] ohci-pci: OHCI PCI platform driver
Nov  9 00:00:23 node-1 kernel: [    1.266943] ohci-platform: OHCI generic platform driver
Nov  9 00:00:23 node-1 kernel: [    1.272152] uhci_hcd: USB Universal Host Controller Interface driver
Nov  9 00:00:23 node-1 kernel: [    1.277498] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  9 00:00:23 node-1 kernel: [    1.470367] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  9 00:00:23 node-1 kernel: [    1.774114] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov  9 00:00:23 node-1 kernel: [    1.790415] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  9 00:00:23 node-1 kernel: [    1.796119] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  9 00:00:23 node-1 kernel: [    1.801934] hub 1-1:1.0: USB hub found
Nov  9 00:00:23 node-1 kernel: [    1.807526] hub 1-1:1.0: 6 ports detected
Nov  9 00:00:23 node-1 kernel: [    1.921997] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  9 00:00:23 node-1 kernel: [    2.316835] i8042: No controller found
Nov  9 00:00:23 node-1 kernel: [    2.322390] mousedev: PS/2 mouse device common for all mice
Nov  9 00:00:23 node-1 kernel: [    2.328148] rtc_cmos 00:02: RTC can wake from S4
Nov  9 00:00:23 node-1 kernel: [    2.330392] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  9 00:00:23 node-1 kernel: [    2.330393] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  9 00:00:23 node-1 kernel: [    2.330903] hub 2-1:1.0: USB hub found
Nov  9 00:00:23 node-1 kernel: [    2.331140] hub 2-1:1.0: 8 ports detected
Nov  9 00:00:23 node-1 kernel: [    2.356516] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  9 00:00:23 node-1 kernel: [    2.362324] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  9 00:00:23 node-1 kernel: [    2.373636] device-mapper: uevent: version 1.0.3
Nov  9 00:00:23 node-1 kernel: [    2.379346] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  9 00:00:23 node-1 kernel: [    2.390722] ledtrig-cpu: registered to indicate activity on CPUs
Nov  9 00:00:23 node-1 kernel: [    2.396685] TCP: cubic registered
Nov  9 00:00:23 node-1 kernel: [    2.402542] NET: Registered protocol family 10
Nov  9 00:00:23 node-1 kernel: [    2.408594] NET: Registered protocol family 17
Nov  9 00:00:23 node-1 kernel: [    2.414364] Key type dns_resolver registered
Nov  9 00:00:23 node-1 kernel: [    2.420437] Loading compiled-in X.509 certificates
Nov  9 00:00:23 node-1 kernel: [    2.426658] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  9 00:00:23 node-1 kernel: [    2.438275] registered taskstats version 1
Nov  9 00:00:23 node-1 kernel: [    2.446366] Key type trusted registered
Nov  9 00:00:23 node-1 kernel: [    2.454019] Key type encrypted registered
Nov  9 00:00:23 node-1 kernel: [    2.459534] AppArmor: AppArmor sha1 policy hashing enabled
Nov  9 00:00:23 node-1 kernel: [    2.465045] IMA: No TPM chip found, activating TPM-bypass!
Nov  9 00:00:23 node-1 kernel: [    2.471164] regulator-dummy: disabling
Nov  9 00:00:23 node-1 kernel: [    2.476672]   Magic number: 8:515:1009
Nov  9 00:00:23 node-1 kernel: [    2.482150]   hash matches /build/linux-EbDtle/linux-3.13.0/drivers/base/power/main.c:504
Nov  9 00:00:23 node-1 kernel: [    2.493538] rtc_cmos 00:02: setting system clock to 2016-11-08 23:59:48 UTC (1478649588)
Nov  9 00:00:23 node-1 kernel: [    2.506335] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  9 00:00:23 node-1 kernel: [    2.512143] EDD information not available.
Nov  9 00:00:23 node-1 kernel: [    2.517940] PM: Hibernation image not present or could not be loaded.
Nov  9 00:00:23 node-1 kernel: [    2.518808] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  9 00:00:23 node-1 kernel: [    2.530593] Write protecting the kernel read-only data: 12288k
Nov  9 00:00:23 node-1 kernel: [    2.537169] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  9 00:00:23 node-1 kernel: [    2.550372] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  9 00:00:23 node-1 kernel: [    2.582643] device-mapper: multipath: version 1.6.0 loaded
Nov  9 00:00:23 node-1 kernel: [    2.590625] systemd-udevd[216]: starting version 204
Nov  9 00:00:23 node-1 kernel: [    2.613402] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov  9 00:00:23 node-1 kernel: [    2.626090] md: linear personality registered for level -1
Nov  9 00:00:23 node-1 kernel: [    2.635484] md: multipath personality registered for level -4
Nov  9 00:00:23 node-1 kernel: [    2.643752] md: raid0 personality registered for level 0
Nov  9 00:00:23 node-1 kernel: [    2.652380] md: raid1 personality registered for level 1
Nov  9 00:00:23 node-1 kernel: [    2.662944] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov  9 00:00:23 node-1 kernel: [    2.669374] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov  9 00:00:23 node-1 kernel: [    2.675762] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov  9 00:00:23 node-1 kernel: [    2.678065] megasas: FW now in Ready state
Nov  9 00:00:23 node-1 kernel: [    2.678771] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.678858] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679006] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679152] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679322] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679440] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679549] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679691] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679835] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.679915] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.680064] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.680163] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.680358] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.680490] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.680626] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.680756] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.681953] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov  9 00:00:23 node-1 kernel: [    2.709663] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Nov  9 00:00:23 node-1 kernel: [    2.723115] 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
Nov  9 00:00:23 node-1 kernel: [    2.725369] raid6: sse2x1   11517 MB/s
Nov  9 00:00:23 node-1 kernel: [    2.743440] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  9 00:00:23 node-1 kernel: [    2.750308] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.750312] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.750316] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.750319] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.750356] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  9 00:00:23 node-1 kernel: [    2.761728] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov  9 00:00:23 node-1 kernel: [    2.761728] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  9 00:00:23 node-1 kernel: [    2.761730] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov  9 00:00:23 node-1 kernel: [    2.761730] usb 2-1.4: Manufacturer: Avocent
Nov  9 00:00:23 node-1 kernel: [    2.761731] usb 2-1.4: SerialNumber: 20111102-00000001
Nov  9 00:00:23 node-1 kernel: [    2.793523] raid6: sse2x2   12669 MB/s
Nov  9 00:00:23 node-1 kernel: [    2.861193] raid6: sse2x4   10032 MB/s
Nov  9 00:00:23 node-1 kernel: [    2.933125] raid6: avx2x1   14951 MB/s
Nov  9 00:00:23 node-1 kernel: [    3.005065] raid6: avx2x2   18861 MB/s
Nov  9 00:00:23 node-1 kernel: [    3.077010] raid6: avx2x4   21248 MB/s
Nov  9 00:00:23 node-1 kernel: [    3.082441] raid6: using algorithm avx2x4 (21248 MB/s)
Nov  9 00:00:23 node-1 kernel: [    3.087885] raid6: using avx2x2 recovery algorithm
Nov  9 00:00:23 node-1 kernel: [    3.093253] megasas:IOC Init cmd success
Nov  9 00:00:23 node-1 kernel: [    3.093257] Switched to clocksource tsc
Nov  9 00:00:23 node-1 kernel: [    3.104756] xor: automatically using best checksumming function:
Nov  9 00:00:23 node-1 kernel: [    3.107971] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Nov  9 00:00:23 node-1 kernel: [    3.107973] 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
Nov  9 00:00:23 node-1 kernel: [    3.107974] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov  9 00:00:23 node-1 kernel: [    3.108061] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.108101] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.108141] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.108180] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.108219] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.108231] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.108323] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.121054] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Nov  9 00:00:23 node-1 kernel: [    3.121055] 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
Nov  9 00:00:23 node-1 kernel: [    3.121056] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  9 00:00:23 node-1 kernel: [    3.121123] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.121158] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.121187] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.121225] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.121302] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.129009] megasas: INIT adapter done
Nov  9 00:00:23 node-1 kernel: [    3.130697] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Nov  9 00:00:23 node-1 kernel: [    3.130698] 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
Nov  9 00:00:23 node-1 kernel: [    3.130699] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  9 00:00:23 node-1 kernel: [    3.130765] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.130800] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.130838] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.130875] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.130957] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  9 00:00:23 node-1 kernel: [    3.200908] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov  9 00:00:23 node-1 kernel: [    3.201309] scsi0 : LSI SAS based MegaRAID driver
Nov  9 00:00:23 node-1 kernel: [    3.208209] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  9 00:00:23 node-1 kernel: [    3.219290] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  9 00:00:23 node-1 kernel: [    3.223467] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov  9 00:00:23 node-1 kernel: [    3.223603] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov  9 00:00:23 node-1 kernel: [    3.223782] sd 0:2:0:0: [sda] Write Protect is off
Nov  9 00:00:23 node-1 kernel: [    3.223783] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov  9 00:00:23 node-1 kernel: [    3.223856] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov  9 00:00:23 node-1 kernel: [    3.253360]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov  9 00:00:23 node-1 kernel: [    3.255191] sd 0:2:0:0: [sda] Attached SCSI disk
Nov  9 00:00:23 node-1 kernel: [    3.326160] hidraw: raw HID events driver (C) Jiri Kosina
Nov  9 00:00:23 node-1 kernel: [    3.335433] usbcore: registered new interface driver usbhid
Nov  9 00:00:23 node-1 kernel: [    3.341944] usbhid: USB HID core driver
Nov  9 00:00:23 node-1 kernel: [    3.349241] 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
Nov  9 00:00:23 node-1 kernel: [    3.362101] 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
Nov  9 00:00:23 node-1 kernel: [    3.364742]    avx       : 35726.000 MB/sec
Nov  9 00:00:23 node-1 kernel: [    3.382305] 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
Nov  9 00:00:23 node-1 kernel: [    3.395941] async_tx: api initialized (async)
Nov  9 00:00:23 node-1 kernel: [    3.396125] 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
Nov  9 00:00:23 node-1 kernel: [    3.396186] 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
Nov  9 00:00:23 node-1 kernel: [    3.396562] 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
Nov  9 00:00:23 node-1 kernel: [    3.448618] md: raid6 personality registered for level 6
Nov  9 00:00:23 node-1 kernel: [    3.455811] md: raid5 personality registered for level 5
Nov  9 00:00:23 node-1 kernel: [    3.462816] md: raid4 personality registered for level 4
Nov  9 00:00:23 node-1 kernel: [    3.472701] md: raid10 personality registered for level 10
Nov  9 00:00:23 node-1 kernel: [    3.487644] random: lvm urandom read with 33 bits of entropy available
Nov  9 00:00:23 node-1 kernel: [    3.540862] multipathd (368): /proc/368/oom_adj is deprecated, please use /proc/368/oom_score_adj instead.
Nov  9 00:00:23 node-1 kernel: [    3.712486] bio: create slab <bio-1> at 1
Nov  9 00:00:23 node-1 kernel: [    4.456746] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 00:00:23 node-1 kernel: [    5.144978] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov  9 00:00:23 node-1 kernel: [    5.179847] random: nonblocking pool is initialized
Nov  9 00:00:23 node-1 kernel: [    5.188516] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov  9 00:00:23 node-1 kernel: [    5.363740] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  9 00:00:23 node-1 kernel: [    5.399682] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  9 00:00:23 node-1 kernel: [    5.457133] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 00:00:23 node-1 kernel: [    5.617007] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  9 00:00:23 node-1 kernel: [    5.654689] XFS (dm-0): Mounting Filesystem
Nov  9 00:00:23 node-1 kernel: [    5.886622] XFS (dm-0): Ending clean mount
Nov  9 00:00:23 node-1 kernel: [    5.947965] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 00:00:23 node-1 kernel: [    5.977826] XFS (dm-1): Mounting Filesystem
Nov  9 00:00:23 node-1 kernel: [    6.079838] XFS (dm-1): Ending clean mount
Nov  9 00:00:23 node-1 kernel: [    8.252096] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  9 00:00:23 node-1 kernel: [    8.280516] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  9 00:00:23 node-1 kernel: [    8.484020] systemd-udevd[777]: starting version 204
Nov  9 00:00:23 node-1 kernel: [    8.696432] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov  9 00:00:23 node-1 kernel: [    8.696438] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  9 00:00:23 node-1 kernel: [    8.696440] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov  9 00:00:23 node-1 kernel: [    8.696442] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  9 00:00:23 node-1 kernel: [    8.696455] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov  9 00:00:23 node-1 kernel: [    8.713232] power_meter ACPI000D:00: Found ACPI power meter.
Nov  9 00:00:23 node-1 kernel: [    8.713244] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  9 00:00:23 node-1 kernel: [    8.719967] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  9 00:00:23 node-1 kernel: [    8.720048] wmi: Mapper loaded
Nov  9 00:00:23 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  9 00:00:23 node-1 kernel: [    8.722507] IPMI System Interface driver.
Nov  9 00:00:23 node-1 kernel: [    8.722561] ipmi_si: probing via ACPI
Nov  9 00:00:23 node-1 kernel: [    8.722579] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov  9 00:00:23 node-1 kernel: [    8.722580] ipmi_si: Adding ACPI-specified kcs state machine
Nov  9 00:00:23 node-1 kernel: [    8.722589] ipmi_si: probing via SMBIOS
Nov  9 00:00:23 node-1 kernel: [    8.722591] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  9 00:00:23 node-1 kernel: [    8.722591] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  9 00:00:23 node-1 kernel: [    8.722593] ipmi_si: probing via SPMI
Nov  9 00:00:23 node-1 kernel: [    8.722594] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov  9 00:00:23 node-1 kernel: [    8.722595] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov  9 00:00:23 node-1 kernel: [    8.722597] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  9 00:00:23 node-1 kernel: [    8.808637] systemd-udevd[816]: renamed network interface eth3 to enp9s0
Nov  9 00:00:23 node-1 kernel: [    8.836501] systemd-udevd[803]: renamed network interface eth1 to enp7s0
Nov  9 00:00:23 node-1 kernel: [    8.868496] systemd-udevd[795]: renamed network interface eth0 to enp6s0
Nov  9 00:00:23 node-1 kernel: [    8.870285] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov  9 00:00:23 node-1 kernel: [    8.870291] ipmi_si 00:09: IPMI kcs interface initialized
Nov  9 00:00:23 node-1 kernel: [    8.908627] systemd-udevd[805]: renamed network interface eth2 to enp8s0
Nov  9 00:00:23 node-1 kernel: [    9.160380] type=1400 audit(1478649595.169:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1042 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.160539] type=1400 audit(1478649595.169:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1042 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.160674] type=1400 audit(1478649595.169:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1042 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.168154] type=1400 audit(1478649595.177:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1041 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.168293] type=1400 audit(1478649595.177:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1041 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.168412] type=1400 audit(1478649595.177:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1041 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.170274] type=1400 audit(1478649595.177:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1039 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.170414] type=1400 audit(1478649595.177:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1039 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.170533] type=1400 audit(1478649595.177:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1039 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.175591] type=1400 audit(1478649595.181:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Nov  9 00:00:23 node-1 kernel: [    9.787086] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  9 00:00:23 node-1 kernel: [    9.787912] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  9 00:00:23 node-1 kernel: [    9.995057] enic 0000:06:00.0 enp6s0: Link UP
Nov  9 00:00:23 node-1 kernel: [    9.995942] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov  9 00:00:23 node-1 kernel: [    9.995947] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov  9 00:00:23 node-1 kernel: [   20.242313] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  9 00:00:24 node-1 failsafe: Failsafe of 120 seconds reached.
Nov  9 00:00:24 node-1 kernel: [   38.905957] init: failsafe main process (8426) killed by TERM signal
Nov  9 00:00:24 node-1 dbus[8458]: [system] AppArmor D-Bus mediation is enabled
Nov  9 00:00:25 node-1 kernel: [   39.184215] audit_printk_skb: 30 callbacks suppressed
Nov  9 00:00:25 node-1 kernel: [   39.184217] type=1400 audit(1478649625.116:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8552 comm="apparmor_parser"
Nov  9 00:00:25 node-1 kernel: [   39.184407] type=1400 audit(1478649625.116:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8551 comm="apparmor_parser"
Nov  9 00:00:25 node-1 kernel: [   39.184413] type=1400 audit(1478649625.116:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8551 comm="apparmor_parser"
Nov  9 00:00:25 node-1 kernel: [   39.184416] type=1400 audit(1478649625.116:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Nov  9 00:00:25 node-1 kernel: [   39.184636] type=1400 audit(1478649625.116:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8551 comm="apparmor_parser"
Nov  9 00:00:25 node-1 kernel: [   39.184639] type=1400 audit(1478649625.116:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Nov  9 00:00:25 node-1 kernel: [   39.184753] type=1400 audit(1478649625.116:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Nov  9 00:00:25 node-1 kernel: [   39.260042] type=1400 audit(1478649625.192:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8554 comm="apparmor_parser"
Nov  9 00:00:25 node-1 cron[8584]: (CRON) INFO (pidfile fd = 3)
Nov  9 00:00:25 node-1 anacron[8634]: Anacron 2.3 started on 2016-11-09
Nov  9 00:00:25 node-1 multipathd: path checkers start up
Nov  9 00:00:25 node-1 cron[8650]: (CRON) STARTUP (fork ok)
Nov  9 00:00:25 node-1 anacron[8634]: Will run job `cron.daily' in 5 min.
Nov  9 00:00:25 node-1 anacron[8634]: Will run job `cron.weekly' in 10 min.
Nov  9 00:00:25 node-1 anacron[8634]: Will run job `cron.monthly' in 15 min.
Nov  9 00:00:25 node-1 anacron[8634]: Jobs will be executed sequentially
Nov  9 00:00:25 node-1 cron[8650]: (CRON) INFO (Running @reboot jobs)
Nov  9 00:00:25 node-1 postfix/master[8763]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  9 00:00:29 node-1 puppet-agent[8947]: Reopening log files
Nov  9 00:00:31 node-1 puppet-agent[8947]: Could not request certificate: Connection refused - connect(2)
Nov  9 00:00:41 node-1 puppet-user[9026]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  9 00:00:41 node-1 puppet-user[9026]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  9 00:00:44 node-1 puppet-user[9026]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  9 00:00:44 node-1 puppet-user[9026]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  9 00:00:44 node-1 puppet-user[9026]: Finished catalog run in 2.05 seconds
Nov  9 00:00:45 node-1 multipathd: uevent trigger error
Nov  9 00:00:45 node-1 puppet-user[9501]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  9 00:00:45 node-1 puppet-user[9501]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Nov  9 00:00:45 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  9 00:00:45 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  9 00:00:45 node-1 puppet-user[9501]: (/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"]'
Nov  9 00:00:45 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  9 00:00:45 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  9 00:00:45 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  9 00:00:45 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  9 00:00:45 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  9 00:00:45 node-1 puppet-user[9501]: Finished catalog run in 0.08 seconds
Nov  9 00:00:47 node-1 puppet-user[9966]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  9 00:00:47 node-1 puppet-user[9966]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov  9 00:00:47 node-1 puppet-user[9966]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  9 00:00:47 node-1 puppet-user[9966]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  9 00:00:47 node-1 puppet-user[9966]: Finished catalog run in 0.04 seconds
Nov  9 00:00:49 node-1 puppet-user[10433]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  9 00:00:49 node-1 puppet-user[10433]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov  9 00:00:49 node-1 puppet-user[10433]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  9 00:00:49 node-1 puppet-user[10433]: Finished catalog run in 0.04 seconds
Nov  9 00:00:50 node-1 puppet-user[10889]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov  9 00:00:50 node-1 puppet-user[10889]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Nov  9 00:00:51 node-1 puppet-user[10889]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov  9 00:00:51 node-1 puppet-user[10889]: (/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
Nov  9 00:00:51 node-1 puppet-user[10889]: Finished catalog run in 0.47 seconds
Nov  9 00:00:52 node-1 puppet-user[11377]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov  9 00:00:53 node-1 puppet-user[11377]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Nov  9 00:00:53 node-1 puppet-user[11377]: (/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
Nov  9 00:00:53 node-1 puppet-user[11377]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  9 00:00:53 node-1 puppet-user[11377]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  9 00:00:53 node-1 puppet-user[11377]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov  9 00:00:53 node-1 puppet-user[11377]: Finished catalog run in 0.22 seconds
Nov  9 00:00:54 node-1 puppet-user[11983]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  9 00:00:54 node-1 puppet-user[11983]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Nov  9 00:00:54 node-1 puppet-user[11983]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  9 00:00:54 node-1 kernel: [   69.023345] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  9 00:00:54 node-1 kernel: [   69.023395] 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.
Nov  9 00:00:54 node-1 puppet-user[11983]: (/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'
Nov  9 00:00:55 node-1 puppet-user[11983]: Finished catalog run in 0.05 seconds
Nov  9 00:00:56 node-1 puppet-user[12444]: (Scope(Class[main])) MODULAR: sync_time
Nov  9 00:00:56 node-1 puppet-user[12444]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  9 00:00:56 node-1 ntpdate[12864]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  9 00:01:01 node-1 CRON[12966]: (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")
Nov  9 00:01:02 node-1 ntpdate[12864]: adjust time server 10.20.0.2 offset 0.046036 sec
Nov  9 00:01:02 node-1 puppet-user[12444]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  9 00:01:02 node-1 puppet-user[12444]: Finished catalog run in 6.18 seconds
Nov  9 00:01:08 node-1 puppet-user[13242]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  9 00:01:08 node-1 puppet-user[13242]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov  9 00:01:08 node-1 puppet-user[13242]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  9 00:01:08 node-1 puppet-user[13242]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs"]'
Nov  9 00:01:08 node-1 puppet-user[13242]: Finished catalog run in 0.07 seconds
Nov  9 00:01:09 node-1 puppet-user[13699]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  9 00:01:10 node-1 puppet-user[13699]: Compiled catalog for node-1.domain.tld in environment production in 0.41 seconds
Nov  9 00:01:10 node-1 puppet-user[13699]: (/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
Nov  9 00:01:10 node-1 puppet-user[13699]: (/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
Nov  9 00:01:10 node-1 puppet-user[13699]: (/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
Nov  9 00:01:10 node-1 puppet-user[13699]: (/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
Nov  9 00:01:10 node-1 puppet-user[13699]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  9 00:01:10 node-1 puppet-user[13699]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov  9 00:01:10 node-1 puppet-user[13699]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  9 00:01:10 node-1 puppet-user[13699]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov  9 00:01:10 node-1 puppet-user[13699]: (/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
Nov  9 00:01:10 node-1 puppet-user[13699]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov  9 00:01:11 node-1 puppet-user[13699]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  9 00:01:11 node-1 puppet-user[13699]: Finished catalog run in 0.83 seconds
Nov  9 00:01:12 node-1 puppet-user[14203]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  9 00:01:12 node-1 puppet-user[14203]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Nov  9 00:01:15 node-1 puppet-user[14203]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  9 00:01:17 node-1 kernel: [   91.412508] init: plymouth-upstart-bridge main process ended, respawning
Nov  9 00:01:17 node-1 puppet-agent[8947]: Could not run: SIGTERM
Nov  9 00:01:17 node-1 kernel: [   91.652496] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  9 00:01:17 node-1 ec2: 
Nov  9 00:01:17 node-1 ec2: #############################################################
Nov  9 00:01:17 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  9 00:01:17 node-1 ec2: 1024 2f:6a:3c:2c:03:86:4e:81:c2:e5:73:68:af:40:af:e7  root@node-1.domain.tld (DSA)
Nov  9 00:01:17 node-1 ec2: 256 66:d1:42:45:b7:8e:45:ec:6b:41:19:0a:0c:e5:8b:9f  root@node-1.domain.tld (ECDSA)
Nov  9 00:01:17 node-1 ec2: 256 68:48:78:89:a8:bc:06:ac:86:49:d0:ff:8c:d5:c7:17  root@node-1.domain.tld (ED25519)
Nov  9 00:01:17 node-1 ec2: 2048 2e:27:c5:7b:d4:a9:c0:2f:29:c6:ae:7b:77:b1:a4:d9  root@node-1.domain.tld (RSA)
Nov  9 00:01:17 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  9 00:01:17 node-1 ec2: #############################################################
Nov  9 00:01:24 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 00:01:24 node-1 nailgun-agent: D, [2016-11-09T00:01:01.556570 #12969] DEBUG -- : Sleep for 23 seconds before sending request
Nov  9 00:01:24 node-1 nailgun-agent: I, [2016-11-09T00:01:24.572431 #12969]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  9 00:01:25 node-1 nailgun-agent: D, [2016-11-09T00:01:25.084109 #12969] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.338606 #12969] DEBUG -- : Trying to find block devices
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.338807 #12969] DEBUG -- : Found block device: sda
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.338920 #12969] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.338992 #12969] DEBUG -- : Trying to get list of physical devices
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.339437 #12969] DEBUG -- : Getting udev properties for device: sda
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.343799 #12969] 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
Nov  9 00:01:37 node-1 nailgun-agent: 6005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1996", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.343837 #12969] DEBUG -- : Trying to find out if device sda is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.343901 #12969] DEBUG -- : Device sda removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.343925 #12969] DEBUG -- : Device sda seems to be appropriate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.344462 #12969] DEBUG -- : Getting udev properties for device: dm-0
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.347506 #12969] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-dn6cCvKEWC01mr0JpY7K89GHANf3o7fixbt2UJyfeU6y2cce1Ms0Q8ief3syuLQc /dev/disk/by-uuid/e3be09bb-abde-42c3-9355-dac46952e746 /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-dn6cCvKEWC01mr0JpY7K89GHANf3o7fixbt2UJyfeU6y2cce1Ms0Q8ief3syuLQc", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e3be09bb-abde-42c3-9355-dac46952e746", "ID_FS_UUID_ENC"=>"e3be09bb-abde-42c3-9355-dac46952e746", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59937", "nomdmonddf"=>"1", "nom
Nov  9 00:01:37 node-1 nailgun-agent: dmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.347610 #12969] DEBUG -- : Trying to find out if device dm-0 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.347738 #12969] DEBUG -- : Device dm-0 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.347781 #12969] DEBUG -- : Device dm-0 seems to be appropriate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.347828 #12969] DEBUG -- : Getting udev properties for device: dm-1
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.350644 #12969] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-wocdTvv6FZdOuGua6JPCbaYcyDpgEy9Dabca2IbfMsrqu8EFaSmOy4w7Sed2UDVt /dev/disk/by-uuid/6a3a3f24-142c-4f86-b8a6-4ba3bf78c337 /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-wocdTvv6FZdOuGua6JPCbaYcyDpgEy9Dabca2IbfMsrqu8EFaSmOy4w7Sed2UDVt", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6a3a3f24-142c-4f86-b8a6-4ba3bf78c337", "ID_FS_UUID_ENC"=>"6a3a3f24-142c-4f86-b8a6-4ba3bf78c337", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8
Nov  9 00:01:37 node-1 nailgun-agent: 7326", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.350724 #12969] DEBUG -- : Trying to find out if device dm-1 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.350813 #12969] DEBUG -- : Device dm-1 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.350854 #12969] DEBUG -- : Device dm-1 seems to be appropriate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.350969 #12969] DEBUG -- : Getting udev properties for device: dm-2
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.354989 #12969] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-RCV3suv6keQiqlmpSDbyVgaXdeivMINZ8d2KQFuqySZwGfCbvLexG9TKsRIzFR99 /dev/disk/by-uuid/8dbe7834-24be-4763-bcd4-4a2a4a3232d8 /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-RCV3suv6keQiqlmpSDbyVgaXdeivMINZ8d2KQFuqySZwGfCbvLexG9TKsRIzFR99", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8dbe7834-24be-4763-bcd4-4a2a4a3232d8", "ID_FS_UUID_ENC"=>"8dbe7834-24be-4763-bcd4-4a2a4a3232d8", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99979", "nomdmon
Nov  9 00:01:37 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.355072 #12969] DEBUG -- : Trying to find out if device dm-2 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.355164 #12969] DEBUG -- : Device dm-2 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.355205 #12969] DEBUG -- : Device dm-2 seems to be appropriate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.355250 #12969] DEBUG -- : Getting udev properties for device: dm-3
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.358452 #12969] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-CixV0L27qGXNnMmkCxTf8PtzPilXAK0aZYzJqJqW7jgdN7pyMnWIQ6DG9yQMl6NY /dev/disk/by-uuid/b7888e04-0b40-4b15-bef6-2ffd194510f9 /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-CixV0L27qGXNnMmkCxTf8PtzPilXAK0aZYzJqJqW7jgdN7pyMnWIQ6DG9yQMl6NY", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b7888e04-0b40-4b15-bef6-2ffd194510f9", "ID_FS_UUID_ENC"=>"b7888e04-0b40-4b15-bef6-2ffd194510f9", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10503", "nomdmonddf"=>"1",
Nov  9 00:01:37 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.358491 #12969] DEBUG -- : Trying to find out if device dm-3 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.358538 #12969] DEBUG -- : Device dm-3 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.358578 #12969] DEBUG -- : Device dm-3 seems to be appropriate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.358599 #12969] DEBUG -- : Getting udev properties for device: dm-4
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.361317 #12969] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-wJk7QGj2MI32LNO0G2ctFBpN3Ajjw5uouhnXtZVFEfv3ufdeluKoVPepVquwoYe7 /dev/disk/by-uuid/064ad23f-0acc-456f-b2bf-1143226f2a1f /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-wJk7QGj2MI32LNO0G2ctFBpN3Ajjw5uouhnXtZVFEfv3ufdeluKoVPepVquwoYe7", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"064ad23f-0acc-456f-b2bf-1143226f2a1f", "ID_FS_UUID_ENC"=>"064ad23f-0acc-456f-b2bf-1143226f2a1f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11298", "nomdmonddf"=>"1", "nom
Nov  9 00:01:37 node-1 nailgun-agent: dmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.361393 #12969] DEBUG -- : Trying to find out if device dm-4 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.361541 #12969] DEBUG -- : Device dm-4 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.361589 #12969] DEBUG -- : Device dm-4 seems to be appropriate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.361635 #12969] DEBUG -- : Getting udev properties for device: dm-5
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.365757 #12969] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-wJk7QGj2MI32LNO0G2ctFBpN3Ajjw5uoftd1dT3DAxM72vWeSoflImUf09lQjEFa /dev/disk/by-uuid/f0ce0119-3a3c-4723-b88b-99dd323ea355 /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-wJk7QGj2MI32LNO0G2ctFBpN3Ajjw5uoftd1dT3DAxM72vWeSoflImUf09lQjEFa", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"f0ce0119-3a3c-4723-b88b-99dd323ea355", "ID_FS_UUID_ENC"=>"f0ce0119-3a3c-4723-b88b-99dd323ea355", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11669", "nomdmonddf"=>"1", "nomdmonisw
Nov  9 00:01:37 node-1 nailgun-agent: "=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.365832 #12969] DEBUG -- : Trying to find out if device dm-5 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.365918 #12969] DEBUG -- : Device dm-5 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.365957 #12969] DEBUG -- : Device dm-5 seems to be appropriate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.365998 #12969] DEBUG -- : Getting udev properties for device: ram0
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.369848 #12969] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45596", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.369888 #12969] DEBUG -- : Trying to find out if device ram0 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.369938 #12969] DEBUG -- : Device ram0 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.369991 #12969] DEBUG -- : Getting udev properties for device: ram1
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.372130 #12969] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45745", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.372166 #12969] DEBUG -- : Trying to find out if device ram1 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.372212 #12969] DEBUG -- : Device ram1 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.372240 #12969] DEBUG -- : Getting udev properties for device: ram2
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.374710 #12969] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47594", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.374778 #12969] DEBUG -- : Trying to find out if device ram2 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.374927 #12969] DEBUG -- : Device ram2 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.374980 #12969] DEBUG -- : Getting udev properties for device: ram3
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.378619 #12969] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47825", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.378717 #12969] DEBUG -- : Trying to find out if device ram3 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.378810 #12969] DEBUG -- : Device ram3 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.378862 #12969] DEBUG -- : Getting udev properties for device: ram4
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.381810 #12969] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48257", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.381880 #12969] DEBUG -- : Trying to find out if device ram4 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.381943 #12969] DEBUG -- : Device ram4 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.381972 #12969] DEBUG -- : Getting udev properties for device: ram5
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.384633 #12969] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48393", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.384670 #12969] DEBUG -- : Trying to find out if device ram5 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.384733 #12969] DEBUG -- : Device ram5 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.384761 #12969] DEBUG -- : Getting udev properties for device: ram6
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.387452 #12969] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48583", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.387521 #12969] DEBUG -- : Trying to find out if device ram6 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.387625 #12969] DEBUG -- : Device ram6 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.387654 #12969] DEBUG -- : Getting udev properties for device: ram7
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.390310 #12969] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48725", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.390346 #12969] DEBUG -- : Trying to find out if device ram7 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.390398 #12969] DEBUG -- : Device ram7 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.390449 #12969] DEBUG -- : Getting udev properties for device: ram8
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.393292 #12969] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48907", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.393360 #12969] DEBUG -- : Trying to find out if device ram8 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.393436 #12969] DEBUG -- : Device ram8 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.393491 #12969] DEBUG -- : Getting udev properties for device: ram9
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.396235 #12969] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49143", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.396306 #12969] DEBUG -- : Trying to find out if device ram9 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.396455 #12969] DEBUG -- : Device ram9 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.396512 #12969] DEBUG -- : Getting udev properties for device: loop0
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.399446 #12969] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44569", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.399554 #12969] DEBUG -- : Trying to find out if device loop0 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.399649 #12969] DEBUG -- : Device loop0 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.399703 #12969] DEBUG -- : Getting udev properties for device: loop1
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.402435 #12969] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44665", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.402507 #12969] DEBUG -- : Trying to find out if device loop1 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.402623 #12969] DEBUG -- : Device loop1 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.402698 #12969] DEBUG -- : Getting udev properties for device: loop2
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.405133 #12969] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44756", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.405240 #12969] DEBUG -- : Trying to find out if device loop2 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.405435 #12969] DEBUG -- : Device loop2 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.405493 #12969] DEBUG -- : Getting udev properties for device: loop3
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.408055 #12969] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44813", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.408135 #12969] DEBUG -- : Trying to find out if device loop3 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.408211 #12969] DEBUG -- : Device loop3 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.408278 #12969] DEBUG -- : Getting udev properties for device: loop4
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.410591 #12969] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44857", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.410697 #12969] DEBUG -- : Trying to find out if device loop4 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.410789 #12969] DEBUG -- : Device loop4 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.410850 #12969] DEBUG -- : Getting udev properties for device: loop5
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.413797 #12969] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45108", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.413871 #12969] DEBUG -- : Trying to find out if device loop5 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.414029 #12969] DEBUG -- : Device loop5 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.414080 #12969] DEBUG -- : Getting udev properties for device: loop6
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.416887 #12969] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45316", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.416973 #12969] DEBUG -- : Trying to find out if device loop6 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.417066 #12969] DEBUG -- : Device loop6 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.417146 #12969] DEBUG -- : Getting udev properties for device: loop7
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.419774 #12969] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45585", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.419857 #12969] DEBUG -- : Trying to find out if device loop7 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.419939 #12969] DEBUG -- : Device loop7 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.420020 #12969] DEBUG -- : Getting udev properties for device: ram10
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.422581 #12969] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45939", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.422686 #12969] DEBUG -- : Trying to find out if device ram10 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.422771 #12969] DEBUG -- : Device ram10 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.422821 #12969] DEBUG -- : Getting udev properties for device: ram11
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.425644 #12969] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46246", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.425709 #12969] DEBUG -- : Trying to find out if device ram11 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.425840 #12969] DEBUG -- : Device ram11 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.425890 #12969] DEBUG -- : Getting udev properties for device: ram12
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.428728 #12969] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46467", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.428804 #12969] DEBUG -- : Trying to find out if device ram12 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.428936 #12969] DEBUG -- : Device ram12 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.428991 #12969] DEBUG -- : Getting udev properties for device: ram13
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.431924 #12969] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46906", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.432027 #12969] DEBUG -- : Trying to find out if device ram13 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.432118 #12969] DEBUG -- : Device ram13 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.432175 #12969] DEBUG -- : Getting udev properties for device: ram14
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.443145 #12969] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47001", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.443190 #12969] DEBUG -- : Trying to find out if device ram14 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.443249 #12969] DEBUG -- : Device ram14 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.443280 #12969] DEBUG -- : Getting udev properties for device: ram15
Nov  9 00:01:37 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.445842 #12969] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47356", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.445882 #12969] DEBUG -- : Trying to find out if device ram15 is removable or not
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.445960 #12969] DEBUG -- : Device ram15 removable parameter: "0"
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446015 #12969] 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"}]
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446036 #12969] DEBUG -- : Block device seems to be physical data storage: sda
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446088 #12969] DEBUG -- : Found block device: dm-0
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446110 #12969] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446129 #12969] DEBUG -- : Found block device: dm-1
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446145 #12969] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446224 #12969] DEBUG -- : Found block device: dm-2
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446240 #12969] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446253 #12969] DEBUG -- : Found block device: dm-3
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446267 #12969] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446280 #12969] DEBUG -- : Found block device: dm-4
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446294 #12969] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446306 #12969] DEBUG -- : Found block device: dm-5
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446320 #12969] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446332 #12969] DEBUG -- : Found block device: ram0
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446400 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446414 #12969] DEBUG -- : Found block device: ram1
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446429 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446442 #12969] DEBUG -- : Found block device: ram2
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446455 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446467 #12969] DEBUG -- : Found block device: ram3
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446482 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446494 #12969] DEBUG -- : Found block device: ram4
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446509 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446521 #12969] DEBUG -- : Found block device: ram5
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446593 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446608 #12969] DEBUG -- : Found block device: ram6
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446623 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446635 #12969] DEBUG -- : Found block device: ram7
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446649 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446662 #12969] DEBUG -- : Found block device: ram8
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446677 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446688 #12969] DEBUG -- : Found block device: ram9
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446702 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446772 #12969] DEBUG -- : Found block device: loop0
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446788 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446800 #12969] DEBUG -- : Found block device: loop1
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446814 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446826 #12969] DEBUG -- : Found block device: loop2
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446840 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446853 #12969] DEBUG -- : Found block device: loop3
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446868 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446880 #12969] DEBUG -- : Found block device: loop4
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446949 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446963 #12969] DEBUG -- : Found block device: loop5
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446977 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.446989 #12969] DEBUG -- : Found block device: loop6
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447002 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447014 #12969] DEBUG -- : Found block device: loop7
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447027 #12969] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447038 #12969] DEBUG -- : Found block device: ram10
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447053 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447066 #12969] DEBUG -- : Found block device: ram11
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447133 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447146 #12969] DEBUG -- : Found block device: ram12
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447159 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447171 #12969] DEBUG -- : Found block device: ram13
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447186 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447198 #12969] DEBUG -- : Found block device: ram14
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447211 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447223 #12969] DEBUG -- : Found block device: ram15
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447237 #12969] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.447338 #12969] 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}]
Nov  9 00:01:37 node-1 nailgun-agent: D, [2016-11-09T00:01:37.650459 #12969] DEBUG -- : Response: status: 200 body: {"id": 1}
Nov  9 00:01:37 node-1 nailgun-agent: I, [2016-11-09T00:01:37.655823 #12969]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Nov  9 00:01:42 node-1 puppet-user[14203]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  9 00:01:42 node-1 puppet-user[14203]: Finished catalog run in 29.75 seconds
Nov  9 00:01:44 node-1 puppet-user[17081]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  9 00:01:44 node-1 puppet-user[17081]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Nov  9 00:01:44 node-1 puppet-user[17081]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  9 00:01:44 node-1 puppet-user[17081]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  9 00:01:44 node-1 puppet-user[17081]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  9 00:01:44 node-1 puppet-user[17081]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  9 00:01:45 node-1 puppet-user[17081]: Finished catalog run in 0.08 seconds
Nov  9 00:01:46 node-1 puppet-user[17552]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  9 00:01:47 node-1 puppet-user[17552]: Compiled catalog for node-1.domain.tld in environment production in 0.88 seconds
Nov  9 00:01:48 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  9 00:01:48 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  9 00:01:48 node-1 crontab[17992]: (root) LIST (root)
Nov  9 00:01:48 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  9 00:01:48 node-1 crontab[17993]: (root) REPLACE (root)
Nov  9 00:01:49 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/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
Nov  9 00:01:50 node-1 puppet-user[17552]: (/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
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/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
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/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
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/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
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/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
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  9 00:01:50 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  9 00:01:51 node-1 puppet-user[17552]: (/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
Nov  9 00:01:51 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  9 00:01:51 node-1 puppet-user[17552]: (/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
Nov  9 00:01:51 node-1 puppet-user[17552]: (/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
Nov  9 00:01:51 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  9 00:01:51 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  9 00:01:51 node-1 puppet-user[17552]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov  9 00:01:51 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8399" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 00:01:51 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  9 00:01:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:01:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:01:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:01:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:01:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:01:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 00:02:56 node-1 ntpdate[28531]: no servers can be used, exiting
<27>Nov  9 00:03:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:03:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:04:53 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 00:04:53 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 00:04:59 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 00:04:59 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 00:05:05 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 00:05:10 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 00:05:10 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 00:05:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:27 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:27 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:27 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:27 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:27 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:45 node-1 multipathd: uevent trigger error
<129>Nov  9 00:05:48 node-1 haproxy[18826]: Server mysqld/node-1 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>Nov  9 00:05:48 node-1 haproxy[18826]: 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>Nov  9 00:05:49 node-1 haproxy[18830]: 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>Nov  9 00:05:49 node-1 haproxy[18830]: proxy mysqld has no server available!
<27>Nov  9 00:05:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:05:54 node-1 multipathd: uevent trigger error
<129>Nov  9 00:05:57 node-1 haproxy[21529]: Server mysqld/node-1 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>Nov  9 00:05:57 node-1 haproxy[21529]: 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>Nov  9 00:05:57 node-1 haproxy[21529]: 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>Nov  9 00:05:57 node-1 haproxy[21529]: proxy mysqld has no server available!
<129>Nov  9 00:05:58 node-1 haproxy[21533]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:05:58 node-1 haproxy[21533]: 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>Nov  9 00:05:58 node-1 haproxy[21533]: 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>Nov  9 00:05:58 node-1 haproxy[21533]: proxy object-storage has no server available!
<27>Nov  9 00:06:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:00 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:02 node-1 haproxy[22934]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:02 node-1 haproxy[22934]: 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>Nov  9 00:06:02 node-1 haproxy[22934]: 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>Nov  9 00:06:02 node-1 haproxy[22934]: proxy neutron has no server available!
<129>Nov  9 00:06:03 node-1 haproxy[22948]: Server mysqld/node-1 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>Nov  9 00:06:03 node-1 haproxy[22948]: 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>Nov  9 00:06:03 node-1 haproxy[22948]: 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>Nov  9 00:06:03 node-1 haproxy[22948]: proxy mysqld has no server available!
<129>Nov  9 00:06:03 node-1 haproxy[22948]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:03 node-1 haproxy[22948]: 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>Nov  9 00:06:04 node-1 haproxy[22948]: 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>Nov  9 00:06:04 node-1 haproxy[22948]: proxy object-storage has no server available!
<27>Nov  9 00:06:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:05 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:08 node-1 haproxy[24412]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:08 node-1 haproxy[24412]: 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>Nov  9 00:06:08 node-1 haproxy[24412]: 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>Nov  9 00:06:08 node-1 haproxy[24412]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:08 node-1 haproxy[24412]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:08 node-1 haproxy[24412]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:08 node-1 haproxy[24412]: 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>Nov  9 00:06:08 node-1 haproxy[24412]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:08 node-1 haproxy[24412]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:09 node-1 haproxy[24416]: 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>Nov  9 00:06:09 node-1 haproxy[24416]: 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>Nov  9 00:06:09 node-1 haproxy[24416]: proxy neutron has no server available!
<129>Nov  9 00:06:09 node-1 haproxy[24416]: Server mysqld/node-1 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>Nov  9 00:06:09 node-1 haproxy[24416]: 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>Nov  9 00:06:09 node-1 haproxy[24416]: 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>Nov  9 00:06:09 node-1 haproxy[24416]: proxy mysqld has no server available!
<129>Nov  9 00:06:09 node-1 haproxy[24416]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:09 node-1 haproxy[24416]: 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>Nov  9 00:06:10 node-1 haproxy[24416]: 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>Nov  9 00:06:10 node-1 haproxy[24416]: proxy object-storage has no server available!
<27>Nov  9 00:06:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:11 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:13 node-1 haproxy[25937]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:13 node-1 haproxy[25937]: 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>Nov  9 00:06:13 node-1 haproxy[25937]: 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>Nov  9 00:06:13 node-1 haproxy[25937]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:13 node-1 haproxy[25937]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:14 node-1 haproxy[25941]: 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>Nov  9 00:06:14 node-1 haproxy[25941]: 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>Nov  9 00:06:14 node-1 haproxy[25941]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:14 node-1 haproxy[25941]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:14 node-1 haproxy[25941]: 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>Nov  9 00:06:14 node-1 haproxy[25941]: 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>Nov  9 00:06:14 node-1 haproxy[25941]: proxy neutron has no server available!
<129>Nov  9 00:06:14 node-1 haproxy[25941]: Server mysqld/node-1 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>Nov  9 00:06:14 node-1 haproxy[25941]: 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>Nov  9 00:06:14 node-1 haproxy[25941]: 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>Nov  9 00:06:14 node-1 haproxy[25941]: proxy mysqld has no server available!
<129>Nov  9 00:06:14 node-1 haproxy[25941]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:15 node-1 haproxy[25941]: 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>Nov  9 00:06:15 node-1 haproxy[25941]: 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>Nov  9 00:06:15 node-1 haproxy[25941]: proxy object-storage has no server available!
<129>Nov  9 00:06:15 node-1 haproxy[25941]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:15 node-1 haproxy[25941]: 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>Nov  9 00:06:15 node-1 haproxy[25941]: 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>Nov  9 00:06:15 node-1 haproxy[25941]: proxy aodh has no server available!
<27>Nov  9 00:06:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:17 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:19 node-1 haproxy[27348]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:19 node-1 haproxy[27348]: 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>Nov  9 00:06:19 node-1 haproxy[27348]: 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>Nov  9 00:06:19 node-1 haproxy[27348]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:19 node-1 haproxy[27348]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:19 node-1 haproxy[27348]: 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>Nov  9 00:06:19 node-1 haproxy[27348]: 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>Nov  9 00:06:19 node-1 haproxy[27348]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:19 node-1 haproxy[27348]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:19 node-1 haproxy[27348]: 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>Nov  9 00:06:19 node-1 haproxy[27348]: 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>Nov  9 00:06:19 node-1 haproxy[27348]: proxy neutron has no server available!
<129>Nov  9 00:06:19 node-1 haproxy[27348]: Server mysqld/node-1 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>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: proxy mysqld has no server available!
<129>Nov  9 00:06:20 node-1 haproxy[27352]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: proxy object-storage has no server available!
<129>Nov  9 00:06:20 node-1 haproxy[27352]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: proxy aodh has no server available!
<129>Nov  9 00:06:20 node-1 haproxy[27352]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: 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>Nov  9 00:06:20 node-1 haproxy[27352]: proxy ceilometer has no server available!
<27>Nov  9 00:06:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:22 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:24 node-1 haproxy[28919]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:24 node-1 haproxy[28919]: 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>Nov  9 00:06:24 node-1 haproxy[28919]: 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>Nov  9 00:06:24 node-1 haproxy[28919]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:25 node-1 haproxy[28923]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:25 node-1 haproxy[28923]: 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>Nov  9 00:06:25 node-1 haproxy[28923]: 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>Nov  9 00:06:25 node-1 haproxy[28923]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:25 node-1 haproxy[28923]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:25 node-1 haproxy[28923]: 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>Nov  9 00:06:25 node-1 haproxy[28923]: 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>Nov  9 00:06:25 node-1 haproxy[28923]: proxy neutron has no server available!
<129>Nov  9 00:06:25 node-1 haproxy[28923]: Server mysqld/node-1 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>Nov  9 00:06:25 node-1 haproxy[28923]: 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>Nov  9 00:06:25 node-1 haproxy[28923]: 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>Nov  9 00:06:25 node-1 haproxy[28923]: proxy mysqld has no server available!
<129>Nov  9 00:06:25 node-1 haproxy[28923]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:26 node-1 haproxy[28923]: 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>Nov  9 00:06:26 node-1 haproxy[28923]: 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>Nov  9 00:06:26 node-1 haproxy[28923]: proxy object-storage has no server available!
<129>Nov  9 00:06:26 node-1 haproxy[28923]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:26 node-1 haproxy[28923]: 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>Nov  9 00:06:26 node-1 haproxy[28923]: 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>Nov  9 00:06:26 node-1 haproxy[28923]: proxy aodh has no server available!
<129>Nov  9 00:06:26 node-1 haproxy[28923]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:26 node-1 haproxy[28923]: 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>Nov  9 00:06:26 node-1 haproxy[28923]: 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>Nov  9 00:06:26 node-1 haproxy[28923]: proxy ceilometer has no server available!
<27>Nov  9 00:06:28 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:28 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:28 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:28 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:28 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:30 node-1 haproxy[30315]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:30 node-1 haproxy[30315]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:30 node-1 haproxy[30315]: 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>Nov  9 00:06:30 node-1 haproxy[30315]: 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>Nov  9 00:06:30 node-1 haproxy[30315]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:30 node-1 haproxy[30315]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:30 node-1 haproxy[30315]: 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>Nov  9 00:06:30 node-1 haproxy[30315]: 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>Nov  9 00:06:30 node-1 haproxy[30315]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:30 node-1 haproxy[30315]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: proxy neutron has no server available!
<129>Nov  9 00:06:31 node-1 haproxy[30319]: Server mysqld/node-1 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>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: proxy mysqld has no server available!
<129>Nov  9 00:06:31 node-1 haproxy[30319]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: proxy object-storage has no server available!
<129>Nov  9 00:06:31 node-1 haproxy[30319]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: 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>Nov  9 00:06:31 node-1 haproxy[30319]: proxy aodh has no server available!
<129>Nov  9 00:06:31 node-1 haproxy[30319]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:32 node-1 haproxy[30319]: 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>Nov  9 00:06:32 node-1 haproxy[30319]: 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>Nov  9 00:06:32 node-1 haproxy[30319]: proxy ceilometer has no server available!
<27>Nov  9 00:06:33 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:33 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:33 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:33 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:33 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:36 node-1 haproxy[31781]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:36 node-1 haproxy[31781]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:36 node-1 haproxy[31781]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:36 node-1 haproxy[31781]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: proxy glance-api has no server available!
<129>Nov  9 00:06:36 node-1 haproxy[31781]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: 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>Nov  9 00:06:36 node-1 haproxy[31781]: proxy glance-glare has no server available!
<129>Nov  9 00:06:37 node-1 haproxy[31785]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: proxy neutron has no server available!
<129>Nov  9 00:06:37 node-1 haproxy[31785]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: proxy glance-registry has no server available!
<129>Nov  9 00:06:37 node-1 haproxy[31785]: Server mysqld/node-1 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>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: proxy mysqld has no server available!
<129>Nov  9 00:06:37 node-1 haproxy[31785]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: proxy object-storage has no server available!
<129>Nov  9 00:06:37 node-1 haproxy[31785]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: 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>Nov  9 00:06:37 node-1 haproxy[31785]: proxy aodh has no server available!
<129>Nov  9 00:06:37 node-1 haproxy[31785]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:38 node-1 haproxy[31785]: 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>Nov  9 00:06:38 node-1 haproxy[31785]: 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>Nov  9 00:06:38 node-1 haproxy[31785]: proxy ceilometer has no server available!
<27>Nov  9 00:06:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:39 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:42 node-1 haproxy[830]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:42 node-1 haproxy[830]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:42 node-1 haproxy[830]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:42 node-1 haproxy[830]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: proxy nova-api has no server available!
<129>Nov  9 00:06:42 node-1 haproxy[830]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: proxy nova-metadata-api has no server available!
<129>Nov  9 00:06:42 node-1 haproxy[830]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: 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>Nov  9 00:06:42 node-1 haproxy[830]: proxy glance-api has no server available!
<129>Nov  9 00:06:43 node-1 haproxy[834]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: proxy glance-glare has no server available!
<129>Nov  9 00:06:43 node-1 haproxy[834]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: proxy neutron has no server available!
<129>Nov  9 00:06:43 node-1 haproxy[834]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: proxy glance-registry has no server available!
<129>Nov  9 00:06:43 node-1 haproxy[834]: Server mysqld/node-1 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: proxy mysqld has no server available!
<129>Nov  9 00:06:43 node-1 haproxy[834]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: proxy object-storage has no server available!
<129>Nov  9 00:06:43 node-1 haproxy[834]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: proxy aodh has no server available!
<129>Nov  9 00:06:43 node-1 haproxy[834]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: 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>Nov  9 00:06:43 node-1 haproxy[834]: proxy ceilometer has no server available!
<129>Nov  9 00:06:44 node-1 haproxy[834]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:44 node-1 haproxy[834]: 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>Nov  9 00:06:44 node-1 haproxy[834]: 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>Nov  9 00:06:44 node-1 haproxy[834]: proxy nova-novncproxy has no server available!
<27>Nov  9 00:06:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:45 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:47 node-1 haproxy[2234]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:47 node-1 haproxy[2234]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:47 node-1 haproxy[2234]: 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>Nov  9 00:06:47 node-1 haproxy[2234]: 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>Nov  9 00:06:47 node-1 haproxy[2234]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:47 node-1 haproxy[2234]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:47 node-1 haproxy[2234]: 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>Nov  9 00:06:47 node-1 haproxy[2234]: 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>Nov  9 00:06:47 node-1 haproxy[2234]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:47 node-1 haproxy[2234]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy nova-api has no server available!
<129>Nov  9 00:06:48 node-1 haproxy[2243]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy nova-metadata-api has no server available!
<129>Nov  9 00:06:48 node-1 haproxy[2243]: Server cinder-api/node-1 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy cinder-api has no server available!
<129>Nov  9 00:06:48 node-1 haproxy[2243]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy glance-api has no server available!
<129>Nov  9 00:06:48 node-1 haproxy[2243]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy glance-glare has no server available!
<129>Nov  9 00:06:48 node-1 haproxy[2243]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy neutron has no server available!
<129>Nov  9 00:06:48 node-1 haproxy[2243]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy glance-registry has no server available!
<129>Nov  9 00:06:48 node-1 haproxy[2243]: Server mysqld/node-1 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: 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>Nov  9 00:06:48 node-1 haproxy[2243]: proxy mysqld has no server available!
<129>Nov  9 00:06:49 node-1 haproxy[2243]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: proxy object-storage has no server available!
<129>Nov  9 00:06:49 node-1 haproxy[2243]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: proxy aodh has no server available!
<129>Nov  9 00:06:49 node-1 haproxy[2243]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: proxy ceilometer has no server available!
<129>Nov  9 00:06:49 node-1 haproxy[2243]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: 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>Nov  9 00:06:49 node-1 haproxy[2243]: proxy nova-novncproxy has no server available!
<27>Nov  9 00:06:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:50 node-1 multipathd: uevent trigger error
<129>Nov  9 00:06:53 node-1 haproxy[3723]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:53 node-1 haproxy[3723]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:53 node-1 haproxy[3723]: 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>Nov  9 00:06:53 node-1 haproxy[3723]: 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>Nov  9 00:06:53 node-1 haproxy[3723]: proxy keystone-1 has no server available!
<129>Nov  9 00:06:53 node-1 haproxy[3723]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:53 node-1 haproxy[3723]: 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>Nov  9 00:06:53 node-1 haproxy[3723]: 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>Nov  9 00:06:53 node-1 haproxy[3723]: proxy keystone-2 has no server available!
<129>Nov  9 00:06:53 node-1 haproxy[3723]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:53 node-1 haproxy[3723]: 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>Nov  9 00:06:53 node-1 haproxy[3723]: 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>Nov  9 00:06:53 node-1 haproxy[3723]: proxy nova-api has no server available!
<129>Nov  9 00:06:53 node-1 haproxy[3723]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy nova-metadata-api has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server cinder-api/node-1 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy cinder-api has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy glance-api has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy glance-glare has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy neutron has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy glance-registry has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server mysqld/node-1 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy mysqld has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy object-storage has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: 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>Nov  9 00:06:54 node-1 haproxy[3732]: proxy aodh has no server available!
<129>Nov  9 00:06:54 node-1 haproxy[3732]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: proxy ceilometer has no server available!
<129>Nov  9 00:06:55 node-1 haproxy[3732]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: proxy heat-api has no server available!
<129>Nov  9 00:06:55 node-1 haproxy[3732]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: proxy heat-api-cfn has no server available!
<129>Nov  9 00:06:55 node-1 haproxy[3732]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: proxy heat-api-cloudwatch has no server available!
<129>Nov  9 00:06:55 node-1 haproxy[3732]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: 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>Nov  9 00:06:55 node-1 haproxy[3732]: proxy nova-novncproxy has no server available!
<27>Nov  9 00:06:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:06:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:07:07 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  9 00:07:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:07:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 00:07:33 node-1 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>Nov  9 00:07:35 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  9 00:08:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:08:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:08:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:08:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:08:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:10:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:44 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:44 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:49 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:10:50 node-1 multipathd: uevent trigger error
<43>Nov  9 00:11:02 node-1 apache2_error [Wed Nov 09 00:11:00.536702 2016] [mpm_event:notice] [pid 10752:tid 139863073318784] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  9 00:11:02 node-1 apache2_error [Wed Nov 09 00:11:00.536846 2016] [core:notice] [pid 10752:tid 139863073318784] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 00:11:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:09 node-1 multipathd: uevent trigger error
<43>Nov  9 00:11:12 node-1 apache2_error [Wed Nov 09 00:11:03.566016 2016] [mpm_event:notice] [pid 10752:tid 139863073318784] AH00491: caught SIGTERM, shutting down
<43>Nov  9 00:11:12 node-1 apache2_error [Wed Nov 09 00:11:04.647912 2016] [mpm_worker:notice] [pid 11959:tid 139882593695616] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  9 00:11:12 node-1 apache2_error [Wed Nov 09 00:11:04.647931 2016] [core:notice] [pid 11959:tid 139882593695616] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 00:11:14 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:14 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:14 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:14 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:14 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:14 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:17 node-1 multipathd: uevent trigger error
<27>Nov  9 00:11:17 node-1 multipathd: uevent trigger error
<43>Nov  9 00:12:22 node-1 apache2_error [Wed Nov 09 00:12:20.580681 2016] [mpm_worker:notice] [pid 11959:tid 139882593695616] AH00295: caught SIGTERM, shutting down
<43>Nov  9 00:12:22 node-1 apache2_error [Wed Nov 09 00:12:21.321552 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 00:12:22 node-1 apache2_error [Wed Nov 09 00:12:21.321575 2016] [core:notice] [pid 25999:tid 139700040669056] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  9 00:13:12 node-1 apache2_error [Wed Nov 09 00:13:04.916742 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 00:13:12 node-1 apache2_error [Wed Nov 09 00:13:05.109365 2016] [mpm_worker:warn] [pid 25999:tid 139700040669056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 00:13:12 node-1 apache2_error [Wed Nov 09 00:13:05.113553 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 00:13:12 node-1 apache2_error [Wed Nov 09 00:13:05.113580 2016] [core:notice] [pid 25999:tid 139700040669056] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 00:13:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:13:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:54 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:13:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:15 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:15 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:15 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:15 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:15 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:14:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:15:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:15:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:15:48 node-1 multipathd: uevent trigger error
<27>Nov  9 00:15:49 node-1 multipathd: uevent trigger error
<27>Nov  9 00:15:49 node-1 multipathd: uevent trigger error
<27>Nov  9 00:15:49 node-1 multipathd: uevent trigger error
<27>Nov  9 00:16:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:16:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:16:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:16:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:16:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:16:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:16:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:17:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:18:21 node-1 multipathd: uevent trigger error
<27>Nov  9 00:18:21 node-1 multipathd: uevent trigger error
<27>Nov  9 00:18:21 node-1 multipathd: uevent trigger error
<27>Nov  9 00:18:21 node-1 multipathd: uevent trigger error
<27>Nov  9 00:18:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:18:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:18:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:19:39 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:20:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:20:59 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:05 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:21:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:22:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:22:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:22:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:22:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:22:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:22:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:23:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:00 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:06 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Interface
<27>Nov  9 00:23:06 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Port
<27>Nov  9 00:23:07 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-prv" in table Port
<27>Nov  9 00:23:08 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Nov  9 00:23:08 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Nov  9 00:23:08 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Nov  9 00:23:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:09 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:22 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:52 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 00:25:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:26:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:23 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:23 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:24 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:36 node-1 multipathd: uevent trigger error
<27>Nov  9 00:26:36 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Nov  9 00:27:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:27:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:39 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:43 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 00:28:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:28:55 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:01 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:01 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:01 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:01 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:01 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:26 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:26 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:26 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:26 node-1 multipathd: uevent trigger error
<27>Nov  9 00:29:26 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:29 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:45 node-1 multipathd: uevent trigger error
<27>Nov  9 00:30:45 node-1 multipathd: uevent trigger error
<11>Nov  9 00:30:58 node-1 liberasurecode[79975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:30:58 node-1 liberasurecode[79975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:30:58 node-1 liberasurecode[79975]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:30:58 node-1 liberasurecode[79975]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:30:58 node-1 liberasurecode[80019]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:30:58 node-1 liberasurecode[80019]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:30:58 node-1 liberasurecode[80019]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:30:58 node-1 liberasurecode[80019]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:00 node-1 liberasurecode[80926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:00 node-1 liberasurecode[80926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:00 node-1 liberasurecode[80926]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:00 node-1 liberasurecode[80926]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81718]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81718]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81718]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81718]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81770]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81770]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81770]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81770]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81849]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81849]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81849]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81849]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81912]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81912]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81912]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81912]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81926]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81926]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81938]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81938]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81938]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81938]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81953]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81953]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81953]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:05 node-1 liberasurecode[81953]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:22 node-1 liberasurecode[82953]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:22 node-1 liberasurecode[82953]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:22 node-1 liberasurecode[82953]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:31:22 node-1 liberasurecode[82953]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  9 00:31:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:31:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:31:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:31:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:31:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:31:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  9 00:32:23 node-1 apache2_error [Wed Nov 09 00:32:16.988172 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 00:32:23 node-1 apache2_error [Wed Nov 09 00:32:17.371866 2016] [mpm_worker:warn] [pid 25999:tid 139700040669056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 00:32:23 node-1 apache2_error [Wed Nov 09 00:32:17.378144 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 00:32:23 node-1 apache2_error [Wed Nov 09 00:32:17.378170 2016] [core:notice] [pid 25999:tid 139700040669056] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 00:32:58 node-1 multipathd: uevent trigger error
<27>Nov  9 00:32:58 node-1 multipathd: uevent trigger error
<27>Nov  9 00:32:58 node-1 multipathd: uevent trigger error
<27>Nov  9 00:32:58 node-1 multipathd: uevent trigger error
<27>Nov  9 00:32:58 node-1 multipathd: uevent trigger error
<43>Nov  9 00:33:03 node-1 apache2_error [Wed Nov 09 00:32:54.294617 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 00:33:03 node-1 apache2_error [Wed Nov 09 00:32:54.488150 2016] [mpm_worker:warn] [pid 25999:tid 139700040669056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 00:33:03 node-1 apache2_error [Wed Nov 09 00:32:54.493715 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 00:33:03 node-1 apache2_error [Wed Nov 09 00:32:54.493750 2016] [core:notice] [pid 25999:tid 139700040669056] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 00:33:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:06 node-1 multipathd: uevent trigger error
<43>Nov  9 00:33:43 node-1 apache2_error [Wed Nov 09 00:33:40.417819 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 00:33:43 node-1 apache2_error [Wed Nov 09 00:33:40.616219 2016] [mpm_worker:warn] [pid 25999:tid 139700040669056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 00:33:43 node-1 apache2_error [Wed Nov 09 00:33:40.623050 2016] [mpm_worker:notice] [pid 25999:tid 139700040669056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 00:33:43 node-1 apache2_error [Wed Nov 09 00:33:40.623080 2016] [core:notice] [pid 25999:tid 139700040669056] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 00:33:44 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:44 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:44 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:44 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:44 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:50 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:33:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:06 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:41 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:48 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  9 00:34:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:57 node-1 multipathd: uevent trigger error
<27>Nov  9 00:34:57 node-1 multipathd: uevent trigger error
<11>Nov  9 00:35:01 node-1 liberasurecode[130307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:35:01 node-1 liberasurecode[130307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:35:01 node-1 liberasurecode[130307]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 00:35:01 node-1 liberasurecode[130307]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  9 00:35:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:11 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:30 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:02 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:15 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:16 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:20 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:32 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:37 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:37 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:37 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:37 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:42 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:47 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:47 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:47 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:47 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:47 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:47 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:51 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:56 node-1 multipathd: uevent trigger error
<27>Nov  9 00:36:56 node-1 multipathd: uevent trigger error
