Nov 13 00:47:41 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] start
Nov 13 00:47:41 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov 13 00:47:41 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov 13 00:47:41 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov 13 00:47:41 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 13 00:47:41 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 13 00:47:41 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov 13 00:47:41 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 13 00:47:41 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=ad9eaf35-e4dd-48ed-90a6-9dacec29419a nomdmonddf nomdmonisw
Nov 13 00:47:41 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov 13 00:47:41 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov 13 00:47:41 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov 13 00:47:41 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov 13 00:47:41 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov 13 00:47:41 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov 13 00:47:41 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov 13 00:47:41 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 13 00:47:41 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 13 00:47:41 node-1 kernel: [    0.000000] No AGP bridge found
Nov 13 00:47:41 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov 13 00:47:41 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov 13 00:47:41 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov 13 00:47:41 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov 13 00:47:41 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov 13 00:47:41 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov 13 00:47:41 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov 13 00:47:41 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov 13 00:47:41 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov 13 00:47:41 node-1 kernel: [    0.000000]   2 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000]   3 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000]   4 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000]   5 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000]   6 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000]   7 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000]   8 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000]   9 disabled
Nov 13 00:47:41 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 13 00:47:41 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov 13 00:47:41 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov 13 00:47:41 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov 13 00:47:41 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov 13 00:47:41 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov 13 00:47:41 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov 13 00:47:41 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov 13 00:47:41 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov 13 00:47:41 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov 13 00:47:41 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov 13 00:47:41 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov 13 00:47:41 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov 13 00:47:41 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov 13 00:47:41 node-1 kernel: [    0.000000] Zone ranges:
Nov 13 00:47:41 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] Movable zone start for each node
Nov 13 00:47:41 node-1 kernel: [    0.000000] Early memory node ranges
Nov 13 00:47:41 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Nov 13 00:47:41 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov 13 00:47:41 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov 13 00:47:41 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov 13 00:47:41 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Nov 13 00:47:41 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Nov 13 00:47:41 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov 13 00:47:41 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov 13 00:47:41 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov 13 00:47:41 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov 13 00:47:41 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov 13 00:47:41 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov 13 00:47:41 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov 13 00:47:41 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov 13 00:47:41 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov 13 00:47:41 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov 13 00:47:41 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov 13 00:47:41 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov 13 00:47:41 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov 13 00:47:41 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov 13 00:47:41 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov 13 00:47:41 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov 13 00:47:41 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov 13 00:47:41 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 13 00:47:41 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Nov 13 00:47:41 node-1 kernel: [    0.000000] Policy zone: Normal
Nov 13 00:47:41 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=ad9eaf35-e4dd-48ed-90a6-9dacec29419a nomdmonddf nomdmonisw
Nov 13 00:47:41 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov 13 00:47:41 node-1 kernel: [    0.000000] Checking aperture...
Nov 13 00:47:41 node-1 kernel: [    0.000000] No AGP bridge found
Nov 13 00:47:41 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov 13 00:47:41 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov 13 00:47:41 node-1 kernel: [    0.000000] Memory: 32653452K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Nov 13 00:47:41 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov 13 00:47:41 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov 13 00:47:41 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov 13 00:47:41 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov 13 00:47:41 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov 13 00:47:41 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov 13 00:47:41 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov 13 00:47:41 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov 13 00:47:41 node-1 kernel: [    0.000000] console [tty0] enabled
Nov 13 00:47:41 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov 13 00:47:41 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 13 00:47:41 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov 13 00:47:41 node-1 kernel: [    0.000000] hpet clockevent registered
Nov 13 00:47:41 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov 13 00:47:41 node-1 kernel: [    0.004000] tsc: Detected 3492.029 MHz processor
Nov 13 00:47:41 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.05 BogoMIPS (lpj=13968116)
Nov 13 00:47:41 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov 13 00:47:41 node-1 kernel: [    0.000043] Security Framework initialized
Nov 13 00:47:41 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Nov 13 00:47:41 node-1 kernel: [    0.000062] Yama: becoming mindful.
Nov 13 00:47:41 node-1 kernel: [    0.001466] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.006397] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.008317] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.008345] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.008632] Initializing cgroup subsys memory
Nov 13 00:47:41 node-1 kernel: [    0.008640] Initializing cgroup subsys devices
Nov 13 00:47:41 node-1 kernel: [    0.008642] Initializing cgroup subsys freezer
Nov 13 00:47:41 node-1 kernel: [    0.008643] Initializing cgroup subsys blkio
Nov 13 00:47:41 node-1 kernel: [    0.008645] Initializing cgroup subsys perf_event
Nov 13 00:47:41 node-1 kernel: [    0.008647] Initializing cgroup subsys hugetlb
Nov 13 00:47:41 node-1 kernel: [    0.008666] CPU: Physical Processor ID: 0
Nov 13 00:47:41 node-1 kernel: [    0.008668] CPU: Processor Core ID: 0
Nov 13 00:47:41 node-1 kernel: [    0.008671] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov 13 00:47:41 node-1 kernel: [    0.008671] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov 13 00:47:41 node-1 kernel: [    0.009365] mce: CPU supports 22 MCE banks
Nov 13 00:47:41 node-1 kernel: [    0.009392] CPU0: Thermal monitoring enabled (TM1)
Nov 13 00:47:41 node-1 kernel: [    0.009413] process: using mwait in idle threads
Nov 13 00:47:41 node-1 kernel: [    0.009416] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov 13 00:47:41 node-1 kernel: [    0.009416] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov 13 00:47:41 node-1 kernel: [    0.009416] tlb_flushall_shift: 6
Nov 13 00:47:41 node-1 kernel: [    0.009504] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov 13 00:47:41 node-1 kernel: [    0.010225] ACPI: Core revision 20131115
Nov 13 00:47:41 node-1 kernel: [    0.023029] ACPI: All ACPI Tables successfully acquired
Nov 13 00:47:41 node-1 kernel: [    0.023195] ftrace: allocating 28622 entries in 112 pages
Nov 13 00:47:41 node-1 kernel: [    0.031938] dmar: Host address width 46
Nov 13 00:47:41 node-1 kernel: [    0.031940] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov 13 00:47:41 node-1 kernel: [    0.031946] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 00:47:41 node-1 kernel: [    0.031948] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov 13 00:47:41 node-1 kernel: [    0.031952] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 00:47:41 node-1 kernel: [    0.031954] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov 13 00:47:41 node-1 kernel: [    0.031955] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov 13 00:47:41 node-1 kernel: [    0.031956] dmar: ATSR flags: 0x0
Nov 13 00:47:41 node-1 kernel: [    0.031957] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov 13 00:47:41 node-1 kernel: [    0.031958] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov 13 00:47:41 node-1 kernel: [    0.032074] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov 13 00:47:41 node-1 kernel: [    0.032075] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 00:47:41 node-1 kernel: [    0.032076] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 00:47:41 node-1 kernel: [    0.032077] HPET id 0 under DRHD base 0xc7ffc000
Nov 13 00:47:41 node-1 kernel: [    0.032078] Your BIOS is broken and requested that x2apic be disabled.
Nov 13 00:47:41 node-1 kernel: [    0.032078] This will slightly decrease performance.
Nov 13 00:47:41 node-1 kernel: [    0.032078] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov 13 00:47:41 node-1 kernel: [    0.032510] Enabled IRQ remapping in xapic mode
Nov 13 00:47:41 node-1 kernel: [    0.032511] x2apic not enabled, IRQ remapping is in xapic mode
Nov 13 00:47:41 node-1 kernel: [    0.032515] Switched APIC routing to physical flat.
Nov 13 00:47:41 node-1 kernel: [    0.033093] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 13 00:47:41 node-1 kernel: [    0.072744] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov 13 00:47:41 node-1 kernel: [    0.072749] TSC deadline timer enabled
Nov 13 00:47:41 node-1 kernel: [    0.072757] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov 13 00:47:41 node-1 kernel: [    0.072763] ... version:                3
Nov 13 00:47:41 node-1 kernel: [    0.072764] ... bit width:              48
Nov 13 00:47:41 node-1 kernel: [    0.072765] ... generic registers:      4
Nov 13 00:47:41 node-1 kernel: [    0.072766] ... value mask:             0000ffffffffffff
Nov 13 00:47:41 node-1 kernel: [    0.072767] ... max period:             0000ffffffffffff
Nov 13 00:47:41 node-1 kernel: [    0.072768] ... fixed-purpose events:   3
Nov 13 00:47:41 node-1 kernel: [    0.072769] ... event mask:             000000070000000f
Nov 13 00:47:41 node-1 kernel: [    0.074177] x86: Booting SMP configuration:
Nov 13 00:47:41 node-1 kernel: [    0.088282] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 13 00:47:41 node-1 kernel: [    0.074179] .... node  #0, CPUs:        #1  #2  #3
Nov 13 00:47:41 node-1 kernel: [    0.116194] .... node  #1, CPUs:    #4  #5  #6  #7
Nov 13 00:47:41 node-1 kernel: [    0.270344] .... node  #0, CPUs:    #8  #9 #10 #11
Nov 13 00:47:41 node-1 kernel: [    0.325964] .... node  #1, CPUs:   #12 #13 #14 #15
Nov 13 00:47:41 node-1 kernel: [    0.383017] x86: Booted up 2 nodes, 16 CPUs
Nov 13 00:47:41 node-1 kernel: [    0.383020] smpboot: Total of 16 processors activated (111757.04 BogoMIPS)
Nov 13 00:47:41 node-1 kernel: [    0.407766] devtmpfs: initialized
Nov 13 00:47:41 node-1 kernel: [    0.410260] EVM: security.selinux
Nov 13 00:47:41 node-1 kernel: [    0.410261] EVM: security.SMACK64
Nov 13 00:47:41 node-1 kernel: [    0.410262] EVM: security.ima
Nov 13 00:47:41 node-1 kernel: [    0.410263] EVM: security.capability
Nov 13 00:47:41 node-1 kernel: [    0.410314] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.410960] pinctrl core: initialized pinctrl subsystem
Nov 13 00:47:41 node-1 kernel: [    0.411021] regulator-dummy: no parameters
Nov 13 00:47:41 node-1 kernel: [    0.411053] RTC time:  0:47:05, date: 11/13/16
Nov 13 00:47:41 node-1 kernel: [    0.411086] NET: Registered protocol family 16
Nov 13 00:47:41 node-1 kernel: [    0.411169] cpuidle: using governor ladder
Nov 13 00:47:41 node-1 kernel: [    0.411171] cpuidle: using governor menu
Nov 13 00:47:41 node-1 kernel: [    0.411205] ACPI: bus type PCI registered
Nov 13 00:47:41 node-1 kernel: [    0.411207] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 13 00:47:41 node-1 kernel: [    0.411265] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov 13 00:47:41 node-1 kernel: [    0.411268] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov 13 00:47:41 node-1 kernel: [    0.425000] PCI: Using configuration type 1 for base access
Nov 13 00:47:41 node-1 kernel: [    0.425988] bio: create slab <bio-0> at 0
Nov 13 00:47:41 node-1 kernel: [    0.426269] ACPI: Added _OSI(Module Device)
Nov 13 00:47:41 node-1 kernel: [    0.426270] ACPI: Added _OSI(Processor Device)
Nov 13 00:47:41 node-1 kernel: [    0.426271] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 13 00:47:41 node-1 kernel: [    0.426272] ACPI: Added _OSI(Processor Aggregator Device)
Nov 13 00:47:41 node-1 kernel: [    0.438971] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov 13 00:47:41 node-1 kernel: [    0.449682] ACPI: Interpreter enabled
Nov 13 00:47:41 node-1 kernel: [    0.449688] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov 13 00:47:41 node-1 kernel: [    0.449692] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov 13 00:47:41 node-1 kernel: [    0.449694] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov 13 00:47:41 node-1 kernel: [    0.449701] ACPI: (supports S0 S4 S5)
Nov 13 00:47:41 node-1 kernel: [    0.449703] ACPI: Using IOAPIC for interrupt routing
Nov 13 00:47:41 node-1 kernel: [    0.449747] HEST: Table parsing has been initialized.
Nov 13 00:47:41 node-1 kernel: [    0.449750] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 13 00:47:41 node-1 kernel: [    0.450305] ACPI: No dock devices found.
Nov 13 00:47:41 node-1 kernel: [    0.461956] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov 13 00:47:41 node-1 kernel: [    0.461961] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 00:47:41 node-1 kernel: [    0.461964] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 00:47:41 node-1 kernel: [    0.461994] PCI host bridge to bus 0000:ff
Nov 13 00:47:41 node-1 kernel: [    0.461996] pci_bus 0000:ff: root bus resource [bus ff]
Nov 13 00:47:41 node-1 kernel: [    0.462004] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462043] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.462074] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462110] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462140] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.462170] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.462201] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462230] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462261] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462289] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462315] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462341] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462369] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462395] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462422] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462449] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462477] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462504] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462531] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.462559] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462585] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.462611] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462637] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462667] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.462702] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462734] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462764] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462795] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462826] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462857] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462888] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462918] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462949] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.462981] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463014] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463046] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463080] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463110] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463138] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463171] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463204] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463242] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463279] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463312] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463343] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463372] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463402] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463434] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463465] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463497] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463529] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463559] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463588] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463618] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463649] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463681] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463713] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463775] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov 13 00:47:41 node-1 kernel: [    0.463778] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 00:47:41 node-1 kernel: [    0.463781] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 00:47:41 node-1 kernel: [    0.463800] PCI host bridge to bus 0000:7f
Nov 13 00:47:41 node-1 kernel: [    0.463802] pci_bus 0000:7f: root bus resource [bus 7f]
Nov 13 00:47:41 node-1 kernel: [    0.463807] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463835] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.463864] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463894] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463916] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.463942] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.463968] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.463995] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464017] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464040] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464063] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464085] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464109] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464131] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464155] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464181] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464203] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464226] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464248] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.464272] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464295] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.464316] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464339] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464366] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 00:47:41 node-1 kernel: [    0.464398] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464427] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464455] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464481] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464506] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464531] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464557] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464585] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464610] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464639] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464670] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464698] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464727] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464754] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464781] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464810] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464835] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464861] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464890] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464918] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464945] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464970] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.464996] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465022] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465047] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465074] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465104] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465130] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465152] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465178] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465204] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465234] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.465261] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.466503] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov 13 00:47:41 node-1 kernel: [    0.466506] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 00:47:41 node-1 kernel: [    0.467625] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 00:47:41 node-1 kernel: [    0.468139] PCI host bridge to bus 0000:00
Nov 13 00:47:41 node-1 kernel: [    0.468141] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov 13 00:47:41 node-1 kernel: [    0.468143] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov 13 00:47:41 node-1 kernel: [    0.468144] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov 13 00:47:41 node-1 kernel: [    0.468146] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov 13 00:47:41 node-1 kernel: [    0.468147] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov 13 00:47:41 node-1 kernel: [    0.468148] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 13 00:47:41 node-1 kernel: [    0.468150] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov 13 00:47:41 node-1 kernel: [    0.468155] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov 13 00:47:41 node-1 kernel: [    0.468238] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.468269] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.468310] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov 13 00:47:41 node-1 kernel: [    0.468331] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.468360] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.468400] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov 13 00:47:41 node-1 kernel: [    0.468419] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.468449] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.468489] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov 13 00:47:41 node-1 kernel: [    0.468506] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.468577] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.468653] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.468734] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 00:47:41 node-1 kernel: [    0.468739] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov 13 00:47:41 node-1 kernel: [    0.468825] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov 13 00:47:41 node-1 kernel: [    0.468974] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov 13 00:47:41 node-1 kernel: [    0.468991] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov 13 00:47:41 node-1 kernel: [    0.469070] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.469123] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov 13 00:47:41 node-1 kernel: [    0.469145] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.469200] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.469244] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 13 00:47:41 node-1 kernel: [    0.469271] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.469327] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.469370] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov 13 00:47:41 node-1 kernel: [    0.469395] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov 13 00:47:41 node-1 kernel: [    0.469412] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov 13 00:47:41 node-1 kernel: [    0.469490] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.469540] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 13 00:47:41 node-1 kernel: [    0.469566] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov 13 00:47:41 node-1 kernel: [    0.469815] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov 13 00:47:41 node-1 kernel: [    0.469821] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov 13 00:47:41 node-1 kernel: [    0.469827] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.469833] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.469840] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov 13 00:47:41 node-1 kernel: [    0.469870] pci 0000:01:00.0: supports D1 D2
Nov 13 00:47:41 node-1 kernel: [    0.475775] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 00:47:41 node-1 kernel: [    0.475781] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 00:47:41 node-1 kernel: [    0.475785] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 00:47:41 node-1 kernel: [    0.476048] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.476107] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov 13 00:47:41 node-1 kernel: [    0.483770] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 00:47:41 node-1 kernel: [    0.483776] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.483780] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 00:47:41 node-1 kernel: [    0.483864] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.483941] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.484039] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.484098] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 00:47:41 node-1 kernel: [    0.484101] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.484103] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 00:47:41 node-1 kernel: [    0.484156] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.484278] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.484332] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 00:47:41 node-1 kernel: [    0.484335] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.484337] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.484386] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.484505] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.484547] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.484666] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.484702] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.484821] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.484865] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov 13 00:47:41 node-1 kernel: [    0.484987] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov 13 00:47:41 node-1 kernel: [    0.485029] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 00:47:41 node-1 kernel: [    0.485031] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.485033] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.485093] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov 13 00:47:41 node-1 kernel: [    0.485157] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.485209] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.485250] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov 13 00:47:41 node-1 kernel: [    0.485332] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov 13 00:47:41 node-1 kernel: [    0.485438] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 00:47:41 node-1 kernel: [    0.485440] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.485442] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.485498] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov 13 00:47:41 node-1 kernel: [    0.485552] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.485600] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.485810] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 00:47:41 node-1 kernel: [    0.485814] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 00:47:41 node-1 kernel: [    0.485898] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov 13 00:47:41 node-1 kernel: [    0.485955] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.486006] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.486217] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 00:47:41 node-1 kernel: [    0.486220] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 00:47:41 node-1 kernel: [    0.486279] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov 13 00:47:41 node-1 kernel: [    0.486339] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.486391] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov 13 00:47:41 node-1 kernel: [    0.486614] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 00:47:41 node-1 kernel: [    0.486618] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 00:47:41 node-1 kernel: [    0.486792] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 00:47:41 node-1 kernel: [    0.486830] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 00:47:41 node-1 kernel: [    0.486909] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov 13 00:47:41 node-1 kernel: [    0.486927] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov 13 00:47:41 node-1 kernel: [    0.486940] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov 13 00:47:41 node-1 kernel: [    0.486954] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov 13 00:47:41 node-1 kernel: [    0.487004] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov 13 00:47:41 node-1 kernel: [    0.491776] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 00:47:41 node-1 kernel: [    0.491785] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 00:47:41 node-1 kernel: [    0.491838] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov 13 00:47:41 node-1 kernel: [    0.492529] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov 13 00:47:41 node-1 kernel: [    0.492532] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 00:47:41 node-1 kernel: [    0.492651] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 00:47:41 node-1 kernel: [    0.492765] PCI host bridge to bus 0000:80
Nov 13 00:47:41 node-1 kernel: [    0.492767] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov 13 00:47:41 node-1 kernel: [    0.492769] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov 13 00:47:41 node-1 kernel: [    0.492770] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov 13 00:47:41 node-1 kernel: [    0.492778] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.492842] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.492910] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 00:47:41 node-1 kernel: [    0.492973] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 00:47:41 node-1 kernel: [    0.492978] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov 13 00:47:41 node-1 kernel: [    0.493051] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov 13 00:47:41 node-1 kernel: [    0.493347] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 13 00:47:41 node-1 kernel: [    0.493379] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 13 00:47:41 node-1 kernel: [    0.493408] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov 13 00:47:41 node-1 kernel: [    0.493437] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov 13 00:47:41 node-1 kernel: [    0.493467] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 00:47:41 node-1 kernel: [    0.493497] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 00:47:41 node-1 kernel: [    0.493526] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 00:47:41 node-1 kernel: [    0.493556] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 00:47:41 node-1 kernel: [    0.493642] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov 13 00:47:41 node-1 kernel: [    0.493646] ACPI: \_SB_.UNC1: notify handler is installed
Nov 13 00:47:41 node-1 kernel: [    0.493647] ACPI: \_SB_.UNC0: notify handler is installed
Nov 13 00:47:41 node-1 kernel: [    0.493662] ACPI: \_SB_.PCI0: notify handler is installed
Nov 13 00:47:41 node-1 kernel: [    0.493714] ACPI: \_SB_.PCI1: notify handler is installed
Nov 13 00:47:41 node-1 kernel: [    0.493794] Found 4 acpi root devices
Nov 13 00:47:41 node-1 kernel: [    0.493903] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov 13 00:47:41 node-1 kernel: [    0.493905] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov 13 00:47:41 node-1 kernel: [    0.493907] vgaarb: loaded
Nov 13 00:47:41 node-1 kernel: [    0.493908] vgaarb: bridge control possible 0000:0c:00.0
Nov 13 00:47:41 node-1 kernel: [    0.494029] SCSI subsystem initialized
Nov 13 00:47:41 node-1 kernel: [    0.494094] libata version 3.00 loaded.
Nov 13 00:47:41 node-1 kernel: [    0.494110] ACPI: bus type USB registered
Nov 13 00:47:41 node-1 kernel: [    0.494121] usbcore: registered new interface driver usbfs
Nov 13 00:47:41 node-1 kernel: [    0.494126] usbcore: registered new interface driver hub
Nov 13 00:47:41 node-1 kernel: [    0.494151] usbcore: registered new device driver usb
Nov 13 00:47:41 node-1 kernel: [    0.494319] PCI: Using ACPI for IRQ routing
Nov 13 00:47:41 node-1 kernel: [    0.497915] PCI: pci_cache_line_size set to 64 bytes
Nov 13 00:47:41 node-1 kernel: [    0.498122] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov 13 00:47:41 node-1 kernel: [    0.498123] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Nov 13 00:47:41 node-1 kernel: [    0.498123] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov 13 00:47:41 node-1 kernel: [    0.498188] NetLabel: Initializing
Nov 13 00:47:41 node-1 kernel: [    0.498190] NetLabel:  domain hash size = 128
Nov 13 00:47:41 node-1 kernel: [    0.498190] NetLabel:  protocols = UNLABELED CIPSOv4
Nov 13 00:47:41 node-1 kernel: [    0.498200] NetLabel:  unlabeled traffic allowed by default
Nov 13 00:47:41 node-1 kernel: [    0.498256] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov 13 00:47:41 node-1 kernel: [    0.498260] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov 13 00:47:41 node-1 kernel: [    0.500330] Switched to clocksource hpet
Nov 13 00:47:41 node-1 kernel: [    0.504865] AppArmor: AppArmor Filesystem Enabled
Nov 13 00:47:41 node-1 kernel: [    0.504903] pnp: PnP ACPI init
Nov 13 00:47:41 node-1 kernel: [    0.504915] ACPI: bus type PNP registered
Nov 13 00:47:41 node-1 kernel: [    0.505093] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505105] pnp 00:01: [dma 4]
Nov 13 00:47:41 node-1 kernel: [    0.505123] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505157] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505182] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505203] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505251] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505363] system 00:06: [io  0x0500-0x057f] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505366] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov 13 00:47:41 node-1 kernel: [    0.505367] system 00:06: [io  0x0580-0x059f] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505369] system 00:06: [io  0x0600-0x061f] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505370] system 00:06: [io  0x0880-0x0883] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505372] system 00:06: [io  0x0800-0x081f] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505375] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov 13 00:47:41 node-1 kernel: [    0.505376] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505378] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505380] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505381] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505383] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505384] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov 13 00:47:41 node-1 kernel: [    0.505386] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505487] pnp 00:07: [dma 0 disabled]
Nov 13 00:47:41 node-1 kernel: [    0.505519] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505601] pnp 00:08: [dma 0 disabled]
Nov 13 00:47:41 node-1 kernel: [    0.505639] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 00:47:41 node-1 kernel: [    0.505698] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov 13 00:47:41 node-1 kernel: [    0.506142] pnp: PnP ACPI: found 10 devices
Nov 13 00:47:41 node-1 kernel: [    0.506144] ACPI: bus type PNP unregistered
Nov 13 00:47:41 node-1 kernel: [    0.512142] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 00:47:41 node-1 kernel: [    0.512146] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 00:47:41 node-1 kernel: [    0.512149] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 00:47:41 node-1 kernel: [    0.512154] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 00:47:41 node-1 kernel: [    0.512156] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512171] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512200] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 00:47:41 node-1 kernel: [    0.512215] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512244] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 00:47:41 node-1 kernel: [    0.512258] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 00:47:41 node-1 kernel: [    0.512287] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 00:47:41 node-1 kernel: [    0.512306] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 00:47:41 node-1 kernel: [    0.512335] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 00:47:41 node-1 kernel: [    0.512337] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512352] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512384] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 00:47:41 node-1 kernel: [    0.512386] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512400] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512429] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 00:47:41 node-1 kernel: [    0.512431] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512434] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512439] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 00:47:41 node-1 kernel: [    0.512440] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512443] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512448] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 00:47:41 node-1 kernel: [    0.512454] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 00:47:41 node-1 kernel: [    0.512463] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 00:47:41 node-1 kernel: [    0.512467] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 00:47:41 node-1 kernel: [    0.512474] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov 13 00:47:41 node-1 kernel: [    0.512475] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov 13 00:47:41 node-1 kernel: [    0.512476] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov 13 00:47:41 node-1 kernel: [    0.512477] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov 13 00:47:41 node-1 kernel: [    0.512478] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov 13 00:47:41 node-1 kernel: [    0.512479] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov 13 00:47:41 node-1 kernel: [    0.512480] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov 13 00:47:41 node-1 kernel: [    0.512480] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov 13 00:47:41 node-1 kernel: [    0.512482] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512483] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512483] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512484] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512485] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512486] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512487] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512488] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512489] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov 13 00:47:41 node-1 kernel: [    0.512490] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512491] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov 13 00:47:41 node-1 kernel: [    0.512493] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov 13 00:47:41 node-1 kernel: [    0.512494] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov 13 00:47:41 node-1 kernel: [    0.512495] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov 13 00:47:41 node-1 kernel: [    0.512498] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov 13 00:47:41 node-1 kernel: [    0.512499] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov 13 00:47:41 node-1 kernel: [    0.512539] NET: Registered protocol family 2
Nov 13 00:47:41 node-1 kernel: [    0.512839] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.513210] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.513378] TCP: Hash tables configured (established 262144 bind 65536)
Nov 13 00:47:41 node-1 kernel: [    0.513423] TCP: reno registered
Nov 13 00:47:41 node-1 kernel: [    0.513454] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 00:47:41 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov 13 00:47:41 node-1 kernel: [    0.513562] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.513727] NET: Registered protocol family 1
Nov 13 00:47:41 node-1 kernel: [    0.552403] pci 0000:0c:00.0: Video device with shadowed ROM
Nov 13 00:47:41 node-1 kernel: [    0.552410] PCI: CLS 64 bytes, default 64
Nov 13 00:47:41 node-1 kernel: [    0.552455] Trying to unpack rootfs image as initramfs...
Nov 13 00:47:41 node-1 kernel: [    0.774876] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Nov 13 00:47:41 node-1 kernel: [    0.774924] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov 13 00:47:41 node-1 kernel: [    0.774927] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Nov 13 00:47:41 node-1 kernel: [    0.775338] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775352] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775376] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775383] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775392] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775400] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775406] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775413] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775421] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775428] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775438] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775445] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775451] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775458] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775463] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775467] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 00:47:41 node-1 kernel: [    0.775516] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 13 00:47:41 node-1 kernel: [    0.775518] Scanning for low memory corruption every 60 seconds
Nov 13 00:47:41 node-1 kernel: [    0.775811] Initialise system trusted keyring
Nov 13 00:47:41 node-1 kernel: [    0.775865] audit: initializing netlink socket (disabled)
Nov 13 00:47:41 node-1 kernel: [    0.775876] type=2000 audit(1478998025.724:1): initialized
Nov 13 00:47:41 node-1 kernel: [    0.793624] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 13 00:47:41 node-1 kernel: [    0.795102] zbud: loaded
Nov 13 00:47:41 node-1 kernel: [    0.795225] VFS: Disk quotas dquot_6.5.2
Nov 13 00:47:41 node-1 kernel: [    0.795265] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 13 00:47:41 node-1 kernel: [    0.795614] fuse init (API version 7.22)
Nov 13 00:47:41 node-1 kernel: [    0.795665] msgmni has been set to 32768
Nov 13 00:47:41 node-1 kernel: [    0.795709] Key type big_key registered
Nov 13 00:47:41 node-1 kernel: [    0.796214] Key type asymmetric registered
Nov 13 00:47:41 node-1 kernel: [    0.796216] Asymmetric key parser 'x509' registered
Nov 13 00:47:41 node-1 kernel: [    0.796240] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 13 00:47:41 node-1 kernel: [    0.796308] io scheduler noop registered
Nov 13 00:47:41 node-1 kernel: [    0.796317] io scheduler deadline registered (default)
Nov 13 00:47:41 node-1 kernel: [    0.796336] io scheduler cfq registered
Nov 13 00:47:41 node-1 kernel: [    0.796827] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    0.797022] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    0.797140] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    0.797254] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    0.797373] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    0.797467] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    0.797910] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov 13 00:47:41 node-1 kernel: [    0.797953] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov 13 00:47:41 node-1 kernel: [    0.797970] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov 13 00:47:41 node-1 kernel: [    0.797983] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.797985] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.797987] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov 13 00:47:41 node-1 kernel: [    0.797993] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.797994] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.797995] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.797997] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.797999] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798000] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798001] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798003] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798004] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798005] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798007] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798008] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798010] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov 13 00:47:41 node-1 kernel: [    0.798024] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798026] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov 13 00:47:41 node-1 kernel: [    0.798037] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798040] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov 13 00:47:41 node-1 kernel: [    0.798051] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798052] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov 13 00:47:41 node-1 kernel: [    0.798055] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov 13 00:47:41 node-1 kernel: [    0.798084] ioapic: probe of 0000:00:05.4 failed with error -22
Nov 13 00:47:41 node-1 kernel: [    0.798089] ioapic: probe of 0000:80:05.4 failed with error -22
Nov 13 00:47:41 node-1 kernel: [    0.798093] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 13 00:47:41 node-1 kernel: [    0.798102] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 13 00:47:41 node-1 kernel: [    0.798139] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov 13 00:47:41 node-1 kernel: [    0.798140] vesafb: scrolling: redraw
Nov 13 00:47:41 node-1 kernel: [    0.798142] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 13 00:47:41 node-1 kernel: [    0.818270] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov 13 00:47:41 node-1 kernel: [    0.826757] Console: switching to colour frame buffer device 80x30
Nov 13 00:47:41 node-1 kernel: [    0.835567] fb0: VESA VGA frame buffer device
Nov 13 00:47:41 node-1 kernel: [    0.835769] intel_idle: MWAIT substates: 0x2120
Nov 13 00:47:41 node-1 kernel: [    0.835769] intel_idle: v0.4 model 0x3F
Nov 13 00:47:41 node-1 kernel: [    0.835770] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov 13 00:47:41 node-1 kernel: [    0.836011] ipmi message handler version 39.2
Nov 13 00:47:41 node-1 kernel: [    0.836297] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov 13 00:47:41 node-1 kernel: [    0.836736] ACPI: AC Adapter [P111] (on-line)
Nov 13 00:47:41 node-1 kernel: [    0.842016] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov 13 00:47:41 node-1 kernel: [    0.853025] ACPI: Power Button [PWRB]
Nov 13 00:47:41 node-1 kernel: [    0.858839] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov 13 00:47:41 node-1 kernel: [    0.870476] ACPI: Power Button [PWRF]
Nov 13 00:47:41 node-1 kernel: [    0.897895] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov 13 00:47:41 node-1 kernel: [    0.909535] pstore: Registered erst as persistent store backend
Nov 13 00:47:41 node-1 kernel: [    0.915724] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov 13 00:47:41 node-1 kernel: [    0.927659] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 13 00:47:41 node-1 kernel: [    0.954396] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov 13 00:47:41 node-1 kernel: [    0.987715] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov 13 00:47:41 node-1 kernel: [    1.001848] Linux agpgart interface v0.103
Nov 13 00:47:41 node-1 kernel: [    1.009551] brd: module loaded
Nov 13 00:47:41 node-1 kernel: [    1.016624] loop: module loaded
Nov 13 00:47:41 node-1 kernel: [    1.023381] libphy: Fixed MDIO Bus: probed
Nov 13 00:47:41 node-1 kernel: [    1.029871] tun: Universal TUN/TAP device driver, 1.6
Nov 13 00:47:41 node-1 kernel: [    1.036351] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 13 00:47:41 node-1 kernel: [    1.042891] PPP generic driver version 2.4.2
Nov 13 00:47:41 node-1 kernel: [    1.049276] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 13 00:47:41 node-1 kernel: [    1.055735] ehci-pci: EHCI PCI platform driver
Nov 13 00:47:41 node-1 kernel: [    1.062285] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov 13 00:47:41 node-1 kernel: [    1.068754] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov 13 00:47:41 node-1 kernel: [    1.081401] ehci-pci 0000:00:1a.0: debug port 2
Nov 13 00:47:41 node-1 kernel: [    1.091643] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov 13 00:47:41 node-1 kernel: [    1.091661] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov 13 00:47:41 node-1 kernel: [    1.107806] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov 13 00:47:41 node-1 kernel: [    1.113860] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 00:47:41 node-1 kernel: [    1.120003] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 00:47:41 node-1 kernel: [    1.131843] usb usb1: Product: EHCI Host Controller
Nov 13 00:47:41 node-1 kernel: [    1.137841] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 00:47:41 node-1 kernel: [    1.143858] usb usb1: SerialNumber: 0000:00:1a.0
Nov 13 00:47:41 node-1 kernel: [    1.149789] hub 1-0:1.0: USB hub found
Nov 13 00:47:41 node-1 kernel: [    1.155537] hub 1-0:1.0: 2 ports detected
Nov 13 00:47:41 node-1 kernel: [    1.161290] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov 13 00:47:41 node-1 kernel: [    1.166850] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov 13 00:47:41 node-1 kernel: [    1.177683] ehci-pci 0000:00:1d.0: debug port 2
Nov 13 00:47:41 node-1 kernel: [    1.186958] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov 13 00:47:41 node-1 kernel: [    1.186961] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov 13 00:47:41 node-1 kernel: [    1.203724] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov 13 00:47:41 node-1 kernel: [    1.208900] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 00:47:41 node-1 kernel: [    1.214187] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 00:47:41 node-1 kernel: [    1.224723] usb usb2: Product: EHCI Host Controller
Nov 13 00:47:41 node-1 kernel: [    1.230170] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 00:47:41 node-1 kernel: [    1.235715] usb usb2: SerialNumber: 0000:00:1d.0
Nov 13 00:47:41 node-1 kernel: [    1.241221] hub 2-0:1.0: USB hub found
Nov 13 00:47:41 node-1 kernel: [    1.246569] hub 2-0:1.0: 2 ports detected
Nov 13 00:47:41 node-1 kernel: [    1.251871] ehci-platform: EHCI generic platform driver
Nov 13 00:47:41 node-1 kernel: [    1.257109] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 13 00:47:41 node-1 kernel: [    1.262423] ohci-pci: OHCI PCI platform driver
Nov 13 00:47:41 node-1 kernel: [    1.267738] ohci-platform: OHCI generic platform driver
Nov 13 00:47:41 node-1 kernel: [    1.272944] uhci_hcd: USB Universal Host Controller Interface driver
Nov 13 00:47:41 node-1 kernel: [    1.278307] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov 13 00:47:41 node-1 kernel: [    1.471504] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov 13 00:47:41 node-1 kernel: [    1.631664] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov 13 00:47:41 node-1 kernel: [    1.637275] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 00:47:41 node-1 kernel: [    1.643055] hub 1-1:1.0: USB hub found
Nov 13 00:47:41 node-1 kernel: [    1.648524] hub 1-1:1.0: 6 ports detected
Nov 13 00:47:41 node-1 kernel: [    1.763248] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov 13 00:47:41 node-1 kernel: [    2.031323] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov 13 00:47:41 node-1 kernel: [    2.036759] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 00:47:41 node-1 kernel: [    2.042466] hub 2-1:1.0: USB hub found
Nov 13 00:47:41 node-1 kernel: [    2.048060] hub 2-1:1.0: 8 ports detected
Nov 13 00:47:41 node-1 kernel: [    2.319428] i8042: No controller found
Nov 13 00:47:41 node-1 kernel: [    2.322845] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov 13 00:47:41 node-1 kernel: [    2.330203] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov 13 00:47:41 node-1 kernel: [    2.331452] mousedev: PS/2 mouse device common for all mice
Nov 13 00:47:41 node-1 kernel: [    2.333022] rtc_cmos 00:02: RTC can wake from S4
Nov 13 00:47:41 node-1 kernel: [    2.334511] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov 13 00:47:41 node-1 kernel: [    2.335135] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 13 00:47:41 node-1 kernel: [    2.336272] device-mapper: uevent: version 1.0.3
Nov 13 00:47:41 node-1 kernel: [    2.337264] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov 13 00:47:41 node-1 kernel: [    2.337457] ledtrig-cpu: registered to indicate activity on CPUs
Nov 13 00:47:41 node-1 kernel: [    2.339619] TCP: cubic registered
Nov 13 00:47:41 node-1 kernel: [    2.340620] NET: Registered protocol family 10
Nov 13 00:47:41 node-1 kernel: [    2.343629] NET: Registered protocol family 17
Nov 13 00:47:41 node-1 kernel: [    2.343789] Key type dns_resolver registered
Nov 13 00:47:41 node-1 kernel: [    2.350089] Loading compiled-in X.509 certificates
Nov 13 00:47:41 node-1 kernel: [    2.352186] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov 13 00:47:41 node-1 kernel: [    2.352482] registered taskstats version 1
Nov 13 00:47:41 node-1 kernel: [    2.391873] Key type trusted registered
Nov 13 00:47:41 node-1 kernel: [    2.412782] Key type encrypted registered
Nov 13 00:47:41 node-1 kernel: [    2.412820] AppArmor: AppArmor sha1 policy hashing enabled
Nov 13 00:47:41 node-1 kernel: [    2.412853] IMA: No TPM chip found, activating TPM-bypass!
Nov 13 00:47:41 node-1 kernel: [    2.421376] regulator-dummy: disabling
Nov 13 00:47:41 node-1 kernel: [    2.422145]   Magic number: 8:240:759
Nov 13 00:47:41 node-1 kernel: [    2.424623] acpi LNXCPU:80: hash matches
Nov 13 00:47:41 node-1 kernel: [    2.460663] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov 13 00:47:41 node-1 kernel: [    2.460665] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 00:47:41 node-1 kernel: [    2.460667] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov 13 00:47:41 node-1 kernel: [    2.460669] usb 2-1.4: Manufacturer: Avocent
Nov 13 00:47:41 node-1 kernel: [    2.460670] usb 2-1.4: SerialNumber: 20111102-00000001
Nov 13 00:47:41 node-1 kernel: [    2.501129] rtc_cmos 00:02: setting system clock to 2016-11-13 00:47:07 UTC (1478998027)
Nov 13 00:47:41 node-1 kernel: [    2.513521] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov 13 00:47:41 node-1 kernel: [    2.519179] EDD information not available.
Nov 13 00:47:41 node-1 kernel: [    2.524781] PM: Hibernation image not present or could not be loaded.
Nov 13 00:47:41 node-1 kernel: [    2.525650] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov 13 00:47:41 node-1 kernel: [    2.536900] Write protecting the kernel read-only data: 12288k
Nov 13 00:47:41 node-1 kernel: [    2.543025] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov 13 00:47:41 node-1 kernel: [    2.555337] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov 13 00:47:41 node-1 kernel: [    2.587685] device-mapper: multipath: version 1.6.0 loaded
Nov 13 00:47:41 node-1 kernel: [    2.595681] systemd-udevd[214]: starting version 204
Nov 13 00:47:41 node-1 kernel: [    2.619118] md: linear personality registered for level -1
Nov 13 00:47:41 node-1 kernel: [    2.633546] md: multipath personality registered for level -4
Nov 13 00:47:41 node-1 kernel: [    2.641550] md: raid0 personality registered for level 0
Nov 13 00:47:41 node-1 kernel: [    2.649892] md: raid1 personality registered for level 1
Nov 13 00:47:41 node-1 kernel: [    2.660267] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov 13 00:47:41 node-1 kernel: [    2.666618] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov 13 00:47:41 node-1 kernel: [    2.672932] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov 13 00:47:41 node-1 kernel: [    2.679450] megasas: FW now in Ready state
Nov 13 00:47:41 node-1 kernel: [    2.685954] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685961] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685967] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685973] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685979] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685984] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685989] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685995] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.685996] hidraw: raw HID events driver (C) Jiri Kosina
Nov 13 00:47:41 node-1 kernel: [    2.690810] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Nov 13 00:47:41 node-1 kernel: [    2.690832] 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 13 00:47:41 node-1 kernel: [    2.690839] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 00:47:41 node-1 kernel: [    2.691444] enic 0000:06:00.0: irq 104 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.691592] enic 0000:06:00.0: irq 105 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.691724] enic 0000:06:00.0: irq 106 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.691818] enic 0000:06:00.0: irq 107 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.692132] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.709686] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Nov 13 00:47:41 node-1 kernel: [    2.709694] 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 13 00:47:41 node-1 kernel: [    2.709695] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov 13 00:47:41 node-1 kernel: [    2.709932] enic 0000:07:00.0: irq 108 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.710096] enic 0000:07:00.0: irq 109 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.710199] enic 0000:07:00.0: irq 110 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.710382] enic 0000:07:00.0: irq 111 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.710595] enic 0000:07:00.0: irq 112 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.710696] enic 0000:07:00.0: irq 113 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.711000] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.722715] raid6: sse2x1     861 MB/s
Nov 13 00:47:41 node-1 kernel: [    2.730586] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Nov 13 00:47:41 node-1 kernel: [    2.730588] 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 13 00:47:41 node-1 kernel: [    2.730589] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 00:47:41 node-1 kernel: [    2.730802] enic 0000:08:00.0: irq 114 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.730926] enic 0000:08:00.0: irq 115 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.731037] enic 0000:08:00.0: irq 116 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.731173] enic 0000:08:00.0: irq 117 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.731415] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.747824] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Nov 13 00:47:41 node-1 kernel: [    2.747825] 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 13 00:47:41 node-1 kernel: [    2.747834] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 00:47:41 node-1 kernel: [    2.748084] enic 0000:09:00.0: irq 118 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.748154] enic 0000:09:00.0: irq 119 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.748269] enic 0000:09:00.0: irq 120 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.748377] enic 0000:09:00.0: irq 121 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.748640] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.790552] raid6: sse2x2     822 MB/s
Nov 13 00:47:41 node-1 kernel: [    2.858649] raid6: sse2x4    1106 MB/s
Nov 13 00:47:41 node-1 kernel: [    2.897730] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.897736] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.897742] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.897747] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.897753] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.897759] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.897765] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.897879] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Nov 13 00:47:41 node-1 kernel: [    2.898145] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov 13 00:47:41 node-1 kernel: [    2.913154] usbcore: registered new interface driver usbhid
Nov 13 00:47:41 node-1 kernel: [    2.919690] usbhid: USB HID core driver
Nov 13 00:47:41 node-1 kernel: [    2.926273] raid6: avx2x1    1967 MB/s
Nov 13 00:47:41 node-1 kernel: [    2.933844] 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 13 00:47:41 node-1 kernel: [    2.946964] 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 13 00:47:41 node-1 kernel: [    2.960127] 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 13 00:47:41 node-1 kernel: [    2.973475] 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 13 00:47:41 node-1 kernel: [    2.987319] 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 13 00:47:41 node-1 kernel: [    2.998403] raid6: avx2x2    1798 MB/s
Nov 13 00:47:41 node-1 kernel: [    3.008222] 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 13 00:47:41 node-1 kernel: [    3.066137] raid6: avx2x4   27411 MB/s
Nov 13 00:47:41 node-1 kernel: [    3.073179] raid6: using algorithm avx2x4 (27411 MB/s)
Nov 13 00:47:41 node-1 kernel: [    3.080171] raid6: using avx2x2 recovery algorithm
Nov 13 00:47:41 node-1 kernel: [    3.087854] xor: automatically using best checksumming function:
Nov 13 00:47:41 node-1 kernel: [    3.134078]    avx       : 35704.000 MB/sec
Nov 13 00:47:41 node-1 kernel: [    3.141509] async_tx: api initialized (async)
Nov 13 00:47:41 node-1 kernel: [    3.152297] md: raid6 personality registered for level 6
Nov 13 00:47:41 node-1 kernel: [    3.158829] md: raid5 personality registered for level 5
Nov 13 00:47:41 node-1 kernel: [    3.165332] md: raid4 personality registered for level 4
Nov 13 00:47:41 node-1 kernel: [    3.174821] md: raid10 personality registered for level 10
Nov 13 00:47:41 node-1 kernel: [    3.228503] multipathd (354): /proc/354/oom_adj is deprecated, please use /proc/354/oom_score_adj instead.
Nov 13 00:47:41 node-1 kernel: [    3.238644] megasas:IOC Init cmd success
Nov 13 00:47:41 node-1 kernel: [    3.285981] megasas: INIT adapter done
Nov 13 00:47:41 node-1 kernel: [    3.361909] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov 13 00:47:41 node-1 kernel: [    3.368261] scsi0 : LSI SAS based MegaRAID driver
Nov 13 00:47:41 node-1 kernel: [    3.375357] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 00:47:41 node-1 kernel: [    3.393452] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 00:47:41 node-1 kernel: [    3.407818] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov 13 00:47:41 node-1 kernel: [    3.413840] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov 13 00:47:41 node-1 kernel: [    3.425664] sd 0:2:0:0: [sda] Write Protect is off
Nov 13 00:47:41 node-1 kernel: [    3.431426] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov 13 00:47:41 node-1 kernel: [    3.431451] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov 13 00:47:41 node-1 kernel: [    3.470479]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov 13 00:47:41 node-1 kernel: [    3.476956] sd 0:2:0:0: [sda] Attached SCSI disk
Nov 13 00:47:41 node-1 kernel: [    3.497911] Switched to clocksource tsc
Nov 13 00:47:41 node-1 kernel: [    3.586893] random: lvm urandom read with 25 bits of entropy available
Nov 13 00:47:41 node-1 kernel: [    3.751366] bio: create slab <bio-1> at 1
Nov 13 00:47:41 node-1 kernel: [    4.565560] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 00:47:41 node-1 kernel: [    5.094347] init: plymouth-upstart-bridge main process (553) terminated with status 1
Nov 13 00:47:41 node-1 kernel: [    5.106799] init: plymouth-upstart-bridge main process ended, respawning
Nov 13 00:47:41 node-1 kernel: [    5.215580] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov 13 00:47:41 node-1 kernel: [    5.260001] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov 13 00:47:41 node-1 kernel: [    5.386469] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov 13 00:47:41 node-1 kernel: [    5.446319] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov 13 00:47:41 node-1 kernel: [    5.539589] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 00:47:41 node-1 kernel: [    5.669624] random: nonblocking pool is initialized
Nov 13 00:47:41 node-1 kernel: [    5.697510] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov 13 00:47:41 node-1 kernel: [    5.734292] XFS (dm-0): Mounting Filesystem
Nov 13 00:47:41 node-1 kernel: [    6.088713] XFS (dm-0): Ending clean mount
Nov 13 00:47:41 node-1 kernel: [    6.144460] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 00:47:41 node-1 kernel: [    6.171082] XFS (dm-1): Mounting Filesystem
Nov 13 00:47:41 node-1 kernel: [    6.272268] XFS (dm-1): Ending clean mount
Nov 13 00:47:41 node-1 kernel: [    8.110052] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov 13 00:47:41 node-1 kernel: [    8.135711] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov 13 00:47:41 node-1 kernel: [    8.340938] systemd-udevd[777]: starting version 204
Nov 13 00:47:41 node-1 kernel: [    8.534748] power_meter ACPI000D:00: Found ACPI power meter.
Nov 13 00:47:41 node-1 kernel: [    8.534783] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov 13 00:47:41 node-1 kernel: [    8.541719] IPMI System Interface driver.
Nov 13 00:47:41 node-1 kernel: [    8.541808] ipmi_si: probing via ACPI
Nov 13 00:47:41 node-1 kernel: [    8.541826] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov 13 00:47:41 node-1 kernel: [    8.541827] ipmi_si: Adding ACPI-specified kcs state machine
Nov 13 00:47:41 node-1 kernel: [    8.541856] ipmi_si: probing via SMBIOS
Nov 13 00:47:41 node-1 kernel: [    8.541857] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 00:47:41 node-1 kernel: [    8.541858] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov 13 00:47:41 node-1 kernel: [    8.541860] ipmi_si: probing via SPMI
Nov 13 00:47:41 node-1 kernel: [    8.541861] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 00:47:41 node-1 kernel: [    8.541861] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov 13 00:47:41 node-1 kernel: [    8.541862] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov 13 00:47:41 node-1 kernel: [    8.577131] wmi: Mapper loaded
Nov 13 00:47:41 node-1 kernel: [    8.605573] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov 13 00:47:41 node-1 kernel: [    8.615551] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov 13 00:47:41 node-1 kernel: [    8.615557] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 00:47:41 node-1 kernel: [    8.615560] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov 13 00:47:41 node-1 kernel: [    8.615562] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 00:47:41 node-1 kernel: [    8.615574] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 13 00:47:41 node-1 kernel: [    8.673915] systemd-udevd[795]: renamed network interface eth0 to enp6s0
Nov 13 00:47:41 node-1 kernel: [    8.677675] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov 13 00:47:41 node-1 kernel: [    8.677680] ipmi_si 00:09: IPMI kcs interface initialized
Nov 13 00:47:41 node-1 kernel: [    8.693726] systemd-udevd[797]: renamed network interface eth2 to enp8s0
Nov 13 00:47:41 node-1 kernel: [    8.701705] systemd-udevd[796]: renamed network interface eth1 to enp7s0
Nov 13 00:47:41 node-1 kernel: [    8.725752] systemd-udevd[817]: renamed network interface eth3 to enp9s0
Nov 13 00:47:41 node-1 kernel: [    9.066933] type=1400 audit(1478998034.142:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1004 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.067092] type=1400 audit(1478998034.142:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1004 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.067224] type=1400 audit(1478998034.142:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1004 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.077977] type=1400 audit(1478998034.154:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1009 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.078122] type=1400 audit(1478998034.154:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1009 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.078243] type=1400 audit(1478998034.154:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1009 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.082864] type=1400 audit(1478998034.158:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=996 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.083009] type=1400 audit(1478998034.158:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=996 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.083130] type=1400 audit(1478998034.158:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=996 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.091011] type=1400 audit(1478998034.166:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1007 comm="apparmor_parser"
Nov 13 00:47:41 node-1 kernel: [    9.642863] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov 13 00:47:41 node-1 kernel: [    9.644038] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov 13 00:47:41 node-1 kernel: [    9.821473] enic 0000:06:00.0 enp6s0: Link UP
Nov 13 00:47:41 node-1 kernel: [    9.821996] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov 13 00:47:41 node-1 kernel: [    9.822005] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov 13 00:47:41 node-1 kernel: [   18.906501] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov 13 00:47:42 node-1 failsafe: Failsafe of 120 seconds reached.
Nov 13 00:47:42 node-1 kernel: [   37.151681] init: failsafe main process (8418) killed by TERM signal
Nov 13 00:47:42 node-1 dbus[8450]: [system] AppArmor D-Bus mediation is enabled
Nov 13 00:47:43 node-1 kernel: [   37.524556] audit_printk_skb: 30 callbacks suppressed
Nov 13 00:47:43 node-1 kernel: [   37.524558] type=1400 audit(1478998063.011:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8543 comm="apparmor_parser"
Nov 13 00:47:43 node-1 kernel: [   37.524562] type=1400 audit(1478998063.011:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Nov 13 00:47:43 node-1 kernel: [   37.524565] type=1400 audit(1478998063.011:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov 13 00:47:43 node-1 kernel: [   37.524797] type=1400 audit(1478998063.011:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Nov 13 00:47:43 node-1 kernel: [   37.524799] type=1400 audit(1478998063.011:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov 13 00:47:43 node-1 kernel: [   37.524924] type=1400 audit(1478998063.011:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov 13 00:47:43 node-1 kernel: [   37.525555] type=1400 audit(1478998063.011:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8544 comm="apparmor_parser"
Nov 13 00:47:43 node-1 kernel: [   37.607548] type=1400 audit(1478998063.091:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8546 comm="apparmor_parser"
Nov 13 00:47:43 node-1 anacron[8611]: Anacron 2.3 started on 2016-11-13
Nov 13 00:47:43 node-1 cron[8577]: (CRON) INFO (pidfile fd = 3)
Nov 13 00:47:43 node-1 anacron[8611]: Will run job `cron.daily' in 5 min.
Nov 13 00:47:43 node-1 anacron[8611]: Will run job `cron.weekly' in 10 min.
Nov 13 00:47:43 node-1 anacron[8611]: Will run job `cron.monthly' in 15 min.
Nov 13 00:47:43 node-1 anacron[8611]: Jobs will be executed sequentially
Nov 13 00:47:43 node-1 cron[8627]: (CRON) STARTUP (fork ok)
Nov 13 00:47:43 node-1 multipathd: path checkers start up
Nov 13 00:47:43 node-1 cron[8627]: (CRON) INFO (Running @reboot jobs)
Nov 13 00:47:43 node-1 postfix/master[8755]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov 13 00:47:46 node-1 puppet-agent[8940]: Reopening log files
Nov 13 00:47:47 node-1 puppet-agent[8940]: Could not request certificate: Connection refused - connect(2)
Nov 13 00:48:01 node-1 CRON[9100]: (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 13 00:48:03 node-1 puppet-user[9159]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov 13 00:48:03 node-1 puppet-user[9159]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov 13 00:48:05 node-1 puppet-user[9159]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov 13 00:48:05 node-1 puppet-user[9159]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov 13 00:48:05 node-1 puppet-user[9159]: Finished catalog run in 1.98 seconds
Nov 13 00:48:07 node-1 multipathd: uevent trigger error
Nov 13 00:48:07 node-1 puppet-user[9804]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 00:48:07 node-1 puppet-user[9804]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Nov 13 00:48:07 node-1 puppet-user[9804]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov 13 00:48:07 node-1 puppet-user[9804]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov 13 00:48:07 node-1 puppet-user[9804]: (/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 13 00:48:07 node-1 puppet-user[9804]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov 13 00:48:07 node-1 puppet-user[9804]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov 13 00:48:07 node-1 puppet-user[9804]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov 13 00:48:07 node-1 puppet-user[9804]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov 13 00:48:07 node-1 puppet-user[9804]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov 13 00:48:07 node-1 puppet-user[9804]: Finished catalog run in 0.07 seconds
Nov 13 00:48:08 node-1 puppet-user[10265]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov 13 00:48:08 node-1 puppet-user[10265]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov 13 00:48:08 node-1 puppet-user[10265]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov 13 00:48:08 node-1 puppet-user[10265]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov 13 00:48:08 node-1 puppet-user[10265]: Finished catalog run in 0.05 seconds
Nov 13 00:48:10 node-1 puppet-user[10737]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov 13 00:48:10 node-1 puppet-user[10737]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov 13 00:48:10 node-1 puppet-user[10737]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov 13 00:48:11 node-1 puppet-user[10737]: Finished catalog run in 0.04 seconds
Nov 13 00:48:12 node-1 puppet-user[11193]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov 13 00:48:12 node-1 puppet-user[11193]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Nov 13 00:48:12 node-1 puppet-user[11193]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov 13 00:48:12 node-1 puppet-user[11193]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Nov 13 00:48:12 node-1 puppet-user[11193]: Finished catalog run in 0.46 seconds
Nov 13 00:48:14 node-1 puppet-user[11671]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov 13 00:48:14 node-1 puppet-user[11671]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Nov 13 00:48:14 node-1 puppet-user[11671]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov 13 00:48:14 node-1 puppet-user[11671]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov 13 00:48:14 node-1 puppet-user[11671]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Nov 13 00:48:14 node-1 puppet-user[11671]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov 13 00:48:14 node-1 puppet-user[11671]: Finished catalog run in 0.24 seconds
Nov 13 00:48:16 node-1 puppet-user[12153]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov 13 00:48:16 node-1 puppet-user[12153]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Nov 13 00:48:16 node-1 puppet-user[12153]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov 13 00:48:16 node-1 kernel: [   70.891133] nr_pdflush_threads exported in /proc is scheduled for removal
Nov 13 00:48:16 node-1 kernel: [   70.891181] 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 13 00:48:16 node-1 puppet-user[12153]: (/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 13 00:48:16 node-1 puppet-user[12153]: Finished catalog run in 0.06 seconds
Nov 13 00:48:17 node-1 kernel: [   71.579282] init: plymouth-upstart-bridge main process ended, respawning
Nov 13 00:48:17 node-1 puppet-agent[8940]: Could not run: SIGTERM
Nov 13 00:48:17 node-1 kernel: [   71.813803] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 13 00:48:17 node-1 ec2: 
Nov 13 00:48:17 node-1 ec2: #############################################################
Nov 13 00:48:17 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov 13 00:48:17 node-1 ec2: 1024 b5:ad:0e:ac:20:a6:12:61:f8:61:54:b2:a1:36:21:45  root@node-1.domain.tld (DSA)
Nov 13 00:48:17 node-1 ec2: 256 c3:22:d4:f4:7d:bf:db:02:df:84:18:e7:fa:68:27:18  root@node-1.domain.tld (ECDSA)
Nov 13 00:48:17 node-1 ec2: 256 8d:4b:fc:42:42:63:1d:bf:3f:4c:a8:33:46:2f:75:c6  root@node-1.domain.tld (ED25519)
Nov 13 00:48:17 node-1 ec2: 2048 79:a7:42:b0:76:5b:4f:af:4e:a2:60:bd:db:9e:7e:1b  root@node-1.domain.tld (RSA)
Nov 13 00:48:17 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov 13 00:48:17 node-1 ec2: #############################################################
Nov 13 00:48:18 node-1 puppet-user[12783]: (Scope(Class[main])) MODULAR: sync_time
Nov 13 00:48:18 node-1 puppet-user[12783]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov 13 00:48:18 node-1 ntpdate[13209]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov 13 00:48:24 node-1 ntpdate[13209]: adjust time server 10.20.0.2 offset -0.200716 sec
Nov 13 00:48:24 node-1 puppet-user[12783]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov 13 00:48:24 node-1 puppet-user[12783]: Finished catalog run in 6.19 seconds
Nov 13 00:48:28 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 00:48:28 node-1 nailgun-agent: D, [2016-11-13T00:48:01.517725 #9103] DEBUG -- : Sleep for 27 seconds before sending request
Nov 13 00:48:28 node-1 nailgun-agent: I, [2016-11-13T00:48:28.535738 #9103]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov 13 00:48:29 node-1 nailgun-agent: D, [2016-11-13T00:48:29.035569 #9103] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Nov 13 00:48:30 node-1 puppet-user[13545]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 00:48:30 node-1 puppet-user[13545]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov 13 00:48:30 node-1 puppet-user[13545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov 13 00:48:30 node-1 puppet-user[13545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Nov 13 00:48:30 node-1 puppet-user[13545]: Finished catalog run in 0.06 seconds
Nov 13 00:48:31 node-1 puppet-user[14002]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov 13 00:48:32 node-1 puppet-user[14002]: Compiled catalog for node-1.domain.tld in environment production in 0.45 seconds
Nov 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:32 node-1 puppet-user[14002]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:32 node-1 puppet-user[14002]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:32 node-1 puppet-user[14002]: (/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 13 00:48:33 node-1 puppet-user[14002]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov 13 00:48:33 node-1 puppet-user[14002]: Finished catalog run in 0.85 seconds
Nov 13 00:48:34 node-1 puppet-user[14523]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov 13 00:48:34 node-1 puppet-user[14523]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Nov 13 00:48:37 node-1 puppet-user[14523]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.043704 #9103] DEBUG -- : Trying to find block devices
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.043768 #9103] DEBUG -- : Found block device: sda
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.043896 #9103] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.043925 #9103] DEBUG -- : Trying to get list of physical devices
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.044079 #9103] DEBUG -- : Getting udev properties for device: sda
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.046326 #9103] 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"=>"0x618e72837273a7701cc7886
Nov 13 00:48:41 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31012", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.046383 #9103] DEBUG -- : Trying to find out if device sda is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.046423 #9103] DEBUG -- : Device sda removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.046437 #9103] DEBUG -- : Device sda seems to be appropriate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.046877 #9103] DEBUG -- : Getting udev properties for device: dm-0
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.048955 #9103] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-jLvflSe2whQ3zOhpYasSDycsKbyaYKzXDz3PN34coHb12KzpI3uuWnoao7qiaCog /dev/disk/by-uuid/d96e081c-f418-4345-af5a-5dd40816d50d /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-jLvflSe2whQ3zOhpYasSDycsKbyaYKzXDz3PN34coHb12KzpI3uuWnoao7qiaCog", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d96e081c-f418-4345-af5a-5dd40816d50d", "ID_FS_UUID_ENC"=>"d96e081c-f418-4345-af5a-5dd40816d50d", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5686", "nomdmonddf"=>"1", "nomdm
Nov 13 00:48:41 node-1 nailgun-agent: onisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.048979 #9103] DEBUG -- : Trying to find out if device dm-0 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.049030 #9103] DEBUG -- : Device dm-0 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.049054 #9103] DEBUG -- : Device dm-0 seems to be appropriate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.049070 #9103] DEBUG -- : Getting udev properties for device: dm-1
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.051172 #9103] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-5XK2U9nxGo8WqzgqRuQ7MnDwDNds33rnQiy3G2BhH68R3fWqTXvXJ09oqUdI24f1 /dev/disk/by-uuid/3aff557d-bbc9-4c63-901b-a2a4286392c1 /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-5XK2U9nxGo8WqzgqRuQ7MnDwDNds33rnQiy3G2BhH68R3fWqTXvXJ09oqUdI24f1", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3aff557d-bbc9-4c63-901b-a2a4286392c1", "ID_FS_UUID_ENC"=>"3aff557d-bbc9-4c63-901b-a2a4286392c1", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35
Nov 13 00:48:41 node-1 nailgun-agent: 654", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.051195 #9103] DEBUG -- : Trying to find out if device dm-1 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.051222 #9103] DEBUG -- : Device dm-1 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.051236 #9103] DEBUG -- : Device dm-1 seems to be appropriate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.051250 #9103] DEBUG -- : Getting udev properties for device: dm-2
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.053085 #9103] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-21sF9zcTpNZVSBF80CuUQuq4BGj39kyf20RK1EV6DcMJflRZIXOXou8QsOI2Et8d /dev/disk/by-uuid/40d12ebd-7ae2-4470-9ef6-4025f456544d /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-21sF9zcTpNZVSBF80CuUQuq4BGj39kyf20RK1EV6DcMJflRZIXOXou8QsOI2Et8d", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"40d12ebd-7ae2-4470-9ef6-4025f456544d", "ID_FS_UUID_ENC"=>"40d12ebd-7ae2-4470-9ef6-4025f456544d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78055", "nomdmond
Nov 13 00:48:41 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.053107 #9103] DEBUG -- : Trying to find out if device dm-2 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.053165 #9103] DEBUG -- : Device dm-2 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.053177 #9103] DEBUG -- : Device dm-2 seems to be appropriate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.053191 #9103] DEBUG -- : Getting udev properties for device: dm-3
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.055126 #9103] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-bg5jVR26TKVhyJir8fE8gHJpASogZibnd2mBsFg9vHEauAuAPWh7Spq2ccrXk6QY /dev/disk/by-uuid/2522e68b-7ad6-48c0-8194-d438c3cd8f92 /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-bg5jVR26TKVhyJir8fE8gHJpASogZibnd2mBsFg9vHEauAuAPWh7Spq2ccrXk6QY", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2522e68b-7ad6-48c0-8194-d438c3cd8f92", "ID_FS_UUID_ENC"=>"2522e68b-7ad6-48c0-8194-d438c3cd8f92", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81935", "nomdmonddf"=>"1", 
Nov 13 00:48:41 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.055151 #9103] DEBUG -- : Trying to find out if device dm-3 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.055210 #9103] DEBUG -- : Device dm-3 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.055222 #9103] DEBUG -- : Device dm-3 seems to be appropriate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.055236 #9103] DEBUG -- : Getting udev properties for device: dm-4
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.057341 #9103] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-QdgYyABTVuIohpqFc8QrO2UAN2fIyhg8wU4kEPyvO9ic9NrtFJbjgsqkb6FVI0U5 /dev/disk/by-uuid/ad9eaf35-e4dd-48ed-90a6-9dacec29419a /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-QdgYyABTVuIohpqFc8QrO2UAN2fIyhg8wU4kEPyvO9ic9NrtFJbjgsqkb6FVI0U5", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ad9eaf35-e4dd-48ed-90a6-9dacec29419a", "ID_FS_UUID_ENC"=>"ad9eaf35-e4dd-48ed-90a6-9dacec29419a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87989", "nomdmonddf"=>"1", "nomd
Nov 13 00:48:41 node-1 nailgun-agent: monisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.057364 #9103] DEBUG -- : Trying to find out if device dm-4 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.057390 #9103] DEBUG -- : Device dm-4 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.057414 #9103] DEBUG -- : Device dm-4 seems to be appropriate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.057428 #9103] DEBUG -- : Getting udev properties for device: dm-5
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.059065 #9103] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-QdgYyABTVuIohpqFc8QrO2UAN2fIyhg8W4Ql21sSIcHyslthh6N0aR3xCZYUPwqP /dev/disk/by-uuid/c298f40a-a76f-491d-9f37-ed56b956ae97 /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-QdgYyABTVuIohpqFc8QrO2UAN2fIyhg8W4Ql21sSIcHyslthh6N0aR3xCZYUPwqP", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"c298f40a-a76f-491d-9f37-ed56b956ae97", "ID_FS_UUID_ENC"=>"c298f40a-a76f-491d-9f37-ed56b956ae97", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88473", "nomdmonddf"=>"1", "nomdmonisw"
Nov 13 00:48:41 node-1 nailgun-agent: =>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.059087 #9103] DEBUG -- : Trying to find out if device dm-5 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.059116 #9103] DEBUG -- : Device dm-5 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.059158 #9103] DEBUG -- : Device dm-5 seems to be appropriate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.059189 #9103] DEBUG -- : Getting udev properties for device: ram0
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.060739 #9103] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13430", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.060761 #9103] DEBUG -- : Trying to find out if device ram0 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.060813 #9103] DEBUG -- : Device ram0 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.060830 #9103] DEBUG -- : Getting udev properties for device: ram1
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.062282 #9103] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13603", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.062303 #9103] DEBUG -- : Trying to find out if device ram1 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.062333 #9103] DEBUG -- : Device ram1 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.062349 #9103] DEBUG -- : Getting udev properties for device: ram2
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.063989 #9103] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14358", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.064009 #9103] DEBUG -- : Trying to find out if device ram2 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.064042 #9103] DEBUG -- : Device ram2 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.064078 #9103] DEBUG -- : Getting udev properties for device: ram3
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.065693 #9103] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14417", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.065713 #9103] DEBUG -- : Trying to find out if device ram3 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.065743 #9103] DEBUG -- : Device ram3 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.065775 #9103] DEBUG -- : Getting udev properties for device: ram4
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.067309 #9103] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14493", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.067340 #9103] DEBUG -- : Trying to find out if device ram4 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.067368 #9103] DEBUG -- : Device ram4 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.067398 #9103] DEBUG -- : Getting udev properties for device: ram5
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.068832 #9103] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14562", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.068886 #9103] DEBUG -- : Trying to find out if device ram5 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.068920 #9103] DEBUG -- : Device ram5 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.068937 #9103] DEBUG -- : Getting udev properties for device: ram6
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.070383 #9103] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14652", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.070403 #9103] DEBUG -- : Trying to find out if device ram6 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.070431 #9103] DEBUG -- : Device ram6 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.070448 #9103] DEBUG -- : Getting udev properties for device: ram7
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.072452 #9103] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14833", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.072516 #9103] DEBUG -- : Trying to find out if device ram7 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.072559 #9103] DEBUG -- : Device ram7 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.072585 #9103] DEBUG -- : Getting udev properties for device: ram8
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.074302 #9103] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14927", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.074366 #9103] DEBUG -- : Trying to find out if device ram8 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.074406 #9103] DEBUG -- : Device ram8 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.074429 #9103] DEBUG -- : Getting udev properties for device: ram9
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.076121 #9103] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15007", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.076165 #9103] DEBUG -- : Trying to find out if device ram9 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.076221 #9103] DEBUG -- : Device ram9 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.076244 #9103] DEBUG -- : Getting udev properties for device: loop0
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.078093 #9103] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12725", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.078129 #9103] DEBUG -- : Trying to find out if device loop0 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.078190 #9103] DEBUG -- : Device loop0 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.078230 #9103] DEBUG -- : Getting udev properties for device: loop1
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.080034 #9103] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12822", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.080078 #9103] DEBUG -- : Trying to find out if device loop1 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.080114 #9103] DEBUG -- : Device loop1 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.080136 #9103] DEBUG -- : Getting udev properties for device: loop2
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.082195 #9103] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12902", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.082224 #9103] DEBUG -- : Trying to find out if device loop2 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.082283 #9103] DEBUG -- : Device loop2 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.082304 #9103] DEBUG -- : Getting udev properties for device: loop3
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.083909 #9103] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12999", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.083937 #9103] DEBUG -- : Trying to find out if device loop3 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.083985 #9103] DEBUG -- : Device loop3 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.084007 #9103] DEBUG -- : Getting udev properties for device: loop4
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.085602 #9103] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13073", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.085630 #9103] DEBUG -- : Trying to find out if device loop4 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.085668 #9103] DEBUG -- : Device loop4 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.085704 #9103] DEBUG -- : Getting udev properties for device: loop5
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.087299 #9103] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13137", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.087327 #9103] DEBUG -- : Trying to find out if device loop5 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.087374 #9103] DEBUG -- : Device loop5 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.087404 #9103] DEBUG -- : Getting udev properties for device: loop6
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.088967 #9103] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13228", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.088995 #9103] DEBUG -- : Trying to find out if device loop6 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.089030 #9103] DEBUG -- : Device loop6 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.089088 #9103] DEBUG -- : Getting udev properties for device: loop7
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.090693 #9103] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13327", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.090742 #9103] DEBUG -- : Trying to find out if device loop7 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.090777 #9103] DEBUG -- : Device loop7 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.090818 #9103] DEBUG -- : Getting udev properties for device: ram10
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.092422 #9103] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13703", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.092471 #9103] DEBUG -- : Trying to find out if device ram10 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.092506 #9103] DEBUG -- : Device ram10 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.092527 #9103] DEBUG -- : Getting udev properties for device: ram11
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.094058 #9103] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13817", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.094086 #9103] DEBUG -- : Trying to find out if device ram11 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.094122 #9103] DEBUG -- : Device ram11 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.094163 #9103] DEBUG -- : Getting udev properties for device: ram12
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.095688 #9103] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13903", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.095715 #9103] DEBUG -- : Trying to find out if device ram12 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.101526 #9103] DEBUG -- : Device ram12 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.101558 #9103] DEBUG -- : Getting udev properties for device: ram13
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.103690 #9103] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13961", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.103720 #9103] DEBUG -- : Trying to find out if device ram13 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.103755 #9103] DEBUG -- : Device ram13 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.103776 #9103] DEBUG -- : Getting udev properties for device: ram14
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.105280 #9103] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14075", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.105308 #9103] DEBUG -- : Trying to find out if device ram14 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.105341 #9103] DEBUG -- : Device ram14 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.105362 #9103] DEBUG -- : Getting udev properties for device: ram15
Nov 13 00:48:41 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.106956 #9103] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14250", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.106983 #9103] DEBUG -- : Trying to find out if device ram15 is removable or not
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107026 #9103] DEBUG -- : Device ram15 removable parameter: "0"
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107064 #9103] 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 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107079 #9103] DEBUG -- : Block device seems to be physical data storage: sda
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107173 #9103] DEBUG -- : Found block device: dm-0
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107188 #9103] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107201 #9103] DEBUG -- : Found block device: dm-1
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107212 #9103] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107221 #9103] DEBUG -- : Found block device: dm-2
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107230 #9103] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107238 #9103] DEBUG -- : Found block device: dm-3
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107248 #9103] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107313 #9103] DEBUG -- : Found block device: dm-4
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107324 #9103] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107333 #9103] DEBUG -- : Found block device: dm-5
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107344 #9103] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107353 #9103] DEBUG -- : Found block device: ram0
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107363 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107371 #9103] DEBUG -- : Found block device: ram1
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107381 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107436 #9103] DEBUG -- : Found block device: ram2
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107448 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107456 #9103] DEBUG -- : Found block device: ram3
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107465 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107474 #9103] DEBUG -- : Found block device: ram4
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107489 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107499 #9103] DEBUG -- : Found block device: ram5
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107509 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107518 #9103] DEBUG -- : Found block device: ram6
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107571 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107582 #9103] DEBUG -- : Found block device: ram7
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107593 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107602 #9103] DEBUG -- : Found block device: ram8
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107611 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107619 #9103] DEBUG -- : Found block device: ram9
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107627 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107635 #9103] DEBUG -- : Found block device: loop0
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107697 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107708 #9103] DEBUG -- : Found block device: loop1
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107718 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107726 #9103] DEBUG -- : Found block device: loop2
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107734 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107742 #9103] DEBUG -- : Found block device: loop3
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107752 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107762 #9103] DEBUG -- : Found block device: loop4
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107770 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107813 #9103] DEBUG -- : Found block device: loop5
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107824 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107833 #9103] DEBUG -- : Found block device: loop6
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107841 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107849 #9103] DEBUG -- : Found block device: loop7
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107858 #9103] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107866 #9103] DEBUG -- : Found block device: ram10
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107876 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107884 #9103] DEBUG -- : Found block device: ram11
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107923 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107932 #9103] DEBUG -- : Found block device: ram12
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107942 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107950 #9103] DEBUG -- : Found block device: ram13
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107959 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107968 #9103] DEBUG -- : Found block device: ram14
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107978 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107987 #9103] DEBUG -- : Found block device: ram15
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.107996 #9103] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.108052 #9103] 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 13 00:48:41 node-1 nailgun-agent: D, [2016-11-13T00:48:41.269656 #9103] DEBUG -- : Response: status: 200 body: {"id": 1}
Nov 13 00:48:41 node-1 nailgun-agent: I, [2016-11-13T00:48:41.269859 #9103]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Nov 13 00:49:01 node-1 CRON[17296]: (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 13 00:49:05 node-1 puppet-user[14523]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov 13 00:49:05 node-1 puppet-user[14523]: Finished catalog run in 30.48 seconds
Nov 13 00:49:07 node-1 puppet-user[17537]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov 13 00:49:07 node-1 puppet-user[17537]: Compiled catalog for node-1.domain.tld in environment production in 0.60 seconds
Nov 13 00:49:07 node-1 puppet-user[17537]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov 13 00:49:07 node-1 puppet-user[17537]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov 13 00:49:07 node-1 puppet-user[17537]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov 13 00:49:07 node-1 puppet-user[17537]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov 13 00:49:07 node-1 puppet-user[17537]: Finished catalog run in 0.08 seconds
Nov 13 00:49:09 node-1 puppet-user[18004]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov 13 00:49:10 node-1 puppet-user[18004]: Compiled catalog for node-1.domain.tld in environment production in 0.82 seconds
Nov 13 00:49:10 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov 13 00:49:10 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov 13 00:49:10 node-1 crontab[18444]: (root) LIST (root)
Nov 13 00:49:10 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov 13 00:49:10 node-1 crontab[18445]: (root) REPLACE (root)
Nov 13 00:49:12 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov 13 00:49:12 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov 13 00:49:13 node-1 puppet-user[18004]: (/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 13 00:49:14 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 00:49:14 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov 13 00:49:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:30 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:30 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:30 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:30 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:30 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:32 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:32 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:32 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:33 node-1 multipathd: uevent trigger error
<27>Nov 13 00:49:33 node-1 multipathd: uevent trigger error
<27>Nov 13 00:50:27 node-1 ntpdate[30474]: no servers can be used, exiting
<27>Nov 13 00:50:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:50:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:50:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:50:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:50:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:50:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:16 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:16 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:16 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:16 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:16 node-1 multipathd: uevent trigger error
<27>Nov 13 00:51:16 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:11 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:11 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:11 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:11 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:11 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:11 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:20 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:20 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:20 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:20 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:20 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:22 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 00:52:22 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 00:52:28 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 00:52:28 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 00:52:34 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 00:52:39 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 00:52:39 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 00:52:46 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:46 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:46 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:47 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:47 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:47 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:52:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:09 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:09 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:09 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:09 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:09 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:09 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:15 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:15 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:17 node-1 haproxy[21843]: 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 13 00:53:18 node-1 haproxy[21847]: 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 13 00:53:18 node-1 haproxy[21847]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:18 node-1 haproxy[21847]: proxy mysqld has no server available!
<27>Nov 13 00:53:21 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:21 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:21 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:21 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:21 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:21 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:24 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:26 node-1 haproxy[24541]: 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 13 00:53:27 node-1 haproxy[24545]: 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 13 00:53:27 node-1 haproxy[24545]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:27 node-1 haproxy[24545]: proxy mysqld has no server available!
<129>Nov 13 00:53:27 node-1 haproxy[24545]: 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 13 00:53:27 node-1 haproxy[24545]: 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 13 00:53:28 node-1 haproxy[24545]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:28 node-1 haproxy[24545]: proxy object-storage has no server available!
<27>Nov 13 00:53:29 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:29 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:29 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:29 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:29 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:29 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:31 node-1 haproxy[26131]: 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 13 00:53:32 node-1 haproxy[26135]: 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 13 00:53:32 node-1 haproxy[26135]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:32 node-1 haproxy[26135]: proxy neutron has no server available!
<129>Nov 13 00:53:32 node-1 haproxy[26135]: 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 13 00:53:32 node-1 haproxy[26135]: 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 13 00:53:32 node-1 haproxy[26135]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:32 node-1 haproxy[26135]: proxy mysqld has no server available!
<129>Nov 13 00:53:33 node-1 haproxy[26135]: 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 13 00:53:33 node-1 haproxy[26135]: 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 13 00:53:33 node-1 haproxy[26135]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:33 node-1 haproxy[26135]: proxy object-storage has no server available!
<27>Nov 13 00:53:35 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:35 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:35 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:35 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:35 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:37 node-1 haproxy[27533]: 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 13 00:53:37 node-1 haproxy[27533]: 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 13 00:53:37 node-1 haproxy[27533]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:37 node-1 haproxy[27533]: proxy keystone-1 has no server available!
<129>Nov 13 00:53:37 node-1 haproxy[27533]: 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 13 00:53:38 node-1 haproxy[27537]: 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 13 00:53:38 node-1 haproxy[27537]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:38 node-1 haproxy[27537]: proxy keystone-2 has no server available!
<129>Nov 13 00:53:38 node-1 haproxy[27537]: 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 13 00:53:38 node-1 haproxy[27537]: 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 13 00:53:38 node-1 haproxy[27537]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:38 node-1 haproxy[27537]: proxy neutron has no server available!
<129>Nov 13 00:53:38 node-1 haproxy[27537]: 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 13 00:53:38 node-1 haproxy[27537]: 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 13 00:53:38 node-1 haproxy[27537]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:38 node-1 haproxy[27537]: proxy mysqld has no server available!
<129>Nov 13 00:53:39 node-1 haproxy[27537]: 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 13 00:53:39 node-1 haproxy[27537]: 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 13 00:53:39 node-1 haproxy[27537]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:39 node-1 haproxy[27537]: proxy object-storage has no server available!
<27>Nov 13 00:53:40 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:40 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:40 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:40 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:42 node-1 haproxy[28872]: 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 13 00:53:42 node-1 haproxy[28872]: 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 13 00:53:43 node-1 haproxy[28876]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:43 node-1 haproxy[28876]: proxy keystone-1 has no server available!
<129>Nov 13 00:53:43 node-1 haproxy[28876]: 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 13 00:53:43 node-1 haproxy[28876]: 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 13 00:53:43 node-1 haproxy[28876]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:43 node-1 haproxy[28876]: proxy keystone-2 has no server available!
<129>Nov 13 00:53:43 node-1 haproxy[28876]: 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 13 00:53:43 node-1 haproxy[28876]: 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 13 00:53:43 node-1 haproxy[28876]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:43 node-1 haproxy[28876]: proxy neutron has no server available!
<129>Nov 13 00:53:43 node-1 haproxy[28876]: 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 13 00:53:43 node-1 haproxy[28876]: 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 13 00:53:43 node-1 haproxy[28876]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:43 node-1 haproxy[28876]: proxy mysqld has no server available!
<129>Nov 13 00:53:44 node-1 haproxy[28876]: 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 13 00:53:44 node-1 haproxy[28876]: 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 13 00:53:44 node-1 haproxy[28876]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:44 node-1 haproxy[28876]: proxy object-storage has no server available!
<129>Nov 13 00:53:44 node-1 haproxy[28876]: 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 13 00:53:44 node-1 haproxy[28876]: 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 13 00:53:44 node-1 haproxy[28876]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:44 node-1 haproxy[28876]: proxy aodh has no server available!
<27>Nov 13 00:53:46 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:46 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:46 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:46 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:48 node-1 haproxy[30244]: 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 13 00:53:48 node-1 haproxy[30244]: 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 13 00:53:48 node-1 haproxy[30244]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:48 node-1 haproxy[30244]: proxy keystone-1 has no server available!
<129>Nov 13 00:53:48 node-1 haproxy[30244]: 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 13 00:53:48 node-1 haproxy[30244]: 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 13 00:53:48 node-1 haproxy[30244]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:48 node-1 haproxy[30244]: proxy keystone-2 has no server available!
<129>Nov 13 00:53:48 node-1 haproxy[30244]: 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 13 00:53:49 node-1 haproxy[30248]: 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 13 00:53:49 node-1 haproxy[30248]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:49 node-1 haproxy[30248]: proxy neutron has no server available!
<129>Nov 13 00:53:49 node-1 haproxy[30248]: 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 13 00:53:49 node-1 haproxy[30248]: 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 13 00:53:49 node-1 haproxy[30248]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:49 node-1 haproxy[30248]: proxy mysqld has no server available!
<129>Nov 13 00:53:49 node-1 haproxy[30248]: 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 13 00:53:49 node-1 haproxy[30248]: 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 13 00:53:49 node-1 haproxy[30248]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:49 node-1 haproxy[30248]: proxy object-storage has no server available!
<129>Nov 13 00:53:49 node-1 haproxy[30248]: 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 13 00:53:49 node-1 haproxy[30248]: 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 13 00:53:49 node-1 haproxy[30248]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:49 node-1 haproxy[30248]: proxy aodh has no server available!
<129>Nov 13 00:53:50 node-1 haproxy[30248]: 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 13 00:53:50 node-1 haproxy[30248]: 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 13 00:53:50 node-1 haproxy[30248]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:50 node-1 haproxy[30248]: proxy ceilometer has no server available!
<27>Nov 13 00:53:51 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:51 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:51 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:51 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:51 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:53 node-1 haproxy[31604]: 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 13 00:53:53 node-1 haproxy[31604]: 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 13 00:53:54 node-1 haproxy[31611]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:54 node-1 haproxy[31611]: proxy keystone-1 has no server available!
<129>Nov 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:54 node-1 haproxy[31611]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:54 node-1 haproxy[31611]: proxy keystone-2 has no server available!
<129>Nov 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:54 node-1 haproxy[31611]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:54 node-1 haproxy[31611]: proxy neutron has no server available!
<129>Nov 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:54 node-1 haproxy[31611]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:54 node-1 haproxy[31611]: proxy mysqld has no server available!
<129>Nov 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:54 node-1 haproxy[31611]: 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 13 00:53:55 node-1 haproxy[31611]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:55 node-1 haproxy[31611]: proxy object-storage has no server available!
<129>Nov 13 00:53:55 node-1 haproxy[31611]: 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 13 00:53:55 node-1 haproxy[31611]: 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 13 00:53:55 node-1 haproxy[31611]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:55 node-1 haproxy[31611]: proxy aodh has no server available!
<129>Nov 13 00:53:55 node-1 haproxy[31611]: 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 13 00:53:55 node-1 haproxy[31611]: 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 13 00:53:55 node-1 haproxy[31611]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:55 node-1 haproxy[31611]: proxy ceilometer has no server available!
<27>Nov 13 00:53:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:56 node-1 multipathd: uevent trigger error
<27>Nov 13 00:53:56 node-1 multipathd: uevent trigger error
<129>Nov 13 00:53:59 node-1 haproxy[519]: 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 13 00:53:59 node-1 haproxy[519]: 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 13 00:53:59 node-1 haproxy[519]: 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 13 00:53:59 node-1 haproxy[519]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:59 node-1 haproxy[519]: proxy keystone-1 has no server available!
<129>Nov 13 00:53:59 node-1 haproxy[519]: 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 13 00:53:59 node-1 haproxy[519]: 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 13 00:53:59 node-1 haproxy[519]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:59 node-1 haproxy[519]: proxy keystone-2 has no server available!
<129>Nov 13 00:53:59 node-1 haproxy[519]: 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 13 00:53:59 node-1 haproxy[519]: 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 13 00:53:59 node-1 haproxy[519]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:53:59 node-1 haproxy[519]: proxy neutron has no server available!
<129>Nov 13 00:53:59 node-1 haproxy[519]: 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 13 00:54:00 node-1 haproxy[523]: 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 13 00:54:00 node-1 haproxy[523]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:00 node-1 haproxy[523]: proxy mysqld has no server available!
<129>Nov 13 00:54:00 node-1 haproxy[523]: 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 13 00:54:00 node-1 haproxy[523]: 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 13 00:54:00 node-1 haproxy[523]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:00 node-1 haproxy[523]: proxy object-storage has no server available!
<129>Nov 13 00:54:00 node-1 haproxy[523]: 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 13 00:54:00 node-1 haproxy[523]: 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 13 00:54:00 node-1 haproxy[523]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:00 node-1 haproxy[523]: proxy aodh has no server available!
<129>Nov 13 00:54:00 node-1 haproxy[523]: 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 13 00:54:00 node-1 haproxy[523]: 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 13 00:54:00 node-1 haproxy[523]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:00 node-1 haproxy[523]: proxy ceilometer has no server available!
<27>Nov 13 00:54:01 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:02 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:02 node-1 multipathd: uevent trigger error
<129>Nov 13 00:54:04 node-1 haproxy[1967]: 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 13 00:54:04 node-1 haproxy[1967]: 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 13 00:54:04 node-1 haproxy[1967]: 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 13 00:54:05 node-1 haproxy[1971]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:05 node-1 haproxy[1971]: proxy keystone-1 has no server available!
<129>Nov 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:05 node-1 haproxy[1971]: proxy keystone-2 has no server available!
<129>Nov 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:05 node-1 haproxy[1971]: proxy glance-api has no server available!
<129>Nov 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:05 node-1 haproxy[1971]: proxy glance-glare has no server available!
<129>Nov 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:05 node-1 haproxy[1971]: proxy neutron has no server available!
<129>Nov 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:05 node-1 haproxy[1971]: proxy glance-registry has no server available!
<129>Nov 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:05 node-1 haproxy[1971]: 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 13 00:54:06 node-1 haproxy[1971]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:06 node-1 haproxy[1971]: proxy mysqld has no server available!
<129>Nov 13 00:54:06 node-1 haproxy[1971]: 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 13 00:54:06 node-1 haproxy[1971]: 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 13 00:54:06 node-1 haproxy[1971]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:06 node-1 haproxy[1971]: proxy object-storage has no server available!
<129>Nov 13 00:54:06 node-1 haproxy[1971]: 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 13 00:54:06 node-1 haproxy[1971]: 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 13 00:54:06 node-1 haproxy[1971]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:06 node-1 haproxy[1971]: proxy aodh has no server available!
<129>Nov 13 00:54:06 node-1 haproxy[1971]: 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 13 00:54:06 node-1 haproxy[1971]: 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 13 00:54:06 node-1 haproxy[1971]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:06 node-1 haproxy[1971]: proxy ceilometer has no server available!
<27>Nov 13 00:54:07 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:07 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:07 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:07 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:07 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:07 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:07 node-1 multipathd: uevent trigger error
<129>Nov 13 00:54:10 node-1 haproxy[3370]: 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 13 00:54:10 node-1 haproxy[3370]: 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 13 00:54:10 node-1 haproxy[3370]: 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 13 00:54:10 node-1 haproxy[3370]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:10 node-1 haproxy[3370]: proxy keystone-1 has no server available!
<129>Nov 13 00:54:10 node-1 haproxy[3370]: 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 13 00:54:10 node-1 haproxy[3370]: 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 13 00:54:10 node-1 haproxy[3370]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:10 node-1 haproxy[3370]: proxy keystone-2 has no server available!
<129>Nov 13 00:54:10 node-1 haproxy[3370]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:11 node-1 haproxy[3374]: proxy nova-api has no server available!
<129>Nov 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:11 node-1 haproxy[3374]: proxy nova-metadata-api has no server available!
<129>Nov 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:11 node-1 haproxy[3374]: proxy glance-api has no server available!
<129>Nov 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:11 node-1 haproxy[3374]: proxy glance-glare has no server available!
<129>Nov 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:11 node-1 haproxy[3374]: proxy neutron has no server available!
<129>Nov 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:11 node-1 haproxy[3374]: proxy glance-registry has no server available!
<129>Nov 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:11 node-1 haproxy[3374]: proxy mysqld has no server available!
<129>Nov 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:11 node-1 haproxy[3374]: 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 13 00:54:12 node-1 haproxy[3374]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:12 node-1 haproxy[3374]: proxy object-storage has no server available!
<129>Nov 13 00:54:12 node-1 haproxy[3374]: 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 13 00:54:12 node-1 haproxy[3374]: 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 13 00:54:12 node-1 haproxy[3374]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:12 node-1 haproxy[3374]: proxy aodh has no server available!
<129>Nov 13 00:54:12 node-1 haproxy[3374]: 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 13 00:54:12 node-1 haproxy[3374]: 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 13 00:54:12 node-1 haproxy[3374]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:12 node-1 haproxy[3374]: proxy ceilometer has no server available!
<129>Nov 13 00:54:12 node-1 haproxy[3374]: 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 13 00:54:12 node-1 haproxy[3374]: 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 13 00:54:12 node-1 haproxy[3374]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:12 node-1 haproxy[3374]: proxy nova-novncproxy has no server available!
<27>Nov 13 00:54:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:13 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:13 node-1 multipathd: uevent trigger error
<129>Nov 13 00:54:15 node-1 haproxy[4754]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:16 node-1 haproxy[4758]: proxy keystone-1 has no server available!
<129>Nov 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:16 node-1 haproxy[4758]: proxy keystone-2 has no server available!
<129>Nov 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:16 node-1 haproxy[4758]: proxy nova-api has no server available!
<129>Nov 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:16 node-1 haproxy[4758]: proxy nova-metadata-api has no server available!
<129>Nov 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:16 node-1 haproxy[4758]: proxy cinder-api has no server available!
<129>Nov 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:16 node-1 haproxy[4758]: proxy glance-api has no server available!
<129>Nov 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: 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 13 00:54:16 node-1 haproxy[4758]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:16 node-1 haproxy[4758]: proxy glance-glare has no server available!
<129>Nov 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:17 node-1 haproxy[4758]: proxy neutron has no server available!
<129>Nov 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:17 node-1 haproxy[4758]: proxy glance-registry has no server available!
<129>Nov 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:17 node-1 haproxy[4758]: proxy mysqld has no server available!
<129>Nov 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:17 node-1 haproxy[4758]: proxy object-storage has no server available!
<129>Nov 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:17 node-1 haproxy[4758]: proxy aodh has no server available!
<129>Nov 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:17 node-1 haproxy[4758]: proxy ceilometer has no server available!
<129>Nov 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: 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 13 00:54:17 node-1 haproxy[4758]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:17 node-1 haproxy[4758]: proxy nova-novncproxy has no server available!
<27>Nov 13 00:54:19 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:19 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:19 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:19 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:19 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:19 node-1 multipathd: uevent trigger error
<129>Nov 13 00:54:21 node-1 haproxy[6339]: 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 13 00:54:21 node-1 haproxy[6339]: 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 13 00:54:21 node-1 haproxy[6339]: 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 13 00:54:21 node-1 haproxy[6339]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:21 node-1 haproxy[6339]: proxy keystone-1 has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy keystone-2 has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy nova-api has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy nova-metadata-api has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy cinder-api has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy glance-api has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy glance-glare has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy neutron has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy glance-registry has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:22 node-1 haproxy[6343]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:22 node-1 haproxy[6343]: proxy mysqld has no server available!
<129>Nov 13 00:54:22 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:23 node-1 haproxy[6343]: proxy object-storage has no server available!
<129>Nov 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:23 node-1 haproxy[6343]: proxy aodh has no server available!
<129>Nov 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:23 node-1 haproxy[6343]: proxy ceilometer has no server available!
<129>Nov 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:23 node-1 haproxy[6343]: proxy heat-api has no server available!
<129>Nov 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:23 node-1 haproxy[6343]: proxy heat-api-cfn has no server available!
<129>Nov 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:23 node-1 haproxy[6343]: proxy heat-api-cloudwatch has no server available!
<129>Nov 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: 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 13 00:54:23 node-1 haproxy[6343]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 00:54:23 node-1 haproxy[6343]: proxy nova-novncproxy has no server available!
<27>Nov 13 00:54:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:24 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:25 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:25 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:25 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:28 node-1 multipathd: uevent trigger error
<27>Nov 13 00:54:35 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov 13 00:54:59 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 13 00:55:01 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov 13 00:55:30 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 00:55:37 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:55:52 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:36 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:36 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:36 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:36 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:36 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:41 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:41 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:41 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:41 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:41 node-1 multipathd: uevent trigger error
<43>Nov 13 00:57:54 node-1 apache2_error [Sun Nov 13 00:57:52.309147 2016] [mpm_event:notice] [pid 12499:tid 139748014335872] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 00:57:54 node-1 apache2_error [Sun Nov 13 00:57:52.309223 2016] [core:notice] [pid 12499:tid 139748014335872] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 00:57:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:59 node-1 multipathd: uevent trigger error
<27>Nov 13 00:57:59 node-1 multipathd: uevent trigger error
<43>Nov 13 00:58:04 node-1 apache2_error [Sun Nov 13 00:57:55.350185 2016] [mpm_event:notice] [pid 12499:tid 139748014335872] AH00491: caught SIGTERM, shutting down
<43>Nov 13 00:58:04 node-1 apache2_error [Sun Nov 13 00:57:56.435387 2016] [mpm_worker:notice] [pid 13474:tid 140433280522112] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 00:58:04 node-1 apache2_error [Sun Nov 13 00:57:56.435420 2016] [core:notice] [pid 13474:tid 140433280522112] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 00:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:04 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:08 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:08 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:08 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:08 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:08 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:08 node-1 multipathd: uevent trigger error
<27>Nov 13 00:58:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov 13 00:59:14 node-1 apache2_error [Sun Nov 13 00:59:10.981706 2016] [mpm_worker:notice] [pid 13474:tid 140433280522112] AH00295: caught SIGTERM, shutting down
<43>Nov 13 00:59:14 node-1 apache2_error [Sun Nov 13 00:59:11.734830 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 00:59:14 node-1 apache2_error [Sun Nov 13 00:59:11.734859 2016] [core:notice] [pid 26818:tid 140046127736704] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 01:00:04 node-1 apache2_error [Sun Nov 13 00:59:55.555183 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 01:00:04 node-1 apache2_error [Sun Nov 13 00:59:55.747371 2016] [mpm_worker:warn] [pid 26818:tid 140046127736704] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 01:00:04 node-1 apache2_error [Sun Nov 13 00:59:55.750109 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 01:00:04 node-1 apache2_error [Sun Nov 13 00:59:55.750126 2016] [core:notice] [pid 26818:tid 140046127736704] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 01:00:39 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:39 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:39 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:39 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:39 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:48 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:48 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:48 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:48 node-1 multipathd: uevent trigger error
<27>Nov 13 01:00:48 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:30 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:30 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:30 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:30 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:30 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:30 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:34 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:01:57 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 01:02:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:02:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:02:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:02:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:02:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:02:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:03:49 node-1 multipathd: uevent trigger error
<27>Nov 13 01:03:49 node-1 multipathd: uevent trigger error
<27>Nov 13 01:03:49 node-1 multipathd: uevent trigger error
<27>Nov 13 01:03:49 node-1 multipathd: uevent trigger error
<27>Nov 13 01:03:49 node-1 multipathd: uevent trigger error
<27>Nov 13 01:03:49 node-1 multipathd: uevent trigger error
<27>Nov 13 01:04:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:04:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:04:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:04:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:04:44 node-1 multipathd: uevent trigger error
<27>Nov 13 01:04:59 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 01:05:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:16 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:16 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:16 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:16 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:16 node-1 multipathd: uevent trigger error
<27>Nov 13 01:05:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:36 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:36 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:36 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:36 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:36 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:36 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:36 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:57 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:57 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:57 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:57 node-1 multipathd: uevent trigger error
<27>Nov 13 01:07:57 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 01:08:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:24 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:24 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:08:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:50 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:50 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:50 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:50 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:50 node-1 multipathd: uevent trigger error
<27>Nov 13 01:09:50 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:10:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:11:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 01:12:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:12:52 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:13:07 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Nov 13 01:14:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 01:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:04 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:47 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:47 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:47 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:47 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:14:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:15:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:43 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:43 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:43 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:43 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:43 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:16:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:17:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Nov 13 01:17:11 node-1 liberasurecode[67904]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:11 node-1 liberasurecode[67904]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:11 node-1 liberasurecode[67904]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:11 node-1 liberasurecode[67904]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:11 node-1 liberasurecode[67930]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:11 node-1 liberasurecode[67930]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:11 node-1 liberasurecode[67930]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:11 node-1 liberasurecode[67930]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:13 node-1 liberasurecode[68331]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:13 node-1 liberasurecode[68331]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:13 node-1 liberasurecode[68331]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:13 node-1 liberasurecode[68331]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69625]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69625]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69625]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69625]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69688]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69688]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69688]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:17 node-1 liberasurecode[69688]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69767]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69767]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69767]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69767]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69958]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69958]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69973]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69973]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69973]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[69973]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70011]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70011]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70040]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70040]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70040]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:18 node-1 liberasurecode[70040]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:34 node-1 liberasurecode[71550]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:34 node-1 liberasurecode[71550]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:34 node-1 liberasurecode[71550]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:17:34 node-1 liberasurecode[71550]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 01:17:42 node-1 multipathd: uevent trigger error
<27>Nov 13 01:17:42 node-1 multipathd: uevent trigger error
<27>Nov 13 01:17:42 node-1 multipathd: uevent trigger error
<27>Nov 13 01:17:42 node-1 multipathd: uevent trigger error
<27>Nov 13 01:17:43 node-1 multipathd: uevent trigger error
<27>Nov 13 01:17:43 node-1 multipathd: uevent trigger error
<43>Nov 13 01:18:36 node-1 apache2_error [Sun Nov 13 01:18:28.901210 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 01:18:36 node-1 apache2_error [Sun Nov 13 01:18:29.288469 2016] [mpm_worker:warn] [pid 26818:tid 140046127736704] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 01:18:36 node-1 apache2_error [Sun Nov 13 01:18:29.294787 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 01:18:36 node-1 apache2_error [Sun Nov 13 01:18:29.294833 2016] [core:notice] [pid 26818:tid 140046127736704] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 01:19:06 node-1 apache2_error [Sun Nov 13 01:19:06.169734 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 01:19:06 node-1 apache2_error [Sun Nov 13 01:19:06.362324 2016] [mpm_worker:warn] [pid 26818:tid 140046127736704] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 01:19:06 node-1 apache2_error [Sun Nov 13 01:19:06.367274 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 01:19:06 node-1 apache2_error [Sun Nov 13 01:19:06.367295 2016] [core:notice] [pid 26818:tid 140046127736704] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 01:19:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:10 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:55 node-1 multipathd: uevent trigger error
<27>Nov 13 01:19:55 node-1 multipathd: uevent trigger error
<43>Nov 13 01:19:56 node-1 apache2_error [Sun Nov 13 01:19:51.294907 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 01:19:56 node-1 apache2_error [Sun Nov 13 01:19:51.489833 2016] [mpm_worker:warn] [pid 26818:tid 140046127736704] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 01:19:56 node-1 apache2_error [Sun Nov 13 01:19:51.495047 2016] [mpm_worker:notice] [pid 26818:tid 140046127736704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 01:19:56 node-1 apache2_error [Sun Nov 13 01:19:51.495066 2016] [core:notice] [pid 26818:tid 140046127736704] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 01:20:01 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:01 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:01 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:01 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:01 node-1 multipathd: uevent trigger error
<11>Nov 13 01:20:02 node-1 liberasurecode[95900]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:20:02 node-1 liberasurecode[95900]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:20:02 node-1 liberasurecode[95900]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:20:02 node-1 liberasurecode[95900]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 01:20:06 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 01:20:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:07 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:22 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:22 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:22 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:22 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:23 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:43 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:51 node-1 multipathd: uevent trigger error
<27>Nov 13 01:20:57 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov 13 01:21:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:20 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:20 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:20 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:20 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:20 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:25 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:21:40 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:06 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:11 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:24 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:24 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:24 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:24 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:24 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:29 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:41 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:22:59 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:03 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:08 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:08 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:08 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:08 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:08 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:12 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:12 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:12 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:13 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:17 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:21 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:21 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:21 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:21 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:21 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:26 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:26 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:26 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:26 node-1 multipathd: uevent trigger error
<27>Nov 13 01:23:26 node-1 multipathd: uevent trigger error
<11>Nov 13 01:25:01 node-1 liberasurecode[161834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:25:01 node-1 liberasurecode[161834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:25:01 node-1 liberasurecode[161834]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 01:25:01 node-1 liberasurecode[161834]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
