Sep 12 02:00:20 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8396" x-info="http://www.rsyslog.com"] start
Sep 12 02:00:20 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 12 02:00:20 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 12 02:00:20 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 12 02:00:20 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 12 02:00:20 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 12 02:00:20 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 12 02:00:20 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 12 02:00:20 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=fee77217-bde6-4f20-8330-8889fdd31919 nomdmonddf nomdmonisw
Sep 12 02:00:20 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 12 02:00:20 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 12 02:00:20 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 12 02:00:20 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 12 02:00:20 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 12 02:00:20 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 12 02:00:20 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 12 02:00:20 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
Sep 12 02:00:20 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 12 02:00:20 node-1 kernel: [    0.000000] No AGP bridge found
Sep 12 02:00:20 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 12 02:00:20 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 12 02:00:20 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 12 02:00:20 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 12 02:00:20 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 12 02:00:20 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 12 02:00:20 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 12 02:00:20 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 12 02:00:20 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 12 02:00:20 node-1 kernel: [    0.000000]   2 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000]   3 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000]   4 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000]   5 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000]   6 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000]   7 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000]   8 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000]   9 disabled
Sep 12 02:00:20 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 12 02:00:20 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 12 02:00:20 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 12 02:00:20 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 12 02:00:20 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 12 02:00:20 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 12 02:00:20 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 12 02:00:20 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 12 02:00:20 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 12 02:00:20 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 12 02:00:20 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 12 02:00:20 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 12 02:00:20 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 12 02:00:20 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 12 02:00:20 node-1 kernel: [    0.000000] Zone ranges:
Sep 12 02:00:20 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 12 02:00:20 node-1 kernel: [    0.000000] Early memory node ranges
Sep 12 02:00:20 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 12 02:00:20 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 12 02:00:20 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 12 02:00:20 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 12 02:00:20 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 12 02:00:20 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 12 02:00:20 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 12 02:00:20 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 12 02:00:20 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 12 02:00:20 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 12 02:00:20 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 12 02:00:20 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 12 02:00:20 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 12 02:00:20 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 12 02:00:20 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 12 02:00:20 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 12 02:00:20 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 12 02:00:20 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 12 02:00:20 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 12 02:00:20 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 12 02:00:20 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 12 02:00:20 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 12 02:00:20 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 12 02:00:20 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 
Sep 12 02:00:20 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 12 02:00:20 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 12 02:00:20 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=fee77217-bde6-4f20-8330-8889fdd31919 nomdmonddf nomdmonisw
Sep 12 02:00:20 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 12 02:00:20 node-1 kernel: [    0.000000] Checking aperture...
Sep 12 02:00:20 node-1 kernel: [    0.000000] No AGP bridge found
Sep 12 02:00:20 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 12 02:00:20 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 12 02:00:20 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep 12 02:00:20 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 12 02:00:20 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 12 02:00:20 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 12 02:00:20 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 12 02:00:20 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 12 02:00:20 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 12 02:00:20 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 12 02:00:20 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 12 02:00:20 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 12 02:00:20 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 12 02:00:20 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 12 02:00:20 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 12 02:00:20 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 12 02:00:20 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 12 02:00:20 node-1 kernel: [    0.004000] tsc: Detected 3491.910 MHz processor
Sep 12 02:00:20 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.82 BogoMIPS (lpj=13967640)
Sep 12 02:00:20 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 12 02:00:20 node-1 kernel: [    0.000044] Security Framework initialized
Sep 12 02:00:20 node-1 kernel: [    0.000062] AppArmor: AppArmor initialized
Sep 12 02:00:20 node-1 kernel: [    0.000063] Yama: becoming mindful.
Sep 12 02:00:20 node-1 kernel: [    0.001450] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.006347] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.008279] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.008307] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.008597] Initializing cgroup subsys memory
Sep 12 02:00:20 node-1 kernel: [    0.008605] Initializing cgroup subsys devices
Sep 12 02:00:20 node-1 kernel: [    0.008607] Initializing cgroup subsys freezer
Sep 12 02:00:20 node-1 kernel: [    0.008609] Initializing cgroup subsys blkio
Sep 12 02:00:20 node-1 kernel: [    0.008610] Initializing cgroup subsys perf_event
Sep 12 02:00:20 node-1 kernel: [    0.008613] Initializing cgroup subsys hugetlb
Sep 12 02:00:20 node-1 kernel: [    0.008632] CPU: Physical Processor ID: 0
Sep 12 02:00:20 node-1 kernel: [    0.008633] CPU: Processor Core ID: 0
Sep 12 02:00:20 node-1 kernel: [    0.008637] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 12 02:00:20 node-1 kernel: [    0.008637] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 12 02:00:20 node-1 kernel: [    0.009330] mce: CPU supports 22 MCE banks
Sep 12 02:00:20 node-1 kernel: [    0.009358] CPU0: Thermal monitoring enabled (TM1)
Sep 12 02:00:20 node-1 kernel: [    0.009379] process: using mwait in idle threads
Sep 12 02:00:20 node-1 kernel: [    0.009382] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 12 02:00:20 node-1 kernel: [    0.009382] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 12 02:00:20 node-1 kernel: [    0.009382] tlb_flushall_shift: 6
Sep 12 02:00:20 node-1 kernel: [    0.009471] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 12 02:00:20 node-1 kernel: [    0.010194] ACPI: Core revision 20131115
Sep 12 02:00:20 node-1 kernel: [    0.022863] ACPI: All ACPI Tables successfully acquired
Sep 12 02:00:20 node-1 kernel: [    0.023023] ftrace: allocating 28617 entries in 112 pages
Sep 12 02:00:20 node-1 kernel: [    0.031996] dmar: Host address width 46
Sep 12 02:00:20 node-1 kernel: [    0.031999] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 12 02:00:20 node-1 kernel: [    0.032005] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 12 02:00:20 node-1 kernel: [    0.032006] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 12 02:00:20 node-1 kernel: [    0.032010] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 12 02:00:20 node-1 kernel: [    0.032012] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 12 02:00:20 node-1 kernel: [    0.032013] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 12 02:00:20 node-1 kernel: [    0.032014] dmar: ATSR flags: 0x0
Sep 12 02:00:20 node-1 kernel: [    0.032015] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 12 02:00:20 node-1 kernel: [    0.032017] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 12 02:00:20 node-1 kernel: [    0.032132] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 12 02:00:20 node-1 kernel: [    0.032133] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 12 02:00:20 node-1 kernel: [    0.032134] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 12 02:00:20 node-1 kernel: [    0.032136] HPET id 0 under DRHD base 0xc7ffc000
Sep 12 02:00:20 node-1 kernel: [    0.032137] Your BIOS is broken and requested that x2apic be disabled.
Sep 12 02:00:20 node-1 kernel: [    0.032137] This will slightly decrease performance.
Sep 12 02:00:20 node-1 kernel: [    0.032137] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 12 02:00:20 node-1 kernel: [    0.032569] Enabled IRQ remapping in xapic mode
Sep 12 02:00:20 node-1 kernel: [    0.032571] x2apic not enabled, IRQ remapping is in xapic mode
Sep 12 02:00:20 node-1 kernel: [    0.032574] Switched APIC routing to physical flat.
Sep 12 02:00:20 node-1 kernel: [    0.033202] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 12 02:00:20 node-1 kernel: [    0.072852] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 12 02:00:20 node-1 kernel: [    0.072857] TSC deadline timer enabled
Sep 12 02:00:20 node-1 kernel: [    0.072865] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 12 02:00:20 node-1 kernel: [    0.072871] ... version:                3
Sep 12 02:00:20 node-1 kernel: [    0.072872] ... bit width:              48
Sep 12 02:00:20 node-1 kernel: [    0.072872] ... generic registers:      4
Sep 12 02:00:20 node-1 kernel: [    0.072873] ... value mask:             0000ffffffffffff
Sep 12 02:00:20 node-1 kernel: [    0.072874] ... max period:             0000ffffffffffff
Sep 12 02:00:20 node-1 kernel: [    0.072875] ... fixed-purpose events:   3
Sep 12 02:00:20 node-1 kernel: [    0.072876] ... event mask:             000000070000000f
Sep 12 02:00:20 node-1 kernel: [    0.074264] x86: Booting SMP configuration:
Sep 12 02:00:20 node-1 kernel: [    0.088368] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 12 02:00:20 node-1 kernel: [    0.074266] .... node  #0, CPUs:        #1  #2  #3
Sep 12 02:00:20 node-1 kernel: [    0.116275] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 12 02:00:20 node-1 kernel: [    0.270429] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 12 02:00:20 node-1 kernel: [    0.326046] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 12 02:00:20 node-1 kernel: [    0.382896] x86: Booted up 2 nodes, 16 CPUs
Sep 12 02:00:20 node-1 kernel: [    0.382899] smpboot: Total of 16 processors activated (111753.41 BogoMIPS)
Sep 12 02:00:20 node-1 kernel: [    0.406359] devtmpfs: initialized
Sep 12 02:00:20 node-1 kernel: [    0.409492] EVM: security.selinux
Sep 12 02:00:20 node-1 kernel: [    0.409494] EVM: security.SMACK64
Sep 12 02:00:20 node-1 kernel: [    0.409495] EVM: security.ima
Sep 12 02:00:20 node-1 kernel: [    0.409496] EVM: security.capability
Sep 12 02:00:20 node-1 kernel: [    0.409547] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.410238] pinctrl core: initialized pinctrl subsystem
Sep 12 02:00:20 node-1 kernel: [    0.410298] regulator-dummy: no parameters
Sep 12 02:00:20 node-1 kernel: [    0.410331] RTC time:  1:59:43, date: 09/12/16
Sep 12 02:00:20 node-1 kernel: [    0.410365] NET: Registered protocol family 16
Sep 12 02:00:20 node-1 kernel: [    0.410451] cpuidle: using governor ladder
Sep 12 02:00:20 node-1 kernel: [    0.410453] cpuidle: using governor menu
Sep 12 02:00:20 node-1 kernel: [    0.410487] ACPI: bus type PCI registered
Sep 12 02:00:20 node-1 kernel: [    0.410489] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 12 02:00:20 node-1 kernel: [    0.410534] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 12 02:00:20 node-1 kernel: [    0.410537] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 12 02:00:20 node-1 kernel: [    0.424271] PCI: Using configuration type 1 for base access
Sep 12 02:00:20 node-1 kernel: [    0.425264] bio: create slab <bio-0> at 0
Sep 12 02:00:20 node-1 kernel: [    0.425528] ACPI: Added _OSI(Module Device)
Sep 12 02:00:20 node-1 kernel: [    0.425530] ACPI: Added _OSI(Processor Device)
Sep 12 02:00:20 node-1 kernel: [    0.425531] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 12 02:00:20 node-1 kernel: [    0.425532] ACPI: Added _OSI(Processor Aggregator Device)
Sep 12 02:00:20 node-1 kernel: [    0.438140] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 12 02:00:20 node-1 kernel: [    0.448789] ACPI: Interpreter enabled
Sep 12 02:00:20 node-1 kernel: [    0.448795] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 12 02:00:20 node-1 kernel: [    0.448799] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 12 02:00:20 node-1 kernel: [    0.448802] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 12 02:00:20 node-1 kernel: [    0.448809] ACPI: (supports S0 S4 S5)
Sep 12 02:00:20 node-1 kernel: [    0.448810] ACPI: Using IOAPIC for interrupt routing
Sep 12 02:00:20 node-1 kernel: [    0.448852] HEST: Table parsing has been initialized.
Sep 12 02:00:20 node-1 kernel: [    0.448855] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 12 02:00:20 node-1 kernel: [    0.449408] ACPI: No dock devices found.
Sep 12 02:00:20 node-1 kernel: [    0.461153] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 12 02:00:20 node-1 kernel: [    0.461158] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 12 02:00:20 node-1 kernel: [    0.461161] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 12 02:00:20 node-1 kernel: [    0.461190] PCI host bridge to bus 0000:ff
Sep 12 02:00:20 node-1 kernel: [    0.461192] pci_bus 0000:ff: root bus resource [bus ff]
Sep 12 02:00:20 node-1 kernel: [    0.461200] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461239] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.461270] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461305] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461335] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.461365] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.461396] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461425] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461457] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461485] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461512] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461539] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461568] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461594] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461621] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461647] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461676] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461704] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461731] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.461759] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461785] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.461811] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461837] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461867] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.461904] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461935] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461965] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.461996] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462027] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462058] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462089] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462121] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462152] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462183] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462216] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462249] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462282] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462311] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462338] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462371] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462405] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462443] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462478] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462509] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462540] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462569] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462600] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462631] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462663] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462694] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462726] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462756] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462786] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462816] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462846] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462878] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462911] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.462974] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 12 02:00:20 node-1 kernel: [    0.462977] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 12 02:00:20 node-1 kernel: [    0.462980] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 12 02:00:20 node-1 kernel: [    0.462999] PCI host bridge to bus 0000:7f
Sep 12 02:00:20 node-1 kernel: [    0.463000] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 12 02:00:20 node-1 kernel: [    0.463005] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463033] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.463062] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463092] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463114] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.463139] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.463166] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463194] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463216] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463239] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463262] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463284] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463308] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463331] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463354] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463381] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463403] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463426] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463449] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.463473] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463495] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.463517] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463540] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463566] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 12 02:00:20 node-1 kernel: [    0.463601] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463628] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463655] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463684] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463709] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463738] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463765] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463793] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463819] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463847] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463876] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463904] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463934] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463959] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.463984] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464012] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464038] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464066] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464097] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464124] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464151] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464176] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464202] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464229] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464256] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464285] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464315] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464340] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464363] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464388] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464414] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464443] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.464471] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.465729] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 12 02:00:20 node-1 kernel: [    0.465732] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 12 02:00:20 node-1 kernel: [    0.466857] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 12 02:00:20 node-1 kernel: [    0.467369] PCI host bridge to bus 0000:00
Sep 12 02:00:20 node-1 kernel: [    0.467371] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 12 02:00:20 node-1 kernel: [    0.467373] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 12 02:00:20 node-1 kernel: [    0.467374] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 12 02:00:20 node-1 kernel: [    0.467376] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 12 02:00:20 node-1 kernel: [    0.467377] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 12 02:00:20 node-1 kernel: [    0.467378] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 12 02:00:20 node-1 kernel: [    0.467380] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 12 02:00:20 node-1 kernel: [    0.467386] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 12 02:00:20 node-1 kernel: [    0.467468] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.467499] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.467541] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 12 02:00:20 node-1 kernel: [    0.467561] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.467590] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.467631] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 12 02:00:20 node-1 kernel: [    0.467650] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.467679] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.467719] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 12 02:00:20 node-1 kernel: [    0.467737] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.467808] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.467886] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.467964] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 12 02:00:20 node-1 kernel: [    0.467969] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 12 02:00:20 node-1 kernel: [    0.468055] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 12 02:00:20 node-1 kernel: [    0.468202] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 12 02:00:20 node-1 kernel: [    0.468219] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 12 02:00:20 node-1 kernel: [    0.468298] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.468353] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 12 02:00:20 node-1 kernel: [    0.468376] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.468431] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.468475] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 12 02:00:20 node-1 kernel: [    0.468503] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.468559] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.468602] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 12 02:00:20 node-1 kernel: [    0.468627] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 12 02:00:20 node-1 kernel: [    0.468644] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 12 02:00:20 node-1 kernel: [    0.468722] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.468772] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 12 02:00:20 node-1 kernel: [    0.468800] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 12 02:00:20 node-1 kernel: [    0.469049] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 12 02:00:20 node-1 kernel: [    0.469055] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 12 02:00:20 node-1 kernel: [    0.469061] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.469067] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.469074] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 12 02:00:20 node-1 kernel: [    0.469105] pci 0000:01:00.0: supports D1 D2
Sep 12 02:00:20 node-1 kernel: [    0.478933] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 12 02:00:20 node-1 kernel: [    0.478939] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 12 02:00:20 node-1 kernel: [    0.478943] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 12 02:00:20 node-1 kernel: [    0.479138] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.479172] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 12 02:00:20 node-1 kernel: [    0.486931] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 12 02:00:20 node-1 kernel: [    0.486937] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.486941] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 12 02:00:20 node-1 kernel: [    0.487025] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.487115] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.487211] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.487295] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 12 02:00:20 node-1 kernel: [    0.487299] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.487301] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 12 02:00:20 node-1 kernel: [    0.487354] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.487476] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.487530] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 12 02:00:20 node-1 kernel: [    0.487533] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.487535] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.487585] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.487704] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.487743] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.487862] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.487899] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.488020] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.488069] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 12 02:00:20 node-1 kernel: [    0.488189] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 12 02:00:20 node-1 kernel: [    0.488231] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 12 02:00:20 node-1 kernel: [    0.488233] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.488235] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.488293] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 12 02:00:20 node-1 kernel: [    0.488357] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.488409] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.488450] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 12 02:00:20 node-1 kernel: [    0.488535] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 12 02:00:20 node-1 kernel: [    0.488641] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 12 02:00:20 node-1 kernel: [    0.488643] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.488645] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.488701] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 12 02:00:20 node-1 kernel: [    0.488754] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.488803] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.489014] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 12 02:00:20 node-1 kernel: [    0.489018] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 12 02:00:20 node-1 kernel: [    0.489098] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 12 02:00:20 node-1 kernel: [    0.489155] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.489204] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.489413] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 12 02:00:20 node-1 kernel: [    0.489417] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 12 02:00:20 node-1 kernel: [    0.489475] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 12 02:00:20 node-1 kernel: [    0.489535] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.489590] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 12 02:00:20 node-1 kernel: [    0.489812] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 12 02:00:20 node-1 kernel: [    0.489815] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 12 02:00:20 node-1 kernel: [    0.489989] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 12 02:00:20 node-1 kernel: [    0.490027] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 12 02:00:20 node-1 kernel: [    0.490105] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 12 02:00:20 node-1 kernel: [    0.490124] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 12 02:00:20 node-1 kernel: [    0.490137] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 12 02:00:20 node-1 kernel: [    0.490151] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 12 02:00:20 node-1 kernel: [    0.490200] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 12 02:00:20 node-1 kernel: [    0.494938] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 12 02:00:20 node-1 kernel: [    0.494947] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 12 02:00:20 node-1 kernel: [    0.494999] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 12 02:00:20 node-1 kernel: [    0.495570] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 12 02:00:20 node-1 kernel: [    0.495573] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 12 02:00:20 node-1 kernel: [    0.495693] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 12 02:00:20 node-1 kernel: [    0.495799] PCI host bridge to bus 0000:80
Sep 12 02:00:20 node-1 kernel: [    0.495802] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 12 02:00:20 node-1 kernel: [    0.495803] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 12 02:00:20 node-1 kernel: [    0.495805] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 12 02:00:20 node-1 kernel: [    0.495813] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.495876] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.495943] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 12 02:00:20 node-1 kernel: [    0.496005] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 12 02:00:20 node-1 kernel: [    0.496010] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 12 02:00:20 node-1 kernel: [    0.496080] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 12 02:00:20 node-1 kernel: [    0.496378] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 12 02:00:20 node-1 kernel: [    0.496410] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 12 02:00:20 node-1 kernel: [    0.496440] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 12 02:00:20 node-1 kernel: [    0.496469] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 12 02:00:20 node-1 kernel: [    0.496498] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 12 02:00:20 node-1 kernel: [    0.496528] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 12 02:00:20 node-1 kernel: [    0.496558] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 12 02:00:20 node-1 kernel: [    0.496588] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 12 02:00:20 node-1 kernel: [    0.496673] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 12 02:00:20 node-1 kernel: [    0.496677] ACPI: \_SB_.UNC1: notify handler is installed
Sep 12 02:00:20 node-1 kernel: [    0.496678] ACPI: \_SB_.UNC0: notify handler is installed
Sep 12 02:00:20 node-1 kernel: [    0.496694] ACPI: \_SB_.PCI0: notify handler is installed
Sep 12 02:00:20 node-1 kernel: [    0.496746] ACPI: \_SB_.PCI1: notify handler is installed
Sep 12 02:00:20 node-1 kernel: [    0.496826] Found 4 acpi root devices
Sep 12 02:00:20 node-1 kernel: [    0.496933] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 12 02:00:20 node-1 kernel: [    0.496935] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 12 02:00:20 node-1 kernel: [    0.496937] vgaarb: loaded
Sep 12 02:00:20 node-1 kernel: [    0.496938] vgaarb: bridge control possible 0000:0c:00.0
Sep 12 02:00:20 node-1 kernel: [    0.497050] SCSI subsystem initialized
Sep 12 02:00:20 node-1 kernel: [    0.497116] libata version 3.00 loaded.
Sep 12 02:00:20 node-1 kernel: [    0.497131] ACPI: bus type USB registered
Sep 12 02:00:20 node-1 kernel: [    0.497142] usbcore: registered new interface driver usbfs
Sep 12 02:00:20 node-1 kernel: [    0.497147] usbcore: registered new interface driver hub
Sep 12 02:00:20 node-1 kernel: [    0.497170] usbcore: registered new device driver usb
Sep 12 02:00:20 node-1 kernel: [    0.497345] PCI: Using ACPI for IRQ routing
Sep 12 02:00:20 node-1 kernel: [    0.500947] PCI: pci_cache_line_size set to 64 bytes
Sep 12 02:00:20 node-1 kernel: [    0.501173] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 12 02:00:20 node-1 kernel: [    0.501175] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 12 02:00:20 node-1 kernel: [    0.501175] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 12 02:00:20 node-1 kernel: [    0.501240] NetLabel: Initializing
Sep 12 02:00:20 node-1 kernel: [    0.501242] NetLabel:  domain hash size = 128
Sep 12 02:00:20 node-1 kernel: [    0.501242] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 12 02:00:20 node-1 kernel: [    0.501252] NetLabel:  unlabeled traffic allowed by default
Sep 12 02:00:20 node-1 kernel: [    0.501308] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 12 02:00:20 node-1 kernel: [    0.501312] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 12 02:00:20 node-1 kernel: [    0.503378] Switched to clocksource hpet
Sep 12 02:00:20 node-1 kernel: [    0.507356] AppArmor: AppArmor Filesystem Enabled
Sep 12 02:00:20 node-1 kernel: [    0.507376] pnp: PnP ACPI init
Sep 12 02:00:20 node-1 kernel: [    0.507382] ACPI: bus type PNP registered
Sep 12 02:00:20 node-1 kernel: [    0.507492] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507501] pnp 00:01: [dma 4]
Sep 12 02:00:20 node-1 kernel: [    0.507512] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507539] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507559] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507577] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507610] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507666] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507668] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 12 02:00:20 node-1 kernel: [    0.507670] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507671] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507673] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507677] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507680] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 12 02:00:20 node-1 kernel: [    0.507682] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507683] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507685] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507686] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507688] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507689] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 12 02:00:20 node-1 kernel: [    0.507691] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507774] pnp 00:07: [dma 0 disabled]
Sep 12 02:00:20 node-1 kernel: [    0.507803] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507878] pnp 00:08: [dma 0 disabled]
Sep 12 02:00:20 node-1 kernel: [    0.507911] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 12 02:00:20 node-1 kernel: [    0.507963] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 12 02:00:20 node-1 kernel: [    0.508314] pnp: PnP ACPI: found 10 devices
Sep 12 02:00:20 node-1 kernel: [    0.508316] ACPI: bus type PNP unregistered
Sep 12 02:00:20 node-1 kernel: [    0.514685] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 12 02:00:20 node-1 kernel: [    0.514688] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 12 02:00:20 node-1 kernel: [    0.514690] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 12 02:00:20 node-1 kernel: [    0.514695] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 12 02:00:20 node-1 kernel: [    0.514697] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.514711] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.514740] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 12 02:00:20 node-1 kernel: [    0.514755] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 12 02:00:20 node-1 kernel: [    0.514783] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 12 02:00:20 node-1 kernel: [    0.514798] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 12 02:00:20 node-1 kernel: [    0.514830] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 12 02:00:20 node-1 kernel: [    0.514844] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 12 02:00:20 node-1 kernel: [    0.514873] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 12 02:00:20 node-1 kernel: [    0.514875] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.514889] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.514918] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 12 02:00:20 node-1 kernel: [    0.514920] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.514934] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.514963] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 12 02:00:20 node-1 kernel: [    0.514965] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.514967] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 12 02:00:20 node-1 kernel: [    0.514972] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 12 02:00:20 node-1 kernel: [    0.514973] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.514976] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 12 02:00:20 node-1 kernel: [    0.514979] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 12 02:00:20 node-1 kernel: [    0.514984] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 12 02:00:20 node-1 kernel: [    0.514992] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 12 02:00:20 node-1 kernel: [    0.514996] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 12 02:00:20 node-1 kernel: [    0.515002] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 12 02:00:20 node-1 kernel: [    0.515003] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 12 02:00:20 node-1 kernel: [    0.515004] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 12 02:00:20 node-1 kernel: [    0.515004] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 12 02:00:20 node-1 kernel: [    0.515005] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 12 02:00:20 node-1 kernel: [    0.515006] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 12 02:00:20 node-1 kernel: [    0.515007] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 12 02:00:20 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 12 02:00:20 node-1 kernel: [    0.515008] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 12 02:00:20 node-1 kernel: [    0.515009] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.515010] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 12 02:00:20 node-1 kernel: [    0.515011] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.515012] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 12 02:00:20 node-1 kernel: [    0.515013] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.515013] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.515014] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.515015] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.515016] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 12 02:00:20 node-1 kernel: [    0.515017] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 12 02:00:20 node-1 kernel: [    0.515018] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 12 02:00:20 node-1 kernel: [    0.515019] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 12 02:00:20 node-1 kernel: [    0.515020] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 12 02:00:20 node-1 kernel: [    0.515021] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 12 02:00:20 node-1 kernel: [    0.515023] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 12 02:00:20 node-1 kernel: [    0.515024] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 12 02:00:20 node-1 kernel: [    0.515060] NET: Registered protocol family 2
Sep 12 02:00:20 node-1 kernel: [    0.515323] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.515663] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.515808] TCP: Hash tables configured (established 262144 bind 65536)
Sep 12 02:00:20 node-1 kernel: [    0.515845] TCP: reno registered
Sep 12 02:00:20 node-1 kernel: [    0.515874] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.515970] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.516122] NET: Registered protocol family 1
Sep 12 02:00:20 node-1 kernel: [    0.555479] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 12 02:00:20 node-1 kernel: [    0.555495] PCI: CLS 64 bytes, default 64
Sep 12 02:00:20 node-1 kernel: [    0.555573] Trying to unpack rootfs image as initramfs...
Sep 12 02:00:20 node-1 kernel: [    0.775723] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep 12 02:00:20 node-1 kernel: [    0.775760] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 12 02:00:20 node-1 kernel: [    0.775763] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 12 02:00:20 node-1 kernel: [    0.776173] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776179] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776184] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776190] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776201] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776218] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776233] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776248] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776260] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776269] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776275] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776281] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776290] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776302] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776315] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776328] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 12 02:00:20 node-1 kernel: [    0.776379] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 12 02:00:20 node-1 kernel: [    0.776383] Scanning for low memory corruption every 60 seconds
Sep 12 02:00:20 node-1 kernel: [    0.776683] Initialise system trusted keyring
Sep 12 02:00:20 node-1 kernel: [    0.776727] audit: initializing netlink socket (disabled)
Sep 12 02:00:20 node-1 kernel: [    0.776737] type=2000 audit(1473645583.732:1): initialized
Sep 12 02:00:20 node-1 kernel: [    0.794556] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 12 02:00:20 node-1 kernel: [    0.796067] zbud: loaded
Sep 12 02:00:20 node-1 kernel: [    0.796177] VFS: Disk quotas dquot_6.5.2
Sep 12 02:00:20 node-1 kernel: [    0.796214] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 12 02:00:20 node-1 kernel: [    0.796574] fuse init (API version 7.22)
Sep 12 02:00:20 node-1 kernel: [    0.796630] msgmni has been set to 32768
Sep 12 02:00:20 node-1 kernel: [    0.796676] Key type big_key registered
Sep 12 02:00:20 node-1 kernel: [    0.797201] Key type asymmetric registered
Sep 12 02:00:20 node-1 kernel: [    0.797202] Asymmetric key parser 'x509' registered
Sep 12 02:00:20 node-1 kernel: [    0.797230] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 12 02:00:20 node-1 kernel: [    0.797288] io scheduler noop registered
Sep 12 02:00:20 node-1 kernel: [    0.797290] io scheduler deadline registered (default)
Sep 12 02:00:20 node-1 kernel: [    0.797306] io scheduler cfq registered
Sep 12 02:00:20 node-1 kernel: [    0.797640] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    0.797733] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    0.797820] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    0.797908] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    0.798004] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    0.798071] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    0.798334] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 12 02:00:20 node-1 kernel: [    0.798352] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 12 02:00:20 node-1 kernel: [    0.798364] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 12 02:00:20 node-1 kernel: [    0.798373] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798376] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798378] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 12 02:00:20 node-1 kernel: [    0.798382] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798383] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798384] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798386] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798387] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798389] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798390] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798391] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798393] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798394] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798396] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798398] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798400] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 12 02:00:20 node-1 kernel: [    0.798403] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798405] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 12 02:00:20 node-1 kernel: [    0.798414] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798417] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 12 02:00:20 node-1 kernel: [    0.798426] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798428] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 12 02:00:20 node-1 kernel: [    0.798430] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 12 02:00:20 node-1 kernel: [    0.798443] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 12 02:00:20 node-1 kernel: [    0.798560] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 12 02:00:20 node-1 kernel: [    0.798564] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 12 02:00:20 node-1 kernel: [    0.798573] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 12 02:00:20 node-1 kernel: [    0.798608] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 12 02:00:20 node-1 kernel: [    0.798610] vesafb: scrolling: redraw
Sep 12 02:00:20 node-1 kernel: [    0.798611] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 12 02:00:20 node-1 kernel: [    0.819480] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 12 02:00:20 node-1 kernel: [    0.828037] Console: switching to colour frame buffer device 80x30
Sep 12 02:00:20 node-1 kernel: [    0.836777] fb0: VESA VGA frame buffer device
Sep 12 02:00:20 node-1 kernel: [    0.836976] intel_idle: MWAIT substates: 0x2120
Sep 12 02:00:20 node-1 kernel: [    0.836977] intel_idle: v0.4 model 0x3F
Sep 12 02:00:20 node-1 kernel: [    0.836978] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 12 02:00:20 node-1 kernel: [    0.837204] ipmi message handler version 39.2
Sep 12 02:00:20 node-1 kernel: [    0.837473] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 12 02:00:20 node-1 kernel: [    0.837907] ACPI: AC Adapter [P111] (on-line)
Sep 12 02:00:20 node-1 kernel: [    0.843174] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 12 02:00:20 node-1 kernel: [    0.854241] ACPI: Power Button [PWRB]
Sep 12 02:00:20 node-1 kernel: [    0.860092] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 12 02:00:20 node-1 kernel: [    0.871818] ACPI: Power Button [PWRF]
Sep 12 02:00:20 node-1 kernel: [    0.897051] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 12 02:00:20 node-1 kernel: [    0.908836] pstore: Registered erst as persistent store backend
Sep 12 02:00:20 node-1 kernel: [    0.915147] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 12 02:00:20 node-1 kernel: [    0.927294] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 12 02:00:20 node-1 kernel: [    0.954135] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 12 02:00:20 node-1 kernel: [    0.987453] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 12 02:00:20 node-1 kernel: [    1.001606] Linux agpgart interface v0.103
Sep 12 02:00:20 node-1 kernel: [    1.009289] brd: module loaded
Sep 12 02:00:20 node-1 kernel: [    1.016333] loop: module loaded
Sep 12 02:00:20 node-1 kernel: [    1.023073] libphy: Fixed MDIO Bus: probed
Sep 12 02:00:20 node-1 kernel: [    1.029633] tun: Universal TUN/TAP device driver, 1.6
Sep 12 02:00:20 node-1 kernel: [    1.036206] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 12 02:00:20 node-1 kernel: [    1.042700] PPP generic driver version 2.4.2
Sep 12 02:00:20 node-1 kernel: [    1.049066] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 12 02:00:20 node-1 kernel: [    1.055488] ehci-pci: EHCI PCI platform driver
Sep 12 02:00:20 node-1 kernel: [    1.062075] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 12 02:00:20 node-1 kernel: [    1.068471] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 12 02:00:20 node-1 kernel: [    1.080969] ehci-pci 0000:00:1a.0: debug port 2
Sep 12 02:00:20 node-1 kernel: [    1.091160] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 12 02:00:20 node-1 kernel: [    1.091178] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 12 02:00:20 node-1 kernel: [    1.106871] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 12 02:00:20 node-1 kernel: [    1.112968] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 12 02:00:20 node-1 kernel: [    1.119132] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 12 02:00:20 node-1 kernel: [    1.131005] usb usb1: Product: EHCI Host Controller
Sep 12 02:00:20 node-1 kernel: [    1.137024] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 12 02:00:20 node-1 kernel: [    1.143050] usb usb1: SerialNumber: 0000:00:1a.0
Sep 12 02:00:20 node-1 kernel: [    1.148983] hub 1-0:1.0: USB hub found
Sep 12 02:00:20 node-1 kernel: [    1.154730] hub 1-0:1.0: 2 ports detected
Sep 12 02:00:20 node-1 kernel: [    1.160498] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 12 02:00:20 node-1 kernel: [    1.166073] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 12 02:00:20 node-1 kernel: [    1.176947] ehci-pci 0000:00:1d.0: debug port 2
Sep 12 02:00:20 node-1 kernel: [    1.186231] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 12 02:00:20 node-1 kernel: [    1.186234] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 12 02:00:20 node-1 kernel: [    1.202790] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 12 02:00:20 node-1 kernel: [    1.208067] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 12 02:00:20 node-1 kernel: [    1.213438] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 12 02:00:20 node-1 kernel: [    1.224257] usb usb2: Product: EHCI Host Controller
Sep 12 02:00:20 node-1 kernel: [    1.229879] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 12 02:00:20 node-1 kernel: [    1.235577] usb usb2: SerialNumber: 0000:00:1d.0
Sep 12 02:00:20 node-1 kernel: [    1.241213] hub 2-0:1.0: USB hub found
Sep 12 02:00:20 node-1 kernel: [    1.246703] hub 2-0:1.0: 2 ports detected
Sep 12 02:00:20 node-1 kernel: [    1.252130] ehci-platform: EHCI generic platform driver
Sep 12 02:00:20 node-1 kernel: [    1.257477] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 12 02:00:20 node-1 kernel: [    1.262913] ohci-pci: OHCI PCI platform driver
Sep 12 02:00:20 node-1 kernel: [    1.268334] ohci-platform: OHCI generic platform driver
Sep 12 02:00:20 node-1 kernel: [    1.273643] uhci_hcd: USB Universal Host Controller Interface driver
Sep 12 02:00:20 node-1 kernel: [    1.279136] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 12 02:00:20 node-1 kernel: [    1.470570] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 12 02:00:20 node-1 kernel: [    1.634780] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 12 02:00:20 node-1 kernel: [    1.640403] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 12 02:00:20 node-1 kernel: [    1.646168] hub 1-1:1.0: USB hub found
Sep 12 02:00:20 node-1 kernel: [    1.651767] hub 1-1:1.0: 6 ports detected
Sep 12 02:00:20 node-1 kernel: [    1.766310] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 12 02:00:20 node-1 kernel: [    1.774330] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 12 02:00:20 node-1 kernel: [    2.034441] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 12 02:00:20 node-1 kernel: [    2.040047] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 12 02:00:20 node-1 kernel: [    2.045957] hub 2-1:1.0: USB hub found
Sep 12 02:00:20 node-1 kernel: [    2.051678] hub 2-1:1.0: 8 ports detected
Sep 12 02:00:20 node-1 kernel: [    2.320713] i8042: No controller found
Sep 12 02:00:20 node-1 kernel: [    2.326096] mousedev: PS/2 mouse device common for all mice
Sep 12 02:00:20 node-1 kernel: [    2.329939] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 12 02:00:20 node-1 kernel: [    2.337169] rtc_cmos 00:02: RTC can wake from S4
Sep 12 02:00:20 node-1 kernel: [    2.342881] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 12 02:00:20 node-1 kernel: [    2.348476] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 12 02:00:20 node-1 kernel: [    2.359531] device-mapper: uevent: version 1.0.3
Sep 12 02:00:20 node-1 kernel: [    2.365136] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 12 02:00:20 node-1 kernel: [    2.376309] ledtrig-cpu: registered to indicate activity on CPUs
Sep 12 02:00:20 node-1 kernel: [    2.382230] TCP: cubic registered
Sep 12 02:00:20 node-1 kernel: [    2.388114] NET: Registered protocol family 10
Sep 12 02:00:20 node-1 kernel: [    2.394120] NET: Registered protocol family 17
Sep 12 02:00:20 node-1 kernel: [    2.399827] Key type dns_resolver registered
Sep 12 02:00:20 node-1 kernel: [    2.405741] Loading compiled-in X.509 certificates
Sep 12 02:00:20 node-1 kernel: [    2.411893] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 12 02:00:20 node-1 kernel: [    2.423251] registered taskstats version 1
Sep 12 02:00:20 node-1 kernel: [    2.431181] Key type trusted registered
Sep 12 02:00:20 node-1 kernel: [    2.438726] Key type encrypted registered
Sep 12 02:00:20 node-1 kernel: [    2.444186] AppArmor: AppArmor sha1 policy hashing enabled
Sep 12 02:00:20 node-1 kernel: [    2.449656] IMA: No TPM chip found, activating TPM-bypass!
Sep 12 02:00:20 node-1 kernel: [    2.455761] regulator-dummy: disabling
Sep 12 02:00:20 node-1 kernel: [    2.461310]   Magic number: 0:465:963
Sep 12 02:00:20 node-1 kernel: [    2.466672] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 12 02:00:20 node-1 kernel: [    2.466673] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 12 02:00:20 node-1 kernel: [    2.466674] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 12 02:00:20 node-1 kernel: [    2.466675] usb 2-1.4: Manufacturer: Avocent
Sep 12 02:00:20 node-1 kernel: [    2.466676] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 12 02:00:20 node-1 kernel: [    2.500052] rtc_cmos 00:02: setting system clock to 2016-09-12 01:59:45 UTC (1473645585)
Sep 12 02:00:20 node-1 kernel: [    2.512559] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 12 02:00:20 node-1 kernel: [    2.518277] EDD information not available.
Sep 12 02:00:20 node-1 kernel: [    2.523972] PM: Hibernation image not present or could not be loaded.
Sep 12 02:00:20 node-1 kernel: [    2.524840] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 12 02:00:20 node-1 kernel: [    2.536190] Write protecting the kernel read-only data: 12288k
Sep 12 02:00:20 node-1 kernel: [    2.542499] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 12 02:00:20 node-1 kernel: [    2.555028] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 12 02:00:20 node-1 kernel: [    2.587931] device-mapper: multipath: version 1.6.0 loaded
Sep 12 02:00:20 node-1 kernel: [    2.595958] systemd-udevd[218]: starting version 204
Sep 12 02:00:20 node-1 kernel: [    2.615950] md: linear personality registered for level -1
Sep 12 02:00:20 node-1 kernel: [    2.629989] md: multipath personality registered for level -4
Sep 12 02:00:20 node-1 kernel: [    2.637929] md: raid0 personality registered for level 0
Sep 12 02:00:20 node-1 kernel: [    2.646280] md: raid1 personality registered for level 1
Sep 12 02:00:20 node-1 kernel: [    2.658000] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 12 02:00:20 node-1 kernel: [    2.664447] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 12 02:00:20 node-1 kernel: [    2.664608] hidraw: raw HID events driver (C) Jiri Kosina
Sep 12 02:00:20 node-1 kernel: [    2.676100] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 12 02:00:20 node-1 kernel: [    2.676110] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 12 02:00:20 node-1 kernel: [    2.676148] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 12 02:00:20 node-1 kernel: [    2.676913] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.677139] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.677264] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.677425] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.677795] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.696558] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 12 02:00:20 node-1 kernel: [    2.696587] 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
Sep 12 02:00:20 node-1 kernel: [    2.696591] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 12 02:00:20 node-1 kernel: [    2.696976] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.697062] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.697192] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.697320] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.697668] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.715857] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 12 02:00:20 node-1 kernel: [    2.715861] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 12 02:00:20 node-1 kernel: [    2.715880] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 12 02:00:20 node-1 kernel: [    2.716274] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.716313] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.716427] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.716628] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.716942] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.721583] raid6: sse2x1   10191 MB/s
Sep 12 02:00:20 node-1 kernel: [    2.732734] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 12 02:00:20 node-1 kernel: [    2.732748] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 12 02:00:20 node-1 kernel: [    2.732779] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 12 02:00:20 node-1 kernel: [    2.733033] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.733095] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.733191] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.733310] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.733704] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 12 02:00:20 node-1 kernel: [    2.789634] raid6: sse2x2   12948 MB/s
Sep 12 02:00:20 node-1 kernel: [    2.857560] raid6: sse2x4    9621 MB/s
Sep 12 02:00:20 node-1 kernel: [    2.925337] raid6: avx2x1   14624 MB/s
Sep 12 02:00:20 node-1 kernel: [    2.997276] raid6: avx2x2   18874 MB/s
Sep 12 02:00:20 node-1 kernel: [    3.069223] raid6: avx2x4   21409 MB/s
Sep 12 02:00:20 node-1 kernel: [    3.075118] raid6: using algorithm avx2x4 (21409 MB/s)
Sep 12 02:00:20 node-1 kernel: [    3.081170] raid6: using avx2x2 recovery algorithm
Sep 12 02:00:20 node-1 kernel: [    3.087157] Switched to clocksource tsc
Sep 12 02:00:20 node-1 kernel: [    3.087319] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 12 02:00:20 node-1 kernel: [    3.088465] megasas: FW now in Ready state
Sep 12 02:00:20 node-1 kernel: [    3.088866] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.089037] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.089130] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090058] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090187] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090292] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090402] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090512] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090596] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090711] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090828] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.090956] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.091031] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.091180] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.091361] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.091466] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Sep 12 02:00:20 node-1 kernel: [    3.091947] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 12 02:00:20 node-1 kernel: [    3.115983] xor: automatically using best checksumming function:
Sep 12 02:00:20 node-1 kernel: [    3.124837] usbcore: registered new interface driver usbhid
Sep 12 02:00:20 node-1 kernel: [    3.130633] usbhid: USB HID core driver
Sep 12 02:00:20 node-1 kernel: [    3.138248] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 12 02:00:20 node-1 kernel: [    3.149778] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 12 02:00:20 node-1 kernel: [    3.161368]    avx       : 36620.000 MB/sec
Sep 12 02:00:20 node-1 kernel: [    3.167420] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 12 02:00:20 node-1 kernel: [    3.179664] async_tx: api initialized (async)
Sep 12 02:00:20 node-1 kernel: [    3.179978] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 12 02:00:20 node-1 kernel: [    3.180956] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 12 02:00:20 node-1 kernel: [    3.181471] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 12 02:00:20 node-1 kernel: [    3.226379] md: raid6 personality registered for level 6
Sep 12 02:00:20 node-1 kernel: [    3.232788] md: raid5 personality registered for level 5
Sep 12 02:00:20 node-1 kernel: [    3.239177] md: raid4 personality registered for level 4
Sep 12 02:00:20 node-1 kernel: [    3.248519] md: raid10 personality registered for level 10
Sep 12 02:00:20 node-1 kernel: [    3.304021] multipathd (357): /proc/357/oom_adj is deprecated, please use /proc/357/oom_score_adj instead.
Sep 12 02:00:20 node-1 kernel: [    3.432950] megasas:IOC Init cmd success
Sep 12 02:00:20 node-1 kernel: [    3.460936] megasas: INIT adapter done
Sep 12 02:00:20 node-1 kernel: [    3.560836] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 12 02:00:20 node-1 kernel: [    3.567747] scsi0 : LSI SAS based MegaRAID driver
Sep 12 02:00:20 node-1 kernel: [    3.575109] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 12 02:00:20 node-1 kernel: [    3.593965] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 12 02:00:20 node-1 kernel: [    3.609312] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 12 02:00:20 node-1 kernel: [    3.615863] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 12 02:00:20 node-1 kernel: [    3.628820] sd 0:2:0:0: [sda] Write Protect is off
Sep 12 02:00:20 node-1 kernel: [    3.635187] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 12 02:00:20 node-1 kernel: [    3.635207] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 12 02:00:20 node-1 kernel: [    3.671926]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 12 02:00:20 node-1 kernel: [    3.678587] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 12 02:00:20 node-1 kernel: [    3.818136] random: lvm urandom read with 29 bits of entropy available
Sep 12 02:00:20 node-1 kernel: [    3.983341] bio: create slab <bio-1> at 1
Sep 12 02:00:20 node-1 kernel: [    4.794265] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 12 02:00:20 node-1 kernel: [    5.286707] init: plymouth-upstart-bridge main process (553) terminated with status 1
Sep 12 02:00:20 node-1 kernel: [    5.299094] init: plymouth-upstart-bridge main process ended, respawning
Sep 12 02:00:20 node-1 kernel: [    5.434094] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 12 02:00:20 node-1 kernel: [    5.461255] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 12 02:00:20 node-1 kernel: [    5.536218] random: nonblocking pool is initialized
Sep 12 02:00:20 node-1 kernel: [    5.563841] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 12 02:00:20 node-1 kernel: [    5.611785] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 12 02:00:20 node-1 kernel: [    5.765632] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 12 02:00:20 node-1 kernel: [    5.951507] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 12 02:00:20 node-1 kernel: [    5.985149] XFS (dm-0): Mounting Filesystem
Sep 12 02:00:20 node-1 kernel: [    6.306995] XFS (dm-0): Ending clean mount
Sep 12 02:00:20 node-1 kernel: [    6.350198] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 12 02:00:20 node-1 kernel: [    6.389049] XFS (dm-1): Mounting Filesystem
Sep 12 02:00:20 node-1 kernel: [    6.479166] XFS (dm-1): Ending clean mount
Sep 12 02:00:20 node-1 kernel: [    8.699722] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 12 02:00:20 node-1 kernel: [    8.724053] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 12 02:00:20 node-1 kernel: [    8.863452] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 12 02:00:20 node-1 kernel: [    8.863456] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 12 02:00:20 node-1 kernel: [    8.863460] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 12 02:00:20 node-1 kernel: [    8.863463] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 12 02:00:20 node-1 kernel: [    8.949115] systemd-udevd[779]: starting version 204
Sep 12 02:00:20 node-1 kernel: [    9.184645] power_meter ACPI000D:00: Found ACPI power meter.
Sep 12 02:00:20 node-1 kernel: [    9.184659] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 12 02:00:20 node-1 kernel: [    9.201202] IPMI System Interface driver.
Sep 12 02:00:20 node-1 kernel: [    9.201318] ipmi_si: probing via ACPI
Sep 12 02:00:20 node-1 kernel: [    9.201333] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 12 02:00:20 node-1 kernel: [    9.201334] ipmi_si: Adding ACPI-specified kcs state machine
Sep 12 02:00:20 node-1 kernel: [    9.201345] ipmi_si: probing via SMBIOS
Sep 12 02:00:20 node-1 kernel: [    9.201347] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 12 02:00:20 node-1 kernel: [    9.201348] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 12 02:00:20 node-1 kernel: [    9.201349] ipmi_si: probing via SPMI
Sep 12 02:00:20 node-1 kernel: [    9.201350] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 12 02:00:20 node-1 kernel: [    9.201351] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 12 02:00:20 node-1 kernel: [    9.201353] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 12 02:00:20 node-1 kernel: [    9.231806] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 12 02:00:20 node-1 kernel: [    9.231813] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 12 02:00:20 node-1 kernel: [    9.231816] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 12 02:00:20 node-1 kernel: [    9.231819] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 12 02:00:20 node-1 kernel: [    9.231870] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 12 02:00:20 node-1 kernel: [    9.242285] wmi: Mapper loaded
Sep 12 02:00:20 node-1 kernel: [    9.244858] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 12 02:00:20 node-1 kernel: [    9.324374] systemd-udevd[825]: renamed network interface eth0 to enp6s0
Sep 12 02:00:20 node-1 kernel: [    9.336734] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 12 02:00:20 node-1 kernel: [    9.336740] ipmi_si 00:09: IPMI kcs interface initialized
Sep 12 02:00:20 node-1 kernel: [    9.352366] systemd-udevd[833]: renamed network interface eth1 to enp7s0
Sep 12 02:00:20 node-1 kernel: [    9.376342] systemd-udevd[832]: renamed network interface eth2 to enp8s0
Sep 12 02:00:20 node-1 kernel: [    9.392452] systemd-udevd[830]: renamed network interface eth3 to enp9s0
Sep 12 02:00:20 node-1 kernel: [    9.708079] type=1400 audit(1473645592.712:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1073 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.708226] type=1400 audit(1473645592.712:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1073 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.708353] type=1400 audit(1473645592.712:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1073 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.711195] type=1400 audit(1473645592.712:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.711315] type=1400 audit(1473645592.712:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.711424] type=1400 audit(1473645592.712:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.713425] type=1400 audit(1473645592.716:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1074 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.713580] type=1400 audit(1473645592.716:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1074 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.713700] type=1400 audit(1473645592.716:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1074 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [    9.716182] type=1400 audit(1473645592.720:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Sep 12 02:00:20 node-1 kernel: [   10.313966] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 12 02:00:20 node-1 kernel: [   10.314673] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 12 02:00:20 node-1 kernel: [   10.474163] enic 0000:06:00.0 enp6s0: Link UP
Sep 12 02:00:20 node-1 kernel: [   10.474583] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 12 02:00:20 node-1 kernel: [   10.474592] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 12 02:00:20 node-1 kernel: [   20.012625] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 12 02:00:21 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 12 02:00:21 node-1 kernel: [   38.105099] init: failsafe main process (8423) killed by TERM signal
Sep 12 02:00:22 node-1 dbus[8489]: [system] AppArmor D-Bus mediation is enabled
Sep 12 02:00:22 node-1 kernel: [   38.314737] audit_printk_skb: 30 callbacks suppressed
Sep 12 02:00:22 node-1 kernel: [   38.314739] type=1400 audit(1473645622.124:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8542 comm="apparmor_parser"
Sep 12 02:00:22 node-1 kernel: [   38.315436] type=1400 audit(1473645622.128:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8541 comm="apparmor_parser"
Sep 12 02:00:22 node-1 kernel: [   38.315441] type=1400 audit(1473645622.128:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Sep 12 02:00:22 node-1 kernel: [   38.315443] type=1400 audit(1473645622.128:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Sep 12 02:00:22 node-1 kernel: [   38.316853] type=1400 audit(1473645622.128:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Sep 12 02:00:22 node-1 kernel: [   38.316918] type=1400 audit(1473645622.128:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Sep 12 02:00:22 node-1 kernel: [   38.318017] type=1400 audit(1473645622.128:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Sep 12 02:00:22 node-1 kernel: [   38.410402] type=1400 audit(1473645622.220:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8544 comm="apparmor_parser"
Sep 12 02:00:22 node-1 anacron[8607]: Anacron 2.3 started on 2016-09-12
Sep 12 02:00:22 node-1 cron[8582]: (CRON) INFO (pidfile fd = 3)
Sep 12 02:00:22 node-1 anacron[8607]: Will run job `cron.daily' in 5 min.
Sep 12 02:00:22 node-1 anacron[8607]: Will run job `cron.weekly' in 10 min.
Sep 12 02:00:22 node-1 anacron[8607]: Will run job `cron.monthly' in 15 min.
Sep 12 02:00:22 node-1 anacron[8607]: Jobs will be executed sequentially
Sep 12 02:00:22 node-1 cron[8634]: (CRON) STARTUP (fork ok)
Sep 12 02:00:22 node-1 multipathd: path checkers start up
Sep 12 02:00:22 node-1 cron[8634]: (CRON) INFO (Running @reboot jobs)
Sep 12 02:00:22 node-1 postfix/master[8761]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 12 02:00:25 node-1 puppet-agent[8947]: Reopening log files
Sep 12 02:00:26 node-1 puppet-agent[8947]: Could not request certificate: Connection refused - connect(2)
Sep 12 02:00:41 node-1 puppet-user[9026]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 12 02:00:41 node-1 puppet-user[9026]: Compiled catalog for node-1.domain.tld in environment production in 0.01 seconds
Sep 12 02:00:42 node-1 puppet-user[9026]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 12 02:00:42 node-1 puppet-user[9026]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 12 02:00:42 node-1 puppet-user[9026]: Finished catalog run in 0.97 seconds
Sep 12 02:00:43 node-1 multipathd: uevent trigger error
Sep 12 02:00:43 node-1 puppet-user[9451]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 12 02:00:43 node-1 puppet-user[9451]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 12 02:00:44 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 12 02:00:44 node-1 puppet-user[9451]: Finished catalog run in 0.06 seconds
Sep 12 02:00:45 node-1 puppet-user[9913]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 12 02:00:45 node-1 puppet-user[9913]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 12 02:00:45 node-1 puppet-user[9913]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 12 02:00:45 node-1 puppet-user[9913]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 12 02:00:45 node-1 puppet-user[9913]: Finished catalog run in 0.03 seconds
Sep 12 02:00:47 node-1 puppet-user[10376]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 12 02:00:47 node-1 puppet-user[10376]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 12 02:00:47 node-1 puppet-user[10376]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 12 02:00:47 node-1 puppet-user[10376]: Finished catalog run in 0.05 seconds
Sep 12 02:00:49 node-1 puppet-user[10948]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 12 02:00:49 node-1 puppet-user[10948]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Sep 12 02:00:49 node-1 puppet-user[10948]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 12 02:00:51 node-1 puppet-user[10948]: (/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
Sep 12 02:00:51 node-1 puppet-user[10948]: Finished catalog run in 2.02 seconds
Sep 12 02:00:52 node-1 puppet-user[11482]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 12 02:00:52 node-1 puppet-user[11482]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 12 02:00:52 node-1 puppet-user[11482]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 12 02:00:52 node-1 puppet-user[11482]: (/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
Sep 12 02:00:52 node-1 puppet-user[11482]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 12 02:00:52 node-1 puppet-user[11482]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 12 02:00:52 node-1 puppet-user[11482]: Finished catalog run in 0.21 seconds
Sep 12 02:00:54 node-1 puppet-user[11957]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 12 02:00:54 node-1 puppet-user[11957]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep 12 02:00:54 node-1 puppet-user[11957]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 12 02:00:54 node-1 kernel: [   71.352389] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 12 02:00:54 node-1 kernel: [   71.352439] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 12 02:00:54 node-1 puppet-user[11957]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 12 02:00:54 node-1 puppet-user[11957]: Finished catalog run in 0.05 seconds
Sep 12 02:00:56 node-1 puppet-user[12414]: (Scope(Class[main])) MODULAR: sync_time
Sep 12 02:00:56 node-1 puppet-user[12414]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 12 02:00:56 node-1 ntpdate[12825]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 12 02:01:01 node-1 CRON[13102]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 12 02:01:02 node-1 ntpdate[12825]: adjust time server 10.20.0.2 offset 0.000201 sec
Sep 12 02:01:02 node-1 puppet-user[12414]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 12 02:01:02 node-1 puppet-user[12414]: Finished catalog run in 6.16 seconds
Sep 12 02:01:08 node-1 puppet-user[13218]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 12 02:01:08 node-1 puppet-user[13218]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Sep 12 02:01:09 node-1 puppet-user[13218]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 12 02:01:09 node-1 puppet-user[13218]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Sep 12 02:01:09 node-1 puppet-user[13218]: Finished catalog run in 0.06 seconds
Sep 12 02:01:10 node-1 puppet-user[13662]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 12 02:01:11 node-1 puppet-user[13662]: Compiled catalog for node-1.domain.tld in environment production in 1.32 seconds
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/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
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/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
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/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
Sep 12 02:01:11 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 12 02:01:11 node-1 puppet-user[13662]: (/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
Sep 12 02:01:11 node-1 puppet-user[13662]: (/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
Sep 12 02:01:12 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 12 02:01:12 node-1 puppet-user[13662]: (/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
Sep 12 02:01:12 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 12 02:01:12 node-1 kernel: [   89.426506] init: plymouth-upstart-bridge main process ended, respawning
Sep 12 02:01:13 node-1 puppet-agent[8947]: Could not run: SIGTERM
Sep 12 02:01:13 node-1 kernel: [   89.693881] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 12 02:01:13 node-1 ec2: 
Sep 12 02:01:13 node-1 ec2: #############################################################
Sep 12 02:01:13 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 12 02:01:13 node-1 ec2: 1024 75:20:f6:74:89:8d:73:0f:f6:f0:96:0c:a2:1b:78:d3  root@node-1.domain.tld (DSA)
Sep 12 02:01:13 node-1 ec2: 256 a8:40:e7:63:a9:81:72:d0:2b:60:a3:69:7c:e7:60:b8  root@node-1.domain.tld (ECDSA)
Sep 12 02:01:13 node-1 ec2: 256 0f:2a:6d:9a:bb:0d:b5:d1:00:92:a0:3c:fd:39:ad:ac  root@node-1.domain.tld (ED25519)
Sep 12 02:01:13 node-1 ec2: 2048 b1:85:20:5b:2f:64:3c:63:6d:33:2a:dc:df:85:d7:f0  root@node-1.domain.tld (RSA)
Sep 12 02:01:13 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 12 02:01:13 node-1 ec2: #############################################################
Sep 12 02:01:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 12 02:01:18 node-1 nailgun-agent: D, [2016-09-12T02:01:01.230522 #13105] DEBUG -- : Sleep for 17 seconds before sending request
Sep 12 02:01:18 node-1 nailgun-agent: I, [2016-09-12T02:01:18.243859 #13105]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 12 02:01:18 node-1 nailgun-agent: D, [2016-09-12T02:01:18.645112 #13105] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 12 02:01:30 node-1 puppet-user[13662]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep 12 02:01:30 node-1 puppet-user[13662]: Finished catalog run in 18.35 seconds
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.774975 #13105] DEBUG -- : Trying to find block devices
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.775170 #13105] DEBUG -- : Found block device: sda
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.775273 #13105] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.775333 #13105] DEBUG -- : Trying to get list of physical devices
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.775778 #13105] DEBUG -- : Getting udev properties for device: sda
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.780569 #13105] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /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"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Sep 12 02:01:30 node-1 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37742", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.780644 #13105] DEBUG -- : Trying to find out if device sda is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.780754 #13105] DEBUG -- : Device sda removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.780793 #13105] DEBUG -- : Device sda seems to be appropriate
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.781873 #13105] DEBUG -- : Getting udev properties for device: dm-0
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.785637 #13105] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-px7zoRhJHfS7RUZ6r3Fv8dyOJHUsoY1FYpSeU9M8hC845k4wdacROdcoPKA5zly9 /dev/disk/by-uuid/7676c75f-96e5-4156-b77f-7df7f8b9aaf0 /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-px7zoRhJHfS7RUZ6r3Fv8dyOJHUsoY1FYpSeU9M8hC845k4wdacROdcoPKA5zly9", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"7676c75f-96e5-4156-b77f-7df7f8b9aaf0", "ID_FS_UUID_ENC"=>"7676c75f-96e5-4156-b77f-7df7f8b9aaf0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42697", "nomdmonddf"=>"1", "nom
Sep 12 02:01:30 node-1 nailgun-agent: dmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.785744 #13105] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.785829 #13105] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.785866 #13105] DEBUG -- : Device dm-0 seems to be appropriate
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.785908 #13105] DEBUG -- : Getting udev properties for device: dm-1
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.790794 #13105] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-XRMW8mRN4I6G822TuMircFS1lNvmZzyyE5gAhWwmjqXfQVNw0uXHayZwdkxlDIho /dev/disk/by-uuid/9ff5e196-cb59-4125-bc49-14900b500cda /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-XRMW8mRN4I6G822TuMircFS1lNvmZzyyE5gAhWwmjqXfQVNw0uXHayZwdkxlDIho", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9ff5e196-cb59-4125-bc49-14900b500cda", "ID_FS_UUID_ENC"=>"9ff5e196-cb59-4125-bc49-14900b500cda", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9
Sep 12 02:01:30 node-1 nailgun-agent: 4539", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.790900 #13105] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.791049 #13105] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.791087 #13105] DEBUG -- : Device dm-1 seems to be appropriate
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.791128 #13105] DEBUG -- : Getting udev properties for device: dm-2
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.796234 #13105] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-zVlHOvPZtXqORwkKX2D9KNiYrnGJfmlRRALQIzTc8qx30T5QJ9GwM3GSQv6RinpJ /dev/disk/by-uuid/fd7d13ed-7351-4728-a502-e18c77c03700 /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-zVlHOvPZtXqORwkKX2D9KNiYrnGJfmlRRALQIzTc8qx30T5QJ9GwM3GSQv6RinpJ", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"fd7d13ed-7351-4728-a502-e18c77c03700", "ID_FS_UUID_ENC"=>"fd7d13ed-7351-4728-a502-e18c77c03700", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2172", "nomdmond
Sep 12 02:01:30 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.796304 #13105] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.796400 #13105] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.796432 #13105] DEBUG -- : Device dm-2 seems to be appropriate
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.796483 #13105] DEBUG -- : Getting udev properties for device: dm-3
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.800915 #13105] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Vm37MocG6Lj203EDPcoHs855i6LSj4XWHlsP06d3mD2dut7LrhOuMalVxnfWZusB /dev/disk/by-uuid/f702ea7a-8db2-4057-bde8-94f7d4b04898 /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-Vm37MocG6Lj203EDPcoHs855i6LSj4XWHlsP06d3mD2dut7LrhOuMalVxnfWZusB", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f702ea7a-8db2-4057-bde8-94f7d4b04898", "ID_FS_UUID_ENC"=>"f702ea7a-8db2-4057-bde8-94f7d4b04898", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16922", "nomdmonddf"=>"1",
Sep 12 02:01:30 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.801002 #13105] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.801073 #13105] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.801106 #13105] DEBUG -- : Device dm-3 seems to be appropriate
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.801141 #13105] DEBUG -- : Getting udev properties for device: dm-4
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.805758 #13105] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-2h6KyedarmGVtAhpQFgb6PYRzfBhW78A4C0TqxvNXjjiWT3PpH04fiLBo20IcYq4 /dev/disk/by-uuid/fee77217-bde6-4f20-8330-8889fdd31919 /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-2h6KyedarmGVtAhpQFgb6PYRzfBhW78A4C0TqxvNXjjiWT3PpH04fiLBo20IcYq4", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"fee77217-bde6-4f20-8330-8889fdd31919", "ID_FS_UUID_ENC"=>"fee77217-bde6-4f20-8330-8889fdd31919", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"26934", "nomdmonddf"=>"1", "nom
Sep 12 02:01:30 node-1 nailgun-agent: dmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.805823 #13105] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.805893 #13105] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.805926 #13105] DEBUG -- : Device dm-4 seems to be appropriate
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.805986 #13105] DEBUG -- : Getting udev properties for device: dm-5
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.810165 #13105] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-2h6KyedarmGVtAhpQFgb6PYRzfBhW78AwAEIn5Wsc61OT57LQwaupV3ffDK9k8U5 /dev/disk/by-uuid/a9116ef3-554e-47b6-81ef-c5647f994ded /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-2h6KyedarmGVtAhpQFgb6PYRzfBhW78AwAEIn5Wsc61OT57LQwaupV3ffDK9k8U5", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"a9116ef3-554e-47b6-81ef-c5647f994ded", "ID_FS_UUID_ENC"=>"a9116ef3-554e-47b6-81ef-c5647f994ded", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27534", "nomdmonddf"=>"1", "nomdmonisw
Sep 12 02:01:30 node-1 nailgun-agent: "=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.810227 #13105] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.810296 #13105] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.810327 #13105] DEBUG -- : Device dm-5 seems to be appropriate
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.810361 #13105] DEBUG -- : Getting udev properties for device: ram0
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.814486 #13105] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80500", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.814584 #13105] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.814674 #13105] DEBUG -- : Device ram0 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.814726 #13105] DEBUG -- : Getting udev properties for device: ram1
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.818749 #13105] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80517", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.818853 #13105] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.818950 #13105] DEBUG -- : Device ram1 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.819019 #13105] DEBUG -- : Getting udev properties for device: ram2
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.823016 #13105] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80621", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.823101 #13105] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.823253 #13105] DEBUG -- : Device ram2 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.823347 #13105] DEBUG -- : Getting udev properties for device: ram3
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.827521 #13105] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3080636", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.827595 #13105] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.827723 #13105] DEBUG -- : Device ram3 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.827777 #13105] DEBUG -- : Getting udev properties for device: ram4
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.832302 #13105] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80971", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.832407 #13105] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.832497 #13105] DEBUG -- : Device ram4 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.832549 #13105] DEBUG -- : Getting udev properties for device: ram5
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.836517 #13105] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80993", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.836656 #13105] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.836773 #13105] DEBUG -- : Device ram5 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.836828 #13105] DEBUG -- : Getting udev properties for device: ram6
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.841732 #13105] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81006", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.841807 #13105] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.841940 #13105] DEBUG -- : Device ram6 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.841994 #13105] DEBUG -- : Getting udev properties for device: ram7
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.846138 #13105] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81018", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.846209 #13105] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.846297 #13105] DEBUG -- : Device ram7 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.846351 #13105] DEBUG -- : Getting udev properties for device: ram8
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.850413 #13105] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81031", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.850509 #13105] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.850597 #13105] DEBUG -- : Device ram8 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.850648 #13105] DEBUG -- : Getting udev properties for device: ram9
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.854921 #13105] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81043", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.854994 #13105] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.855092 #13105] DEBUG -- : Device ram9 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.855175 #13105] DEBUG -- : Getting udev properties for device: loop0
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.859923 #13105] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80397", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.859998 #13105] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.860084 #13105] DEBUG -- : Device loop0 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.860158 #13105] DEBUG -- : Getting udev properties for device: loop1
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.865564 #13105] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80411", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.865637 #13105] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.865724 #13105] DEBUG -- : Device loop1 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.865798 #13105] DEBUG -- : Getting udev properties for device: loop2
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.871326 #13105] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80421", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.871403 #13105] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.871546 #13105] DEBUG -- : Device loop2 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.871599 #13105] DEBUG -- : Getting udev properties for device: loop3
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.876131 #13105] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80432", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.876200 #13105] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.876343 #13105] DEBUG -- : Device loop3 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.876396 #13105] DEBUG -- : Getting udev properties for device: loop4
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.880353 #13105] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80445", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.880455 #13105] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.880542 #13105] DEBUG -- : Device loop4 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.880623 #13105] DEBUG -- : Getting udev properties for device: loop5
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.884452 #13105] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80461", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.884523 #13105] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.884668 #13105] DEBUG -- : Device loop5 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.884720 #13105] DEBUG -- : Getting udev properties for device: loop6
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.890204 #13105] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80472", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.890289 #13105] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.890407 #13105] DEBUG -- : Device loop6 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.890461 #13105] DEBUG -- : Getting udev properties for device: loop7
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.894567 #13105] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80486", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.894637 #13105] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.894719 #13105] DEBUG -- : Device loop7 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.894773 #13105] DEBUG -- : Getting udev properties for device: ram10
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.898343 #13105] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80534", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.898455 #13105] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.898543 #13105] DEBUG -- : Device ram10 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.898592 #13105] DEBUG -- : Getting udev properties for device: ram11
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.902496 #13105] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80546", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.902577 #13105] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.902725 #13105] DEBUG -- : Device ram11 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.902775 #13105] DEBUG -- : Getting udev properties for device: ram12
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.913867 #13105] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80559", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.913925 #13105] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.913994 #13105] DEBUG -- : Device ram12 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.914031 #13105] DEBUG -- : Getting udev properties for device: ram13
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.918429 #13105] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80578", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.918505 #13105] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.918601 #13105] DEBUG -- : Device ram13 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.918634 #13105] DEBUG -- : Getting udev properties for device: ram14
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.922354 #13105] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80591", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.922403 #13105] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.922463 #13105] DEBUG -- : Device ram14 removable parameter: "0"
Sep 12 02:01:30 node-1 nailgun-agent: D, [2016-09-12T02:01:30.922497 #13105] DEBUG -- : Getting udev properties for device: ram15
Sep 12 02:01:30 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.926972 #13105] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80607", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927029 #13105] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927114 #13105] DEBUG -- : Device ram15 removable parameter: "0"
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927177 #13105] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927201 #13105] DEBUG -- : Block device seems to be physical data storage: sda
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927265 #13105] DEBUG -- : Found block device: dm-0
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927289 #13105] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927313 #13105] DEBUG -- : Found block device: dm-1
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927330 #13105] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927423 #13105] DEBUG -- : Found block device: dm-2
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927441 #13105] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927456 #13105] DEBUG -- : Found block device: dm-3
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927472 #13105] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927488 #13105] DEBUG -- : Found block device: dm-4
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927505 #13105] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927520 #13105] DEBUG -- : Found block device: dm-5
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927537 #13105] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927630 #13105] DEBUG -- : Found block device: ram0
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927649 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927667 #13105] DEBUG -- : Found block device: ram1
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927685 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927701 #13105] DEBUG -- : Found block device: ram2
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927719 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927733 #13105] DEBUG -- : Found block device: ram3
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927750 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927843 #13105] DEBUG -- : Found block device: ram4
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927861 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927876 #13105] DEBUG -- : Found block device: ram5
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927892 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927906 #13105] DEBUG -- : Found block device: ram6
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927922 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927937 #13105] DEBUG -- : Found block device: ram7
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927957 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.927972 #13105] DEBUG -- : Found block device: ram8
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928052 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928068 #13105] DEBUG -- : Found block device: ram9
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928086 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928100 #13105] DEBUG -- : Found block device: loop0
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928117 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928132 #13105] DEBUG -- : Found block device: loop1
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928150 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928165 #13105] DEBUG -- : Found block device: loop2
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928241 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928257 #13105] DEBUG -- : Found block device: loop3
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928273 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928288 #13105] DEBUG -- : Found block device: loop4
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928309 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928324 #13105] DEBUG -- : Found block device: loop5
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928342 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928356 #13105] DEBUG -- : Found block device: loop6
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928423 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928440 #13105] DEBUG -- : Found block device: loop7
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928456 #13105] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928470 #13105] DEBUG -- : Found block device: ram10
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928487 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928501 #13105] DEBUG -- : Found block device: ram11
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928517 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928531 #13105] DEBUG -- : Found block device: ram12
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928549 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928564 #13105] DEBUG -- : Found block device: ram13
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928633 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928649 #13105] DEBUG -- : Found block device: ram14
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928665 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928684 #13105] DEBUG -- : Found block device: ram15
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928700 #13105] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:30.928753 #13105] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Sep 12 02:01:31 node-1 nailgun-agent: D, [2016-09-12T02:01:31.092138 #13105] DEBUG -- : Response: status: 200 body: {"id": 1}
Sep 12 02:01:31 node-1 nailgun-agent: I, [2016-09-12T02:01:31.092575 #13105]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 12 02:01:32 node-1 puppet-user[14998]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 12 02:01:32 node-1 puppet-user[14998]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep 12 02:01:36 node-1 puppet-user[14998]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 12 02:02:01 node-1 CRON[17212]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 12 02:02:07 node-1 puppet-user[14998]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 12 02:02:07 node-1 puppet-user[14998]: Finished catalog run in 35.31 seconds
Sep 12 02:02:08 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 12 02:02:08 node-1 nailgun-agent: I, [2016-09-12T02:02:08.271567 #17215]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 12 02:02:09 node-1 puppet-user[17582]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 12 02:02:09 node-1 puppet-user[17582]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Sep 12 02:02:10 node-1 puppet-user[17582]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 12 02:02:10 node-1 puppet-user[17582]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 12 02:02:10 node-1 puppet-user[17582]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 12 02:02:10 node-1 puppet-user[17582]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 12 02:02:10 node-1 puppet-user[17582]: Finished catalog run in 0.08 seconds
Sep 12 02:02:12 node-1 puppet-user[18169]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 12 02:02:12 node-1 puppet-user[18169]: Compiled catalog for node-1.domain.tld in environment production in 0.80 seconds
Sep 12 02:02:13 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 12 02:02:13 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 12 02:02:13 node-1 crontab[18604]: (root) LIST (root)
Sep 12 02:02:13 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 12 02:02:13 node-1 crontab[18605]: (root) REPLACE (root)
Sep 12 02:02:15 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 12 02:02:16 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 12 02:02:17 node-1 puppet-user[18169]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 12 02:02:17 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8396" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 12 02:02:17 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 12 02:02:19 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:19 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:19 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:19 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:19 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:39 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:39 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:39 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:39 node-1 multipathd: uevent trigger error
<27>Sep 12 02:02:39 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:03:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:13 node-1 ntpdate[2236]: no servers can be used, exiting
<27>Sep 12 02:04:13 node-1 ntpdate[2518]: no servers can be used, exiting
<27>Sep 12 02:04:44 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:44 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:44 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:44 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:48 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:48 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:48 node-1 multipathd: uevent trigger error
<27>Sep 12 02:04:48 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:05:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:12 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:12 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:12 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:12 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:12 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:14 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 12 02:06:14 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 12 02:06:20 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 12 02:06:20 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 12 02:06:26 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 12 02:06:31 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 12 02:06:31 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 12 02:06:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:52 node-1 multipathd: uevent trigger error
<129>Sep 12 02:06:54 node-1 haproxy[22845]: 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>Sep 12 02:06:54 node-1 haproxy[22845]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:06:55 node-1 haproxy[22849]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:06:55 node-1 haproxy[22849]: proxy mysqld has no server available!
<27>Sep 12 02:06:57 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:57 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:57 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:57 node-1 multipathd: uevent trigger error
<27>Sep 12 02:06:57 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:00 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:03 node-1 haproxy[25474]: 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>Sep 12 02:07:03 node-1 haproxy[25474]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:04 node-1 haproxy[25478]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:04 node-1 haproxy[25478]: proxy mysqld has no server available!
<129>Sep 12 02:07:04 node-1 haproxy[25478]: 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>Sep 12 02:07:04 node-1 haproxy[25478]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:05 node-1 haproxy[25478]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:05 node-1 haproxy[25478]: proxy object-storage has no server available!
<27>Sep 12 02:07:06 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:06 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:06 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:06 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:08 node-1 haproxy[26845]: 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>Sep 12 02:07:08 node-1 haproxy[26845]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:09 node-1 haproxy[26849]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:09 node-1 haproxy[26849]: proxy neutron has no server available!
<129>Sep 12 02:07:09 node-1 haproxy[26849]: 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>Sep 12 02:07:09 node-1 haproxy[26849]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:09 node-1 haproxy[26849]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:09 node-1 haproxy[26849]: proxy mysqld has no server available!
<129>Sep 12 02:07:09 node-1 haproxy[26849]: 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>Sep 12 02:07:10 node-1 haproxy[26849]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:10 node-1 haproxy[26849]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:10 node-1 haproxy[26849]: proxy object-storage has no server available!
<27>Sep 12 02:07:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:11 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:14 node-1 haproxy[28265]: 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>Sep 12 02:07:14 node-1 haproxy[28265]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:14 node-1 haproxy[28265]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:14 node-1 haproxy[28265]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:14 node-1 haproxy[28265]: 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>Sep 12 02:07:14 node-1 haproxy[28265]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:14 node-1 haproxy[28265]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:14 node-1 haproxy[28265]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:14 node-1 haproxy[28265]: 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>Sep 12 02:07:15 node-1 haproxy[28276]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:15 node-1 haproxy[28276]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:15 node-1 haproxy[28276]: proxy neutron has no server available!
<129>Sep 12 02:07:15 node-1 haproxy[28276]: 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>Sep 12 02:07:15 node-1 haproxy[28276]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:15 node-1 haproxy[28276]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:15 node-1 haproxy[28276]: proxy mysqld has no server available!
<129>Sep 12 02:07:15 node-1 haproxy[28276]: 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>Sep 12 02:07:15 node-1 haproxy[28276]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:16 node-1 haproxy[28276]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:16 node-1 haproxy[28276]: proxy object-storage has no server available!
<27>Sep 12 02:07:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:17 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:19 node-1 haproxy[29622]: 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>Sep 12 02:07:19 node-1 haproxy[29622]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:19 node-1 haproxy[29622]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:19 node-1 haproxy[29622]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:19 node-1 haproxy[29622]: 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>Sep 12 02:07:19 node-1 haproxy[29622]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:20 node-1 haproxy[29646]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:20 node-1 haproxy[29646]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:20 node-1 haproxy[29646]: 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>Sep 12 02:07:20 node-1 haproxy[29646]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:20 node-1 haproxy[29646]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:20 node-1 haproxy[29646]: proxy neutron has no server available!
<129>Sep 12 02:07:20 node-1 haproxy[29646]: 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>Sep 12 02:07:20 node-1 haproxy[29646]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:20 node-1 haproxy[29646]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:20 node-1 haproxy[29646]: proxy mysqld has no server available!
<129>Sep 12 02:07:20 node-1 haproxy[29646]: 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>Sep 12 02:07:20 node-1 haproxy[29646]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:21 node-1 haproxy[29646]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:21 node-1 haproxy[29646]: proxy object-storage has no server available!
<129>Sep 12 02:07:21 node-1 haproxy[29646]: 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>Sep 12 02:07:21 node-1 haproxy[29646]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:21 node-1 haproxy[29646]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:21 node-1 haproxy[29646]: proxy aodh has no server available!
<27>Sep 12 02:07:22 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:22 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:22 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:22 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:22 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:22 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:24 node-1 haproxy[31109]: 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>Sep 12 02:07:24 node-1 haproxy[31109]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:25 node-1 haproxy[31113]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:25 node-1 haproxy[31113]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:25 node-1 haproxy[31113]: 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>Sep 12 02:07:25 node-1 haproxy[31113]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:25 node-1 haproxy[31113]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:25 node-1 haproxy[31113]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:25 node-1 haproxy[31113]: 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>Sep 12 02:07:25 node-1 haproxy[31113]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:25 node-1 haproxy[31113]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:25 node-1 haproxy[31113]: proxy neutron has no server available!
<129>Sep 12 02:07:25 node-1 haproxy[31113]: 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>Sep 12 02:07:25 node-1 haproxy[31113]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:25 node-1 haproxy[31113]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:25 node-1 haproxy[31113]: proxy mysqld has no server available!
<129>Sep 12 02:07:26 node-1 haproxy[31113]: 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>Sep 12 02:07:26 node-1 haproxy[31113]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:26 node-1 haproxy[31113]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:26 node-1 haproxy[31113]: proxy object-storage has no server available!
<129>Sep 12 02:07:26 node-1 haproxy[31113]: 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>Sep 12 02:07:26 node-1 haproxy[31113]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:26 node-1 haproxy[31113]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:26 node-1 haproxy[31113]: proxy aodh has no server available!
<129>Sep 12 02:07:26 node-1 haproxy[31113]: 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>Sep 12 02:07:26 node-1 haproxy[31113]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:26 node-1 haproxy[31113]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:26 node-1 haproxy[31113]: proxy ceilometer has no server available!
<27>Sep 12 02:07:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:28 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:30 node-1 haproxy[32458]: 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>Sep 12 02:07:30 node-1 haproxy[32458]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:30 node-1 haproxy[32458]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:30 node-1 haproxy[32458]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:30 node-1 haproxy[32458]: 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>Sep 12 02:07:30 node-1 haproxy[32458]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:30 node-1 haproxy[32458]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:30 node-1 haproxy[32458]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:30 node-1 haproxy[32458]: 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>Sep 12 02:07:30 node-1 haproxy[32458]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:30 node-1 haproxy[32458]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:30 node-1 haproxy[32458]: proxy neutron has no server available!
<129>Sep 12 02:07:31 node-1 haproxy[32462]: 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>Sep 12 02:07:31 node-1 haproxy[32462]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:31 node-1 haproxy[32462]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:31 node-1 haproxy[32462]: proxy mysqld has no server available!
<129>Sep 12 02:07:31 node-1 haproxy[32462]: 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>Sep 12 02:07:31 node-1 haproxy[32462]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:31 node-1 haproxy[32462]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:31 node-1 haproxy[32462]: proxy object-storage has no server available!
<129>Sep 12 02:07:31 node-1 haproxy[32462]: 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>Sep 12 02:07:31 node-1 haproxy[32462]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:31 node-1 haproxy[32462]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:31 node-1 haproxy[32462]: proxy aodh has no server available!
<129>Sep 12 02:07:31 node-1 haproxy[32462]: 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>Sep 12 02:07:32 node-1 haproxy[32462]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:32 node-1 haproxy[32462]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:32 node-1 haproxy[32462]: proxy ceilometer has no server available!
<27>Sep 12 02:07:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:33 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:35 node-1 haproxy[1563]: 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>Sep 12 02:07:35 node-1 haproxy[1563]: 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>Sep 12 02:07:35 node-1 haproxy[1563]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:35 node-1 haproxy[1563]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:35 node-1 haproxy[1563]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:35 node-1 haproxy[1563]: 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>Sep 12 02:07:36 node-1 haproxy[1575]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:36 node-1 haproxy[1575]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:36 node-1 haproxy[1575]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:36 node-1 haproxy[1575]: 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>Sep 12 02:07:36 node-1 haproxy[1575]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:36 node-1 haproxy[1575]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:36 node-1 haproxy[1575]: proxy neutron has no server available!
<129>Sep 12 02:07:36 node-1 haproxy[1575]: 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>Sep 12 02:07:36 node-1 haproxy[1575]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:36 node-1 haproxy[1575]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:36 node-1 haproxy[1575]: proxy mysqld has no server available!
<129>Sep 12 02:07:36 node-1 haproxy[1575]: 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>Sep 12 02:07:36 node-1 haproxy[1575]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:36 node-1 haproxy[1575]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:36 node-1 haproxy[1575]: proxy object-storage has no server available!
<129>Sep 12 02:07:36 node-1 haproxy[1575]: 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>Sep 12 02:07:37 node-1 haproxy[1575]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:37 node-1 haproxy[1575]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:37 node-1 haproxy[1575]: proxy aodh has no server available!
<129>Sep 12 02:07:37 node-1 haproxy[1575]: 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>Sep 12 02:07:37 node-1 haproxy[1575]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:37 node-1 haproxy[1575]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:37 node-1 haproxy[1575]: proxy ceilometer has no server available!
<27>Sep 12 02:07:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:38 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:38 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:41 node-1 haproxy[2935]: 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>Sep 12 02:07:41 node-1 haproxy[2935]: 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>Sep 12 02:07:41 node-1 haproxy[2935]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:41 node-1 haproxy[2935]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:41 node-1 haproxy[2935]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:41 node-1 haproxy[2935]: 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>Sep 12 02:07:41 node-1 haproxy[2935]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:41 node-1 haproxy[2935]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:41 node-1 haproxy[2935]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:41 node-1 haproxy[2935]: 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>Sep 12 02:07:41 node-1 haproxy[2935]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:41 node-1 haproxy[2935]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:41 node-1 haproxy[2935]: proxy glance-api has no server available!
<129>Sep 12 02:07:41 node-1 haproxy[2935]: 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>Sep 12 02:07:42 node-1 haproxy[2939]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:42 node-1 haproxy[2939]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:42 node-1 haproxy[2939]: proxy glance-glare has no server available!
<129>Sep 12 02:07:42 node-1 haproxy[2939]: 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>Sep 12 02:07:42 node-1 haproxy[2939]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:42 node-1 haproxy[2939]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:42 node-1 haproxy[2939]: proxy neutron has no server available!
<129>Sep 12 02:07:42 node-1 haproxy[2939]: 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>Sep 12 02:07:42 node-1 haproxy[2939]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:42 node-1 haproxy[2939]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:42 node-1 haproxy[2939]: proxy glance-registry has no server available!
<129>Sep 12 02:07:42 node-1 haproxy[2939]: 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>Sep 12 02:07:42 node-1 haproxy[2939]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:42 node-1 haproxy[2939]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:42 node-1 haproxy[2939]: proxy mysqld has no server available!
<129>Sep 12 02:07:42 node-1 haproxy[2939]: 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>Sep 12 02:07:42 node-1 haproxy[2939]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:42 node-1 haproxy[2939]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:42 node-1 haproxy[2939]: proxy object-storage has no server available!
<129>Sep 12 02:07:42 node-1 haproxy[2939]: 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>Sep 12 02:07:42 node-1 haproxy[2939]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:43 node-1 haproxy[2939]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:43 node-1 haproxy[2939]: proxy aodh has no server available!
<129>Sep 12 02:07:43 node-1 haproxy[2939]: 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>Sep 12 02:07:43 node-1 haproxy[2939]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:43 node-1 haproxy[2939]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:43 node-1 haproxy[2939]: proxy ceilometer has no server available!
<27>Sep 12 02:07:44 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:44 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:44 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:44 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:47 node-1 haproxy[4353]: 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>Sep 12 02:07:47 node-1 haproxy[4353]: 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>Sep 12 02:07:47 node-1 haproxy[4353]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:47 node-1 haproxy[4353]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:47 node-1 haproxy[4353]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:47 node-1 haproxy[4353]: 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>Sep 12 02:07:47 node-1 haproxy[4353]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:47 node-1 haproxy[4353]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:47 node-1 haproxy[4353]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:47 node-1 haproxy[4353]: 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>Sep 12 02:07:47 node-1 haproxy[4353]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:47 node-1 haproxy[4353]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:47 node-1 haproxy[4353]: proxy nova-api has no server available!
<129>Sep 12 02:07:47 node-1 haproxy[4353]: 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>Sep 12 02:07:47 node-1 haproxy[4353]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:47 node-1 haproxy[4353]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:47 node-1 haproxy[4353]: proxy nova-metadata-api has no server available!
<129>Sep 12 02:07:47 node-1 haproxy[4353]: 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>Sep 12 02:07:47 node-1 haproxy[4353]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:47 node-1 haproxy[4353]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:47 node-1 haproxy[4353]: proxy glance-api has no server available!
<129>Sep 12 02:07:48 node-1 haproxy[4357]: 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>Sep 12 02:07:48 node-1 haproxy[4357]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:48 node-1 haproxy[4357]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:48 node-1 haproxy[4357]: proxy glance-glare has no server available!
<129>Sep 12 02:07:48 node-1 haproxy[4357]: 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>Sep 12 02:07:48 node-1 haproxy[4357]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:48 node-1 haproxy[4357]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:48 node-1 haproxy[4357]: proxy neutron has no server available!
<129>Sep 12 02:07:48 node-1 haproxy[4357]: 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>Sep 12 02:07:48 node-1 haproxy[4357]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:48 node-1 haproxy[4357]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:48 node-1 haproxy[4357]: proxy glance-registry has no server available!
<129>Sep 12 02:07:48 node-1 haproxy[4357]: 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>Sep 12 02:07:48 node-1 haproxy[4357]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:48 node-1 haproxy[4357]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:48 node-1 haproxy[4357]: proxy mysqld has no server available!
<129>Sep 12 02:07:48 node-1 haproxy[4357]: 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>Sep 12 02:07:48 node-1 haproxy[4357]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:48 node-1 haproxy[4357]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:48 node-1 haproxy[4357]: proxy object-storage has no server available!
<129>Sep 12 02:07:48 node-1 haproxy[4357]: 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>Sep 12 02:07:48 node-1 haproxy[4357]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:48 node-1 haproxy[4357]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:48 node-1 haproxy[4357]: proxy aodh has no server available!
<129>Sep 12 02:07:48 node-1 haproxy[4357]: 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>Sep 12 02:07:48 node-1 haproxy[4357]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:48 node-1 haproxy[4357]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:48 node-1 haproxy[4357]: proxy ceilometer has no server available!
<129>Sep 12 02:07:49 node-1 haproxy[4357]: 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>Sep 12 02:07:49 node-1 haproxy[4357]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:49 node-1 haproxy[4357]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:49 node-1 haproxy[4357]: proxy nova-novncproxy has no server available!
<27>Sep 12 02:07:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:50 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:53 node-1 haproxy[5680]: 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>Sep 12 02:07:53 node-1 haproxy[5680]: 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>Sep 12 02:07:53 node-1 haproxy[5680]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:53 node-1 haproxy[5680]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:53 node-1 haproxy[5680]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:53 node-1 haproxy[5680]: 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>Sep 12 02:07:53 node-1 haproxy[5680]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:53 node-1 haproxy[5680]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:53 node-1 haproxy[5680]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:53 node-1 haproxy[5680]: 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>Sep 12 02:07:53 node-1 haproxy[5680]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:53 node-1 haproxy[5680]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:53 node-1 haproxy[5680]: proxy nova-api has no server available!
<129>Sep 12 02:07:53 node-1 haproxy[5680]: 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>Sep 12 02:07:53 node-1 haproxy[5680]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:53 node-1 haproxy[5680]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:53 node-1 haproxy[5680]: proxy nova-metadata-api has no server available!
<129>Sep 12 02:07:53 node-1 haproxy[5680]: 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>Sep 12 02:07:53 node-1 haproxy[5680]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:53 node-1 haproxy[5680]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:53 node-1 haproxy[5680]: proxy cinder-api has no server available!
<129>Sep 12 02:07:53 node-1 haproxy[5680]: 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>Sep 12 02:07:53 node-1 haproxy[5680]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:53 node-1 haproxy[5680]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:53 node-1 haproxy[5680]: proxy glance-api has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:54 node-1 haproxy[5684]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:54 node-1 haproxy[5684]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:54 node-1 haproxy[5684]: proxy glance-glare has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:54 node-1 haproxy[5684]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:54 node-1 haproxy[5684]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:54 node-1 haproxy[5684]: proxy neutron has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:54 node-1 haproxy[5684]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:54 node-1 haproxy[5684]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:54 node-1 haproxy[5684]: proxy glance-registry has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:54 node-1 haproxy[5684]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:54 node-1 haproxy[5684]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:54 node-1 haproxy[5684]: proxy mysqld has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:54 node-1 haproxy[5684]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:54 node-1 haproxy[5684]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:54 node-1 haproxy[5684]: proxy object-storage has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:54 node-1 haproxy[5684]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:54 node-1 haproxy[5684]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:54 node-1 haproxy[5684]: proxy aodh has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:54 node-1 haproxy[5684]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:54 node-1 haproxy[5684]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:54 node-1 haproxy[5684]: proxy ceilometer has no server available!
<129>Sep 12 02:07:54 node-1 haproxy[5684]: 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>Sep 12 02:07:55 node-1 haproxy[5684]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:55 node-1 haproxy[5684]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:55 node-1 haproxy[5684]: proxy nova-novncproxy has no server available!
<27>Sep 12 02:07:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:07:56 node-1 multipathd: uevent trigger error
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:59 node-1 haproxy[7050]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:59 node-1 haproxy[7050]: proxy keystone-1 has no server available!
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:59 node-1 haproxy[7050]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:59 node-1 haproxy[7050]: proxy keystone-2 has no server available!
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:59 node-1 haproxy[7050]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:59 node-1 haproxy[7050]: proxy nova-api has no server available!
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:59 node-1 haproxy[7050]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:59 node-1 haproxy[7050]: proxy nova-metadata-api has no server available!
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:59 node-1 haproxy[7050]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:59 node-1 haproxy[7050]: proxy cinder-api has no server available!
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:59 node-1 haproxy[7050]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:59 node-1 haproxy[7050]: proxy glance-api has no server available!
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:07:59 node-1 haproxy[7050]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:07:59 node-1 haproxy[7050]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:07:59 node-1 haproxy[7050]: proxy glance-glare has no server available!
<129>Sep 12 02:07:59 node-1 haproxy[7050]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy neutron has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy glance-registry has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy mysqld has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy object-storage has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy aodh has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy ceilometer has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy heat-api has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy heat-api-cfn has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:00 node-1 haproxy[7054]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:00 node-1 haproxy[7054]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:00 node-1 haproxy[7054]: proxy heat-api-cloudwatch has no server available!
<129>Sep 12 02:08:00 node-1 haproxy[7054]: 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>Sep 12 02:08:01 node-1 haproxy[7054]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:08:01 node-1 haproxy[7054]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 12 02:08:01 node-1 haproxy[7054]: proxy nova-novncproxy has no server available!
<27>Sep 12 02:08:02 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:02 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:02 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:02 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:02 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:08:15 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 12 02:08:40 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>Sep 12 02:08:42 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 12 02:09:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:09:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 12 02:09:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:09:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:09:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:09:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:30 node-1 multipathd: uevent trigger error
<43>Sep 12 02:11:48 node-1 apache2_error [Mon Sep 12 02:11:43.669192 2016] [mpm_event:notice] [pid 12954:tid 140116104755072] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 12 02:11:48 node-1 apache2_error [Mon Sep 12 02:11:43.669339 2016] [core:notice] [pid 12954:tid 140116104755072] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 12 02:11:48 node-1 apache2_error [Mon Sep 12 02:11:46.838342 2016] [mpm_event:notice] [pid 12954:tid 140116104755072] AH00491: caught SIGTERM, shutting down
<43>Sep 12 02:11:48 node-1 apache2_error [Mon Sep 12 02:11:47.931191 2016] [mpm_worker:notice] [pid 13374:tid 140703956879232] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 12 02:11:48 node-1 apache2_error [Mon Sep 12 02:11:47.931263 2016] [core:notice] [pid 13374:tid 140703956879232] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 12 02:11:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:52 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:11:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:12:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:14 node-1 multipathd: uevent trigger error
<43>Sep 12 02:12:48 node-1 apache2_error [Mon Sep 12 02:12:47.936932 2016] [mpm_worker:notice] [pid 13374:tid 140703956879232] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 12 02:12:48 node-1 apache2_error [Mon Sep 12 02:12:47.943812 2016] [mpm_worker:warn] [pid 13374:tid 140703956879232] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 12 02:12:48 node-1 apache2_error [Mon Sep 12 02:12:47.944896 2016] [mpm_worker:notice] [pid 13374:tid 140703956879232] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 12 02:12:48 node-1 apache2_error [Mon Sep 12 02:12:47.944915 2016] [core:notice] [pid 13374:tid 140703956879232] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 12 02:12:51 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:51 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:51 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:51 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:51 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:51 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:12:56 node-1 multipathd: uevent trigger error
<43>Sep 12 02:14:08 node-1 apache2_error [Mon Sep 12 02:14:05.660463 2016] [mpm_worker:notice] [pid 13374:tid 140703956879232] AH00295: caught SIGTERM, shutting down
<43>Sep 12 02:14:08 node-1 apache2_error [Mon Sep 12 02:14:06.409608 2016] [mpm_worker:notice] [pid 5505:tid 140558617671552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 12 02:14:08 node-1 apache2_error [Mon Sep 12 02:14:06.409655 2016] [core:notice] [pid 5505:tid 140558617671552] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 12 02:14:58 node-1 apache2_error [Mon Sep 12 02:14:50.556791 2016] [mpm_worker:notice] [pid 5505:tid 140558617671552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 12 02:14:58 node-1 apache2_error [Mon Sep 12 02:14:50.567508 2016] [mpm_worker:warn] [pid 5505:tid 140558617671552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 12 02:14:58 node-1 apache2_error [Mon Sep 12 02:14:50.573711 2016] [mpm_worker:notice] [pid 5505:tid 140558617671552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 12 02:14:58 node-1 apache2_error [Mon Sep 12 02:14:50.573739 2016] [core:notice] [pid 5505:tid 140558617671552] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 12 02:15:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:16:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:11 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:16:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:01 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:01 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:01 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:01 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:01 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:01 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:17:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:18:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:18:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:18:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:18:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:18:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:18:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:18:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:19:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:19:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:19:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:19:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:19:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:19:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:47 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:47 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:47 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:47 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:47 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:20:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:21:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:23:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:23:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:24:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:28 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:24:53 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:37 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:44 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Sep 12 02:25:44 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Sep 12 02:25:44 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Sep 12 02:25:45 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Sep 12 02:25:45 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Sep 12 02:25:46 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:46 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:46 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:46 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:46 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:46 node-1 multipathd: uevent trigger error
<27>Sep 12 02:25:46 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:32 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:32 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:32 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:32 node-1 multipathd: uevent trigger error
<27>Sep 12 02:26:32 node-1 multipathd: uevent trigger error
<27>Sep 12 02:27:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:28:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:28:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:28:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:28:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:28:55 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:36 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:29:41 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:05 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 12 02:30:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:25 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:30:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:31:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:31:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:31:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:31:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:27 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:43 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:43 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:43 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:43 node-1 multipathd: uevent trigger error
<27>Sep 12 02:32:43 node-1 multipathd: uevent trigger error
<11>Sep 12 02:32:57 node-1 liberasurecode[732]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:57 node-1 liberasurecode[732]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:57 node-1 liberasurecode[732]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:57 node-1 liberasurecode[732]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:57 node-1 liberasurecode[761]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:57 node-1 liberasurecode[761]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:57 node-1 liberasurecode[761]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:57 node-1 liberasurecode[761]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:59 node-1 liberasurecode[1399]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:59 node-1 liberasurecode[1399]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:59 node-1 liberasurecode[1399]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:32:59 node-1 liberasurecode[1399]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2051]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2051]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2091]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2091]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2091]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2091]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2135]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2135]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2135]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2135]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2213]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2213]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2225]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2225]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2225]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2225]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2237]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2237]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2237]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:05 node-1 liberasurecode[2237]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:06 node-1 liberasurecode[2256]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:06 node-1 liberasurecode[2256]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:06 node-1 liberasurecode[2256]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:06 node-1 liberasurecode[2256]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 12 02:33:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Sep 12 02:33:22 node-1 liberasurecode[3213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:22 node-1 liberasurecode[3213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:22 node-1 liberasurecode[3213]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:33:22 node-1 liberasurecode[3213]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 12 02:33:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:33:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:33:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:33:31 node-1 multipathd: uevent trigger error
<27>Sep 12 02:33:31 node-1 multipathd: uevent trigger error
<43>Sep 12 02:34:20 node-1 apache2_error [Mon Sep 12 02:34:18.459483 2016] [mpm_worker:notice] [pid 5505:tid 140558617671552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 12 02:34:20 node-1 apache2_error [Mon Sep 12 02:34:18.841294 2016] [mpm_worker:warn] [pid 5505:tid 140558617671552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 12 02:34:20 node-1 apache2_error [Mon Sep 12 02:34:18.845004 2016] [mpm_worker:notice] [pid 5505:tid 140558617671552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 12 02:34:20 node-1 apache2_error [Mon Sep 12 02:34:18.845025 2016] [core:notice] [pid 5505:tid 140558617671552] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 12 02:35:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:00 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:00 node-1 multipathd: uevent trigger error
<43>Sep 12 02:35:00 node-1 apache2_error [Mon Sep 12 02:34:55.954515 2016] [mpm_worker:notice] [pid 5505:tid 140558617671552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 12 02:35:00 node-1 apache2_error [Mon Sep 12 02:34:56.152923 2016] [mpm_worker:warn] [pid 5505:tid 140558617671552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 12 02:35:00 node-1 apache2_error [Mon Sep 12 02:34:56.161312 2016] [mpm_worker:notice] [pid 5505:tid 140558617671552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 12 02:35:00 node-1 apache2_error [Mon Sep 12 02:34:56.161344 2016] [core:notice] [pid 5505:tid 140558617671552] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 12 02:35:01 node-1 liberasurecode[18908]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:35:01 node-1 liberasurecode[18908]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:35:01 node-1 liberasurecode[18908]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:35:01 node-1 liberasurecode[18908]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 12 02:35:07 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:07 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:07 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:07 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:07 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:13 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:30 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:58 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:58 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:58 node-1 multipathd: uevent trigger error
<27>Sep 12 02:35:58 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:05 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 12 02:36:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:20 node-1 multipathd: uevent trigger error
<27>Sep 12 02:36:55 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 12 02:39:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:09 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:14 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:15 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:23 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:34 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:34 node-1 multipathd: uevent trigger error
<129>Sep 12 02:39:34 node-1 haproxy[9439]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 12 02:39:34 node-1 haproxy[9439]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 12 02:39:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:56 node-1 multipathd: uevent trigger error
<27>Sep 12 02:39:56 node-1 multipathd: uevent trigger error
<11>Sep 12 02:40:01 node-1 liberasurecode[20617]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:40:01 node-1 liberasurecode[20617]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:40:01 node-1 liberasurecode[20617]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 12 02:40:01 node-1 liberasurecode[20617]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 12 02:40:10 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:10 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:10 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:10 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:16 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:17 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:21 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:33 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:40:45 node-1 multipathd: uevent trigger error
<129>Sep 12 02:40:54 node-1 haproxy[9439]: 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.
<27>Sep 12 02:41:40 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:40 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:40 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:40 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:40 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:45 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:50 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:54 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:54 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:54 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:54 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:59 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:59 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:59 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:59 node-1 multipathd: uevent trigger error
<27>Sep 12 02:41:59 node-1 multipathd: uevent trigger error
<27>Sep 12 02:42:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:42:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:42:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:42:03 node-1 multipathd: uevent trigger error
<27>Sep 12 02:42:03 node-1 multipathd: uevent trigger error
