Jul 22 00:14:31 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8396" x-info="http://www.rsyslog.com"] start
Jul 22 00:14:31 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 22 00:14:31 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 22 00:14:31 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 22 00:14:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 22 00:14:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 22 00:14:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 22 00:14:31 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 22 00:14:31 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4a7ab7cc-1206-433b-8521-154fd466d804 nomdmonddf nomdmonisw
Jul 22 00:14:31 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 22 00:14:31 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 22 00:14:31 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 22 00:14:31 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 22 00:14:31 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 22 00:14:31 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 22 00:14:31 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 22 00:14:31 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 22 00:14:31 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 22 00:14:31 node-1 kernel: [    0.000000] No AGP bridge found
Jul 22 00:14:31 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 22 00:14:31 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 22 00:14:31 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 22 00:14:31 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 22 00:14:31 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 22 00:14:31 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 22 00:14:31 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 22 00:14:31 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 22 00:14:31 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 22 00:14:31 node-1 kernel: [    0.000000]   2 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000]   3 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000]   4 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000]   5 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000]   6 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000]   7 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000]   8 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000]   9 disabled
Jul 22 00:14:31 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 22 00:14:31 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 22 00:14:31 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 22 00:14:31 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 22 00:14:31 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 22 00:14:31 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 22 00:14:31 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 22 00:14:31 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 22 00:14:31 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 22 00:14:31 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 22 00:14:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 22 00:14:31 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 22 00:14:31 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 22 00:14:31 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 22 00:14:31 node-1 kernel: [    0.000000] Zone ranges:
Jul 22 00:14:31 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 22 00:14:31 node-1 kernel: [    0.000000] Early memory node ranges
Jul 22 00:14:31 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 22 00:14:31 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 22 00:14:31 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 22 00:14:31 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 22 00:14:31 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 22 00:14:31 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 22 00:14:31 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 22 00:14:31 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 22 00:14:31 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 22 00:14:31 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 22 00:14:31 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 22 00:14:31 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 22 00:14:31 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 22 00:14:31 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 22 00:14:31 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 22 00:14:31 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 22 00:14:31 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 22 00:14:31 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 22 00:14:31 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 22 00:14:31 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 22 00:14:31 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 22 00:14:31 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 22 00:14:31 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 22 00:14:31 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 22 00:14:31 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 22 00:14:31 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 22 00:14:31 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4a7ab7cc-1206-433b-8521-154fd466d804 nomdmonddf nomdmonisw
Jul 22 00:14:31 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 22 00:14:31 node-1 kernel: [    0.000000] Checking aperture...
Jul 22 00:14:31 node-1 kernel: [    0.000000] No AGP bridge found
Jul 22 00:14:31 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 22 00:14:31 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 22 00:14:31 node-1 kernel: [    0.000000] Memory: 32653324K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Jul 22 00:14:31 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 22 00:14:31 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 22 00:14:31 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 22 00:14:31 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 22 00:14:31 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 22 00:14:31 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 22 00:14:31 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 22 00:14:31 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 22 00:14:31 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 22 00:14:31 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 22 00:14:31 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 22 00:14:31 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 22 00:14:31 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 22 00:14:31 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 22 00:14:31 node-1 kernel: [    0.004000] tsc: Detected 3491.991 MHz processor
Jul 22 00:14:31 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.98 BogoMIPS (lpj=13967964)
Jul 22 00:14:31 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 22 00:14:31 node-1 kernel: [    0.000044] Security Framework initialized
Jul 22 00:14:31 node-1 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 22 00:14:31 node-1 kernel: [    0.000063] Yama: becoming mindful.
Jul 22 00:14:31 node-1 kernel: [    0.001466] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.006381] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.008313] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.008341] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.008637] Initializing cgroup subsys memory
Jul 22 00:14:31 node-1 kernel: [    0.008645] Initializing cgroup subsys devices
Jul 22 00:14:31 node-1 kernel: [    0.008646] Initializing cgroup subsys freezer
Jul 22 00:14:31 node-1 kernel: [    0.008648] Initializing cgroup subsys blkio
Jul 22 00:14:31 node-1 kernel: [    0.008650] Initializing cgroup subsys perf_event
Jul 22 00:14:31 node-1 kernel: [    0.008652] Initializing cgroup subsys hugetlb
Jul 22 00:14:31 node-1 kernel: [    0.008672] CPU: Physical Processor ID: 0
Jul 22 00:14:31 node-1 kernel: [    0.008673] CPU: Processor Core ID: 0
Jul 22 00:14:31 node-1 kernel: [    0.008677] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 22 00:14:31 node-1 kernel: [    0.008677] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 22 00:14:31 node-1 kernel: [    0.009370] mce: CPU supports 22 MCE banks
Jul 22 00:14:31 node-1 kernel: [    0.009398] CPU0: Thermal monitoring enabled (TM1)
Jul 22 00:14:31 node-1 kernel: [    0.009418] process: using mwait in idle threads
Jul 22 00:14:31 node-1 kernel: [    0.009421] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 22 00:14:31 node-1 kernel: [    0.009421] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 22 00:14:31 node-1 kernel: [    0.009421] tlb_flushall_shift: 6
Jul 22 00:14:31 node-1 kernel: [    0.009509] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 22 00:14:31 node-1 kernel: [    0.010234] ACPI: Core revision 20131115
Jul 22 00:14:31 node-1 kernel: [    0.022907] ACPI: All ACPI Tables successfully acquired
Jul 22 00:14:31 node-1 kernel: [    0.023067] ftrace: allocating 28617 entries in 112 pages
Jul 22 00:14:31 node-1 kernel: [    0.031885] dmar: Host address width 46
Jul 22 00:14:31 node-1 kernel: [    0.031887] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 22 00:14:31 node-1 kernel: [    0.031893] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 00:14:31 node-1 kernel: [    0.031895] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 22 00:14:31 node-1 kernel: [    0.031898] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 00:14:31 node-1 kernel: [    0.031900] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 22 00:14:31 node-1 kernel: [    0.031901] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 22 00:14:31 node-1 kernel: [    0.031902] dmar: ATSR flags: 0x0
Jul 22 00:14:31 node-1 kernel: [    0.031904] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 22 00:14:31 node-1 kernel: [    0.031905] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 22 00:14:31 node-1 kernel: [    0.032021] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 22 00:14:31 node-1 kernel: [    0.032022] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 00:14:31 node-1 kernel: [    0.032023] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 00:14:31 node-1 kernel: [    0.032024] HPET id 0 under DRHD base 0xc7ffc000
Jul 22 00:14:31 node-1 kernel: [    0.032025] Your BIOS is broken and requested that x2apic be disabled.
Jul 22 00:14:31 node-1 kernel: [    0.032025] This will slightly decrease performance.
Jul 22 00:14:31 node-1 kernel: [    0.032025] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 22 00:14:31 node-1 kernel: [    0.032457] Enabled IRQ remapping in xapic mode
Jul 22 00:14:31 node-1 kernel: [    0.032459] x2apic not enabled, IRQ remapping is in xapic mode
Jul 22 00:14:31 node-1 kernel: [    0.032462] Switched APIC routing to physical flat.
Jul 22 00:14:31 node-1 kernel: [    0.033089] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 22 00:14:31 node-1 kernel: [    0.072739] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 22 00:14:31 node-1 kernel: [    0.072745] TSC deadline timer enabled
Jul 22 00:14:31 node-1 kernel: [    0.072753] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 22 00:14:31 node-1 kernel: [    0.072758] ... version:                3
Jul 22 00:14:31 node-1 kernel: [    0.072759] ... bit width:              48
Jul 22 00:14:31 node-1 kernel: [    0.072760] ... generic registers:      4
Jul 22 00:14:31 node-1 kernel: [    0.072761] ... value mask:             0000ffffffffffff
Jul 22 00:14:31 node-1 kernel: [    0.072762] ... max period:             0000ffffffffffff
Jul 22 00:14:31 node-1 kernel: [    0.072763] ... fixed-purpose events:   3
Jul 22 00:14:31 node-1 kernel: [    0.072764] ... event mask:             000000070000000f
Jul 22 00:14:31 node-1 kernel: [    0.074188] x86: Booting SMP configuration:
Jul 22 00:14:31 node-1 kernel: [    0.088294] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 22 00:14:31 node-1 kernel: [    0.074190] .... node  #0, CPUs:        #1  #2  #3
Jul 22 00:14:31 node-1 kernel: [    0.116201] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 22 00:14:31 node-1 kernel: [    0.270163] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 22 00:14:31 node-1 kernel: [    0.325777] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 22 00:14:31 node-1 kernel: [    0.382632] x86: Booted up 2 nodes, 16 CPUs
Jul 22 00:14:31 node-1 kernel: [    0.382635] smpboot: Total of 16 processors activated (111755.80 BogoMIPS)
Jul 22 00:14:31 node-1 kernel: [    0.406596] devtmpfs: initialized
Jul 22 00:14:31 node-1 kernel: [    0.409702] EVM: security.selinux
Jul 22 00:14:31 node-1 kernel: [    0.409704] EVM: security.SMACK64
Jul 22 00:14:31 node-1 kernel: [    0.409705] EVM: security.ima
Jul 22 00:14:31 node-1 kernel: [    0.409706] EVM: security.capability
Jul 22 00:14:31 node-1 kernel: [    0.409757] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.410422] pinctrl core: initialized pinctrl subsystem
Jul 22 00:14:31 node-1 kernel: [    0.410484] regulator-dummy: no parameters
Jul 22 00:14:31 node-1 kernel: [    0.410516] RTC time:  0:13:55, date: 07/22/16
Jul 22 00:14:31 node-1 kernel: [    0.410549] NET: Registered protocol family 16
Jul 22 00:14:31 node-1 kernel: [    0.410633] cpuidle: using governor ladder
Jul 22 00:14:31 node-1 kernel: [    0.410634] cpuidle: using governor menu
Jul 22 00:14:31 node-1 kernel: [    0.410668] ACPI: bus type PCI registered
Jul 22 00:14:31 node-1 kernel: [    0.410669] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 22 00:14:31 node-1 kernel: [    0.410715] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 22 00:14:31 node-1 kernel: [    0.410718] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 22 00:14:31 node-1 kernel: [    0.424451] PCI: Using configuration type 1 for base access
Jul 22 00:14:31 node-1 kernel: [    0.425444] bio: create slab <bio-0> at 0
Jul 22 00:14:31 node-1 kernel: [    0.425718] ACPI: Added _OSI(Module Device)
Jul 22 00:14:31 node-1 kernel: [    0.425720] ACPI: Added _OSI(Processor Device)
Jul 22 00:14:31 node-1 kernel: [    0.425721] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 22 00:14:31 node-1 kernel: [    0.425722] ACPI: Added _OSI(Processor Aggregator Device)
Jul 22 00:14:31 node-1 kernel: [    0.438409] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 22 00:14:31 node-1 kernel: [    0.449889] ACPI: Interpreter enabled
Jul 22 00:14:31 node-1 kernel: [    0.449894] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 22 00:14:31 node-1 kernel: [    0.449898] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 22 00:14:31 node-1 kernel: [    0.449901] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 22 00:14:31 node-1 kernel: [    0.449908] ACPI: (supports S0 S4 S5)
Jul 22 00:14:31 node-1 kernel: [    0.449909] ACPI: Using IOAPIC for interrupt routing
Jul 22 00:14:31 node-1 kernel: [    0.449952] HEST: Table parsing has been initialized.
Jul 22 00:14:31 node-1 kernel: [    0.449954] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 22 00:14:31 node-1 kernel: [    0.450505] ACPI: No dock devices found.
Jul 22 00:14:31 node-1 kernel: [    0.462064] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 22 00:14:31 node-1 kernel: [    0.462069] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 00:14:31 node-1 kernel: [    0.462072] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 00:14:31 node-1 kernel: [    0.462101] PCI host bridge to bus 0000:ff
Jul 22 00:14:31 node-1 kernel: [    0.462103] pci_bus 0000:ff: root bus resource [bus ff]
Jul 22 00:14:31 node-1 kernel: [    0.462111] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462150] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.462180] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462215] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462245] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.462274] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.462306] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462335] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462366] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462394] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462420] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462447] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462476] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462502] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462529] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462556] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462583] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462610] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462637] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.462664] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462690] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.462715] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462741] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462771] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.462805] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462836] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462865] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462896] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462926] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462957] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.462989] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463020] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463050] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463081] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463111] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463142] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463173] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463201] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463229] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463261] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463293] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463330] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463363] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463395] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463423] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463452] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463483] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463513] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463545] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463575] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463607] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463635] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463663] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463692] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463721] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463751] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463782] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463839] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 22 00:14:31 node-1 kernel: [    0.463842] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 00:14:31 node-1 kernel: [    0.463844] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 00:14:31 node-1 kernel: [    0.463862] PCI host bridge to bus 0000:7f
Jul 22 00:14:31 node-1 kernel: [    0.463863] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 22 00:14:31 node-1 kernel: [    0.463868] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463895] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.463921] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463950] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.463972] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.463996] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.464021] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464047] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464069] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464091] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464113] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464135] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464159] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464181] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464204] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464233] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464255] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464279] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464303] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.464328] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464351] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.464376] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464399] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464425] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 00:14:31 node-1 kernel: [    0.464460] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464488] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464516] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464544] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464569] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464596] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464623] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464652] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464676] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464702] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464730] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464758] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464788] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464814] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464841] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464871] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464896] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464922] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464952] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.464980] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465007] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465032] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465057] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465084] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465108] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465135] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465165] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465190] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465213] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465239] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465264] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465295] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.465321] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.466578] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 22 00:14:31 node-1 kernel: [    0.466582] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 00:14:31 node-1 kernel: [    0.467700] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 00:14:31 node-1 kernel: [    0.468213] PCI host bridge to bus 0000:00
Jul 22 00:14:31 node-1 kernel: [    0.468215] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 22 00:14:31 node-1 kernel: [    0.468217] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 22 00:14:31 node-1 kernel: [    0.468218] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 22 00:14:31 node-1 kernel: [    0.468219] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 22 00:14:31 node-1 kernel: [    0.468221] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 22 00:14:31 node-1 kernel: [    0.468222] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 22 00:14:31 node-1 kernel: [    0.468224] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 22 00:14:31 node-1 kernel: [    0.468232] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 22 00:14:31 node-1 kernel: [    0.468316] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.468347] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.468388] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 22 00:14:31 node-1 kernel: [    0.468408] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.468437] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.468478] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 22 00:14:31 node-1 kernel: [    0.468497] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.468526] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.468566] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 22 00:14:31 node-1 kernel: [    0.468584] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.468654] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.468732] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.468809] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 00:14:31 node-1 kernel: [    0.468814] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 22 00:14:31 node-1 kernel: [    0.468898] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 22 00:14:31 node-1 kernel: [    0.469046] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 22 00:14:31 node-1 kernel: [    0.469064] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 22 00:14:31 node-1 kernel: [    0.469142] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.469197] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 22 00:14:31 node-1 kernel: [    0.469219] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.469275] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.469318] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 22 00:14:31 node-1 kernel: [    0.469345] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.469401] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.469444] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 22 00:14:31 node-1 kernel: [    0.469468] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 22 00:14:31 node-1 kernel: [    0.469486] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 22 00:14:31 node-1 kernel: [    0.469564] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.469613] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 22 00:14:31 node-1 kernel: [    0.469639] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 22 00:14:31 node-1 kernel: [    0.469885] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 22 00:14:31 node-1 kernel: [    0.469891] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 22 00:14:31 node-1 kernel: [    0.469897] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.469902] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.469910] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 22 00:14:31 node-1 kernel: [    0.469940] pci 0000:01:00.0: supports D1 D2
Jul 22 00:14:31 node-1 kernel: [    0.480242] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 00:14:31 node-1 kernel: [    0.480248] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 00:14:31 node-1 kernel: [    0.480252] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 00:14:31 node-1 kernel: [    0.480523] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.480556] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 22 00:14:31 node-1 kernel: [    0.488239] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 00:14:31 node-1 kernel: [    0.488245] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.488249] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 00:14:31 node-1 kernel: [    0.488333] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.488423] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.488519] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.488601] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 00:14:31 node-1 kernel: [    0.488608] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.488612] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 00:14:31 node-1 kernel: [    0.488699] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.488820] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.488874] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 00:14:31 node-1 kernel: [    0.488877] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.488879] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.488929] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.489048] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.489087] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.489206] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.489241] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.489363] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.489418] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 22 00:14:31 node-1 kernel: [    0.489537] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 22 00:14:31 node-1 kernel: [    0.489580] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 00:14:31 node-1 kernel: [    0.489583] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.489585] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.489644] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 22 00:14:31 node-1 kernel: [    0.489707] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.489775] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.489816] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 22 00:14:31 node-1 kernel: [    0.489902] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 22 00:14:31 node-1 kernel: [    0.490008] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 00:14:31 node-1 kernel: [    0.490010] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.490012] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.490068] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 22 00:14:31 node-1 kernel: [    0.490121] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.490170] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.490403] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 00:14:31 node-1 kernel: [    0.490407] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 00:14:31 node-1 kernel: [    0.490474] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 22 00:14:31 node-1 kernel: [    0.490531] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.490579] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.490788] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 00:14:31 node-1 kernel: [    0.490792] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 00:14:31 node-1 kernel: [    0.490852] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 22 00:14:31 node-1 kernel: [    0.490911] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.490966] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 22 00:14:31 node-1 kernel: [    0.491186] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 00:14:31 node-1 kernel: [    0.491190] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 00:14:31 node-1 kernel: [    0.491364] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 00:14:31 node-1 kernel: [    0.491403] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 00:14:31 node-1 kernel: [    0.491481] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 22 00:14:31 node-1 kernel: [    0.491500] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 22 00:14:31 node-1 kernel: [    0.491513] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 22 00:14:31 node-1 kernel: [    0.491526] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 22 00:14:31 node-1 kernel: [    0.491576] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 22 00:14:31 node-1 kernel: [    0.496245] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 00:14:31 node-1 kernel: [    0.496254] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 00:14:31 node-1 kernel: [    0.496317] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 22 00:14:31 node-1 kernel: [    0.496806] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 22 00:14:31 node-1 kernel: [    0.496809] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 00:14:31 node-1 kernel: [    0.496928] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 00:14:31 node-1 kernel: [    0.497038] PCI host bridge to bus 0000:80
Jul 22 00:14:31 node-1 kernel: [    0.497040] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 22 00:14:31 node-1 kernel: [    0.497041] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 22 00:14:31 node-1 kernel: [    0.497043] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 22 00:14:31 node-1 kernel: [    0.497051] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.497114] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.497182] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 00:14:31 node-1 kernel: [    0.497245] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 00:14:31 node-1 kernel: [    0.497250] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 22 00:14:31 node-1 kernel: [    0.497323] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 22 00:14:31 node-1 kernel: [    0.497620] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 22 00:14:31 node-1 kernel: [    0.497652] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 22 00:14:31 node-1 kernel: [    0.497681] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 22 00:14:31 node-1 kernel: [    0.497710] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 22 00:14:31 node-1 kernel: [    0.497739] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 00:14:31 node-1 kernel: [    0.497769] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 00:14:31 node-1 kernel: [    0.497799] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 00:14:31 node-1 kernel: [    0.497828] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 00:14:31 node-1 kernel: [    0.497913] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 22 00:14:31 node-1 kernel: [    0.497918] ACPI: \_SB_.UNC1: notify handler is installed
Jul 22 00:14:31 node-1 kernel: [    0.497919] ACPI: \_SB_.UNC0: notify handler is installed
Jul 22 00:14:31 node-1 kernel: [    0.497934] ACPI: \_SB_.PCI0: notify handler is installed
Jul 22 00:14:31 node-1 kernel: [    0.497987] ACPI: \_SB_.PCI1: notify handler is installed
Jul 22 00:14:31 node-1 kernel: [    0.498066] Found 4 acpi root devices
Jul 22 00:14:31 node-1 kernel: [    0.498175] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 22 00:14:31 node-1 kernel: [    0.498177] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 22 00:14:31 node-1 kernel: [    0.498179] vgaarb: loaded
Jul 22 00:14:31 node-1 kernel: [    0.498180] vgaarb: bridge control possible 0000:0c:00.0
Jul 22 00:14:31 node-1 kernel: [    0.498302] SCSI subsystem initialized
Jul 22 00:14:31 node-1 kernel: [    0.498367] libata version 3.00 loaded.
Jul 22 00:14:31 node-1 kernel: [    0.498381] ACPI: bus type USB registered
Jul 22 00:14:31 node-1 kernel: [    0.498391] usbcore: registered new interface driver usbfs
Jul 22 00:14:31 node-1 kernel: [    0.498396] usbcore: registered new interface driver hub
Jul 22 00:14:31 node-1 kernel: [    0.498420] usbcore: registered new device driver usb
Jul 22 00:14:31 node-1 kernel: [    0.498590] PCI: Using ACPI for IRQ routing
Jul 22 00:14:31 node-1 kernel: [    0.502207] PCI: pci_cache_line_size set to 64 bytes
Jul 22 00:14:31 node-1 kernel: [    0.502432] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 22 00:14:31 node-1 kernel: [    0.502433] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 22 00:14:31 node-1 kernel: [    0.502434] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 22 00:14:31 node-1 kernel: [    0.502499] NetLabel: Initializing
Jul 22 00:14:31 node-1 kernel: [    0.502500] NetLabel:  domain hash size = 128
Jul 22 00:14:31 node-1 kernel: [    0.502501] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 22 00:14:31 node-1 kernel: [    0.502511] NetLabel:  unlabeled traffic allowed by default
Jul 22 00:14:31 node-1 kernel: [    0.502566] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 22 00:14:31 node-1 kernel: [    0.502570] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 22 00:14:31 node-1 kernel: [    0.504641] Switched to clocksource hpet
Jul 22 00:14:31 node-1 kernel: [    0.509155] AppArmor: AppArmor Filesystem Enabled
Jul 22 00:14:31 node-1 kernel: [    0.509195] pnp: PnP ACPI init
Jul 22 00:14:31 node-1 kernel: [    0.509207] ACPI: bus type PNP registered
Jul 22 00:14:31 node-1 kernel: [    0.509385] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509396] pnp 00:01: [dma 4]
Jul 22 00:14:31 node-1 kernel: [    0.509415] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509449] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509474] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509495] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509543] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509658] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509661] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 22 00:14:31 node-1 kernel: [    0.509663] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509664] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509666] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509667] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509671] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 22 00:14:31 node-1 kernel: [    0.509673] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509674] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509676] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509677] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509679] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509680] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 22 00:14:31 node-1 kernel: [    0.509683] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509785] pnp 00:07: [dma 0 disabled]
Jul 22 00:14:31 node-1 kernel: [    0.509817] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509899] pnp 00:08: [dma 0 disabled]
Jul 22 00:14:31 node-1 kernel: [    0.509935] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 00:14:31 node-1 kernel: [    0.509993] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 22 00:14:31 node-1 kernel: [    0.510438] pnp: PnP ACPI: found 10 devices
Jul 22 00:14:31 node-1 kernel: [    0.510440] ACPI: bus type PNP unregistered
Jul 22 00:14:31 node-1 kernel: [    0.516469] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 00:14:31 node-1 kernel: [    0.516472] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 00:14:31 node-1 kernel: [    0.516475] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 00:14:31 node-1 kernel: [    0.516480] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 00:14:31 node-1 kernel: [    0.516482] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516497] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516526] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 00:14:31 node-1 kernel: [    0.516541] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516570] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 00:14:31 node-1 kernel: [    0.516584] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 00:14:31 node-1 kernel: [    0.516621] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 00:14:31 node-1 kernel: [    0.516635] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 00:14:31 node-1 kernel: [    0.516664] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 00:14:31 node-1 kernel: [    0.516666] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516681] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516710] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 00:14:31 node-1 kernel: [    0.516712] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516726] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516755] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 00:14:31 node-1 kernel: [    0.516757] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516760] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516765] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 00:14:31 node-1 kernel: [    0.516766] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516769] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516773] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 00:14:31 node-1 kernel: [    0.516779] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 00:14:31 node-1 kernel: [    0.516789] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 00:14:31 node-1 kernel: [    0.516792] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 00:14:31 node-1 kernel: [    0.516799] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 22 00:14:31 node-1 kernel: [    0.516800] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 22 00:14:31 node-1 kernel: [    0.516801] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 22 00:14:31 node-1 kernel: [    0.516802] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 22 00:14:31 node-1 kernel: [    0.516803] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 22 00:14:31 node-1 kernel: [    0.516804] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 22 00:14:31 node-1 kernel: [    0.516805] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 22 00:14:31 node-1 kernel: [    0.516806] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 22 00:14:31 node-1 kernel: [    0.516807] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516808] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516809] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516810] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516811] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516811] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516812] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516813] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516814] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 22 00:14:31 node-1 kernel: [    0.516815] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516816] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 22 00:14:31 node-1 kernel: [    0.516818] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 22 00:14:31 node-1 kernel: [    0.516819] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 22 00:14:31 node-1 kernel: [    0.516820] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 22 00:14:31 node-1 kernel: [    0.516822] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 22 00:14:31 node-1 kernel: [    0.516823] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 22 00:14:31 node-1 kernel: [    0.516866] NET: Registered protocol family 2
Jul 22 00:14:31 node-1 kernel: [    0.517168] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.517542] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.517707] TCP: Hash tables configured (established 262144 bind 65536)
Jul 22 00:14:31 node-1 kernel: [    0.517750] TCP: reno registered
Jul 22 00:14:31 node-1 kernel: [    0.517781] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.517897] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.518071] NET: Registered protocol family 1
Jul 22 00:14:31 node-1 kernel: [    0.556729] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 22 00:14:31 node-1 kernel: [    0.556743] PCI: CLS 64 bytes, default 64
Jul 22 00:14:31 node-1 kernel: [    0.556828] Trying to unpack rootfs image as initramfs...
Jul 22 00:14:31 node-1 kernel: [    0.778509] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Jul 22 00:14:31 node-1 kernel: [    0.778565] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 22 00:14:31 node-1 kernel: [    0.778575] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 22 00:14:31 node-1 kernel: [    0.779088] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779095] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779103] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779110] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779121] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779135] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779153] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779165] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779178] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779185] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779193] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779199] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779208] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779221] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779233] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779245] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 00:14:31 node-1 kernel: [    0.779312] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 22 00:14:31 node-1 kernel: [    0.779316] Scanning for low memory corruption every 60 seconds
Jul 22 00:14:31 node-1 kernel: [    0.779634] Initialise system trusted keyring
Jul 22 00:14:31 node-1 kernel: [    0.779679] audit: initializing netlink socket (disabled)
Jul 22 00:14:31 node-1 kernel: [    0.779691] type=2000 audit(1469146434.732:1): initialized
Jul 22 00:14:31 node-1 kernel: [    0.797463] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 22 00:14:31 node-1 kernel: [    0.798905] zbud: loaded
Jul 22 00:14:31 node-1 kernel: [    0.799017] VFS: Disk quotas dquot_6.5.2
Jul 22 00:14:31 node-1 kernel: [    0.799049] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 22 00:14:31 node-1 kernel: [    0.799393] fuse init (API version 7.22)
Jul 22 00:14:31 node-1 kernel: [    0.799453] msgmni has been set to 32768
Jul 22 00:14:31 node-1 kernel: [    0.799499] Key type big_key registered
Jul 22 00:14:31 node-1 kernel: [    0.800032] Key type asymmetric registered
Jul 22 00:14:31 node-1 kernel: [    0.800034] Asymmetric key parser 'x509' registered
Jul 22 00:14:31 node-1 kernel: [    0.800054] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 22 00:14:31 node-1 kernel: [    0.800110] io scheduler noop registered
Jul 22 00:14:31 node-1 kernel: [    0.800112] io scheduler deadline registered (default)
Jul 22 00:14:31 node-1 kernel: [    0.800132] io scheduler cfq registered
Jul 22 00:14:31 node-1 kernel: [    0.800448] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    0.800545] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    0.800635] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    0.800722] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    0.800818] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    0.800882] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    0.801131] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 22 00:14:31 node-1 kernel: [    0.801150] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 22 00:14:31 node-1 kernel: [    0.801170] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 22 00:14:31 node-1 kernel: [    0.801180] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801182] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801185] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 22 00:14:31 node-1 kernel: [    0.801189] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801190] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801191] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801192] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801194] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801195] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801197] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801198] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801200] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801201] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801202] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801204] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801206] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 22 00:14:31 node-1 kernel: [    0.801210] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801212] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 22 00:14:31 node-1 kernel: [    0.801222] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801225] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 22 00:14:31 node-1 kernel: [    0.801236] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801237] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 22 00:14:31 node-1 kernel: [    0.801240] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 22 00:14:31 node-1 kernel: [    0.801252] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 22 00:14:31 node-1 kernel: [    0.801349] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 22 00:14:31 node-1 kernel: [    0.801353] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 22 00:14:31 node-1 kernel: [    0.801362] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 22 00:14:31 node-1 kernel: [    0.801397] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 22 00:14:31 node-1 kernel: [    0.801398] vesafb: scrolling: redraw
Jul 22 00:14:31 node-1 kernel: [    0.801400] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 22 00:14:31 node-1 kernel: [    0.821042] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 22 00:14:31 node-1 kernel: [    0.829533] Console: switching to colour frame buffer device 80x30
Jul 22 00:14:31 node-1 kernel: [    0.838222] fb0: VESA VGA frame buffer device
Jul 22 00:14:31 node-1 kernel: [    0.838419] intel_idle: MWAIT substates: 0x2120
Jul 22 00:14:31 node-1 kernel: [    0.838420] intel_idle: v0.4 model 0x3F
Jul 22 00:14:31 node-1 kernel: [    0.838420] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 22 00:14:31 node-1 kernel: [    0.838648] ipmi message handler version 39.2
Jul 22 00:14:31 node-1 kernel: [    0.838903] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 22 00:14:31 node-1 kernel: [    0.839332] ACPI: AC Adapter [P111] (on-line)
Jul 22 00:14:31 node-1 kernel: [    0.844563] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 22 00:14:31 node-1 kernel: [    0.855599] ACPI: Power Button [PWRB]
Jul 22 00:14:31 node-1 kernel: [    0.861380] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 22 00:14:31 node-1 kernel: [    0.873060] ACPI: Power Button [PWRF]
Jul 22 00:14:31 node-1 kernel: [    0.894155] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 22 00:14:31 node-1 kernel: [    0.905847] pstore: Registered erst as persistent store backend
Jul 22 00:14:31 node-1 kernel: [    0.912043] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 22 00:14:31 node-1 kernel: [    0.924009] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 22 00:14:31 node-1 kernel: [    0.950773] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 22 00:14:31 node-1 kernel: [    0.984094] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 22 00:14:31 node-1 kernel: [    0.998189] Linux agpgart interface v0.103
Jul 22 00:14:31 node-1 kernel: [    1.005838] brd: module loaded
Jul 22 00:14:31 node-1 kernel: [    1.012866] loop: module loaded
Jul 22 00:14:31 node-1 kernel: [    1.019591] libphy: Fixed MDIO Bus: probed
Jul 22 00:14:31 node-1 kernel: [    1.026060] tun: Universal TUN/TAP device driver, 1.6
Jul 22 00:14:31 node-1 kernel: [    1.032528] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 22 00:14:31 node-1 kernel: [    1.039054] PPP generic driver version 2.4.2
Jul 22 00:14:31 node-1 kernel: [    1.045440] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 22 00:14:31 node-1 kernel: [    1.051882] ehci-pci: EHCI PCI platform driver
Jul 22 00:14:31 node-1 kernel: [    1.058398] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 22 00:14:31 node-1 kernel: [    1.064820] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 22 00:14:31 node-1 kernel: [    1.077366] ehci-pci 0000:00:1a.0: debug port 2
Jul 22 00:14:31 node-1 kernel: [    1.087574] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 22 00:14:31 node-1 kernel: [    1.087598] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 22 00:14:31 node-1 kernel: [    1.104123] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 22 00:14:31 node-1 kernel: [    1.110208] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 00:14:31 node-1 kernel: [    1.116384] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 00:14:31 node-1 kernel: [    1.128304] usb usb1: Product: EHCI Host Controller
Jul 22 00:14:31 node-1 kernel: [    1.134388] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 00:14:31 node-1 kernel: [    1.140538] usb usb1: SerialNumber: 0000:00:1a.0
Jul 22 00:14:31 node-1 kernel: [    1.146591] hub 1-0:1.0: USB hub found
Jul 22 00:14:31 node-1 kernel: [    1.152432] hub 1-0:1.0: 2 ports detected
Jul 22 00:14:31 node-1 kernel: [    1.158222] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 22 00:14:31 node-1 kernel: [    1.163806] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 22 00:14:31 node-1 kernel: [    1.174709] ehci-pci 0000:00:1d.0: debug port 2
Jul 22 00:14:31 node-1 kernel: [    1.184013] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 22 00:14:31 node-1 kernel: [    1.184016] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 22 00:14:31 node-1 kernel: [    1.200042] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 22 00:14:31 node-1 kernel: [    1.205245] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 00:14:31 node-1 kernel: [    1.210544] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 00:14:31 node-1 kernel: [    1.221109] usb usb2: Product: EHCI Host Controller
Jul 22 00:14:31 node-1 kernel: [    1.226578] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 00:14:31 node-1 kernel: [    1.232116] usb usb2: SerialNumber: 0000:00:1d.0
Jul 22 00:14:31 node-1 kernel: [    1.237627] hub 2-0:1.0: USB hub found
Jul 22 00:14:31 node-1 kernel: [    1.242971] hub 2-0:1.0: 2 ports detected
Jul 22 00:14:31 node-1 kernel: [    1.248266] ehci-platform: EHCI generic platform driver
Jul 22 00:14:31 node-1 kernel: [    1.253492] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 22 00:14:31 node-1 kernel: [    1.258800] ohci-pci: OHCI PCI platform driver
Jul 22 00:14:31 node-1 kernel: [    1.264093] ohci-platform: OHCI generic platform driver
Jul 22 00:14:31 node-1 kernel: [    1.269287] uhci_hcd: USB Universal Host Controller Interface driver
Jul 22 00:14:31 node-1 kernel: [    1.274614] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 22 00:14:31 node-1 kernel: [    1.467822] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 22 00:14:31 node-1 kernel: [    1.640001] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 22 00:14:31 node-1 kernel: [    1.645582] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 00:14:31 node-1 kernel: [    1.651394] hub 1-1:1.0: USB hub found
Jul 22 00:14:31 node-1 kernel: [    1.656862] hub 1-1:1.0: 6 ports detected
Jul 22 00:14:31 node-1 kernel: [    1.771555] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 22 00:14:31 node-1 kernel: [    1.799530] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 22 00:14:31 node-1 kernel: [    2.039662] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 22 00:14:31 node-1 kernel: [    2.045208] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 00:14:31 node-1 kernel: [    2.051051] hub 2-1:1.0: USB hub found
Jul 22 00:14:31 node-1 kernel: [    2.056773] hub 2-1:1.0: 8 ports detected
Jul 22 00:14:31 node-1 kernel: [    2.316235] i8042: No controller found
Jul 22 00:14:31 node-1 kernel: [    2.321720] mousedev: PS/2 mouse device common for all mice
Jul 22 00:14:31 node-1 kernel: [    2.327319] rtc_cmos 00:02: RTC can wake from S4
Jul 22 00:14:31 node-1 kernel: [    2.332978] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 22 00:14:31 node-1 kernel: [    2.335148] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 22 00:14:31 node-1 kernel: [    2.344284] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 22 00:14:31 node-1 kernel: [    2.355522] device-mapper: uevent: version 1.0.3
Jul 22 00:14:31 node-1 kernel: [    2.361253] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 22 00:14:31 node-1 kernel: [    2.372634] ledtrig-cpu: registered to indicate activity on CPUs
Jul 22 00:14:31 node-1 kernel: [    2.378642] TCP: cubic registered
Jul 22 00:14:31 node-1 kernel: [    2.384610] NET: Registered protocol family 10
Jul 22 00:14:31 node-1 kernel: [    2.390712] NET: Registered protocol family 17
Jul 22 00:14:31 node-1 kernel: [    2.396484] Key type dns_resolver registered
Jul 22 00:14:31 node-1 kernel: [    2.402509] Loading compiled-in X.509 certificates
Jul 22 00:14:31 node-1 kernel: [    2.408755] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 22 00:14:31 node-1 kernel: [    2.420266] registered taskstats version 1
Jul 22 00:14:31 node-1 kernel: [    2.428590] Key type trusted registered
Jul 22 00:14:31 node-1 kernel: [    2.436373] Key type encrypted registered
Jul 22 00:14:31 node-1 kernel: [    2.441852] AppArmor: AppArmor sha1 policy hashing enabled
Jul 22 00:14:31 node-1 kernel: [    2.447338] IMA: No TPM chip found, activating TPM-bypass!
Jul 22 00:14:31 node-1 kernel: [    2.453507] regulator-dummy: disabling
Jul 22 00:14:31 node-1 kernel: [    2.459077]   Magic number: 8:822:203
Jul 22 00:14:31 node-1 kernel: [    2.464572] acpi device:58: hash matches
Jul 22 00:14:31 node-1 kernel: [    2.467500] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 22 00:14:31 node-1 kernel: [    2.467501] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 22 00:14:31 node-1 kernel: [    2.467501] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 22 00:14:31 node-1 kernel: [    2.467502] usb 2-1.4: Manufacturer: Avocent
Jul 22 00:14:31 node-1 kernel: [    2.467503] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 22 00:14:31 node-1 kernel: [    2.503006] acpi device:2b: hash matches
Jul 22 00:14:31 node-1 kernel: [    2.508643] rtc_cmos 00:02: setting system clock to 2016-07-22 00:13:57 UTC (1469146437)
Jul 22 00:14:31 node-1 kernel: [    2.521175] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 22 00:14:31 node-1 kernel: [    2.526750] EDD information not available.
Jul 22 00:14:31 node-1 kernel: [    2.532275] PM: Hibernation image not present or could not be loaded.
Jul 22 00:14:31 node-1 kernel: [    2.533139] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 22 00:14:31 node-1 kernel: [    2.544220] Write protecting the kernel read-only data: 12288k
Jul 22 00:14:31 node-1 kernel: [    2.550308] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 22 00:14:31 node-1 kernel: [    2.562669] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 22 00:14:31 node-1 kernel: [    2.594122] device-mapper: multipath: version 1.6.0 loaded
Jul 22 00:14:31 node-1 kernel: [    2.602050] systemd-udevd[218]: starting version 204
Jul 22 00:14:31 node-1 kernel: [    2.626225] md: linear personality registered for level -1
Jul 22 00:14:31 node-1 kernel: [    2.640089] md: multipath personality registered for level -4
Jul 22 00:14:31 node-1 kernel: [    2.648196] md: raid0 personality registered for level 0
Jul 22 00:14:31 node-1 kernel: [    2.656528] md: raid1 personality registered for level 1
Jul 22 00:14:31 node-1 kernel: [    2.666603] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 22 00:14:31 node-1 kernel: [    2.672947] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 22 00:14:31 node-1 kernel: [    2.672982] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 22 00:14:31 node-1 kernel: [    2.673386] megasas: FW now in Ready state
Jul 22 00:14:31 node-1 kernel: [    2.673511] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673557] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673616] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673658] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673718] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673763] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673816] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673862] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673904] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673951] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.673986] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.674031] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.674073] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.674117] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.674165] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.674210] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.674410] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 22 00:14:31 node-1 kernel: [    2.707658] hidraw: raw HID events driver (C) Jiri Kosina
Jul 22 00:14:31 node-1 kernel: [    2.713747] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 22 00:14:31 node-1 kernel: [    2.713749] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 22 00:14:31 node-1 kernel: [    2.713750] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 00:14:31 node-1 kernel: [    2.713817] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.713855] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.713894] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.713934] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.714022] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.726306] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 22 00:14:31 node-1 kernel: [    2.726308] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 22 00:14:31 node-1 kernel: [    2.726309] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 00:14:31 node-1 kernel: [    2.726368] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.726407] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.726451] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.726486] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.726571] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.730854] raid6: sse2x1    6078 MB/s
Jul 22 00:14:31 node-1 kernel: [    2.739485] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 22 00:14:31 node-1 kernel: [    2.739488] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 22 00:14:31 node-1 kernel: [    2.739489] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 00:14:31 node-1 kernel: [    2.739560] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.739620] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.739655] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.739692] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.739788] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.749786] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 22 00:14:31 node-1 kernel: [    2.749787] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 22 00:14:31 node-1 kernel: [    2.749788] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 00:14:31 node-1 kernel: [    2.749846] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.749884] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.749923] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.749954] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.750038] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 00:14:31 node-1 kernel: [    2.909991] raid6: sse2x2   28635 MB/s
Jul 22 00:14:31 node-1 kernel: [    2.982533] raid6: sse2x4   10135 MB/s
Jul 22 00:14:31 node-1 kernel: [    3.054486] raid6: avx2x1   14950 MB/s
Jul 22 00:14:31 node-1 kernel: [    3.126418] raid6: avx2x2   18843 MB/s
Jul 22 00:14:31 node-1 kernel: [    3.198356] raid6: avx2x4   21320 MB/s
Jul 22 00:14:31 node-1 kernel: [    3.204292] raid6: using algorithm sse2x2 (28635 MB/s)
Jul 22 00:14:31 node-1 kernel: [    3.210342] raid6: using avx2x2 recovery algorithm
Jul 22 00:14:31 node-1 kernel: [    3.216205] Switched to clocksource tsc
Jul 22 00:14:31 node-1 kernel: [    3.216211] megasas:IOC Init cmd success
Jul 22 00:14:31 node-1 kernel: [    3.228187] xor: automatically using best checksumming function:
Jul 22 00:14:31 node-1 kernel: [    3.235444] usbcore: registered new interface driver usbhid
Jul 22 00:14:31 node-1 kernel: [    3.240938] usbhid: USB HID core driver
Jul 22 00:14:31 node-1 kernel: [    3.241286] megasas: INIT adapter done
Jul 22 00:14:31 node-1 kernel: [    3.252624] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 22 00:14:31 node-1 kernel: [    3.263887] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 22 00:14:31 node-1 kernel: [    3.275346]    avx       : 40449.000 MB/sec
Jul 22 00:14:31 node-1 kernel: [    3.275420] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 22 00:14:31 node-1 kernel: [    3.275467] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 22 00:14:31 node-1 kernel: [    3.275522] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 22 00:14:31 node-1 kernel: [    3.275563] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 22 00:14:31 node-1 kernel: [    3.310588] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 22 00:14:31 node-1 kernel: [    3.312007] scsi0 : LSI SAS based MegaRAID driver
Jul 22 00:14:31 node-1 kernel: [    3.320075] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 00:14:31 node-1 kernel: [    3.353307] async_tx: api initialized (async)
Jul 22 00:14:31 node-1 kernel: [    3.362110] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 00:14:31 node-1 kernel: [    3.375144] md: raid6 personality registered for level 6
Jul 22 00:14:31 node-1 kernel: [    3.381917] md: raid5 personality registered for level 5
Jul 22 00:14:31 node-1 kernel: [    3.388582] md: raid4 personality registered for level 4
Jul 22 00:14:31 node-1 kernel: [    3.396592] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 22 00:14:31 node-1 kernel: [    3.403199] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 22 00:14:31 node-1 kernel: [    3.416560] md: raid10 personality registered for level 10
Jul 22 00:14:31 node-1 kernel: [    3.417363] sd 0:2:0:0: [sda] Write Protect is off
Jul 22 00:14:31 node-1 kernel: [    3.417437] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 22 00:14:31 node-1 kernel: [    3.417755] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 22 00:14:31 node-1 kernel: [    3.450439]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 22 00:14:31 node-1 kernel: [    3.457516] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 22 00:14:31 node-1 kernel: [    3.508913] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Jul 22 00:14:31 node-1 kernel: [    3.591468] random: lvm urandom read with 29 bits of entropy available
Jul 22 00:14:31 node-1 kernel: [    3.826430] bio: create slab <bio-1> at 1
Jul 22 00:14:31 node-1 kernel: [    4.617710] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 00:14:31 node-1 kernel: [    5.294719] random: nonblocking pool is initialized
Jul 22 00:14:31 node-1 kernel: [    5.347939] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 22 00:14:31 node-1 kernel: [    5.373200] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 22 00:14:31 node-1 kernel: [    5.511754] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 22 00:14:31 node-1 kernel: [    5.559632] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 22 00:14:31 node-1 kernel: [    5.629246] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 00:14:31 node-1 kernel: [    5.828748] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 22 00:14:31 node-1 kernel: [    5.853153] XFS (dm-1): Mounting Filesystem
Jul 22 00:14:31 node-1 kernel: [    5.990085] XFS (dm-1): Ending clean mount
Jul 22 00:14:31 node-1 kernel: [    6.054544] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 00:14:31 node-1 kernel: [    6.090924] XFS (dm-2): Mounting Filesystem
Jul 22 00:14:31 node-1 kernel: [    6.309031] XFS (dm-2): Ending clean mount
Jul 22 00:14:31 node-1 kernel: [    6.506751] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 00:14:31 node-1 kernel: [    8.188978] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 22 00:14:31 node-1 kernel: [    8.203629] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 22 00:14:31 node-1 kernel: [    8.344320] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 22 00:14:31 node-1 kernel: [    8.344325] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 22 00:14:31 node-1 kernel: [    8.344329] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 22 00:14:31 node-1 kernel: [    8.344333] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 22 00:14:31 node-1 kernel: [    8.399654] systemd-udevd[797]: starting version 204
Jul 22 00:14:31 node-1 kernel: [    8.563964] power_meter ACPI000D:00: Found ACPI power meter.
Jul 22 00:14:31 node-1 kernel: [    8.564015] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 22 00:14:31 node-1 kernel: [    8.613702] wmi: Mapper loaded
Jul 22 00:14:31 node-1 kernel: [    8.625150] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 22 00:14:31 node-1 kernel: [    8.630696] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 22 00:14:31 node-1 kernel: [    8.630701] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 00:14:31 node-1 kernel: [    8.630703] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 22 00:14:31 node-1 kernel: [    8.630705] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 00:14:31 node-1 kernel: [    8.630720] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 22 00:14:31 node-1 kernel: [    8.645058] IPMI System Interface driver.
Jul 22 00:14:31 node-1 kernel: [    8.645088] ipmi_si: probing via ACPI
Jul 22 00:14:31 node-1 kernel: [    8.645102] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 22 00:14:31 node-1 kernel: [    8.645103] ipmi_si: Adding ACPI-specified kcs state machine
Jul 22 00:14:31 node-1 kernel: [    8.645110] ipmi_si: probing via SMBIOS
Jul 22 00:14:31 node-1 kernel: [    8.645111] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 00:14:31 node-1 kernel: [    8.645111] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 22 00:14:31 node-1 kernel: [    8.645113] ipmi_si: probing via SPMI
Jul 22 00:14:31 node-1 kernel: [    8.645113] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 00:14:31 node-1 kernel: [    8.645114] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 22 00:14:31 node-1 kernel: [    8.645115] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 22 00:14:31 node-1 kernel: [    8.670197] systemd-udevd[826]: renamed network interface eth0 to enp6s0
Jul 22 00:14:31 node-1 kernel: [    8.686056] systemd-udevd[821]: renamed network interface eth1 to enp7s0
Jul 22 00:14:31 node-1 kernel: [    8.710087] systemd-udevd[816]: renamed network interface eth2 to enp8s0
Jul 22 00:14:31 node-1 kernel: [    8.742037] systemd-udevd[814]: renamed network interface eth3 to enp9s0
Jul 22 00:14:31 node-1 kernel: [    8.772680] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 22 00:14:31 node-1 kernel: [    8.772686] ipmi_si 00:09: IPMI kcs interface initialized
Jul 22 00:14:31 node-1 kernel: [    9.060638] type=1400 audit(1469146444.051:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.060788] type=1400 audit(1469146444.051:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1072 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.060916] type=1400 audit(1469146444.051:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1072 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.077404] type=1400 audit(1469146444.071:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1075 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.077555] type=1400 audit(1469146444.071:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1075 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.077683] type=1400 audit(1469146444.071:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1075 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.080052] type=1400 audit(1469146444.071:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1073 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.080204] type=1400 audit(1469146444.071:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1073 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.080323] type=1400 audit(1469146444.071:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1073 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.086694] type=1400 audit(1469146444.079:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1074 comm="apparmor_parser"
Jul 22 00:14:31 node-1 kernel: [    9.602468] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 22 00:14:31 node-1 kernel: [    9.611818] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 22 00:14:31 node-1 kernel: [    9.793216] enic 0000:06:00.0 enp6s0: Link UP
Jul 22 00:14:31 node-1 kernel: [    9.794372] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 22 00:14:31 node-1 kernel: [    9.794387] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 22 00:14:31 node-1 kernel: [   19.358836] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 22 00:14:31 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 22 00:14:32 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 22 00:14:32 node-1 kernel: [   38.017847] init: failsafe main process (8423) killed by TERM signal
Jul 22 00:14:33 node-1 dbus[8486]: [system] AppArmor D-Bus mediation is enabled
Jul 22 00:14:33 node-1 kernel: [   38.224848] audit_printk_skb: 30 callbacks suppressed
Jul 22 00:14:33 node-1 kernel: [   38.224850] type=1400 audit(1469146473.154:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8542 comm="apparmor_parser"
Jul 22 00:14:33 node-1 kernel: [   38.225139] type=1400 audit(1469146473.154:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8541 comm="apparmor_parser"
Jul 22 00:14:33 node-1 kernel: [   38.225144] type=1400 audit(1469146473.154:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Jul 22 00:14:33 node-1 kernel: [   38.225147] type=1400 audit(1469146473.154:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Jul 22 00:14:33 node-1 kernel: [   38.225382] type=1400 audit(1469146473.154:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Jul 22 00:14:33 node-1 kernel: [   38.225383] type=1400 audit(1469146473.154:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Jul 22 00:14:33 node-1 kernel: [   38.225497] type=1400 audit(1469146473.154:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Jul 22 00:14:33 node-1 kernel: [   38.314733] type=1400 audit(1469146473.242:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8544 comm="apparmor_parser"
Jul 22 00:14:33 node-1 anacron[8616]: Anacron 2.3 started on 2016-07-22
Jul 22 00:14:33 node-1 cron[8582]: (CRON) INFO (pidfile fd = 3)
Jul 22 00:14:33 node-1 anacron[8616]: Will run job `cron.daily' in 5 min.
Jul 22 00:14:33 node-1 anacron[8616]: Will run job `cron.weekly' in 10 min.
Jul 22 00:14:33 node-1 anacron[8616]: Will run job `cron.monthly' in 15 min.
Jul 22 00:14:33 node-1 anacron[8616]: Jobs will be executed sequentially
Jul 22 00:14:33 node-1 cron[8624]: (CRON) STARTUP (fork ok)
Jul 22 00:14:33 node-1 multipathd: path checkers start up
Jul 22 00:14:33 node-1 cron[8624]: (CRON) INFO (Running @reboot jobs)
Jul 22 00:14:33 node-1 postfix/master[8761]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 22 00:14:37 node-1 puppet-agent[8945]: Reopening log files
Jul 22 00:14:38 node-1 puppet-agent[8945]: Could not request certificate: Connection refused - connect(2)
Jul 22 00:15:01 node-1 CRON[8985]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 22 00:15:16 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 00:15:16 node-1 nailgun-agent: D, [2016-07-22T00:15:01.712470 #8988] DEBUG -- : Sleep for 15 seconds before sending request
Jul 22 00:15:16 node-1 nailgun-agent: I, [2016-07-22T00:15:16.727611 #8988]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 00:15:17 node-1 nailgun-agent: D, [2016-07-22T00:15:17.104438 #8988] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 22 00:15:24 node-1 puppet-user[9475]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 22 00:15:24 node-1 puppet-user[9475]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 22 00:15:26 node-1 puppet-user[9475]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 22 00:15:26 node-1 puppet-user[9475]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 22 00:15:26 node-1 puppet-user[9475]: Finished catalog run in 1.07 seconds
Jul 22 00:15:27 node-1 multipathd: uevent trigger error
Jul 22 00:15:27 node-1 puppet-user[9910]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 00:15:28 node-1 puppet-user[9910]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 22 00:15:28 node-1 puppet-user[9910]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 22 00:15:28 node-1 puppet-user[9910]: Finished catalog run in 0.10 seconds
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.066539 #8988] DEBUG -- : Trying to find block devices
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.066651 #8988] DEBUG -- : Found block device: sda
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.066690 #8988] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.066713 #8988] DEBUG -- : Trying to get list of physical devices
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.066864 #8988] DEBUG -- : Getting udev properties for device: sda
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.069026 #8988] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc7884
Jul 22 00:15:29 node-1 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15270", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.069075 #8988] DEBUG -- : Trying to find out if device sda is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.069120 #8988] DEBUG -- : Device sda removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.069134 #8988] DEBUG -- : Device sda seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.069555 #8988] DEBUG -- : Getting udev properties for device: dm-0
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.071352 #8988] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-N3Km2YgAdXgjGfdMnH9TSfDckn8Mh3tNjlR2TJhLyQRLv4U7w2708KVu8lQG5B02 /dev/disk/by-uuid/ce99bddb-493e-4489-9546-4069acd202d6 /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-N3Km2YgAdXgjGfdMnH9TSfDckn8Mh3tNjlR2TJhLyQRLv4U7w2708KVu8lQG5B02", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ce99bddb-493e-4489-9546-4069acd202d6", "ID_FS_UUID_ENC"=>"ce99bddb-493e-4489-9546-4069acd202d6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84
Jul 22 00:15:29 node-1 nailgun-agent: 602", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.071377 #8988] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.071410 #8988] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.071434 #8988] DEBUG -- : Device dm-0 seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.071448 #8988] DEBUG -- : Getting udev properties for device: dm-1
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.073351 #8988] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-KqJ6fhOMka3V2pafTSKO7o9yy8zYsxN4x13c3e8rBFBGINBgDUFccdtPc0uCr43R /dev/disk/by-uuid/44130f27-0c7f-4d81-93b5-d0e525066ef2 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-KqJ6fhOMka3V2pafTSKO7o9yy8zYsxN4x13c3e8rBFBGINBgDUFccdtPc0uCr43R", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"44130f27-0c7f-4d81-93b5-d0e525066ef2", "ID_FS_UUID_ENC"=>"44130f27-0c7f-4d81-93b5-d0e525066ef2", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14152", "nomdmonddf"=>"1", "nomd
Jul 22 00:15:29 node-1 nailgun-agent: monisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.073394 #8988] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.073469 #8988] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.073485 #8988] DEBUG -- : Device dm-1 seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.073502 #8988] DEBUG -- : Getting udev properties for device: dm-2
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.075559 #8988] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-6CJVmXO7s2LwRag3x2KT26Y9ZWYMtwuHL0BDkheyaeR62M1W0b6pzcXbipyagKt9 /dev/disk/by-uuid/fa01f632-02f5-4ee7-a730-904aba4248e7 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-6CJVmXO7s2LwRag3x2KT26Y9ZWYMtwuHL0BDkheyaeR62M1W0b6pzcXbipyagKt9", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"fa01f632-02f5-4ee7-a730-904aba4248e7", "ID_FS_UUID_ENC"=>"fa01f632-02f5-4ee7-a730-904aba4248e7", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27
Jul 22 00:15:29 node-1 nailgun-agent: 817", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.075597 #8988] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.075629 #8988] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.075643 #8988] DEBUG -- : Device dm-2 seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.075658 #8988] DEBUG -- : Getting udev properties for device: dm-3
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.077216 #8988] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-FQIQeFrHDFV7vBNVbUrYSIVReCgU6O2dAqsYxWtVzmaNjVO3XpsnQQPP2YPEJMBD /dev/disk/by-uuid/6ea31ca1-8a1e-45ca-abee-605a45ecb149 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-FQIQeFrHDFV7vBNVbUrYSIVReCgU6O2dAqsYxWtVzmaNjVO3XpsnQQPP2YPEJMBD", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6ea31ca1-8a1e-45ca-abee-605a45ecb149", "ID_FS_UUID_ENC"=>"6ea31ca1-8a1e-45ca-abee-605a45ecb149", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31057", "nomdmond
Jul 22 00:15:29 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.077239 #8988] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.077281 #8988] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.077294 #8988] DEBUG -- : Device dm-3 seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.077320 #8988] DEBUG -- : Getting udev properties for device: dm-4
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.079005 #8988] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-BE9b4CrR0bfGgpIXt9VnZoQLZSDkNzQ3y2XLgeMXklWucHwZ0t8Y6GAb1xRvezb6 /dev/disk/by-uuid/2c2efeab-2303-4e92-a53e-528a7e6a7897 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-BE9b4CrR0bfGgpIXt9VnZoQLZSDkNzQ3y2XLgeMXklWucHwZ0t8Y6GAb1xRvezb6", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2c2efeab-2303-4e92-a53e-528a7e6a7897", "ID_FS_UUID_ENC"=>"2c2efeab-2303-4e92-a53e-528a7e6a7897", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40741", "nomdmonddf"=>"1", 
Jul 22 00:15:29 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.079040 #8988] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.079069 #8988] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.079082 #8988] DEBUG -- : Device dm-4 seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.079096 #8988] DEBUG -- : Getting udev properties for device: dm-5
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.081033 #8988] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-ITrIfM8R2kZqbFaQR6T08d23Vu6dNaCaWgm4d14bFyevs3yAqn2PMIZ3wVb09CiY /dev/disk/by-uuid/4a7ab7cc-1206-433b-8521-154fd466d804 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-ITrIfM8R2kZqbFaQR6T08d23Vu6dNaCaWgm4d14bFyevs3yAqn2PMIZ3wVb09CiY", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4a7ab7cc-1206-433b-8521-154fd466d804", "ID_FS_UUID_ENC"=>"4a7ab7cc-1206-433b-8521-154fd466d804", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38106", "nomdmonddf"=>"1", "nomd
Jul 22 00:15:29 node-1 nailgun-agent: monisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.081057 #8988] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.081125 #8988] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.081138 #8988] DEBUG -- : Device dm-5 seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.081153 #8988] DEBUG -- : Getting udev properties for device: dm-6
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.083067 #8988] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-ITrIfM8R2kZqbFaQR6T08d23Vu6dNaCaze15GxTzwfU1Kt9Sb4JTJMqhhXzBzytk /dev/disk/by-uuid/9229ebfd-214b-4f66-b1fa-f3fa1bcc35a2 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-ITrIfM8R2kZqbFaQR6T08d23Vu6dNaCaze15GxTzwfU1Kt9Sb4JTJMqhhXzBzytk", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"9229ebfd-214b-4f66-b1fa-f3fa1bcc35a2", "ID_FS_UUID_ENC"=>"9229ebfd-214b-4f66-b1fa-f3fa1bcc35a2", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38430", "nomdmonddf"=>"1", "nomdmonisw"
Jul 22 00:15:29 node-1 nailgun-agent: =>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.083114 #8988] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.083166 #8988] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.083181 #8988] DEBUG -- : Device dm-6 seems to be appropriate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.083197 #8988] DEBUG -- : Getting udev properties for device: ram0
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.085027 #8988] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84353", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.085070 #8988] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.085112 #8988] DEBUG -- : Device ram0 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.085134 #8988] DEBUG -- : Getting udev properties for device: ram1
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.086595 #8988] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84435", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.086631 #8988] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.086667 #8988] DEBUG -- : Device ram1 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.086696 #8988] DEBUG -- : Getting udev properties for device: ram2
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.088125 #8988] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85277", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.088150 #8988] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.088186 #8988] DEBUG -- : Device ram2 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.088216 #8988] DEBUG -- : Getting udev properties for device: ram3
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.089672 #8988] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85366", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.089698 #8988] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.089749 #8988] DEBUG -- : Device ram3 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.089779 #8988] DEBUG -- : Getting udev properties for device: ram4
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.091253 #8988] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85441", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.091285 #8988] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.091339 #8988] DEBUG -- : Device ram4 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.091359 #8988] DEBUG -- : Getting udev properties for device: ram5
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.092861 #8988] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85511", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.092887 #8988] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.092923 #8988] DEBUG -- : Device ram5 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.092950 #8988] DEBUG -- : Getting udev properties for device: ram6
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.094366 #8988] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85594", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.094391 #8988] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.094452 #8988] DEBUG -- : Device ram6 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.094471 #8988] DEBUG -- : Getting udev properties for device: ram7
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.095939 #8988] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85677", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.095971 #8988] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.096012 #8988] DEBUG -- : Device ram7 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.096041 #8988] DEBUG -- : Getting udev properties for device: ram8
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.097447 #8988] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85745", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.097472 #8988] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.097544 #8988] DEBUG -- : Device ram8 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.097564 #8988] DEBUG -- : Getting udev properties for device: ram9
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.099002 #8988] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85826", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.099047 #8988] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.099079 #8988] DEBUG -- : Device ram9 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.099098 #8988] DEBUG -- : Getting udev properties for device: loop0
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.104735 #8988] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83359", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.104775 #8988] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.104813 #8988] DEBUG -- : Device loop0 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.104832 #8988] DEBUG -- : Getting udev properties for device: loop1
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.106284 #8988] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83445", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.106309 #8988] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.106371 #8988] DEBUG -- : Device loop1 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.106391 #8988] DEBUG -- : Getting udev properties for device: loop2
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.107780 #8988] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83554", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.107804 #8988] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.107849 #8988] DEBUG -- : Device loop2 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.107868 #8988] DEBUG -- : Getting udev properties for device: loop3
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.109373 #8988] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83640", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.115115 #8988] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.115166 #8988] DEBUG -- : Device loop3 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.115186 #8988] DEBUG -- : Getting udev properties for device: loop4
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.116759 #8988] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83740", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.116786 #8988] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.116857 #8988] DEBUG -- : Device loop4 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.116877 #8988] DEBUG -- : Getting udev properties for device: loop5
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.118227 #8988] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83836", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.118253 #8988] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.118283 #8988] DEBUG -- : Device loop5 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.118303 #8988] DEBUG -- : Getting udev properties for device: loop6
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.119685 #8988] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83946", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.119712 #8988] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.119742 #8988] DEBUG -- : Device loop6 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.119763 #8988] DEBUG -- : Getting udev properties for device: loop7
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.121142 #8988] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83985", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.121166 #8988] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.121206 #8988] DEBUG -- : Device loop7 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.121226 #8988] DEBUG -- : Getting udev properties for device: ram10
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.122608 #8988] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84554", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.122633 #8988] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.122670 #8988] DEBUG -- : Device ram10 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.122689 #8988] DEBUG -- : Getting udev properties for device: ram11
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.124111 #8988] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84686", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.124136 #8988] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.124182 #8988] DEBUG -- : Device ram11 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.124202 #8988] DEBUG -- : Getting udev properties for device: ram12
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.125591 #8988] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84822", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.125617 #8988] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.125653 #8988] DEBUG -- : Device ram12 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.125673 #8988] DEBUG -- : Getting udev properties for device: ram13
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.127014 #8988] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84883", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.127040 #8988] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.127106 #8988] DEBUG -- : Device ram13 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.127126 #8988] DEBUG -- : Getting udev properties for device: ram14
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.128468 #8988] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84952", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.128494 #8988] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.128528 #8988] DEBUG -- : Device ram14 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.128593 #8988] DEBUG -- : Getting udev properties for device: ram15
Jul 22 00:15:29 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.129927 #8988] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85182", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.129955 #8988] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.129990 #8988] DEBUG -- : Device ram15 removable parameter: "0"
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130028 #8988] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130043 #8988] DEBUG -- : Block device seems to be physical data storage: sda
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130125 #8988] DEBUG -- : Found block device: dm-0
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130140 #8988] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130153 #8988] DEBUG -- : Found block device: dm-1
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130164 #8988] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130174 #8988] DEBUG -- : Found block device: dm-2
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130184 #8988] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130193 #8988] DEBUG -- : Found block device: dm-3
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130203 #8988] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130211 #8988] DEBUG -- : Found block device: dm-4
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130222 #8988] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130259 #8988] DEBUG -- : Found block device: dm-5
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130270 #8988] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130279 #8988] DEBUG -- : Found block device: dm-6
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130291 #8988] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130300 #8988] DEBUG -- : Found block device: ram0
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130310 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130319 #8988] DEBUG -- : Found block device: ram1
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130329 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130337 #8988] DEBUG -- : Found block device: ram2
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130347 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130355 #8988] DEBUG -- : Found block device: ram3
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130413 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130422 #8988] DEBUG -- : Found block device: ram4
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130433 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130441 #8988] DEBUG -- : Found block device: ram5
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130451 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130459 #8988] DEBUG -- : Found block device: ram6
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130469 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130478 #8988] DEBUG -- : Found block device: ram7
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130528 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130537 #8988] DEBUG -- : Found block device: ram8
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130548 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130557 #8988] DEBUG -- : Found block device: ram9
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130567 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130576 #8988] DEBUG -- : Found block device: loop0
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130585 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130593 #8988] DEBUG -- : Found block device: loop1
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130603 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130659 #8988] DEBUG -- : Found block device: loop2
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130670 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130679 #8988] DEBUG -- : Found block device: loop3
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130689 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130698 #8988] DEBUG -- : Found block device: loop4
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130708 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130716 #8988] DEBUG -- : Found block device: loop5
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130727 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130735 #8988] DEBUG -- : Found block device: loop6
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130792 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130801 #8988] DEBUG -- : Found block device: loop7
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130811 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130820 #8988] DEBUG -- : Found block device: ram10
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130829 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130837 #8988] DEBUG -- : Found block device: ram11
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130847 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130856 #8988] DEBUG -- : Found block device: ram12
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130866 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130913 #8988] DEBUG -- : Found block device: ram13
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130923 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130931 #8988] DEBUG -- : Found block device: ram14
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130942 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130951 #8988] DEBUG -- : Found block device: ram15
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130960 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.130989 #8988] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.224551 #8988] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 22 00:15:29 node-1 nailgun-agent: D, [2016-07-22T00:15:29.224604 #8988] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 22 00:15:29 node-1 puppet-user[10493]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 22 00:15:29 node-1 puppet-user[10493]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 22 00:15:29 node-1 kernel: [   94.560894] init: plymouth-upstart-bridge main process ended, respawning
Jul 22 00:15:29 node-1 puppet-user[10493]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 22 00:15:29 node-1 puppet-user[10493]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 22 00:15:29 node-1 puppet-user[10493]: Finished catalog run in 0.03 seconds
Jul 22 00:15:29 node-1 puppet-agent[8945]: Could not run: SIGTERM
Jul 22 00:15:29 node-1 kernel: [   94.870921] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 22 00:15:29 node-1 ec2: 
Jul 22 00:15:29 node-1 ec2: #############################################################
Jul 22 00:15:29 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 22 00:15:29 node-1 ec2: 1024 bf:4c:e4:54:96:ff:2d:54:47:d8:4a:3b:bd:2e:55:bc  root@node-1.domain.tld (DSA)
Jul 22 00:15:29 node-1 ec2: 256 da:bd:3a:5a:d8:88:23:19:2e:93:98:14:4a:cd:b6:2e  root@node-1.domain.tld (ECDSA)
Jul 22 00:15:29 node-1 ec2: 256 e3:b9:fe:25:16:79:c3:39:8d:90:45:03:39:c8:ab:80  root@node-1.domain.tld (ED25519)
Jul 22 00:15:29 node-1 ec2: 2048 ac:7b:64:88:fc:b4:3f:6a:39:dc:c2:f7:17:f1:65:04  root@node-1.domain.tld (RSA)
Jul 22 00:15:29 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 22 00:15:29 node-1 ec2: #############################################################
Jul 22 00:15:31 node-1 puppet-user[11200]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 22 00:15:31 node-1 puppet-user[11200]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 22 00:15:31 node-1 puppet-user[11200]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 22 00:15:31 node-1 puppet-user[11200]: Finished catalog run in 0.04 seconds
Jul 22 00:15:32 node-1 puppet-user[11650]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 22 00:15:32 node-1 puppet-user[11650]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Jul 22 00:15:33 node-1 puppet-user[11650]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 22 00:15:33 node-1 puppet-user[11650]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 22 00:15:33 node-1 puppet-user[11650]: Finished catalog run in 0.43 seconds
Jul 22 00:15:35 node-1 puppet-user[12126]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 22 00:15:35 node-1 puppet-user[12126]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Jul 22 00:15:35 node-1 puppet-user[12126]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 22 00:15:35 node-1 puppet-user[12126]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 22 00:15:35 node-1 puppet-user[12126]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 22 00:15:35 node-1 puppet-user[12126]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 22 00:15:35 node-1 puppet-user[12126]: Finished catalog run in 0.28 seconds
Jul 22 00:15:38 node-1 puppet-user[12607]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 22 00:15:38 node-1 puppet-user[12607]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Jul 22 00:15:38 node-1 puppet-user[12607]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 22 00:15:38 node-1 kernel: [  103.472274] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 22 00:15:38 node-1 kernel: [  103.472325] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 22 00:15:38 node-1 puppet-user[12607]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 22 00:15:38 node-1 puppet-user[12607]: Finished catalog run in 0.06 seconds
Jul 22 00:15:40 node-1 puppet-user[13070]: (Scope(Class[main])) MODULAR: sync_time
Jul 22 00:15:40 node-1 puppet-user[13070]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 22 00:15:40 node-1 ntpdate[13497]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 22 00:15:41 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.483652 #8988] DEBUG -- : Trying to find block devices
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.483790 #8988] DEBUG -- : Found block device: sda
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.483870 #8988] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.483916 #8988] DEBUG -- : Block device seems to be physical data storage: sda
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484007 #8988] DEBUG -- : Found block device: dm-0
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484044 #8988] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484074 #8988] DEBUG -- : Found block device: dm-1
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484102 #8988] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484127 #8988] DEBUG -- : Found block device: dm-2
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484155 #8988] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484179 #8988] DEBUG -- : Found block device: dm-3
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484206 #8988] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484232 #8988] DEBUG -- : Found block device: dm-4
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484258 #8988] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484327 #8988] DEBUG -- : Found block device: dm-5
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484354 #8988] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484379 #8988] DEBUG -- : Found block device: dm-6
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484404 #8988] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484427 #8988] DEBUG -- : Found block device: ram0
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484452 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484475 #8988] DEBUG -- : Found block device: ram1
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484501 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484568 #8988] DEBUG -- : Found block device: ram2
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484594 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484618 #8988] DEBUG -- : Found block device: ram3
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484644 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484668 #8988] DEBUG -- : Found block device: ram4
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484693 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484767 #8988] DEBUG -- : Found block device: ram5
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484794 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484817 #8988] DEBUG -- : Found block device: ram6
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484844 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484869 #8988] DEBUG -- : Found block device: ram7
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484895 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484918 #8988] DEBUG -- : Found block device: ram8
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484943 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.484968 #8988] DEBUG -- : Found block device: ram9
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485022 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485048 #8988] DEBUG -- : Found block device: loop0
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485074 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485100 #8988] DEBUG -- : Found block device: loop1
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485125 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485176 #8988] DEBUG -- : Found block device: loop2
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485204 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485229 #8988] DEBUG -- : Found block device: loop3
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485256 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485280 #8988] DEBUG -- : Found block device: loop4
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485333 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485357 #8988] DEBUG -- : Found block device: loop5
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485382 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485407 #8988] DEBUG -- : Found block device: loop6
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485459 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485483 #8988] DEBUG -- : Found block device: loop7
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485508 #8988] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485561 #8988] DEBUG -- : Found block device: ram10
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485587 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485611 #8988] DEBUG -- : Found block device: ram11
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485637 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485698 #8988] DEBUG -- : Found block device: ram12
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485725 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485748 #8988] DEBUG -- : Found block device: ram13
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485773 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485829 #8988] DEBUG -- : Found block device: ram14
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485856 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485879 #8988] DEBUG -- : Found block device: ram15
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.485904 #8988] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.486017 #8988] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 22 00:15:41 node-1 nailgun-agent: D, [2016-07-22T00:15:41.699988 #8988] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 22 00:15:41 node-1 nailgun-agent: I, [2016-07-22T00:15:41.700351 #8988]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 22 00:15:47 node-1 ntpdate[13497]: adjust time server 10.20.0.2 offset 0.002600 sec
Jul 22 00:15:47 node-1 puppet-user[13070]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 22 00:15:47 node-1 puppet-user[13070]: Finished catalog run in 6.19 seconds
Jul 22 00:15:51 node-1 puppet-user[13776]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 00:15:51 node-1 puppet-user[13776]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Jul 22 00:15:51 node-1 puppet-user[13776]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 22 00:15:51 node-1 puppet-user[13776]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 22 00:15:51 node-1 puppet-user[13776]: Finished catalog run in 0.07 seconds
Jul 22 00:15:53 node-1 puppet-user[14231]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 22 00:15:54 node-1 puppet-user[14231]: Compiled catalog for node-1.domain.tld in environment production in 1.22 seconds
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 22 00:15:54 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 22 00:15:55 node-1 puppet-user[14231]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 22 00:16:01 node-1 CRON[14869]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 22 00:16:15 node-1 puppet-user[14231]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 22 00:16:15 node-1 puppet-user[14231]: Finished catalog run in 20.63 seconds
Jul 22 00:16:16 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 00:16:16 node-1 nailgun-agent: I, [2016-07-22T00:16:16.896025 #14872]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 00:16:17 node-1 puppet-user[15196]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 22 00:16:17 node-1 puppet-user[15196]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Jul 22 00:16:22 node-1 puppet-user[15196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 22 00:16:29 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 00:16:29 node-1 nailgun-agent: I, [2016-07-22T00:16:29.918537 #14872]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 22 00:16:57 node-1 puppet-user[15196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 22 00:16:57 node-1 puppet-user[15196]: Finished catalog run in 39.93 seconds
Jul 22 00:16:59 node-1 puppet-user[18055]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 22 00:17:00 node-1 puppet-user[18055]: Compiled catalog for node-1.domain.tld in environment production in 0.55 seconds
Jul 22 00:17:00 node-1 puppet-user[18055]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 22 00:17:00 node-1 puppet-user[18055]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 22 00:17:00 node-1 puppet-user[18055]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 22 00:17:00 node-1 puppet-user[18055]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 22 00:17:00 node-1 puppet-user[18055]: Finished catalog run in 0.09 seconds
Jul 22 00:17:01 node-1 CRON[18728]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 22 00:17:01 node-1 CRON[18729]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 22 00:17:02 node-1 puppet-user[18510]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 22 00:17:03 node-1 puppet-user[18510]: Compiled catalog for node-1.domain.tld in environment production in 0.98 seconds
Jul 22 00:17:03 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 22 00:17:03 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 22 00:17:03 node-1 crontab[18948]: (root) LIST (root)
Jul 22 00:17:03 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 22 00:17:03 node-1 crontab[18954]: (root) REPLACE (root)
Jul 22 00:17:06 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 22 00:17:07 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 22 00:17:08 node-1 puppet-user[18510]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 22 00:17:08 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8396" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 00:17:08 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 22 00:17:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:17:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:18:34 node-1 ntpdate[29992]: no servers can be used, exiting
<27>Jul 22 00:18:34 node-1 ntpdate[30284]: no servers can be used, exiting
<27>Jul 22 00:19:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:25 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:25 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:25 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:25 node-1 multipathd: uevent trigger error
<27>Jul 22 00:19:25 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:20:40 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 00:20:40 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 00:20:46 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 00:20:46 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 00:20:52 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 00:20:58 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 00:20:58 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 00:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:18 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:18 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:18 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:18 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:18 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:18 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:18 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:24 node-1 multipathd: uevent trigger error
<129>Jul 22 00:21:26 node-1 haproxy[19292]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:26 node-1 haproxy[19292]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:27 node-1 haproxy[19298]: 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>Jul 22 00:21:27 node-1 haproxy[19298]: proxy mysqld has no server available!
<27>Jul 22 00:21:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:29 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:33 node-1 multipathd: uevent trigger error
<129>Jul 22 00:21:35 node-1 haproxy[22189]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:35 node-1 haproxy[22189]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:36 node-1 haproxy[22193]: 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>Jul 22 00:21:36 node-1 haproxy[22193]: proxy mysqld has no server available!
<129>Jul 22 00:21:36 node-1 haproxy[22193]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:36 node-1 haproxy[22193]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:36 node-1 haproxy[22193]: 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>Jul 22 00:21:36 node-1 haproxy[22193]: proxy object-storage has no server available!
<27>Jul 22 00:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:38 node-1 multipathd: uevent trigger error
<129>Jul 22 00:21:40 node-1 haproxy[23621]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:41 node-1 haproxy[23627]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:41 node-1 haproxy[23627]: 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>Jul 22 00:21:41 node-1 haproxy[23627]: proxy neutron has no server available!
<129>Jul 22 00:21:41 node-1 haproxy[23627]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:41 node-1 haproxy[23627]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:41 node-1 haproxy[23627]: 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>Jul 22 00:21:41 node-1 haproxy[23627]: proxy mysqld has no server available!
<129>Jul 22 00:21:42 node-1 haproxy[23627]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:42 node-1 haproxy[23627]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:42 node-1 haproxy[23627]: 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>Jul 22 00:21:42 node-1 haproxy[23627]: proxy object-storage has no server available!
<27>Jul 22 00:21:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:44 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:44 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:44 node-1 multipathd: uevent trigger error
<129>Jul 22 00:21:46 node-1 haproxy[25049]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:46 node-1 haproxy[25049]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:46 node-1 haproxy[25049]: 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>Jul 22 00:21:46 node-1 haproxy[25049]: proxy keystone-1 has no server available!
<129>Jul 22 00:21:46 node-1 haproxy[25049]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:47 node-1 haproxy[25053]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:47 node-1 haproxy[25053]: 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>Jul 22 00:21:47 node-1 haproxy[25053]: proxy keystone-2 has no server available!
<129>Jul 22 00:21:47 node-1 haproxy[25053]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:47 node-1 haproxy[25053]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:47 node-1 haproxy[25053]: 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>Jul 22 00:21:47 node-1 haproxy[25053]: proxy neutron has no server available!
<129>Jul 22 00:21:47 node-1 haproxy[25053]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:47 node-1 haproxy[25053]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:47 node-1 haproxy[25053]: 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>Jul 22 00:21:47 node-1 haproxy[25053]: proxy mysqld has no server available!
<129>Jul 22 00:21:47 node-1 haproxy[25053]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:48 node-1 haproxy[25053]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:48 node-1 haproxy[25053]: 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>Jul 22 00:21:48 node-1 haproxy[25053]: proxy object-storage has no server available!
<27>Jul 22 00:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:49 node-1 multipathd: uevent trigger error
<129>Jul 22 00:21:52 node-1 haproxy[26462]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:52 node-1 haproxy[26462]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:52 node-1 haproxy[26462]: 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>Jul 22 00:21:52 node-1 haproxy[26462]: proxy keystone-1 has no server available!
<129>Jul 22 00:21:52 node-1 haproxy[26462]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:52 node-1 haproxy[26462]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:52 node-1 haproxy[26462]: 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>Jul 22 00:21:52 node-1 haproxy[26462]: proxy keystone-2 has no server available!
<129>Jul 22 00:21:52 node-1 haproxy[26462]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:52 node-1 haproxy[26462]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:52 node-1 haproxy[26462]: 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>Jul 22 00:21:52 node-1 haproxy[26462]: proxy neutron has no server available!
<129>Jul 22 00:21:52 node-1 haproxy[26462]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:53 node-1 haproxy[26466]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:53 node-1 haproxy[26466]: 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>Jul 22 00:21:53 node-1 haproxy[26466]: proxy mysqld has no server available!
<129>Jul 22 00:21:53 node-1 haproxy[26466]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:53 node-1 haproxy[26466]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:53 node-1 haproxy[26466]: 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>Jul 22 00:21:53 node-1 haproxy[26466]: proxy object-storage has no server available!
<129>Jul 22 00:21:53 node-1 haproxy[26466]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:53 node-1 haproxy[26466]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:53 node-1 haproxy[26466]: 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>Jul 22 00:21:53 node-1 haproxy[26466]: proxy aodh has no server available!
<27>Jul 22 00:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 00:21:55 node-1 multipathd: uevent trigger error
<129>Jul 22 00:21:57 node-1 haproxy[27895]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:57 node-1 haproxy[27895]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:57 node-1 haproxy[27895]: 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>Jul 22 00:21:57 node-1 haproxy[27895]: proxy keystone-1 has no server available!
<129>Jul 22 00:21:57 node-1 haproxy[27895]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: 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>Jul 22 00:21:58 node-1 haproxy[27899]: proxy keystone-2 has no server available!
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: 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>Jul 22 00:21:58 node-1 haproxy[27899]: proxy neutron has no server available!
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: 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>Jul 22 00:21:58 node-1 haproxy[27899]: proxy mysqld has no server available!
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:58 node-1 haproxy[27899]: 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>Jul 22 00:21:58 node-1 haproxy[27899]: proxy object-storage has no server available!
<129>Jul 22 00:21:58 node-1 haproxy[27899]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:59 node-1 haproxy[27899]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:59 node-1 haproxy[27899]: 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>Jul 22 00:21:59 node-1 haproxy[27899]: proxy aodh has no server available!
<129>Jul 22 00:21:59 node-1 haproxy[27899]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:59 node-1 haproxy[27899]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:21:59 node-1 haproxy[27899]: 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>Jul 22 00:21:59 node-1 haproxy[27899]: proxy ceilometer has no server available!
<27>Jul 22 00:22:00 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:00 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:00 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:00 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:00 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:00 node-1 multipathd: uevent trigger error
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:03 node-1 haproxy[29349]: 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>Jul 22 00:22:03 node-1 haproxy[29349]: proxy keystone-1 has no server available!
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:03 node-1 haproxy[29349]: 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>Jul 22 00:22:03 node-1 haproxy[29349]: proxy keystone-2 has no server available!
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:03 node-1 haproxy[29349]: 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>Jul 22 00:22:03 node-1 haproxy[29349]: proxy neutron has no server available!
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:03 node-1 haproxy[29349]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:04 node-1 haproxy[29353]: 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>Jul 22 00:22:04 node-1 haproxy[29353]: proxy mysqld has no server available!
<129>Jul 22 00:22:04 node-1 haproxy[29353]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:04 node-1 haproxy[29353]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:04 node-1 haproxy[29353]: 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>Jul 22 00:22:04 node-1 haproxy[29353]: proxy object-storage has no server available!
<129>Jul 22 00:22:04 node-1 haproxy[29353]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:04 node-1 haproxy[29353]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:04 node-1 haproxy[29353]: 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>Jul 22 00:22:04 node-1 haproxy[29353]: proxy aodh has no server available!
<129>Jul 22 00:22:04 node-1 haproxy[29353]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:04 node-1 haproxy[29353]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:04 node-1 haproxy[29353]: 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>Jul 22 00:22:04 node-1 haproxy[29353]: proxy ceilometer has no server available!
<27>Jul 22 00:22:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:06 node-1 multipathd: uevent trigger error
<129>Jul 22 00:22:08 node-1 haproxy[30732]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:08 node-1 haproxy[30732]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:08 node-1 haproxy[30732]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:08 node-1 haproxy[30732]: 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>Jul 22 00:22:08 node-1 haproxy[30732]: proxy keystone-1 has no server available!
<129>Jul 22 00:22:08 node-1 haproxy[30732]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:08 node-1 haproxy[30732]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:08 node-1 haproxy[30732]: 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>Jul 22 00:22:08 node-1 haproxy[30732]: proxy keystone-2 has no server available!
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: 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>Jul 22 00:22:09 node-1 haproxy[30736]: proxy neutron has no server available!
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: 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>Jul 22 00:22:09 node-1 haproxy[30736]: proxy mysqld has no server available!
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: 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>Jul 22 00:22:09 node-1 haproxy[30736]: proxy object-storage has no server available!
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:09 node-1 haproxy[30736]: 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>Jul 22 00:22:09 node-1 haproxy[30736]: proxy aodh has no server available!
<129>Jul 22 00:22:09 node-1 haproxy[30736]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:10 node-1 haproxy[30736]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:10 node-1 haproxy[30736]: 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>Jul 22 00:22:10 node-1 haproxy[30736]: proxy ceilometer has no server available!
<27>Jul 22 00:22:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:11 node-1 multipathd: uevent trigger error
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:14 node-1 haproxy[32224]: 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>Jul 22 00:22:14 node-1 haproxy[32224]: proxy keystone-1 has no server available!
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:14 node-1 haproxy[32224]: 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>Jul 22 00:22:14 node-1 haproxy[32224]: proxy keystone-2 has no server available!
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:14 node-1 haproxy[32224]: 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>Jul 22 00:22:14 node-1 haproxy[32224]: proxy glance-api has no server available!
<129>Jul 22 00:22:14 node-1 haproxy[32224]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: 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>Jul 22 00:22:15 node-1 haproxy[32233]: proxy glance-glare has no server available!
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: 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>Jul 22 00:22:15 node-1 haproxy[32233]: proxy neutron has no server available!
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: 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>Jul 22 00:22:15 node-1 haproxy[32233]: proxy glance-registry has no server available!
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: 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>Jul 22 00:22:15 node-1 haproxy[32233]: proxy mysqld has no server available!
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: 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>Jul 22 00:22:15 node-1 haproxy[32233]: proxy object-storage has no server available!
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:15 node-1 haproxy[32233]: 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>Jul 22 00:22:15 node-1 haproxy[32233]: proxy aodh has no server available!
<129>Jul 22 00:22:15 node-1 haproxy[32233]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:16 node-1 haproxy[32233]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:16 node-1 haproxy[32233]: 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>Jul 22 00:22:16 node-1 haproxy[32233]: proxy ceilometer has no server available!
<27>Jul 22 00:22:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:17 node-1 multipathd: uevent trigger error
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: 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>Jul 22 00:22:20 node-1 haproxy[1381]: proxy keystone-1 has no server available!
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: 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>Jul 22 00:22:20 node-1 haproxy[1381]: proxy keystone-2 has no server available!
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: 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>Jul 22 00:22:20 node-1 haproxy[1381]: proxy nova-api has no server available!
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: 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>Jul 22 00:22:20 node-1 haproxy[1381]: proxy nova-metadata-api has no server available!
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:20 node-1 haproxy[1381]: 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>Jul 22 00:22:20 node-1 haproxy[1381]: proxy glance-api has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: 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>Jul 22 00:22:21 node-1 haproxy[1385]: proxy glance-glare has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: 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>Jul 22 00:22:21 node-1 haproxy[1385]: proxy neutron has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: 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>Jul 22 00:22:21 node-1 haproxy[1385]: proxy glance-registry has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: 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>Jul 22 00:22:21 node-1 haproxy[1385]: proxy mysqld has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: 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>Jul 22 00:22:21 node-1 haproxy[1385]: proxy object-storage has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: 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>Jul 22 00:22:21 node-1 haproxy[1385]: proxy aodh has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:21 node-1 haproxy[1385]: 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>Jul 22 00:22:21 node-1 haproxy[1385]: proxy ceilometer has no server available!
<129>Jul 22 00:22:21 node-1 haproxy[1385]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:22 node-1 haproxy[1385]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:22 node-1 haproxy[1385]: 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>Jul 22 00:22:22 node-1 haproxy[1385]: proxy nova-novncproxy has no server available!
<27>Jul 22 00:22:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:23 node-1 multipathd: uevent trigger error
<129>Jul 22 00:22:25 node-1 haproxy[2780]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:25 node-1 haproxy[2780]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:25 node-1 haproxy[2780]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:25 node-1 haproxy[2780]: 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>Jul 22 00:22:25 node-1 haproxy[2780]: proxy keystone-1 has no server available!
<129>Jul 22 00:22:25 node-1 haproxy[2780]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:25 node-1 haproxy[2780]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy keystone-2 has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy nova-api has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy nova-metadata-api has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy cinder-api has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy glance-api has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy glance-glare has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy neutron has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: 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>Jul 22 00:22:26 node-1 haproxy[2784]: proxy glance-registry has no server available!
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:26 node-1 haproxy[2784]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: 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>Jul 22 00:22:27 node-1 haproxy[2784]: proxy mysqld has no server available!
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: 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>Jul 22 00:22:27 node-1 haproxy[2784]: proxy object-storage has no server available!
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: 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>Jul 22 00:22:27 node-1 haproxy[2784]: proxy aodh has no server available!
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: 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>Jul 22 00:22:27 node-1 haproxy[2784]: proxy ceilometer has no server available!
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:27 node-1 haproxy[2784]: 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>Jul 22 00:22:27 node-1 haproxy[2784]: proxy nova-novncproxy has no server available!
<27>Jul 22 00:22:28 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:28 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:28 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:28 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:28 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:28 node-1 multipathd: uevent trigger error
<129>Jul 22 00:22:31 node-1 haproxy[4435]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:31 node-1 haproxy[4435]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:31 node-1 haproxy[4435]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:31 node-1 haproxy[4435]: 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>Jul 22 00:22:31 node-1 haproxy[4435]: proxy keystone-1 has no server available!
<129>Jul 22 00:22:31 node-1 haproxy[4435]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:31 node-1 haproxy[4435]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:31 node-1 haproxy[4435]: 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>Jul 22 00:22:31 node-1 haproxy[4435]: proxy keystone-2 has no server available!
<129>Jul 22 00:22:31 node-1 haproxy[4435]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:31 node-1 haproxy[4435]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:31 node-1 haproxy[4435]: 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>Jul 22 00:22:31 node-1 haproxy[4435]: proxy nova-api has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy nova-metadata-api has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy cinder-api has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy glance-api has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy glance-glare has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy neutron has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy glance-registry has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy mysqld has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy object-storage has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:32 node-1 haproxy[4439]: 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>Jul 22 00:22:32 node-1 haproxy[4439]: proxy aodh has no server available!
<129>Jul 22 00:22:32 node-1 haproxy[4439]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: 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>Jul 22 00:22:33 node-1 haproxy[4439]: proxy ceilometer has no server available!
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: 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>Jul 22 00:22:33 node-1 haproxy[4439]: proxy heat-api has no server available!
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: 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>Jul 22 00:22:33 node-1 haproxy[4439]: proxy heat-api-cfn has no server available!
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: 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>Jul 22 00:22:33 node-1 haproxy[4439]: proxy heat-api-cloudwatch has no server available!
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 00:22:33 node-1 haproxy[4439]: 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>Jul 22 00:22:33 node-1 haproxy[4439]: proxy nova-novncproxy has no server available!
<27>Jul 22 00:22:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:22:49 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 22 00:23:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:23:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 00:23:15 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 22 00:23:17 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 22 00:24:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:24:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:24:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:24:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:26:36 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:36 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:36 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:36 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:36 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:36 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:26:43 node-1 multipathd: uevent trigger error
<43>Jul 22 00:26:59 node-1 apache2_error [Fri Jul 22 00:26:58.143678 2016] [mpm_event:notice] [pid 16491:tid 139889987164032] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 00:26:59 node-1 apache2_error [Fri Jul 22 00:26:58.143751 2016] [core:notice] [pid 16491:tid 139889987164032] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 00:27:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:07 node-1 multipathd: uevent trigger error
<43>Jul 22 00:27:09 node-1 apache2_error [Fri Jul 22 00:27:01.440956 2016] [mpm_event:notice] [pid 16491:tid 139889987164032] AH00491: caught SIGTERM, shutting down
<43>Jul 22 00:27:09 node-1 apache2_error [Fri Jul 22 00:27:02.528182 2016] [mpm_worker:notice] [pid 16958:tid 139728464775040] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 00:27:09 node-1 apache2_error [Fri Jul 22 00:27:02.528234 2016] [core:notice] [pid 16958:tid 139728464775040] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 00:27:12 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:12 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:12 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:12 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:12 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:12 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:27:15 node-1 multipathd: uevent trigger error
<43>Jul 22 00:28:39 node-1 apache2_error [Fri Jul 22 00:28:31.785546 2016] [mpm_worker:notice] [pid 16958:tid 139728464775040] AH00295: caught SIGTERM, shutting down
<43>Jul 22 00:28:39 node-1 apache2_error [Fri Jul 22 00:28:32.547743 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 00:28:39 node-1 apache2_error [Fri Jul 22 00:28:32.547791 2016] [core:notice] [pid 818:tid 140356242573184] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 22 00:29:19 node-1 apache2_error [Fri Jul 22 00:29:18.236491 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 00:29:19 node-1 apache2_error [Fri Jul 22 00:29:18.437584 2016] [mpm_worker:warn] [pid 818:tid 140356242573184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 00:29:19 node-1 apache2_error [Fri Jul 22 00:29:18.440455 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 00:29:19 node-1 apache2_error [Fri Jul 22 00:29:18.440474 2016] [core:notice] [pid 818:tid 140356242573184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 00:29:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:30:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:03 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:48 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:48 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:48 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:48 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:48 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:48 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:30:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:41 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:41 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:41 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:41 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:41 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:41 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:31:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:32:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:32:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:32:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:32:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:32:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:32:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:32:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:34:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:34:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:34:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:34:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:34:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:34:07 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:31 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:35:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:32 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:35:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:38:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:34 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:39 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:39 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:39 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:39 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:39 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:39 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:38:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:39:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:40:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:41:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:41:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:41:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:41:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:41:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:41:34 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:43:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:43:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:43:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:43:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:43:33 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:44:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:45:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:21 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:21 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:26 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:26 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:26 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:26 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:26 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:26 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:38 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:44 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:44 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:44 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:44 node-1 multipathd: uevent trigger error
<27>Jul 22 00:45:44 node-1 multipathd: uevent trigger error
<27>Jul 22 00:46:14 node-1 multipathd: uevent trigger error
<27>Jul 22 00:46:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:46:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:46:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:46:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:46:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:47:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:47:37 node-1 multipathd: uevent trigger error
<11>Jul 22 00:47:51 node-1 liberasurecode[25697]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:51 node-1 liberasurecode[25697]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:51 node-1 liberasurecode[25697]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:51 node-1 liberasurecode[25697]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:52 node-1 liberasurecode[25721]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:52 node-1 liberasurecode[25721]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:52 node-1 liberasurecode[25721]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:52 node-1 liberasurecode[25721]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:54 node-1 liberasurecode[26247]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:54 node-1 liberasurecode[26247]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:54 node-1 liberasurecode[26247]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:54 node-1 liberasurecode[26247]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[28036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[28036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[28036]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:47:59 node-1 liberasurecode[28036]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28116]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28116]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28116]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28116]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28335]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28335]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28335]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28335]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28353]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28353]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28353]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28353]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28368]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28368]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28383]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28383]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28383]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:00 node-1 liberasurecode[28383]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:09 node-1 liberasurecode[29217]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:09 node-1 liberasurecode[29217]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:09 node-1 liberasurecode[29217]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:48:09 node-1 liberasurecode[29217]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 00:48:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:48:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:48:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:48:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:48:17 node-1 multipathd: uevent trigger error
<27>Jul 22 00:48:17 node-1 multipathd: uevent trigger error
<43>Jul 22 00:49:11 node-1 apache2_error [Fri Jul 22 00:49:04.526899 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 00:49:11 node-1 apache2_error [Fri Jul 22 00:49:04.909988 2016] [mpm_worker:warn] [pid 818:tid 140356242573184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 00:49:11 node-1 apache2_error [Fri Jul 22 00:49:04.915525 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 00:49:11 node-1 apache2_error [Fri Jul 22 00:49:04.915565 2016] [core:notice] [pid 818:tid 140356242573184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 00:49:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:45 node-1 multipathd: uevent trigger error
<43>Jul 22 00:49:51 node-1 apache2_error [Fri Jul 22 00:49:41.880705 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 00:49:51 node-1 apache2_error [Fri Jul 22 00:49:42.261138 2016] [mpm_worker:warn] [pid 818:tid 140356242573184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 00:49:51 node-1 apache2_error [Fri Jul 22 00:49:42.270614 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 00:49:51 node-1 apache2_error [Fri Jul 22 00:49:42.270646 2016] [core:notice] [pid 818:tid 140356242573184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 00:49:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:53 node-1 multipathd: uevent trigger error
<27>Jul 22 00:49:53 node-1 multipathd: uevent trigger error
<11>Jul 22 00:50:01 node-1 liberasurecode[13315]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:50:01 node-1 liberasurecode[13315]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:50:01 node-1 liberasurecode[13315]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:50:01 node-1 liberasurecode[13315]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 00:50:31 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:31 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:31 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:31 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:31 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:31 node-1 multipathd: uevent trigger error
<43>Jul 22 00:50:31 node-1 apache2_error [Fri Jul 22 00:50:27.549673 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 00:50:31 node-1 apache2_error [Fri Jul 22 00:50:27.742691 2016] [mpm_worker:warn] [pid 818:tid 140356242573184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 00:50:31 node-1 apache2_error [Fri Jul 22 00:50:27.750354 2016] [mpm_worker:notice] [pid 818:tid 140356242573184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 00:50:31 node-1 apache2_error [Fri Jul 22 00:50:27.750381 2016] [core:notice] [pid 818:tid 140356242573184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 00:50:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:37 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:39 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 00:50:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:50:43 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:23 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:30 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:38 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 22 00:51:47 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:47 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:47 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:47 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:47 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:51:57 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:02 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:03 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:13 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:13 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:13 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:13 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:13 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:14 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 00:52:40 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:40 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:40 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:40 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:40 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:45 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:58 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:58 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:58 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:58 node-1 multipathd: uevent trigger error
<27>Jul 22 00:52:58 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:05 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:10 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:22 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:51 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:52 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:56 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:56 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:56 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:56 node-1 multipathd: uevent trigger error
<27>Jul 22 00:53:56 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:01 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:06 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:11 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:15 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:19 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:20 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:20 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:20 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:24 node-1 multipathd: uevent trigger error
<27>Jul 22 00:54:24 node-1 multipathd: uevent trigger error
<11>Jul 22 00:55:02 node-1 liberasurecode[27082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:55:02 node-1 liberasurecode[27082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:55:02 node-1 liberasurecode[27082]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 00:55:02 node-1 liberasurecode[27082]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
