Jul 27 06:39:12 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8373" x-info="http://www.rsyslog.com"] start
Jul 27 06:39:12 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 27 06:39:12 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 27 06:39:12 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 27 06:39:12 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 27 06:39:12 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 27 06:39:12 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 27 06:39:12 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 27 06:39:12 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=c7d749c3-34ee-4112-aa45-7daa1505d11d nomdmonddf nomdmonisw
Jul 27 06:39:12 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 27 06:39:12 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 27 06:39:12 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 27 06:39:12 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 27 06:39:12 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 27 06:39:12 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 27 06:39:12 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 27 06:39:12 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
Jul 27 06:39:12 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 27 06:39:12 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 06:39:12 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 27 06:39:12 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 27 06:39:12 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 27 06:39:12 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 27 06:39:12 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 27 06:39:12 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 27 06:39:12 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 27 06:39:12 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 27 06:39:12 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 27 06:39:12 node-1 kernel: [    0.000000]   2 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000]   3 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000]   4 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000]   5 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000]   6 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000]   7 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000]   8 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000]   9 disabled
Jul 27 06:39:12 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 27 06:39:12 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 27 06:39:12 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 27 06:39:12 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 27 06:39:12 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 27 06:39:12 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 27 06:39:12 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 27 06:39:12 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 27 06:39:12 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 27 06:39:12 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 27 06:39:12 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 27 06:39:12 node-1 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 27 06:39:12 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 27 06:39:12 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 27 06:39:12 node-1 kernel: [    0.000000] Zone ranges:
Jul 27 06:39:12 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 27 06:39:12 node-1 kernel: [    0.000000] Early memory node ranges
Jul 27 06:39:12 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 27 06:39:12 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 27 06:39:12 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 27 06:39:12 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 27 06:39:12 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 27 06:39:12 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 27 06:39:12 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 27 06:39:12 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 27 06:39:12 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 27 06:39:12 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 27 06:39:12 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 27 06:39:12 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 27 06:39:12 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 27 06:39:12 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 27 06:39:12 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 27 06:39:12 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 27 06:39:12 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 27 06:39:12 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 27 06:39:12 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 27 06:39:12 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 27 06:39:12 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 27 06:39:12 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 27 06:39:12 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 27 06:39:12 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 
Jul 27 06:39:12 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 27 06:39:12 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 27 06:39:12 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=c7d749c3-34ee-4112-aa45-7daa1505d11d nomdmonddf nomdmonisw
Jul 27 06:39:12 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 27 06:39:12 node-1 kernel: [    0.000000] Checking aperture...
Jul 27 06:39:12 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 06:39:12 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 27 06:39:12 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 27 06:39:12 node-1 kernel: [    0.000000] Memory: 32653448K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627188K reserved)
Jul 27 06:39:12 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 27 06:39:12 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 27 06:39:12 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 27 06:39:12 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 27 06:39:12 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 27 06:39:12 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 27 06:39:12 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 27 06:39:12 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 27 06:39:12 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 27 06:39:12 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 27 06:39:12 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 27 06:39:12 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 27 06:39:12 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 27 06:39:12 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 27 06:39:12 node-1 kernel: [    0.004000] tsc: Detected 3491.877 MHz processor
Jul 27 06:39:12 node-1 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.75 BogoMIPS (lpj=13967508)
Jul 27 06:39:12 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 27 06:39:12 node-1 kernel: [    0.000044] Security Framework initialized
Jul 27 06:39:12 node-1 kernel: [    0.000064] AppArmor: AppArmor initialized
Jul 27 06:39:12 node-1 kernel: [    0.000066] Yama: becoming mindful.
Jul 27 06:39:12 node-1 kernel: [    0.001446] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.006356] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.008282] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.008310] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.008585] Initializing cgroup subsys memory
Jul 27 06:39:12 node-1 kernel: [    0.008593] Initializing cgroup subsys devices
Jul 27 06:39:12 node-1 kernel: [    0.008594] Initializing cgroup subsys freezer
Jul 27 06:39:12 node-1 kernel: [    0.008596] Initializing cgroup subsys blkio
Jul 27 06:39:12 node-1 kernel: [    0.008598] Initializing cgroup subsys perf_event
Jul 27 06:39:12 node-1 kernel: [    0.008600] Initializing cgroup subsys hugetlb
Jul 27 06:39:12 node-1 kernel: [    0.008620] CPU: Physical Processor ID: 0
Jul 27 06:39:12 node-1 kernel: [    0.008621] CPU: Processor Core ID: 0
Jul 27 06:39:12 node-1 kernel: [    0.008624] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 27 06:39:12 node-1 kernel: [    0.008624] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 27 06:39:12 node-1 kernel: [    0.009318] mce: CPU supports 22 MCE banks
Jul 27 06:39:12 node-1 kernel: [    0.009346] CPU0: Thermal monitoring enabled (TM1)
Jul 27 06:39:12 node-1 kernel: [    0.009367] process: using mwait in idle threads
Jul 27 06:39:12 node-1 kernel: [    0.009370] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 27 06:39:12 node-1 kernel: [    0.009370] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 27 06:39:12 node-1 kernel: [    0.009370] tlb_flushall_shift: 6
Jul 27 06:39:12 node-1 kernel: [    0.009459] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 27 06:39:12 node-1 kernel: [    0.010185] ACPI: Core revision 20131115
Jul 27 06:39:12 node-1 kernel: [    0.022869] ACPI: All ACPI Tables successfully acquired
Jul 27 06:39:12 node-1 kernel: [    0.023030] ftrace: allocating 28617 entries in 112 pages
Jul 27 06:39:12 node-1 kernel: [    0.031829] dmar: Host address width 46
Jul 27 06:39:12 node-1 kernel: [    0.031831] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 27 06:39:12 node-1 kernel: [    0.031837] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 06:39:12 node-1 kernel: [    0.031839] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 27 06:39:12 node-1 kernel: [    0.031843] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 06:39:12 node-1 kernel: [    0.031845] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 27 06:39:12 node-1 kernel: [    0.031846] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 27 06:39:12 node-1 kernel: [    0.031847] dmar: ATSR flags: 0x0
Jul 27 06:39:12 node-1 kernel: [    0.031848] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 27 06:39:12 node-1 kernel: [    0.031849] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 27 06:39:12 node-1 kernel: [    0.031965] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 27 06:39:12 node-1 kernel: [    0.031966] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 06:39:12 node-1 kernel: [    0.031967] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 06:39:12 node-1 kernel: [    0.031968] HPET id 0 under DRHD base 0xc7ffc000
Jul 27 06:39:12 node-1 kernel: [    0.031969] Your BIOS is broken and requested that x2apic be disabled.
Jul 27 06:39:12 node-1 kernel: [    0.031969] This will slightly decrease performance.
Jul 27 06:39:12 node-1 kernel: [    0.031969] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 27 06:39:12 node-1 kernel: [    0.032400] Enabled IRQ remapping in xapic mode
Jul 27 06:39:12 node-1 kernel: [    0.032402] x2apic not enabled, IRQ remapping is in xapic mode
Jul 27 06:39:12 node-1 kernel: [    0.032405] Switched APIC routing to physical flat.
Jul 27 06:39:12 node-1 kernel: [    0.032960] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 27 06:39:12 node-1 kernel: [    0.072609] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 27 06:39:12 node-1 kernel: [    0.072615] TSC deadline timer enabled
Jul 27 06:39:12 node-1 kernel: [    0.072623] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 27 06:39:12 node-1 kernel: [    0.072628] ... version:                3
Jul 27 06:39:12 node-1 kernel: [    0.072629] ... bit width:              48
Jul 27 06:39:12 node-1 kernel: [    0.072630] ... generic registers:      4
Jul 27 06:39:12 node-1 kernel: [    0.072631] ... value mask:             0000ffffffffffff
Jul 27 06:39:12 node-1 kernel: [    0.072632] ... max period:             0000ffffffffffff
Jul 27 06:39:12 node-1 kernel: [    0.072633] ... fixed-purpose events:   3
Jul 27 06:39:12 node-1 kernel: [    0.072634] ... event mask:             000000070000000f
Jul 27 06:39:12 node-1 kernel: [    0.074060] x86: Booting SMP configuration:
Jul 27 06:39:12 node-1 kernel: [    0.088163] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 27 06:39:12 node-1 kernel: [    0.074062] .... node  #0, CPUs:        #1  #2  #3
Jul 27 06:39:12 node-1 kernel: [    0.116068] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 27 06:39:12 node-1 kernel: [    0.270199] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 27 06:39:12 node-1 kernel: [    0.325814] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 27 06:39:12 node-1 kernel: [    0.382881] x86: Booted up 2 nodes, 16 CPUs
Jul 27 06:39:12 node-1 kernel: [    0.382885] smpboot: Total of 16 processors activated (111772.34 BogoMIPS)
Jul 27 06:39:12 node-1 kernel: [    0.407493] devtmpfs: initialized
Jul 27 06:39:12 node-1 kernel: [    0.410582] EVM: security.selinux
Jul 27 06:39:12 node-1 kernel: [    0.410583] EVM: security.SMACK64
Jul 27 06:39:12 node-1 kernel: [    0.410584] EVM: security.ima
Jul 27 06:39:12 node-1 kernel: [    0.410585] EVM: security.capability
Jul 27 06:39:12 node-1 kernel: [    0.410636] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.411286] pinctrl core: initialized pinctrl subsystem
Jul 27 06:39:12 node-1 kernel: [    0.411342] regulator-dummy: no parameters
Jul 27 06:39:12 node-1 kernel: [    0.411374] RTC time:  6:38:37, date: 07/27/16
Jul 27 06:39:12 node-1 kernel: [    0.411408] NET: Registered protocol family 16
Jul 27 06:39:12 node-1 kernel: [    0.411490] cpuidle: using governor ladder
Jul 27 06:39:12 node-1 kernel: [    0.411491] cpuidle: using governor menu
Jul 27 06:39:12 node-1 kernel: [    0.411524] ACPI: bus type PCI registered
Jul 27 06:39:12 node-1 kernel: [    0.411526] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 27 06:39:12 node-1 kernel: [    0.411572] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 27 06:39:12 node-1 kernel: [    0.411575] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 27 06:39:12 node-1 kernel: [    0.425310] PCI: Using configuration type 1 for base access
Jul 27 06:39:12 node-1 kernel: [    0.426304] bio: create slab <bio-0> at 0
Jul 27 06:39:12 node-1 kernel: [    0.426591] ACPI: Added _OSI(Module Device)
Jul 27 06:39:12 node-1 kernel: [    0.426593] ACPI: Added _OSI(Processor Device)
Jul 27 06:39:12 node-1 kernel: [    0.426594] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 27 06:39:12 node-1 kernel: [    0.426595] ACPI: Added _OSI(Processor Aggregator Device)
Jul 27 06:39:12 node-1 kernel: [    0.439242] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 27 06:39:12 node-1 kernel: [    0.449870] ACPI: Interpreter enabled
Jul 27 06:39:12 node-1 kernel: [    0.449875] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 27 06:39:12 node-1 kernel: [    0.449879] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 27 06:39:12 node-1 kernel: [    0.449882] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 27 06:39:12 node-1 kernel: [    0.449889] ACPI: (supports S0 S4 S5)
Jul 27 06:39:12 node-1 kernel: [    0.449890] ACPI: Using IOAPIC for interrupt routing
Jul 27 06:39:12 node-1 kernel: [    0.449932] HEST: Table parsing has been initialized.
Jul 27 06:39:12 node-1 kernel: [    0.449935] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 27 06:39:12 node-1 kernel: [    0.450486] ACPI: No dock devices found.
Jul 27 06:39:12 node-1 kernel: [    0.462050] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 27 06:39:12 node-1 kernel: [    0.462055] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 06:39:12 node-1 kernel: [    0.462058] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 06:39:12 node-1 kernel: [    0.462087] PCI host bridge to bus 0000:ff
Jul 27 06:39:12 node-1 kernel: [    0.462089] pci_bus 0000:ff: root bus resource [bus ff]
Jul 27 06:39:12 node-1 kernel: [    0.462097] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462138] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.462168] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462204] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462234] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.462264] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.462296] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462325] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462356] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462387] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462414] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462440] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462469] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462495] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462522] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462549] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462577] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462605] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462632] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.462659] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462685] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.462711] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462737] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462767] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.462802] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462833] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462863] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462893] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462924] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462955] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.462986] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463016] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463048] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463081] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463113] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463146] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463179] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463209] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463237] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463269] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463301] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463339] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463375] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463407] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463437] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463466] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463496] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463525] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463555] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463586] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463617] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463646] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463674] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463703] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463731] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463762] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463794] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463850] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 27 06:39:12 node-1 kernel: [    0.463853] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 06:39:12 node-1 kernel: [    0.463856] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 06:39:12 node-1 kernel: [    0.463873] PCI host bridge to bus 0000:7f
Jul 27 06:39:12 node-1 kernel: [    0.463874] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 27 06:39:12 node-1 kernel: [    0.463879] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463906] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.463934] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463963] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.463985] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.464009] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.464039] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464065] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464092] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464115] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464138] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464160] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464185] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464208] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464233] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464258] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464280] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464302] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464324] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.464348] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464369] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.464391] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464413] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464439] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 06:39:12 node-1 kernel: [    0.464471] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464497] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464523] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464549] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464574] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464601] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464628] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464657] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464681] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464707] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464733] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464760] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464788] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464813] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464837] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464865] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464890] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464917] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464947] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464973] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.464997] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465022] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465047] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465073] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465099] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465125] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465154] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465178] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465200] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465225] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465250] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465279] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.465304] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.466545] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 27 06:39:12 node-1 kernel: [    0.466549] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 06:39:12 node-1 kernel: [    0.467674] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 06:39:12 node-1 kernel: [    0.468184] PCI host bridge to bus 0000:00
Jul 27 06:39:12 node-1 kernel: [    0.468186] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 27 06:39:12 node-1 kernel: [    0.468188] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 27 06:39:12 node-1 kernel: [    0.468189] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 27 06:39:12 node-1 kernel: [    0.468191] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 27 06:39:12 node-1 kernel: [    0.468192] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 27 06:39:12 node-1 kernel: [    0.468193] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 27 06:39:12 node-1 kernel: [    0.468195] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 27 06:39:12 node-1 kernel: [    0.468201] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 27 06:39:12 node-1 kernel: [    0.468282] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.468313] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.468354] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 27 06:39:12 node-1 kernel: [    0.468374] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.468403] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.468443] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 27 06:39:12 node-1 kernel: [    0.468461] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.468490] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.468533] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 27 06:39:12 node-1 kernel: [    0.468548] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.468617] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.468694] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.468770] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 06:39:12 node-1 kernel: [    0.468775] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 27 06:39:12 node-1 kernel: [    0.468859] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 27 06:39:12 node-1 kernel: [    0.469007] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 27 06:39:12 node-1 kernel: [    0.469024] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 27 06:39:12 node-1 kernel: [    0.469102] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.469157] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 27 06:39:12 node-1 kernel: [    0.469178] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.469233] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.469276] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 27 06:39:12 node-1 kernel: [    0.469303] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.469359] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.469402] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 27 06:39:12 node-1 kernel: [    0.469426] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 27 06:39:12 node-1 kernel: [    0.469443] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 27 06:39:12 node-1 kernel: [    0.469520] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.469570] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 27 06:39:12 node-1 kernel: [    0.469595] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 27 06:39:12 node-1 kernel: [    0.469841] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 27 06:39:12 node-1 kernel: [    0.469847] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 27 06:39:12 node-1 kernel: [    0.469853] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.469859] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.469866] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 27 06:39:12 node-1 kernel: [    0.469896] pci 0000:01:00.0: supports D1 D2
Jul 27 06:39:12 node-1 kernel: [    0.476042] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 06:39:12 node-1 kernel: [    0.476048] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 06:39:12 node-1 kernel: [    0.476052] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 06:39:12 node-1 kernel: [    0.476311] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.476345] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 27 06:39:12 node-1 kernel: [    0.484051] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 06:39:12 node-1 kernel: [    0.484053] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.484055] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 06:39:12 node-1 kernel: [    0.484110] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.484177] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.484254] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.484298] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 06:39:12 node-1 kernel: [    0.484302] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.484303] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 06:39:12 node-1 kernel: [    0.484355] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.484496] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.484549] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 06:39:12 node-1 kernel: [    0.484552] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.484554] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.484603] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.484722] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.484759] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.484878] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.484915] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.485035] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.485072] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 27 06:39:12 node-1 kernel: [    0.485193] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 27 06:39:12 node-1 kernel: [    0.485234] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 06:39:12 node-1 kernel: [    0.485237] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.485239] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.485296] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 27 06:39:12 node-1 kernel: [    0.485359] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.485411] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.485477] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 27 06:39:12 node-1 kernel: [    0.485557] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 27 06:39:12 node-1 kernel: [    0.485664] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 06:39:12 node-1 kernel: [    0.485667] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.485669] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.485725] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 27 06:39:12 node-1 kernel: [    0.485782] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.485830] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.486043] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 06:39:12 node-1 kernel: [    0.486047] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 06:39:12 node-1 kernel: [    0.486113] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 27 06:39:12 node-1 kernel: [    0.486165] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.486214] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.486446] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 06:39:12 node-1 kernel: [    0.486449] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 06:39:12 node-1 kernel: [    0.486510] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 27 06:39:12 node-1 kernel: [    0.486573] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.486625] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 27 06:39:12 node-1 kernel: [    0.486848] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 06:39:12 node-1 kernel: [    0.486852] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 06:39:12 node-1 kernel: [    0.487026] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 06:39:12 node-1 kernel: [    0.487064] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 06:39:12 node-1 kernel: [    0.487139] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 27 06:39:12 node-1 kernel: [    0.487158] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 27 06:39:12 node-1 kernel: [    0.487171] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 27 06:39:12 node-1 kernel: [    0.487184] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 27 06:39:12 node-1 kernel: [    0.487234] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 27 06:39:12 node-1 kernel: [    0.492044] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 06:39:12 node-1 kernel: [    0.492053] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 06:39:12 node-1 kernel: [    0.492106] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 27 06:39:12 node-1 kernel: [    0.492609] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 27 06:39:12 node-1 kernel: [    0.492612] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 06:39:12 node-1 kernel: [    0.492735] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 06:39:12 node-1 kernel: [    0.492844] PCI host bridge to bus 0000:80
Jul 27 06:39:12 node-1 kernel: [    0.492846] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 27 06:39:12 node-1 kernel: [    0.492848] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 27 06:39:12 node-1 kernel: [    0.492849] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 27 06:39:12 node-1 kernel: [    0.492857] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.492921] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.492989] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 06:39:12 node-1 kernel: [    0.493051] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 06:39:12 node-1 kernel: [    0.493056] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 27 06:39:12 node-1 kernel: [    0.493126] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 27 06:39:12 node-1 kernel: [    0.493426] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 27 06:39:12 node-1 kernel: [    0.493457] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 27 06:39:12 node-1 kernel: [    0.493486] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 27 06:39:12 node-1 kernel: [    0.493515] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 27 06:39:12 node-1 kernel: [    0.493544] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 06:39:12 node-1 kernel: [    0.493574] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 06:39:12 node-1 kernel: [    0.493604] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 06:39:12 node-1 kernel: [    0.493634] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 06:39:12 node-1 kernel: [    0.493719] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 27 06:39:12 node-1 kernel: [    0.493723] ACPI: \_SB_.UNC1: notify handler is installed
Jul 27 06:39:12 node-1 kernel: [    0.493725] ACPI: \_SB_.UNC0: notify handler is installed
Jul 27 06:39:12 node-1 kernel: [    0.493739] ACPI: \_SB_.PCI0: notify handler is installed
Jul 27 06:39:12 node-1 kernel: [    0.493793] ACPI: \_SB_.PCI1: notify handler is installed
Jul 27 06:39:12 node-1 kernel: [    0.493872] Found 4 acpi root devices
Jul 27 06:39:12 node-1 kernel: [    0.493980] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 27 06:39:12 node-1 kernel: [    0.493982] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 27 06:39:12 node-1 kernel: [    0.493984] vgaarb: loaded
Jul 27 06:39:12 node-1 kernel: [    0.493985] vgaarb: bridge control possible 0000:0c:00.0
Jul 27 06:39:12 node-1 kernel: [    0.494103] SCSI subsystem initialized
Jul 27 06:39:12 node-1 kernel: [    0.494167] libata version 3.00 loaded.
Jul 27 06:39:12 node-1 kernel: [    0.494182] ACPI: bus type USB registered
Jul 27 06:39:12 node-1 kernel: [    0.494192] usbcore: registered new interface driver usbfs
Jul 27 06:39:12 node-1 kernel: [    0.494197] usbcore: registered new interface driver hub
Jul 27 06:39:12 node-1 kernel: [    0.494220] usbcore: registered new device driver usb
Jul 27 06:39:12 node-1 kernel: [    0.494384] PCI: Using ACPI for IRQ routing
Jul 27 06:39:12 node-1 kernel: [    0.497983] PCI: pci_cache_line_size set to 64 bytes
Jul 27 06:39:12 node-1 kernel: [    0.498184] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 27 06:39:12 node-1 kernel: [    0.498185] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 27 06:39:12 node-1 kernel: [    0.498186] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 27 06:39:12 node-1 kernel: [    0.498251] NetLabel: Initializing
Jul 27 06:39:12 node-1 kernel: [    0.498252] NetLabel:  domain hash size = 128
Jul 27 06:39:12 node-1 kernel: [    0.498253] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 27 06:39:12 node-1 kernel: [    0.498263] NetLabel:  unlabeled traffic allowed by default
Jul 27 06:39:12 node-1 kernel: [    0.498320] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 27 06:39:12 node-1 kernel: [    0.498324] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 27 06:39:12 node-1 kernel: [    0.500390] Switched to clocksource hpet
Jul 27 06:39:12 node-1 kernel: [    0.504783] AppArmor: AppArmor Filesystem Enabled
Jul 27 06:39:12 node-1 kernel: [    0.504821] pnp: PnP ACPI init
Jul 27 06:39:12 node-1 kernel: [    0.504834] ACPI: bus type PNP registered
Jul 27 06:39:12 node-1 kernel: [    0.505012] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505024] pnp 00:01: [dma 4]
Jul 27 06:39:12 node-1 kernel: [    0.505042] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505076] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505101] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505122] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505172] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505281] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505284] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 27 06:39:12 node-1 kernel: [    0.505285] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505287] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505289] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505290] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505293] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 27 06:39:12 node-1 kernel: [    0.505295] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505297] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505298] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505300] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505301] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505303] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 27 06:39:12 node-1 kernel: [    0.505305] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505408] pnp 00:07: [dma 0 disabled]
Jul 27 06:39:12 node-1 kernel: [    0.505441] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505522] pnp 00:08: [dma 0 disabled]
Jul 27 06:39:12 node-1 kernel: [    0.505558] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 06:39:12 node-1 kernel: [    0.505615] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 27 06:39:12 node-1 kernel: [    0.506052] pnp: PnP ACPI: found 10 devices
Jul 27 06:39:12 node-1 kernel: [    0.506054] ACPI: bus type PNP unregistered
Jul 27 06:39:12 node-1 kernel: [    0.512051] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 06:39:12 node-1 kernel: [    0.512055] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 06:39:12 node-1 kernel: [    0.512058] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 06:39:12 node-1 kernel: [    0.512063] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 06:39:12 node-1 kernel: [    0.512065] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512080] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512109] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 06:39:12 node-1 kernel: [    0.512123] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512152] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 06:39:12 node-1 kernel: [    0.512167] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 06:39:12 node-1 kernel: [    0.512196] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 06:39:12 node-1 kernel: [    0.512210] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 06:39:12 node-1 kernel: [    0.512239] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 06:39:12 node-1 kernel: [    0.512241] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512255] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512284] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 06:39:12 node-1 kernel: [    0.512286] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512301] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512333] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 06:39:12 node-1 kernel: [    0.512334] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512337] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512342] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 06:39:12 node-1 kernel: [    0.512344] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512347] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512351] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 06:39:12 node-1 kernel: [    0.512357] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 06:39:12 node-1 kernel: [    0.512370] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 06:39:12 node-1 kernel: [    0.512374] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 06:39:12 node-1 kernel: [    0.512381] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 27 06:39:12 node-1 kernel: [    0.512382] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 27 06:39:12 node-1 kernel: [    0.512383] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 27 06:39:12 node-1 kernel: [    0.512384] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 27 06:39:12 node-1 kernel: [    0.512385] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 27 06:39:12 node-1 kernel: [    0.512386] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 27 06:39:12 node-1 kernel: [    0.512387] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 27 06:39:12 node-1 kernel: [    0.512388] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 27 06:39:12 node-1 kernel: [    0.512389] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512389] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512391] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512392] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512393] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512393] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512394] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512395] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512397] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 27 06:39:12 node-1 kernel: [    0.512397] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512399] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 27 06:39:12 node-1 kernel: [    0.512400] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 27 06:39:12 node-1 kernel: [    0.512401] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 27 06:39:12 node-1 kernel: [    0.512402] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 27 06:39:12 node-1 kernel: [    0.512405] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 27 06:39:12 node-1 kernel: [    0.512406] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 27 06:39:12 node-1 kernel: [    0.512446] NET: Registered protocol family 2
Jul 27 06:39:12 node-1 kernel: [    0.512742] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.513126] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.513293] TCP: Hash tables configured (established 262144 bind 65536)
Jul 27 06:39:12 node-1 kernel: [    0.513338] TCP: reno registered
Jul 27 06:39:12 node-1 kernel: [    0.513371] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.513478] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.513639] NET: Registered protocol family 1
Jul 27 06:39:12 node-1 kernel: [    0.552478] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 27 06:39:12 node-1 kernel: [    0.552492] PCI: CLS 64 bytes, default 64
Jul 27 06:39:12 node-1 kernel: [    0.552583] Trying to unpack rootfs image as initramfs...
Jul 27 06:39:12 node-1 kernel: [    0.774246] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Jul 27 06:39:12 node-1 kernel: [    0.774307] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 27 06:39:12 node-1 kernel: [    0.774317] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 27 06:39:12 node-1 kernel: [    0.774918] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.774925] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.774932] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.774939] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.774951] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.774966] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.774995] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775002] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775010] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775017] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775024] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775030] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775037] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775044] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775051] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775057] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 06:39:12 node-1 kernel: [    0.775132] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 27 06:39:12 node-1 kernel: [    0.775135] Scanning for low memory corruption every 60 seconds
Jul 27 06:39:12 node-1 kernel: [    0.775493] Initialise system trusted keyring
Jul 27 06:39:12 node-1 kernel: [    0.775541] audit: initializing netlink socket (disabled)
Jul 27 06:39:12 node-1 kernel: [    0.775551] type=2000 audit(1469601516.728:1): initialized
Jul 27 06:39:12 node-1 kernel: [    0.793455] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 27 06:39:12 node-1 kernel: [    0.794901] zbud: loaded
Jul 27 06:39:12 node-1 kernel: [    0.795020] VFS: Disk quotas dquot_6.5.2
Jul 27 06:39:12 node-1 kernel: [    0.795057] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 27 06:39:12 node-1 kernel: [    0.795408] fuse init (API version 7.22)
Jul 27 06:39:12 node-1 kernel: [    0.795458] msgmni has been set to 32768
Jul 27 06:39:12 node-1 kernel: [    0.795503] Key type big_key registered
Jul 27 06:39:12 node-1 kernel: [    0.796006] Key type asymmetric registered
Jul 27 06:39:12 node-1 kernel: [    0.796008] Asymmetric key parser 'x509' registered
Jul 27 06:39:12 node-1 kernel: [    0.796035] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 27 06:39:12 node-1 kernel: [    0.796103] io scheduler noop registered
Jul 27 06:39:12 node-1 kernel: [    0.796104] io scheduler deadline registered (default)
Jul 27 06:39:12 node-1 kernel: [    0.796132] io scheduler cfq registered
Jul 27 06:39:12 node-1 kernel: [    0.796468] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    0.796594] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    0.796721] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    0.796837] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    0.796965] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    0.797056] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    0.797445] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 27 06:39:12 node-1 kernel: [    0.797478] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 27 06:39:12 node-1 kernel: [    0.797494] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 27 06:39:12 node-1 kernel: [    0.797507] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797509] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797512] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 27 06:39:12 node-1 kernel: [    0.797517] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797518] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797519] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797521] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797523] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797524] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797526] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797527] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797529] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797530] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797531] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797533] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797535] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 27 06:39:12 node-1 kernel: [    0.797549] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797551] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 27 06:39:12 node-1 kernel: [    0.797562] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797565] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 27 06:39:12 node-1 kernel: [    0.797576] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797578] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 27 06:39:12 node-1 kernel: [    0.797581] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 27 06:39:12 node-1 kernel: [    0.797610] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 27 06:39:12 node-1 kernel: [    0.797616] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 27 06:39:12 node-1 kernel: [    0.797620] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 27 06:39:12 node-1 kernel: [    0.797628] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 27 06:39:12 node-1 kernel: [    0.797665] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 27 06:39:12 node-1 kernel: [    0.797667] vesafb: scrolling: redraw
Jul 27 06:39:12 node-1 kernel: [    0.797668] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 27 06:39:12 node-1 kernel: [    0.818463] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 27 06:39:12 node-1 kernel: [    0.826969] Console: switching to colour frame buffer device 80x30
Jul 27 06:39:12 node-1 kernel: [    0.835634] fb0: VESA VGA frame buffer device
Jul 27 06:39:12 node-1 kernel: [    0.835835] intel_idle: MWAIT substates: 0x2120
Jul 27 06:39:12 node-1 kernel: [    0.835836] intel_idle: v0.4 model 0x3F
Jul 27 06:39:12 node-1 kernel: [    0.835836] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 27 06:39:12 node-1 kernel: [    0.836079] ipmi message handler version 39.2
Jul 27 06:39:12 node-1 kernel: [    0.836366] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 27 06:39:12 node-1 kernel: [    0.836799] ACPI: AC Adapter [P111] (on-line)
Jul 27 06:39:12 node-1 kernel: [    0.842051] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 27 06:39:12 node-1 kernel: [    0.853060] ACPI: Power Button [PWRB]
Jul 27 06:39:12 node-1 kernel: [    0.858835] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 27 06:39:12 node-1 kernel: [    0.870467] ACPI: Power Button [PWRF]
Jul 27 06:39:12 node-1 kernel: [    0.889917] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 27 06:39:12 node-1 kernel: [    0.901557] pstore: Registered erst as persistent store backend
Jul 27 06:39:12 node-1 kernel: [    0.907741] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 27 06:39:12 node-1 kernel: [    0.919644] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 27 06:39:12 node-1 kernel: [    0.946376] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 27 06:39:12 node-1 kernel: [    0.979628] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 27 06:39:12 node-1 kernel: [    0.993681] Linux agpgart interface v0.103
Jul 27 06:39:12 node-1 kernel: [    1.001376] brd: module loaded
Jul 27 06:39:12 node-1 kernel: [    1.008441] loop: module loaded
Jul 27 06:39:12 node-1 kernel: [    1.015193] libphy: Fixed MDIO Bus: probed
Jul 27 06:39:12 node-1 kernel: [    1.021703] tun: Universal TUN/TAP device driver, 1.6
Jul 27 06:39:12 node-1 kernel: [    1.028212] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 27 06:39:12 node-1 kernel: [    1.034765] PPP generic driver version 2.4.2
Jul 27 06:39:12 node-1 kernel: [    1.041183] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 27 06:39:12 node-1 kernel: [    1.047649] ehci-pci: EHCI PCI platform driver
Jul 27 06:39:12 node-1 kernel: [    1.054214] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 27 06:39:12 node-1 kernel: [    1.060707] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 27 06:39:12 node-1 kernel: [    1.073413] ehci-pci 0000:00:1a.0: debug port 2
Jul 27 06:39:12 node-1 kernel: [    1.083736] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 27 06:39:12 node-1 kernel: [    1.083755] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 27 06:39:12 node-1 kernel: [    1.099874] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 27 06:39:12 node-1 kernel: [    1.105970] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 06:39:12 node-1 kernel: [    1.112146] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 06:39:12 node-1 kernel: [    1.124057] usb usb1: Product: EHCI Host Controller
Jul 27 06:39:12 node-1 kernel: [    1.130091] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 06:39:12 node-1 kernel: [    1.136141] usb usb1: SerialNumber: 0000:00:1a.0
Jul 27 06:39:12 node-1 kernel: [    1.142096] hub 1-0:1.0: USB hub found
Jul 27 06:39:12 node-1 kernel: [    1.147868] hub 1-0:1.0: 2 ports detected
Jul 27 06:39:12 node-1 kernel: [    1.153676] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 27 06:39:12 node-1 kernel: [    1.159265] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 27 06:39:12 node-1 kernel: [    1.170174] ehci-pci 0000:00:1d.0: debug port 2
Jul 27 06:39:12 node-1 kernel: [    1.179479] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 27 06:39:12 node-1 kernel: [    1.179482] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 27 06:39:12 node-1 kernel: [    1.195792] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 27 06:39:12 node-1 kernel: [    1.200988] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 06:39:12 node-1 kernel: [    1.206291] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 06:39:12 node-1 kernel: [    1.216856] usb usb2: Product: EHCI Host Controller
Jul 27 06:39:12 node-1 kernel: [    1.222315] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 06:39:12 node-1 kernel: [    1.227877] usb usb2: SerialNumber: 0000:00:1d.0
Jul 27 06:39:12 node-1 kernel: [    1.233401] hub 2-0:1.0: USB hub found
Jul 27 06:39:12 node-1 kernel: [    1.238755] hub 2-0:1.0: 2 ports detected
Jul 27 06:39:12 node-1 kernel: [    1.244167] ehci-platform: EHCI generic platform driver
Jul 27 06:39:12 node-1 kernel: [    1.249435] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 27 06:39:12 node-1 kernel: [    1.254748] ohci-pci: OHCI PCI platform driver
Jul 27 06:39:12 node-1 kernel: [    1.260051] ohci-platform: OHCI generic platform driver
Jul 27 06:39:12 node-1 kernel: [    1.265252] uhci_hcd: USB Universal Host Controller Interface driver
Jul 27 06:39:12 node-1 kernel: [    1.270606] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 27 06:39:12 node-1 kernel: [    1.463571] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 27 06:39:12 node-1 kernel: [    1.631727] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 27 06:39:12 node-1 kernel: [    1.637255] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 06:39:12 node-1 kernel: [    1.642995] hub 1-1:1.0: USB hub found
Jul 27 06:39:12 node-1 kernel: [    1.648463] hub 1-1:1.0: 6 ports detected
Jul 27 06:39:12 node-1 kernel: [    1.763309] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 27 06:39:12 node-1 kernel: [    1.795281] tsc: Refined TSC clocksource calibration: 3491.912 MHz
Jul 27 06:39:12 node-1 kernel: [    2.035384] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 27 06:39:12 node-1 kernel: [    2.040924] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 06:39:12 node-1 kernel: [    2.046778] hub 2-1:1.0: USB hub found
Jul 27 06:39:12 node-1 kernel: [    2.052371] hub 2-1:1.0: 8 ports detected
Jul 27 06:39:12 node-1 kernel: [    2.312616] i8042: No controller found
Jul 27 06:39:12 node-1 kernel: [    2.318050] mousedev: PS/2 mouse device common for all mice
Jul 27 06:39:12 node-1 kernel: [    2.323575] rtc_cmos 00:02: RTC can wake from S4
Jul 27 06:39:12 node-1 kernel: [    2.329161] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 27 06:39:12 node-1 kernel: [    2.330901] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 27 06:39:12 node-1 kernel: [    2.340293] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 27 06:39:12 node-1 kernel: [    2.351387] device-mapper: uevent: version 1.0.3
Jul 27 06:39:12 node-1 kernel: [    2.357024] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 27 06:39:12 node-1 kernel: [    2.368244] ledtrig-cpu: registered to indicate activity on CPUs
Jul 27 06:39:12 node-1 kernel: [    2.374169] TCP: cubic registered
Jul 27 06:39:12 node-1 kernel: [    2.380052] NET: Registered protocol family 10
Jul 27 06:39:12 node-1 kernel: [    2.386039] NET: Registered protocol family 17
Jul 27 06:39:12 node-1 kernel: [    2.391716] Key type dns_resolver registered
Jul 27 06:39:12 node-1 kernel: [    2.397679] Loading compiled-in X.509 certificates
Jul 27 06:39:12 node-1 kernel: [    2.403832] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 27 06:39:12 node-1 kernel: [    2.415219] registered taskstats version 1
Jul 27 06:39:12 node-1 kernel: [    2.423174] Key type trusted registered
Jul 27 06:39:12 node-1 kernel: [    2.430732] Key type encrypted registered
Jul 27 06:39:12 node-1 kernel: [    2.436209] AppArmor: AppArmor sha1 policy hashing enabled
Jul 27 06:39:12 node-1 kernel: [    2.441700] IMA: No TPM chip found, activating TPM-bypass!
Jul 27 06:39:12 node-1 kernel: [    2.447878] regulator-dummy: disabling
Jul 27 06:39:12 node-1 kernel: [    2.453442]   Magic number: 8:251:621
Jul 27 06:39:12 node-1 kernel: [    2.459123] rtc_cmos 00:02: setting system clock to 2016-07-27 06:38:39 UTC (1469601519)
Jul 27 06:39:12 node-1 kernel: [    2.463093] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 27 06:39:12 node-1 kernel: [    2.463095] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 27 06:39:12 node-1 kernel: [    2.463096] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 27 06:39:12 node-1 kernel: [    2.463096] usb 2-1.4: Manufacturer: Avocent
Jul 27 06:39:12 node-1 kernel: [    2.463097] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 27 06:39:12 node-1 kernel: [    2.506010] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 27 06:39:12 node-1 kernel: [    2.511785] EDD information not available.
Jul 27 06:39:12 node-1 kernel: [    2.517463] PM: Hibernation image not present or could not be loaded.
Jul 27 06:39:12 node-1 kernel: [    2.518326] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 27 06:39:12 node-1 kernel: [    2.529692] Write protecting the kernel read-only data: 12288k
Jul 27 06:39:12 node-1 kernel: [    2.535991] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 27 06:39:12 node-1 kernel: [    2.548534] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 27 06:39:12 node-1 kernel: [    2.579808] device-mapper: multipath: version 1.6.0 loaded
Jul 27 06:39:12 node-1 kernel: [    2.587821] systemd-udevd[215]: starting version 204
Jul 27 06:39:12 node-1 kernel: [    2.612695] md: linear personality registered for level -1
Jul 27 06:39:12 node-1 kernel: [    2.627384] md: multipath personality registered for level -4
Jul 27 06:39:12 node-1 kernel: [    2.635339] md: raid0 personality registered for level 0
Jul 27 06:39:12 node-1 kernel: [    2.643641] md: raid1 personality registered for level 1
Jul 27 06:39:12 node-1 kernel: [    2.653439] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 27 06:39:12 node-1 kernel: [    2.659803] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 27 06:39:12 node-1 kernel: [    2.666130] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 27 06:39:12 node-1 kernel: [    2.667672] megasas: FW now in Ready state
Jul 27 06:39:12 node-1 kernel: [    2.668188] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.668329] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.668468] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.668617] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.668742] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.668857] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.668994] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669074] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669171] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669260] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669407] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669501] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669642] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669820] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.669915] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.670040] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.670753] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 27 06:39:12 node-1 kernel: [    2.691745] hidraw: raw HID events driver (C) Jiri Kosina
Jul 27 06:39:12 node-1 kernel: [    2.700026] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 27 06:39:12 node-1 kernel: [    2.706469] usbcore: registered new interface driver usbhid
Jul 27 06:39:12 node-1 kernel: [    2.706501] usbhid: USB HID core driver
Jul 27 06:39:12 node-1 kernel: [    2.718544] raid6: sse2x1   10154 MB/s
Jul 27 06:39:12 node-1 kernel: [    2.732151] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 06:39:12 node-1 kernel: [    2.745346] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 06:39:12 node-1 kernel: [    2.752084] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.752100] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.752105] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.752109] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.752147] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 06:39:12 node-1 kernel: [    2.771592] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 27 06:39:12 node-1 kernel: [    2.784322] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 06:39:12 node-1 kernel: [    2.786551] raid6: sse2x2   13322 MB/s
Jul 27 06:39:12 node-1 kernel: [    2.803803] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 06:39:12 node-1 kernel: [    2.854397] raid6: sse2x4   10497 MB/s
Jul 27 06:39:12 node-1 kernel: [    2.926335] raid6: avx2x1   14939 MB/s
Jul 27 06:39:12 node-1 kernel: [    2.998276] raid6: avx2x2   18883 MB/s
Jul 27 06:39:12 node-1 kernel: [    3.070212] raid6: avx2x4   21372 MB/s
Jul 27 06:39:12 node-1 kernel: [    3.076148] raid6: using algorithm avx2x4 (21372 MB/s)
Jul 27 06:39:12 node-1 kernel: [    3.082100] raid6: using avx2x2 recovery algorithm
Jul 27 06:39:12 node-1 kernel: [    3.088146] megasas:IOC Init cmd success
Jul 27 06:39:12 node-1 kernel: [    3.088147] Switched to clocksource tsc
Jul 27 06:39:12 node-1 kernel: [    3.088915] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.088950] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.088991] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.089026] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.089118] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.097995] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 27 06:39:12 node-1 kernel: [    3.097996] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 06:39:12 node-1 kernel: [    3.097997] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 06:39:12 node-1 kernel: [    3.098062] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.098099] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.098135] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.098172] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.098271] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.105451] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 27 06:39:12 node-1 kernel: [    3.105453] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 06:39:12 node-1 kernel: [    3.105453] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 06:39:12 node-1 kernel: [    3.105518] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.105557] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.105585] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.105614] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.105696] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 06:39:12 node-1 kernel: [    3.110217] megasas: INIT adapter done
Jul 27 06:39:12 node-1 kernel: [    3.155349] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 27 06:39:12 node-1 kernel: [    3.156405] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 27 06:39:12 node-1 kernel: [    3.157247] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 27 06:39:12 node-1 kernel: [    3.158214] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 27 06:39:12 node-1 kernel: [    3.158596] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 27 06:39:12 node-1 kernel: [    3.159463] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 27 06:39:12 node-1 kernel: [    3.186122] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 27 06:39:12 node-1 kernel: [    3.186473] scsi0 : LSI SAS based MegaRAID driver
Jul 27 06:39:12 node-1 kernel: [    3.193572] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 06:39:12 node-1 kernel: [    3.197140] xor: automatically using best checksumming function:
Jul 27 06:39:12 node-1 kernel: [    3.204422] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 06:39:12 node-1 kernel: [    3.208555] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 27 06:39:12 node-1 kernel: [    3.208563] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 27 06:39:12 node-1 kernel: [    3.208875] sd 0:2:0:0: [sda] Write Protect is off
Jul 27 06:39:12 node-1 kernel: [    3.208876] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 27 06:39:12 node-1 kernel: [    3.208947] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 27 06:39:12 node-1 kernel: [    3.234066]    avx       : 36870.000 MB/sec
Jul 27 06:39:12 node-1 kernel: [    3.236362]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 27 06:39:12 node-1 kernel: [    3.238008] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 27 06:39:12 node-1 kernel: [    3.364757] async_tx: api initialized (async)
Jul 27 06:39:12 node-1 kernel: [    3.410617] md: raid6 personality registered for level 6
Jul 27 06:39:12 node-1 kernel: [    3.417699] md: raid5 personality registered for level 5
Jul 27 06:39:12 node-1 kernel: [    3.424540] md: raid4 personality registered for level 4
Jul 27 06:39:12 node-1 kernel: [    3.434297] md: raid10 personality registered for level 10
Jul 27 06:39:12 node-1 kernel: [    3.448437] random: lvm urandom read with 26 bits of entropy available
Jul 27 06:39:12 node-1 kernel: [    3.497298] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Jul 27 06:39:12 node-1 kernel: [    3.644015] bio: create slab <bio-1> at 1
Jul 27 06:39:12 node-1 kernel: [    4.405294] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 06:39:12 node-1 kernel: [    5.044148] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 27 06:39:12 node-1 kernel: [    5.089404] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 27 06:39:12 node-1 kernel: [    5.221073] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 27 06:39:12 node-1 kernel: [    5.261073] random: nonblocking pool is initialized
Jul 27 06:39:12 node-1 kernel: [    5.267599] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 27 06:39:12 node-1 kernel: [    5.326138] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 06:39:12 node-1 kernel: [    5.494847] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 27 06:39:12 node-1 kernel: [    5.535953] XFS (dm-0): Mounting Filesystem
Jul 27 06:39:12 node-1 kernel: [    5.701853] XFS (dm-0): Ending clean mount
Jul 27 06:39:12 node-1 kernel: [    5.775401] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 06:39:12 node-1 kernel: [    5.811202] XFS (dm-1): Mounting Filesystem
Jul 27 06:39:12 node-1 kernel: [    6.041339] XFS (dm-1): Ending clean mount
Jul 27 06:39:12 node-1 kernel: [    7.831241] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 06:39:12 node-1 kernel: [    7.856636] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 06:39:12 node-1 kernel: [    8.029401] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 27 06:39:12 node-1 kernel: [    8.029407] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 27 06:39:12 node-1 kernel: [    8.029412] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 27 06:39:12 node-1 kernel: [    8.029417] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 27 06:39:12 node-1 kernel: [    8.074807] systemd-udevd[776]: starting version 204
Jul 27 06:39:12 node-1 kernel: [    8.305158] power_meter ACPI000D:00: Found ACPI power meter.
Jul 27 06:39:12 node-1 kernel: [    8.305167] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 27 06:39:12 node-1 kernel: [    8.341469] IPMI System Interface driver.
Jul 27 06:39:12 node-1 kernel: [    8.341548] ipmi_si: probing via ACPI
Jul 27 06:39:12 node-1 kernel: [    8.341578] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 27 06:39:12 node-1 kernel: [    8.341579] ipmi_si: Adding ACPI-specified kcs state machine
Jul 27 06:39:12 node-1 kernel: [    8.341614] ipmi_si: probing via SMBIOS
Jul 27 06:39:12 node-1 kernel: [    8.341615] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 06:39:12 node-1 kernel: [    8.341616] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 27 06:39:12 node-1 kernel: [    8.341618] ipmi_si: probing via SPMI
Jul 27 06:39:12 node-1 kernel: [    8.341619] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 06:39:12 node-1 kernel: [    8.341620] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 27 06:39:12 node-1 kernel: [    8.341622] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 27 06:39:12 node-1 kernel: [    8.359429] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 27 06:39:12 node-1 kernel: [    8.359436] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 06:39:12 node-1 kernel: [    8.359439] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 27 06:39:12 node-1 kernel: [    8.359441] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 06:39:12 node-1 kernel: [    8.359509] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 27 06:39:12 node-1 kernel: [    8.367616] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 27 06:39:12 node-1 kernel: [    8.376021] wmi: Mapper loaded
Jul 27 06:39:12 node-1 kernel: [    8.442141] systemd-udevd[805]: renamed network interface eth0 to enp6s0
Jul 27 06:39:12 node-1 kernel: [    8.474035] systemd-udevd[797]: renamed network interface eth2 to enp8s0
Jul 27 06:39:12 node-1 kernel: [    8.479462] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 27 06:39:12 node-1 kernel: [    8.479467] ipmi_si 00:09: IPMI kcs interface initialized
Jul 27 06:39:12 node-1 kernel: [    8.521983] systemd-udevd[817]: renamed network interface eth1 to enp7s0
Jul 27 06:39:12 node-1 kernel: [    8.541953] systemd-udevd[802]: renamed network interface eth3 to enp9s0
Jul 27 06:39:12 node-1 kernel: [    8.794174] type=1400 audit(1469601525.836:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1041 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.794332] type=1400 audit(1469601525.836:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1041 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.794493] type=1400 audit(1469601525.836:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1041 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.794559] type=1400 audit(1469601525.836:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1040 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.794702] type=1400 audit(1469601525.836:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1040 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.794824] type=1400 audit(1469601525.836:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1040 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.825953] type=1400 audit(1469601525.868:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1042 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.826103] type=1400 audit(1469601525.868:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1042 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.826227] type=1400 audit(1469601525.868:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1042 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    8.831971] type=1400 audit(1469601525.872:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1039 comm="apparmor_parser"
Jul 27 06:39:12 node-1 kernel: [    9.375378] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 06:39:12 node-1 kernel: [    9.376443] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 06:39:12 node-1 kernel: [    9.567757] enic 0000:06:00.0 enp6s0: Link UP
Jul 27 06:39:12 node-1 kernel: [    9.568881] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 27 06:39:12 node-1 kernel: [    9.568893] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 27 06:39:12 node-1 kernel: [   18.874522] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 27 06:39:12 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 27 06:39:13 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 27 06:39:13 node-1 kernel: [   37.336102] init: failsafe main process (8400) killed by TERM signal
Jul 27 06:39:13 node-1 dbus[8429]: [system] AppArmor D-Bus mediation is enabled
Jul 27 06:39:14 node-1 kernel: [   37.582631] audit_printk_skb: 30 callbacks suppressed
Jul 27 06:39:14 node-1 kernel: [   37.582633] type=1400 audit(1469601554.081:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8525 comm="apparmor_parser"
Jul 27 06:39:14 node-1 kernel: [   37.582637] type=1400 audit(1469601554.081:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8525 comm="apparmor_parser"
Jul 27 06:39:14 node-1 kernel: [   37.582640] type=1400 audit(1469601554.081:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8525 comm="apparmor_parser"
Jul 27 06:39:14 node-1 kernel: [   37.582865] type=1400 audit(1469601554.081:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8525 comm="apparmor_parser"
Jul 27 06:39:14 node-1 kernel: [   37.582867] type=1400 audit(1469601554.081:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8525 comm="apparmor_parser"
Jul 27 06:39:14 node-1 kernel: [   37.582983] type=1400 audit(1469601554.081:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8525 comm="apparmor_parser"
Jul 27 06:39:14 node-1 kernel: [   37.583292] type=1400 audit(1469601554.081:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8526 comm="apparmor_parser"
Jul 27 06:39:14 node-1 kernel: [   37.659771] type=1400 audit(1469601554.157:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8528 comm="apparmor_parser"
Jul 27 06:39:14 node-1 anacron[8594]: Anacron 2.3 started on 2016-07-27
Jul 27 06:39:14 node-1 anacron[8594]: Will run job `cron.daily' in 5 min.
Jul 27 06:39:14 node-1 anacron[8594]: Will run job `cron.weekly' in 10 min.
Jul 27 06:39:14 node-1 anacron[8594]: Will run job `cron.monthly' in 15 min.
Jul 27 06:39:14 node-1 anacron[8594]: Jobs will be executed sequentially
Jul 27 06:39:14 node-1 cron[8559]: (CRON) INFO (pidfile fd = 3)
Jul 27 06:39:14 node-1 multipathd: path checkers start up
Jul 27 06:39:14 node-1 cron[8647]: (CRON) STARTUP (fork ok)
Jul 27 06:39:14 node-1 cron[8647]: (CRON) INFO (Running @reboot jobs)
Jul 27 06:39:14 node-1 postfix/master[8738]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 27 06:39:17 node-1 puppet-agent[8922]: Reopening log files
Jul 27 06:39:19 node-1 puppet-agent[8922]: Could not request certificate: Connection refused - connect(2)
Jul 27 06:39:32 node-1 puppet-user[9001]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 27 06:39:32 node-1 puppet-user[9001]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Jul 27 06:39:34 node-1 puppet-user[9001]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 27 06:39:34 node-1 puppet-user[9001]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 27 06:39:34 node-1 puppet-user[9001]: Finished catalog run in 1.03 seconds
Jul 27 06:39:35 node-1 multipathd: uevent trigger error
Jul 27 06:39:35 node-1 puppet-user[9436]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 06:39:35 node-1 puppet-user[9436]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 27 06:39:36 node-1 puppet-user[9436]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 27 06:39:36 node-1 puppet-user[9436]: Finished catalog run in 0.07 seconds
Jul 27 06:39:37 node-1 puppet-user[9906]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 27 06:39:37 node-1 puppet-user[9906]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 27 06:39:37 node-1 puppet-user[9906]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 27 06:39:37 node-1 puppet-user[9906]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 27 06:39:37 node-1 puppet-user[9906]: Finished catalog run in 0.03 seconds
Jul 27 06:39:39 node-1 puppet-user[10368]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 27 06:39:39 node-1 puppet-user[10368]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 27 06:39:39 node-1 puppet-user[10368]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 27 06:39:39 node-1 puppet-user[10368]: Finished catalog run in 0.03 seconds
Jul 27 06:39:40 node-1 puppet-user[10824]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 27 06:39:41 node-1 puppet-user[10824]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Jul 27 06:39:41 node-1 puppet-user[10824]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 27 06:39:42 node-1 puppet-user[10824]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Jul 27 06:39:42 node-1 puppet-user[10824]: Finished catalog run in 1.60 seconds
Jul 27 06:39:43 node-1 puppet-user[11375]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 27 06:39:44 node-1 puppet-user[11375]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Jul 27 06:39:44 node-1 puppet-user[11375]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 27 06:39:44 node-1 puppet-user[11375]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Jul 27 06:39:44 node-1 puppet-user[11375]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 27 06:39:44 node-1 puppet-user[11375]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 27 06:39:44 node-1 puppet-user[11375]: Finished catalog run in 0.23 seconds
Jul 27 06:39:45 node-1 puppet-user[11964]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 27 06:39:46 node-1 puppet-user[11964]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 27 06:39:46 node-1 puppet-user[11964]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 27 06:39:46 node-1 kernel: [   69.638476] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 27 06:39:46 node-1 kernel: [   69.638525] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 27 06:39:46 node-1 puppet-user[11964]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 27 06:39:46 node-1 puppet-user[11964]: Finished catalog run in 0.05 seconds
Jul 27 06:39:47 node-1 puppet-user[12425]: (Scope(Class[main])) MODULAR: sync_time
Jul 27 06:39:47 node-1 puppet-user[12425]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 27 06:39:48 node-1 ntpdate[12845]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 27 06:39:54 node-1 ntpdate[12845]: adjust time server 10.20.0.2 offset 0.283339 sec
Jul 27 06:39:54 node-1 puppet-user[12425]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 27 06:39:54 node-1 puppet-user[12425]: Finished catalog run in 6.17 seconds
Jul 27 06:39:58 node-1 puppet-user[13232]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 06:39:59 node-1 puppet-user[13232]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 27 06:39:59 node-1 puppet-user[13232]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 27 06:39:59 node-1 puppet-user[13232]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 27 06:39:59 node-1 puppet-user[13232]: Finished catalog run in 0.09 seconds
Jul 27 06:40:00 node-1 puppet-user[13694]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 27 06:40:01 node-1 CRON[14140]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 27 06:40:01 node-1 puppet-user[13694]: Compiled catalog for node-1.domain.tld in environment production in 1.20 seconds
Jul 27 06:40:01 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 27 06:40:01 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 27 06:40:01 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 27 06:40:01 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 27 06:40:01 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 27 06:40:02 node-1 puppet-user[13694]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 27 06:40:08 node-1 kernel: [   91.585805] init: plymouth-upstart-bridge main process ended, respawning
Jul 27 06:40:08 node-1 puppet-agent[8922]: Could not run: SIGTERM
Jul 27 06:40:08 node-1 kernel: [   92.081119] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 27 06:40:08 node-1 ec2: 
Jul 27 06:40:08 node-1 ec2: #############################################################
Jul 27 06:40:08 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 27 06:40:08 node-1 ec2: 1024 cf:3c:6e:4d:ba:60:5d:14:eb:0d:4a:92:1e:3a:c9:3e  root@node-1.domain.tld (DSA)
Jul 27 06:40:08 node-1 ec2: 256 f7:d1:ad:15:8f:4e:c7:2e:f3:c2:be:45:8d:61:c8:92  root@node-1.domain.tld (ECDSA)
Jul 27 06:40:08 node-1 ec2: 256 3f:be:58:b9:08:d8:f4:73:a1:48:ba:48:e6:4a:87:a2  root@node-1.domain.tld (ED25519)
Jul 27 06:40:08 node-1 ec2: 2048 30:90:5b:65:53:86:bc:13:03:61:a0:a9:98:8b:20:72  root@node-1.domain.tld (RSA)
Jul 27 06:40:08 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 27 06:40:08 node-1 ec2: #############################################################
Jul 27 06:40:14 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 06:40:14 node-1 nailgun-agent: D, [2016-07-27T06:40:01.666078 #14143] DEBUG -- : Sleep for 13 seconds before sending request
Jul 27 06:40:14 node-1 nailgun-agent: I, [2016-07-27T06:40:14.680894 #14143]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 06:40:15 node-1 nailgun-agent: D, [2016-07-27T06:40:15.130807 #14143] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 27 06:40:18 node-1 puppet-user[13694]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 27 06:40:18 node-1 puppet-user[13694]: Finished catalog run in 16.90 seconds
Jul 27 06:40:20 node-1 puppet-user[15002]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 27 06:40:20 node-1 puppet-user[15002]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Jul 27 06:40:25 node-1 puppet-user[15002]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.513269 #14143] DEBUG -- : Trying to find block devices
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.513499 #14143] DEBUG -- : Found block device: sda
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.513610 #14143] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.513677 #14143] DEBUG -- : Trying to get list of physical devices
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.514087 #14143] DEBUG -- : Getting udev properties for device: sda
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.518011 #14143] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc788
Jul 27 06:40:27 node-1 nailgun-agent: 6005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95645", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.518087 #14143] DEBUG -- : Trying to find out if device sda is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.518199 #14143] DEBUG -- : Device sda removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.518294 #14143] DEBUG -- : Device sda seems to be appropriate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.519505 #14143] DEBUG -- : Getting udev properties for device: dm-0
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.523015 #14143] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-2c0c7xtdaPPqt4Z6dh0cG8Dzajbi2lcD5xotUG5Kab3jyDrBJpuLP0MRtXGLpusS /dev/disk/by-uuid/302c3dea-4198-4cc5-a77c-5ff81a873c1d /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-2c0c7xtdaPPqt4Z6dh0cG8Dzajbi2lcD5xotUG5Kab3jyDrBJpuLP0MRtXGLpusS", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"302c3dea-4198-4cc5-a77c-5ff81a873c1d", "ID_FS_UUID_ENC"=>"302c3dea-4198-4cc5-a77c-5ff81a873c1d", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2208", "nomdmonddf"=>"1", "nomd
Jul 27 06:40:27 node-1 nailgun-agent: monisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.523092 #14143] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.523180 #14143] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.523221 #14143] DEBUG -- : Device dm-0 seems to be appropriate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.523263 #14143] DEBUG -- : Getting udev properties for device: dm-1
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.527146 #14143] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-DXT1oWzrUQ7w0DlogLGjwG0l8logrIOH6oDIfEpucBwUettLLrhDKGTxKsnLkEGp /dev/disk/by-uuid/c2c41dd9-0b34-41b6-831e-264ff3951938 /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-DXT1oWzrUQ7w0DlogLGjwG0l8logrIOH6oDIfEpucBwUettLLrhDKGTxKsnLkEGp", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c2c41dd9-0b34-41b6-831e-264ff3951938", "ID_FS_UUID_ENC"=>"c2c41dd9-0b34-41b6-831e-264ff3951938", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Jul 27 06:40:27 node-1 nailgun-agent: 7253", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.527227 #14143] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.527316 #14143] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.527430 #14143] DEBUG -- : Device dm-1 seems to be appropriate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.527472 #14143] DEBUG -- : Getting udev properties for device: dm-2
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.531522 #14143] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-ARntDhTwEbDd0EwCEjE63MffDM2mzXjbKwtIAM7W0aDlNNAAn8WhigjsbfQVVJfI /dev/disk/by-uuid/6313dcc2-b128-4fc1-884b-c4c8c5ef7821 /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-ARntDhTwEbDd0EwCEjE63MffDM2mzXjbKwtIAM7W0aDlNNAAn8WhigjsbfQVVJfI", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6313dcc2-b128-4fc1-884b-c4c8c5ef7821", "ID_FS_UUID_ENC"=>"6313dcc2-b128-4fc1-884b-c4c8c5ef7821", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38387", "nomdmon
Jul 27 06:40:27 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.531598 #14143] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.531684 #14143] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.531724 #14143] DEBUG -- : Device dm-2 seems to be appropriate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.531767 #14143] DEBUG -- : Getting udev properties for device: dm-3
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.535830 #14143] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-6yjf659flCtsVSMU7ZrqQdcsRsPgjSzc8U8b8tSUfs3ZvhFOGzrARIfOEFesJYtw /dev/disk/by-uuid/0f8afcb8-cc92-42fc-b2e1-654ff021e523 /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-6yjf659flCtsVSMU7ZrqQdcsRsPgjSzc8U8b8tSUfs3ZvhFOGzrARIfOEFesJYtw", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0f8afcb8-cc92-42fc-b2e1-654ff021e523", "ID_FS_UUID_ENC"=>"0f8afcb8-cc92-42fc-b2e1-654ff021e523", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38009", "nomdmonddf"=>"1",
Jul 27 06:40:27 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.535969 #14143] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.536056 #14143] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.536095 #14143] DEBUG -- : Device dm-3 seems to be appropriate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.536136 #14143] DEBUG -- : Getting udev properties for device: dm-4
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.540133 #14143] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-Bo89TpzntdQy1L9OfGZ4mAdOI0Q0AHohViTPeFpC4pnAqkpT0P5mX7fh0R3gItH7 /dev/disk/by-uuid/c7d749c3-34ee-4112-aa45-7daa1505d11d /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-Bo89TpzntdQy1L9OfGZ4mAdOI0Q0AHohViTPeFpC4pnAqkpT0P5mX7fh0R3gItH7", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c7d749c3-34ee-4112-aa45-7daa1505d11d", "ID_FS_UUID_ENC"=>"c7d749c3-34ee-4112-aa45-7daa1505d11d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38630", "nomdmonddf"=>"1", "nom
Jul 27 06:40:27 node-1 nailgun-agent: dmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.540193 #14143] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.540260 #14143] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.540336 #14143] DEBUG -- : Device dm-4 seems to be appropriate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.540368 #14143] DEBUG -- : Getting udev properties for device: dm-5
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.544251 #14143] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-Bo89TpzntdQy1L9OfGZ4mAdOI0Q0AHohlClO7LKtacfOPGGRIgKf6PfuUEy2WPdX /dev/disk/by-uuid/00784a0f-30d5-45bd-a49c-df03653efc51 /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-Bo89TpzntdQy1L9OfGZ4mAdOI0Q0AHohlClO7LKtacfOPGGRIgKf6PfuUEy2WPdX", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"00784a0f-30d5-45bd-a49c-df03653efc51", "ID_FS_UUID_ENC"=>"00784a0f-30d5-45bd-a49c-df03653efc51", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38954", "nomdmonddf"=>"1", "nomdmonisw
Jul 27 06:40:27 node-1 nailgun-agent: "=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.544306 #14143] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.544456 #14143] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.544487 #14143] DEBUG -- : Device dm-5 seems to be appropriate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.544519 #14143] DEBUG -- : Getting udev properties for device: ram0
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.548136 #14143] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28084", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.548196 #14143] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.548282 #14143] DEBUG -- : Device ram0 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.548327 #14143] DEBUG -- : Getting udev properties for device: ram1
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.551890 #14143] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28101", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.551963 #14143] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.552062 #14143] DEBUG -- : Device ram1 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.552119 #14143] DEBUG -- : Getting udev properties for device: ram2
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.555785 #14143] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28196", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.555859 #14143] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.555956 #14143] DEBUG -- : Device ram2 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.556013 #14143] DEBUG -- : Getting udev properties for device: ram3
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.559733 #14143] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28212", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.559841 #14143] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.559929 #14143] DEBUG -- : Device ram3 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.559988 #14143] DEBUG -- : Getting udev properties for device: ram4
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.563712 #14143] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28225", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.563787 #14143] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.563923 #14143] DEBUG -- : Device ram4 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.563974 #14143] DEBUG -- : Getting udev properties for device: ram5
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.567724 #14143] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28239", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.567816 #14143] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.567949 #14143] DEBUG -- : Device ram5 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.568069 #14143] DEBUG -- : Getting udev properties for device: ram6
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.571698 #14143] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28255", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.571763 #14143] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.571883 #14143] DEBUG -- : Device ram6 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.571935 #14143] DEBUG -- : Getting udev properties for device: ram7
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.575648 #14143] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28269", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.575756 #14143] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.575850 #14143] DEBUG -- : Device ram7 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.575907 #14143] DEBUG -- : Getting udev properties for device: ram8
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.579650 #14143] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28287", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.579722 #14143] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.579817 #14143] DEBUG -- : Device ram8 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.579875 #14143] DEBUG -- : Getting udev properties for device: ram9
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.583632 #14143] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28303", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.583706 #14143] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.583815 #14143] DEBUG -- : Device ram9 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.583912 #14143] DEBUG -- : Getting udev properties for device: loop0
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.587609 #14143] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27961", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.587713 #14143] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.587801 #14143] DEBUG -- : Device loop0 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.587852 #14143] DEBUG -- : Getting udev properties for device: loop1
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.591573 #14143] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27976", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.591637 #14143] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.591724 #14143] DEBUG -- : Device loop1 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.591777 #14143] DEBUG -- : Getting udev properties for device: loop2
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.595409 #14143] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27989", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.595476 #14143] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.595590 #14143] DEBUG -- : Device loop2 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.595643 #14143] DEBUG -- : Getting udev properties for device: loop3
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.599442 #14143] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28017", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.599523 #14143] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.599627 #14143] DEBUG -- : Device loop3 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.599706 #14143] DEBUG -- : Getting udev properties for device: loop4
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.603345 #14143] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28035", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.603482 #14143] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.603585 #14143] DEBUG -- : Device loop4 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.603638 #14143] DEBUG -- : Getting udev properties for device: loop5
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.607302 #14143] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28050", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.607384 #14143] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.607467 #14143] DEBUG -- : Device loop5 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.607555 #14143] DEBUG -- : Getting udev properties for device: loop6
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.611179 #14143] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28063", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.611283 #14143] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.611377 #14143] DEBUG -- : Device loop6 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.611444 #14143] DEBUG -- : Getting udev properties for device: loop7
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.614624 #14143] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28074", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.614700 #14143] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.614853 #14143] DEBUG -- : Device loop7 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.614904 #14143] DEBUG -- : Getting udev properties for device: ram10
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.617830 #14143] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28113", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.617907 #14143] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.618009 #14143] DEBUG -- : Device ram10 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.618084 #14143] DEBUG -- : Getting udev properties for device: ram11
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.621020 #14143] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28129", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.621086 #14143] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.621174 #14143] DEBUG -- : Device ram11 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.621315 #14143] DEBUG -- : Getting udev properties for device: ram12
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.624263 #14143] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28143", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.624326 #14143] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.624429 #14143] DEBUG -- : Device ram12 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.624480 #14143] DEBUG -- : Getting udev properties for device: ram13
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.628292 #14143] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28156", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.628341 #14143] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.628402 #14143] DEBUG -- : Device ram13 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.628440 #14143] DEBUG -- : Getting udev properties for device: ram14
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.631603 #14143] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28171", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.631649 #14143] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.631709 #14143] DEBUG -- : Device ram14 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.631766 #14143] DEBUG -- : Getting udev properties for device: ram15
Jul 27 06:40:27 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.634632 #14143] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28184", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.634677 #14143] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.634770 #14143] DEBUG -- : Device ram15 removable parameter: "0"
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642363 #14143] 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"}]
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642393 #14143] DEBUG -- : Block device seems to be physical data storage: sda
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642448 #14143] DEBUG -- : Found block device: dm-0
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642475 #14143] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642498 #14143] DEBUG -- : Found block device: dm-1
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642517 #14143] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642532 #14143] DEBUG -- : Found block device: dm-2
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642550 #14143] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642565 #14143] DEBUG -- : Found block device: dm-3
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642633 #14143] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642649 #14143] DEBUG -- : Found block device: dm-4
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642667 #14143] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642681 #14143] DEBUG -- : Found block device: dm-5
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642698 #14143] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642712 #14143] DEBUG -- : Found block device: ram0
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642730 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642744 #14143] DEBUG -- : Found block device: ram1
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642762 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642841 #14143] DEBUG -- : Found block device: ram2
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642859 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642874 #14143] DEBUG -- : Found block device: ram3
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642890 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642904 #14143] DEBUG -- : Found block device: ram4
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642922 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642936 #14143] DEBUG -- : Found block device: ram5
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642961 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.642976 #14143] DEBUG -- : Found block device: ram6
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643059 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643076 #14143] DEBUG -- : Found block device: ram7
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643092 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643106 #14143] DEBUG -- : Found block device: ram8
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643125 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643139 #14143] DEBUG -- : Found block device: ram9
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643156 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643170 #14143] DEBUG -- : Found block device: loop0
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643186 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643200 #14143] DEBUG -- : Found block device: loop1
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643276 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643291 #14143] DEBUG -- : Found block device: loop2
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643307 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643321 #14143] DEBUG -- : Found block device: loop3
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643337 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643352 #14143] DEBUG -- : Found block device: loop4
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643369 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643383 #14143] DEBUG -- : Found block device: loop5
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643400 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643471 #14143] DEBUG -- : Found block device: loop6
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643490 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643505 #14143] DEBUG -- : Found block device: loop7
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643521 #14143] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643535 #14143] DEBUG -- : Found block device: ram10
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643552 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643567 #14143] DEBUG -- : Found block device: ram11
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643583 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643597 #14143] DEBUG -- : Found block device: ram12
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643674 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643691 #14143] DEBUG -- : Found block device: ram13
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643708 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643722 #14143] DEBUG -- : Found block device: ram14
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643739 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643754 #14143] DEBUG -- : Found block device: ram15
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643770 #14143] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.643820 #14143] 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}]
Jul 27 06:40:27 node-1 nailgun-agent: D, [2016-07-27T06:40:27.860827 #14143] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 27 06:40:27 node-1 nailgun-agent: I, [2016-07-27T06:40:27.861187 #14143]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 27 06:40:56 node-1 puppet-user[15002]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 27 06:40:56 node-1 puppet-user[15002]: Finished catalog run in 35.16 seconds
Jul 27 06:40:57 node-1 puppet-user[17624]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 27 06:40:58 node-1 puppet-user[17624]: Compiled catalog for node-1.domain.tld in environment production in 0.59 seconds
Jul 27 06:40:58 node-1 puppet-user[17624]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 27 06:40:58 node-1 puppet-user[17624]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 27 06:40:58 node-1 puppet-user[17624]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 27 06:40:58 node-1 puppet-user[17624]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 27 06:40:58 node-1 puppet-user[17624]: Finished catalog run in 0.08 seconds
Jul 27 06:41:00 node-1 puppet-user[18086]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 27 06:41:01 node-1 puppet-user[18086]: Compiled catalog for node-1.domain.tld in environment production in 0.83 seconds
Jul 27 06:41:01 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 27 06:41:01 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 27 06:41:01 node-1 crontab[18530]: (root) LIST (root)
Jul 27 06:41:01 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 27 06:41:01 node-1 crontab[18531]: (root) REPLACE (root)
Jul 27 06:41:01 node-1 CRON[18552]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 27 06:41:03 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 27 06:41:05 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 27 06:41:06 node-1 puppet-user[18086]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 27 06:41:06 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8373" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 06:41:06 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 27 06:41:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:27 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:27 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:27 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:27 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:27 node-1 multipathd: uevent trigger error
<27>Jul 27 06:41:27 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:18 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:18 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:18 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:18 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:18 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:42:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:03 node-1 ntpdate[2397]: no servers can be used, exiting
<27>Jul 27 06:43:34 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:34 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:34 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:35 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:35 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:38 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:38 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:38 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:38 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:38 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:50 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:50 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:50 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:50 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:50 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:43:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:44:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:44:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:44:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:44:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:44:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:06 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 06:45:06 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 06:45:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 06:45:12 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 06:45:17 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 06:45:23 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 06:45:23 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 06:45:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:43 node-1 multipathd: uevent trigger error
<129>Jul 27 06:45:45 node-1 haproxy[22697]: 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>Jul 27 06:45:45 node-1 haproxy[22697]: 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>Jul 27 06:45:46 node-1 haproxy[22701]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:45:46 node-1 haproxy[22701]: proxy mysqld has no server available!
<27>Jul 27 06:45:48 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:48 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:48 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:48 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:48 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:52 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:52 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:52 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:52 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:52 node-1 multipathd: uevent trigger error
<129>Jul 27 06:45:54 node-1 haproxy[25296]: 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>Jul 27 06:45:55 node-1 haproxy[25300]: 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>Jul 27 06:45:55 node-1 haproxy[25300]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:45:55 node-1 haproxy[25300]: proxy mysqld has no server available!
<129>Jul 27 06:45:55 node-1 haproxy[25300]: 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>Jul 27 06:45:56 node-1 haproxy[25300]: 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>Jul 27 06:45:56 node-1 haproxy[25300]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:45:56 node-1 haproxy[25300]: proxy object-storage has no server available!
<27>Jul 27 06:45:57 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:57 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:57 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:57 node-1 multipathd: uevent trigger error
<27>Jul 27 06:45:57 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:00 node-1 haproxy[26702]: 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>Jul 27 06:46:00 node-1 haproxy[26702]: 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>Jul 27 06:46:00 node-1 haproxy[26702]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:00 node-1 haproxy[26702]: proxy neutron has no server available!
<129>Jul 27 06:46:00 node-1 haproxy[26702]: 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>Jul 27 06:46:00 node-1 haproxy[26702]: 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>Jul 27 06:46:01 node-1 haproxy[26707]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:01 node-1 haproxy[26707]: proxy mysqld has no server available!
<129>Jul 27 06:46:01 node-1 haproxy[26707]: 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>Jul 27 06:46:01 node-1 haproxy[26707]: 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>Jul 27 06:46:01 node-1 haproxy[26707]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:01 node-1 haproxy[26707]: proxy object-storage has no server available!
<27>Jul 27 06:46:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:03 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:03 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:05 node-1 haproxy[28130]: 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>Jul 27 06:46:05 node-1 haproxy[28130]: 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>Jul 27 06:46:05 node-1 haproxy[28130]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:05 node-1 haproxy[28130]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:05 node-1 haproxy[28130]: 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>Jul 27 06:46:06 node-1 haproxy[28134]: 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>Jul 27 06:46:06 node-1 haproxy[28134]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:06 node-1 haproxy[28134]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:06 node-1 haproxy[28134]: 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>Jul 27 06:46:06 node-1 haproxy[28134]: 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>Jul 27 06:46:06 node-1 haproxy[28134]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:06 node-1 haproxy[28134]: proxy neutron has no server available!
<129>Jul 27 06:46:06 node-1 haproxy[28134]: 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>Jul 27 06:46:06 node-1 haproxy[28134]: 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>Jul 27 06:46:06 node-1 haproxy[28134]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:06 node-1 haproxy[28134]: proxy mysqld has no server available!
<129>Jul 27 06:46:07 node-1 haproxy[28134]: 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>Jul 27 06:46:07 node-1 haproxy[28134]: 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>Jul 27 06:46:07 node-1 haproxy[28134]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:07 node-1 haproxy[28134]: proxy object-storage has no server available!
<27>Jul 27 06:46:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:08 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:10 node-1 haproxy[29511]: 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>Jul 27 06:46:11 node-1 haproxy[29515]: 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>Jul 27 06:46:11 node-1 haproxy[29515]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:11 node-1 haproxy[29515]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:11 node-1 haproxy[29515]: 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>Jul 27 06:46:11 node-1 haproxy[29515]: 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>Jul 27 06:46:11 node-1 haproxy[29515]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:11 node-1 haproxy[29515]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:11 node-1 haproxy[29515]: 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>Jul 27 06:46:11 node-1 haproxy[29515]: 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>Jul 27 06:46:11 node-1 haproxy[29515]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:11 node-1 haproxy[29515]: proxy neutron has no server available!
<129>Jul 27 06:46:11 node-1 haproxy[29515]: 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>Jul 27 06:46:12 node-1 haproxy[29515]: 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>Jul 27 06:46:12 node-1 haproxy[29515]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:12 node-1 haproxy[29515]: proxy mysqld has no server available!
<129>Jul 27 06:46:12 node-1 haproxy[29515]: 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>Jul 27 06:46:12 node-1 haproxy[29515]: 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>Jul 27 06:46:12 node-1 haproxy[29515]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:12 node-1 haproxy[29515]: proxy object-storage has no server available!
<129>Jul 27 06:46:12 node-1 haproxy[29515]: 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>Jul 27 06:46:12 node-1 haproxy[29515]: 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>Jul 27 06:46:12 node-1 haproxy[29515]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:12 node-1 haproxy[29515]: proxy aodh has no server available!
<27>Jul 27 06:46:14 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:14 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:14 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:14 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:14 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:16 node-1 haproxy[30964]: 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>Jul 27 06:46:16 node-1 haproxy[30964]: 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>Jul 27 06:46:16 node-1 haproxy[30964]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:16 node-1 haproxy[30964]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:16 node-1 haproxy[30964]: 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>Jul 27 06:46:16 node-1 haproxy[30964]: 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>Jul 27 06:46:16 node-1 haproxy[30964]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:16 node-1 haproxy[30964]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:17 node-1 haproxy[30968]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:17 node-1 haproxy[30968]: proxy neutron has no server available!
<129>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:17 node-1 haproxy[30968]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:17 node-1 haproxy[30968]: proxy mysqld has no server available!
<129>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:17 node-1 haproxy[30968]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:17 node-1 haproxy[30968]: proxy object-storage has no server available!
<129>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:17 node-1 haproxy[30968]: 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>Jul 27 06:46:18 node-1 haproxy[30968]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:18 node-1 haproxy[30968]: proxy aodh has no server available!
<129>Jul 27 06:46:18 node-1 haproxy[30968]: 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>Jul 27 06:46:18 node-1 haproxy[30968]: 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>Jul 27 06:46:18 node-1 haproxy[30968]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:18 node-1 haproxy[30968]: proxy ceilometer has no server available!
<27>Jul 27 06:46:19 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:19 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:19 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:19 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:19 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:19 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:21 node-1 haproxy[32329]: 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>Jul 27 06:46:21 node-1 haproxy[32329]: 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>Jul 27 06:46:21 node-1 haproxy[32329]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:21 node-1 haproxy[32329]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:22 node-1 haproxy[32335]: 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>Jul 27 06:46:22 node-1 haproxy[32335]: 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>Jul 27 06:46:22 node-1 haproxy[32335]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:22 node-1 haproxy[32335]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:22 node-1 haproxy[32335]: 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>Jul 27 06:46:22 node-1 haproxy[32335]: 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>Jul 27 06:46:22 node-1 haproxy[32335]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:22 node-1 haproxy[32335]: proxy neutron has no server available!
<129>Jul 27 06:46:22 node-1 haproxy[32335]: 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>Jul 27 06:46:22 node-1 haproxy[32335]: 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>Jul 27 06:46:22 node-1 haproxy[32335]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:22 node-1 haproxy[32335]: proxy mysqld has no server available!
<129>Jul 27 06:46:22 node-1 haproxy[32335]: 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>Jul 27 06:46:23 node-1 haproxy[32335]: 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>Jul 27 06:46:23 node-1 haproxy[32335]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:23 node-1 haproxy[32335]: proxy object-storage has no server available!
<129>Jul 27 06:46:23 node-1 haproxy[32335]: 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>Jul 27 06:46:23 node-1 haproxy[32335]: 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>Jul 27 06:46:23 node-1 haproxy[32335]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:23 node-1 haproxy[32335]: proxy aodh has no server available!
<129>Jul 27 06:46:23 node-1 haproxy[32335]: 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>Jul 27 06:46:23 node-1 haproxy[32335]: 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>Jul 27 06:46:23 node-1 haproxy[32335]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:23 node-1 haproxy[32335]: proxy ceilometer has no server available!
<27>Jul 27 06:46:24 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:24 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:24 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:24 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:24 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:24 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:24 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:27 node-1 haproxy[1264]: 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>Jul 27 06:46:27 node-1 haproxy[1264]: 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>Jul 27 06:46:27 node-1 haproxy[1264]: 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>Jul 27 06:46:27 node-1 haproxy[1264]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:27 node-1 haproxy[1264]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:27 node-1 haproxy[1264]: 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>Jul 27 06:46:27 node-1 haproxy[1264]: 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>Jul 27 06:46:27 node-1 haproxy[1264]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:27 node-1 haproxy[1264]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:27 node-1 haproxy[1264]: 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>Jul 27 06:46:27 node-1 haproxy[1264]: 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>Jul 27 06:46:27 node-1 haproxy[1264]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:27 node-1 haproxy[1264]: proxy neutron has no server available!
<129>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:28 node-1 haproxy[1280]: proxy mysqld has no server available!
<129>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:28 node-1 haproxy[1280]: proxy object-storage has no server available!
<129>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:28 node-1 haproxy[1280]: proxy aodh has no server available!
<129>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: 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>Jul 27 06:46:28 node-1 haproxy[1280]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:28 node-1 haproxy[1280]: proxy ceilometer has no server available!
<27>Jul 27 06:46:30 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:30 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:30 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:30 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:30 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:32 node-1 haproxy[2825]: 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>Jul 27 06:46:32 node-1 haproxy[2825]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:33 node-1 haproxy[2829]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:33 node-1 haproxy[2829]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:33 node-1 haproxy[2829]: proxy glance-api has no server available!
<129>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:33 node-1 haproxy[2829]: proxy glance-glare has no server available!
<129>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:33 node-1 haproxy[2829]: proxy neutron has no server available!
<129>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:33 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:34 node-1 haproxy[2829]: proxy glance-registry has no server available!
<129>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:34 node-1 haproxy[2829]: proxy mysqld has no server available!
<129>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:34 node-1 haproxy[2829]: proxy object-storage has no server available!
<129>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:34 node-1 haproxy[2829]: proxy aodh has no server available!
<129>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: 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>Jul 27 06:46:34 node-1 haproxy[2829]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:34 node-1 haproxy[2829]: proxy ceilometer has no server available!
<27>Jul 27 06:46:35 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:36 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:36 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:36 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:36 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:36 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:38 node-1 haproxy[4252]: 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>Jul 27 06:46:38 node-1 haproxy[4252]: 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>Jul 27 06:46:38 node-1 haproxy[4252]: 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>Jul 27 06:46:38 node-1 haproxy[4252]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:38 node-1 haproxy[4252]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:39 node-1 haproxy[4256]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:39 node-1 haproxy[4256]: proxy nova-api has no server available!
<129>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:39 node-1 haproxy[4256]: proxy nova-metadata-api has no server available!
<129>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:39 node-1 haproxy[4256]: proxy glance-api has no server available!
<129>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:39 node-1 haproxy[4256]: proxy glance-glare has no server available!
<129>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:39 node-1 haproxy[4256]: proxy neutron has no server available!
<129>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: 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>Jul 27 06:46:39 node-1 haproxy[4256]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:39 node-1 haproxy[4256]: proxy glance-registry has no server available!
<129>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:40 node-1 haproxy[4256]: proxy mysqld has no server available!
<129>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:40 node-1 haproxy[4256]: proxy object-storage has no server available!
<129>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:40 node-1 haproxy[4256]: proxy aodh has no server available!
<129>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:40 node-1 haproxy[4256]: proxy ceilometer has no server available!
<129>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: 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>Jul 27 06:46:40 node-1 haproxy[4256]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:40 node-1 haproxy[4256]: proxy nova-novncproxy has no server available!
<27>Jul 27 06:46:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:42 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:44 node-1 haproxy[5575]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:44 node-1 haproxy[5575]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:44 node-1 haproxy[5575]: proxy nova-api has no server available!
<129>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:44 node-1 haproxy[5575]: proxy nova-metadata-api has no server available!
<129>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: 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>Jul 27 06:46:44 node-1 haproxy[5575]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:44 node-1 haproxy[5575]: proxy cinder-api has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:45 node-1 haproxy[5586]: proxy glance-api has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:45 node-1 haproxy[5586]: proxy glance-glare has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:45 node-1 haproxy[5586]: proxy neutron has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:45 node-1 haproxy[5586]: proxy glance-registry has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:45 node-1 haproxy[5586]: proxy mysqld has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:45 node-1 haproxy[5586]: proxy object-storage has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:45 node-1 haproxy[5586]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:45 node-1 haproxy[5586]: proxy aodh has no server available!
<129>Jul 27 06:46:45 node-1 haproxy[5586]: 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>Jul 27 06:46:46 node-1 haproxy[5586]: 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>Jul 27 06:46:46 node-1 haproxy[5586]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:46 node-1 haproxy[5586]: proxy ceilometer has no server available!
<129>Jul 27 06:46:46 node-1 haproxy[5586]: 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>Jul 27 06:46:46 node-1 haproxy[5586]: 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>Jul 27 06:46:46 node-1 haproxy[5586]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:46 node-1 haproxy[5586]: proxy nova-novncproxy has no server available!
<27>Jul 27 06:46:47 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:47 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:47 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:47 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:47 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:47 node-1 multipathd: uevent trigger error
<129>Jul 27 06:46:49 node-1 haproxy[6986]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy keystone-1 has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy keystone-2 has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy nova-api has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy nova-metadata-api has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy cinder-api has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy glance-api has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy glance-glare has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:50 node-1 haproxy[6990]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:50 node-1 haproxy[6990]: proxy neutron has no server available!
<129>Jul 27 06:46:50 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy glance-registry has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy mysqld has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy object-storage has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy aodh has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy ceilometer has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy heat-api has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy heat-api-cfn has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy heat-api-cloudwatch has no server available!
<129>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: 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>Jul 27 06:46:51 node-1 haproxy[6990]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 06:46:51 node-1 haproxy[6990]: proxy nova-novncproxy has no server available!
<27>Jul 27 06:46:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:56 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:56 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:56 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:56 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:56 node-1 multipathd: uevent trigger error
<27>Jul 27 06:46:56 node-1 multipathd: uevent trigger error
<27>Jul 27 06:47:08 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 06:47:33 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 27 06:47:35 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 27 06:48:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 06:48:06 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 06:48:32 node-1 multipathd: uevent trigger error
<27>Jul 27 06:48:32 node-1 multipathd: uevent trigger error
<27>Jul 27 06:48:32 node-1 multipathd: uevent trigger error
<27>Jul 27 06:48:32 node-1 multipathd: uevent trigger error
<27>Jul 27 06:48:32 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:59 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:59 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:59 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:59 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:59 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:59 node-1 multipathd: uevent trigger error
<27>Jul 27 06:50:59 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 27 06:51:17 node-1 apache2_error [Wed Jul 27 06:51:12.364197 2016] [mpm_event:notice] [pid 16624:tid 140469065561984] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 06:51:17 node-1 apache2_error [Wed Jul 27 06:51:12.364333 2016] [core:notice] [pid 16624:tid 140469065561984] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 06:51:17 node-1 apache2_error [Wed Jul 27 06:51:15.383332 2016] [mpm_event:notice] [pid 16624:tid 140469065561984] AH00491: caught SIGTERM, shutting down
<43>Jul 27 06:51:17 node-1 apache2_error [Wed Jul 27 06:51:16.476894 2016] [mpm_worker:notice] [pid 17007:tid 139809141180288] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 06:51:17 node-1 apache2_error [Wed Jul 27 06:51:16.476962 2016] [core:notice] [pid 17007:tid 139809141180288] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 06:51:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:20 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:25 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:25 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:25 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:25 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:25 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:25 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:29 node-1 multipathd: uevent trigger error
<27>Jul 27 06:51:29 node-1 multipathd: uevent trigger error
<43>Jul 27 06:52:47 node-1 apache2_error [Wed Jul 27 06:52:38.321721 2016] [mpm_worker:notice] [pid 17007:tid 139809141180288] AH00295: caught SIGTERM, shutting down
<43>Jul 27 06:52:47 node-1 apache2_error [Wed Jul 27 06:52:39.066928 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 06:52:47 node-1 apache2_error [Wed Jul 27 06:52:39.066953 2016] [core:notice] [pid 30774:tid 139630806898560] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 06:53:27 node-1 apache2_error [Wed Jul 27 06:53:23.228027 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 06:53:27 node-1 apache2_error [Wed Jul 27 06:53:23.424762 2016] [mpm_worker:warn] [pid 30774:tid 139630806898560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 06:53:27 node-1 apache2_error [Wed Jul 27 06:53:23.429576 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 06:53:27 node-1 apache2_error [Wed Jul 27 06:53:23.429596 2016] [core:notice] [pid 30774:tid 139630806898560] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 06:54:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 06:54:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:08 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:12 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:12 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:12 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:12 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:12 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:28 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:28 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:28 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:28 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:28 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:49 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:54:54 node-1 multipathd: uevent trigger error
<27>Jul 27 06:55:09 node-1 multipathd: uevent trigger error
<27>Jul 27 06:55:09 node-1 multipathd: uevent trigger error
<27>Jul 27 06:55:09 node-1 multipathd: uevent trigger error
<27>Jul 27 06:55:09 node-1 multipathd: uevent trigger error
<27>Jul 27 06:55:09 node-1 multipathd: uevent trigger error
<27>Jul 27 06:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 06:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 06:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 06:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 06:56:01 node-1 multipathd: uevent trigger error
<27>Jul 27 06:57:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 06:57:16 node-1 multipathd: uevent trigger error
<27>Jul 27 06:57:16 node-1 multipathd: uevent trigger error
<27>Jul 27 06:57:16 node-1 multipathd: uevent trigger error
<27>Jul 27 06:57:16 node-1 multipathd: uevent trigger error
<27>Jul 27 06:57:16 node-1 multipathd: uevent trigger error
<27>Jul 27 06:57:16 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:14 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:15 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:15 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:15 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:15 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:15 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:36 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:36 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:37 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:37 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:37 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:42 node-1 multipathd: uevent trigger error
<27>Jul 27 06:58:42 node-1 multipathd: uevent trigger error
<27>Jul 27 07:00:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 07:01:10 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:10 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:10 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:10 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:10 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:10 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:31 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:31 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:31 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:31 node-1 multipathd: uevent trigger error
<27>Jul 27 07:01:31 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:43 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:43 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:43 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:43 node-1 multipathd: uevent trigger error
<27>Jul 27 07:02:43 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 07:03:27 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:27 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:27 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:27 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:27 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:27 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:34 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 27 07:03:34 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 27 07:03:35 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 27 07:03:36 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 27 07:03:36 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 27 07:03:36 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:36 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:36 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:37 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:37 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:37 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:37 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:03:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:04 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:04 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:04 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:04 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:04 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:23 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:23 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:23 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:23 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:23 node-1 multipathd: uevent trigger error
<27>Jul 27 07:04:23 node-1 multipathd: uevent trigger error
<27>Jul 27 07:06:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 07:06:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:06:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:06:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:06:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:06:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:06:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:07:16 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 27 07:08:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:35 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:35 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:35 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:35 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:35 node-1 multipathd: uevent trigger error
<27>Jul 27 07:08:35 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 07:09:18 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:18 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:18 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:18 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:18 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:26 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:09:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:10:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:10:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:10:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:10:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:10:13 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:18 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:18 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:37 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:37 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:37 node-1 multipathd: uevent trigger error
<27>Jul 27 07:11:37 node-1 multipathd: uevent trigger error
<11>Jul 27 07:11:51 node-1 liberasurecode[60797]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:51 node-1 liberasurecode[60797]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:51 node-1 liberasurecode[60797]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:51 node-1 liberasurecode[60797]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:51 node-1 liberasurecode[60821]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:51 node-1 liberasurecode[60821]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:51 node-1 liberasurecode[60821]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:51 node-1 liberasurecode[60821]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:53 node-1 liberasurecode[61262]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:53 node-1 liberasurecode[61262]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:53 node-1 liberasurecode[61262]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:53 node-1 liberasurecode[61262]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:58 node-1 liberasurecode[61926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:58 node-1 liberasurecode[61926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:58 node-1 liberasurecode[61926]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:58 node-1 liberasurecode[61926]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[61964]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[61964]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[61964]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[61964]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62015]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62015]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62015]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62015]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62114]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62114]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62114]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62114]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62128]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62128]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62141]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62141]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62141]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62141]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62158]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:11:59 node-1 liberasurecode[62158]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 07:12:08 node-1 liberasurecode[62823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:12:08 node-1 liberasurecode[62823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:12:08 node-1 liberasurecode[62823]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:12:08 node-1 liberasurecode[62823]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 07:12:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 07:12:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:12:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:12:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:12:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:12:16 node-1 multipathd: uevent trigger error
<43>Jul 27 07:13:09 node-1 apache2_error [Wed Jul 27 07:13:05.110131 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 07:13:09 node-1 apache2_error [Wed Jul 27 07:13:05.495300 2016] [mpm_worker:warn] [pid 30774:tid 139630806898560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 07:13:09 node-1 apache2_error [Wed Jul 27 07:13:05.500334 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 07:13:09 node-1 apache2_error [Wed Jul 27 07:13:05.500382 2016] [core:notice] [pid 30774:tid 139630806898560] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 07:13:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:46 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:46 node-1 multipathd: uevent trigger error
<43>Jul 27 07:13:49 node-1 apache2_error [Wed Jul 27 07:13:42.674255 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 07:13:49 node-1 apache2_error [Wed Jul 27 07:13:43.055430 2016] [mpm_worker:warn] [pid 30774:tid 139630806898560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 07:13:49 node-1 apache2_error [Wed Jul 27 07:13:43.062815 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 07:13:49 node-1 apache2_error [Wed Jul 27 07:13:43.062841 2016] [core:notice] [pid 30774:tid 139630806898560] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 07:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 07:13:54 node-1 multipathd: uevent trigger error
<43>Jul 27 07:14:29 node-1 apache2_error [Wed Jul 27 07:14:28.745820 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 07:14:29 node-1 apache2_error [Wed Jul 27 07:14:28.942903 2016] [mpm_worker:warn] [pid 30774:tid 139630806898560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 07:14:29 node-1 apache2_error [Wed Jul 27 07:14:28.950062 2016] [mpm_worker:notice] [pid 30774:tid 139630806898560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 07:14:29 node-1 apache2_error [Wed Jul 27 07:14:28.950093 2016] [core:notice] [pid 30774:tid 139630806898560] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 07:14:32 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:32 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:32 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:32 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:32 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:39 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:14:45 node-1 multipathd: uevent trigger error
<11>Jul 27 07:15:01 node-1 liberasurecode[95509]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:15:01 node-1 liberasurecode[95509]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:15:01 node-1 liberasurecode[95509]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:15:01 node-1 liberasurecode[95509]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 07:15:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 07:15:22 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:29 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:29 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:29 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:29 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:29 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:29 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:36 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 27 07:15:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:45 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:15:50 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:20 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:24 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:24 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:24 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:24 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:24 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:38 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:38 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:38 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:38 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:38 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:38 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:41 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 07:16:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:56 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:56 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:56 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:56 node-1 multipathd: uevent trigger error
<27>Jul 27 07:16:56 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:01 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:06 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:17:16 node-1 multipathd: uevent trigger error
<27>Jul 27 07:18:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:18:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:18:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:18:51 node-1 multipathd: uevent trigger error
<27>Jul 27 07:18:52 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:00 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:11 node-1 multipathd: uevent trigger error
<27>Jul 27 07:19:11 node-1 multipathd: uevent trigger error
<129>Jul 27 07:19:21 node-1 haproxy[143485]: 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>Jul 27 07:19:21 node-1 haproxy[143485]: 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>Jul 27 07:20:00 node-1 haproxy[143485]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 07:20:00 node-1 haproxy[143485]: proxy neutron has no server available!
<11>Jul 27 07:20:01 node-1 liberasurecode[155455]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:20:01 node-1 liberasurecode[155455]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:20:01 node-1 liberasurecode[155455]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 07:20:01 node-1 liberasurecode[155455]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 07:20:09 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:09 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:09 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:09 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:09 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:14 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:14 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:14 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:14 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:14 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:19 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:30 node-1 multipathd: uevent trigger error
<27>Jul 27 07:20:30 node-1 multipathd: uevent trigger error
