Jul 27 00:23:57 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8367" x-info="http://www.rsyslog.com"] start
Jul 27 00:23:57 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 27 00:23:57 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 27 00:23:57 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 27 00:23:57 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 27 00:23:57 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 27 00:23:57 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 27 00:23:57 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 27 00:23:57 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=621e68c3-1f19-4ce9-9701-f780c68c437d nomdmonddf nomdmonisw
Jul 27 00:23:57 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 27 00:23:57 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 27 00:23:57 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 27 00:23:57 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 27 00:23:57 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 27 00:23:57 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 27 00:23:57 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 27 00:23:57 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 27 00:23:57 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 27 00:23:57 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 00:23:57 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 27 00:23:57 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 27 00:23:57 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 27 00:23:57 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 27 00:23:57 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 27 00:23:57 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 27 00:23:57 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 27 00:23:57 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 27 00:23:57 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 27 00:23:57 node-1 kernel: [    0.000000]   2 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000]   3 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000]   4 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000]   5 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000]   6 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000]   7 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000]   8 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000]   9 disabled
Jul 27 00:23:57 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 27 00:23:57 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 27 00:23:57 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 27 00:23:57 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 27 00:23:57 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 27 00:23:57 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 27 00:23:57 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 27 00:23:57 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 27 00:23:57 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 27 00:23:57 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 27 00:23:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 27 00:23:57 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 27 00:23:57 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 27 00:23:57 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 27 00:23:57 node-1 kernel: [    0.000000] Zone ranges:
Jul 27 00:23:57 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 27 00:23:57 node-1 kernel: [    0.000000] Early memory node ranges
Jul 27 00:23:57 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 27 00:23:57 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 27 00:23:57 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 27 00:23:57 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 27 00:23:57 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 27 00:23:57 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 27 00:23:57 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 27 00:23:57 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 27 00:23:57 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 27 00:23:57 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 27 00:23:57 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 27 00:23:57 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 27 00:23:57 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 27 00:23:57 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 27 00:23:57 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 27 00:23:57 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 27 00:23:57 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 27 00:23:57 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 27 00:23:57 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 27 00:23:57 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 27 00:23:57 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 27 00:23:57 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 27 00:23:57 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 27 00:23:57 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 27 00:23:57 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 27 00:23:57 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 27 00:23:57 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=621e68c3-1f19-4ce9-9701-f780c68c437d nomdmonddf nomdmonisw
Jul 27 00:23:57 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 27 00:23:57 node-1 kernel: [    0.000000] Checking aperture...
Jul 27 00:23:57 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 00:23:57 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 27 00:23:57 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 27 00:23:57 node-1 kernel: [    0.000000] Memory: 32653452K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 27 00:23:57 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 27 00:23:57 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 27 00:23:57 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 27 00:23:57 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 27 00:23:57 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 27 00:23:57 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 27 00:23:57 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 27 00:23:57 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 27 00:23:57 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 27 00:23:57 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 27 00:23:57 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 27 00:23:57 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 27 00:23:57 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 27 00:23:57 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 27 00:23:57 node-1 kernel: [    0.004000] tsc: Detected 3492.132 MHz processor
Jul 27 00:23:57 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.26 BogoMIPS (lpj=13968528)
Jul 27 00:23:57 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 27 00:23:57 node-1 kernel: [    0.000043] Security Framework initialized
Jul 27 00:23:57 node-1 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 27 00:23:57 node-1 kernel: [    0.000064] Yama: becoming mindful.
Jul 27 00:23:57 node-1 kernel: [    0.001464] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.006344] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.008276] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.008304] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.008590] Initializing cgroup subsys memory
Jul 27 00:23:57 node-1 kernel: [    0.008599] Initializing cgroup subsys devices
Jul 27 00:23:57 node-1 kernel: [    0.008600] Initializing cgroup subsys freezer
Jul 27 00:23:57 node-1 kernel: [    0.008602] Initializing cgroup subsys blkio
Jul 27 00:23:57 node-1 kernel: [    0.008603] Initializing cgroup subsys perf_event
Jul 27 00:23:57 node-1 kernel: [    0.008606] Initializing cgroup subsys hugetlb
Jul 27 00:23:57 node-1 kernel: [    0.008625] CPU: Physical Processor ID: 0
Jul 27 00:23:57 node-1 kernel: [    0.008626] CPU: Processor Core ID: 0
Jul 27 00:23:57 node-1 kernel: [    0.008630] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 27 00:23:57 node-1 kernel: [    0.008630] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 27 00:23:57 node-1 kernel: [    0.009324] mce: CPU supports 22 MCE banks
Jul 27 00:23:57 node-1 kernel: [    0.009351] CPU0: Thermal monitoring enabled (TM1)
Jul 27 00:23:57 node-1 kernel: [    0.009372] process: using mwait in idle threads
Jul 27 00:23:57 node-1 kernel: [    0.009375] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 27 00:23:57 node-1 kernel: [    0.009375] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 27 00:23:57 node-1 kernel: [    0.009375] tlb_flushall_shift: 6
Jul 27 00:23:57 node-1 kernel: [    0.009464] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 27 00:23:57 node-1 kernel: [    0.010189] ACPI: Core revision 20131115
Jul 27 00:23:57 node-1 kernel: [    0.022864] ACPI: All ACPI Tables successfully acquired
Jul 27 00:23:57 node-1 kernel: [    0.023025] ftrace: allocating 28617 entries in 112 pages
Jul 27 00:23:57 node-1 kernel: [    0.031838] dmar: Host address width 46
Jul 27 00:23:57 node-1 kernel: [    0.031840] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 27 00:23:57 node-1 kernel: [    0.031846] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 00:23:57 node-1 kernel: [    0.031848] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 27 00:23:57 node-1 kernel: [    0.031852] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 00:23:57 node-1 kernel: [    0.031853] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 27 00:23:57 node-1 kernel: [    0.031855] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 27 00:23:57 node-1 kernel: [    0.031856] dmar: ATSR flags: 0x0
Jul 27 00:23:57 node-1 kernel: [    0.031857] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 27 00:23:57 node-1 kernel: [    0.031858] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 27 00:23:57 node-1 kernel: [    0.031974] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 27 00:23:57 node-1 kernel: [    0.031976] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 00:23:57 node-1 kernel: [    0.031977] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 00:23:57 node-1 kernel: [    0.031978] HPET id 0 under DRHD base 0xc7ffc000
Jul 27 00:23:57 node-1 kernel: [    0.031979] Your BIOS is broken and requested that x2apic be disabled.
Jul 27 00:23:57 node-1 kernel: [    0.031979] This will slightly decrease performance.
Jul 27 00:23:57 node-1 kernel: [    0.031979] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 27 00:23:57 node-1 kernel: [    0.032410] Enabled IRQ remapping in xapic mode
Jul 27 00:23:57 node-1 kernel: [    0.032411] x2apic not enabled, IRQ remapping is in xapic mode
Jul 27 00:23:57 node-1 kernel: [    0.032415] Switched APIC routing to physical flat.
Jul 27 00:23:57 node-1 kernel: [    0.033048] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 27 00:23:57 node-1 kernel: [    0.072700] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 27 00:23:57 node-1 kernel: [    0.072706] TSC deadline timer enabled
Jul 27 00:23:57 node-1 kernel: [    0.072713] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 27 00:23:57 node-1 kernel: [    0.072719] ... version:                3
Jul 27 00:23:57 node-1 kernel: [    0.072720] ... bit width:              48
Jul 27 00:23:57 node-1 kernel: [    0.072721] ... generic registers:      4
Jul 27 00:23:57 node-1 kernel: [    0.072722] ... value mask:             0000ffffffffffff
Jul 27 00:23:57 node-1 kernel: [    0.072723] ... max period:             0000ffffffffffff
Jul 27 00:23:57 node-1 kernel: [    0.072724] ... fixed-purpose events:   3
Jul 27 00:23:57 node-1 kernel: [    0.072725] ... event mask:             000000070000000f
Jul 27 00:23:57 node-1 kernel: [    0.074144] x86: Booting SMP configuration:
Jul 27 00:23:57 node-1 kernel: [    0.088249] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 27 00:23:57 node-1 kernel: [    0.074146] .... node  #0, CPUs:        #1  #2  #3
Jul 27 00:23:57 node-1 kernel: [    0.116167] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 27 00:23:57 node-1 kernel: [    0.270028] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 27 00:23:57 node-1 kernel: [    0.325641] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 27 00:23:57 node-1 kernel: [    0.382297] x86: Booted up 2 nodes, 16 CPUs
Jul 27 00:23:57 node-1 kernel: [    0.382300] smpboot: Total of 16 processors activated (111760.34 BogoMIPS)
Jul 27 00:23:57 node-1 kernel: [    0.405325] devtmpfs: initialized
Jul 27 00:23:57 node-1 kernel: [    0.408401] EVM: security.selinux
Jul 27 00:23:57 node-1 kernel: [    0.408402] EVM: security.SMACK64
Jul 27 00:23:57 node-1 kernel: [    0.408403] EVM: security.ima
Jul 27 00:23:57 node-1 kernel: [    0.408404] EVM: security.capability
Jul 27 00:23:57 node-1 kernel: [    0.408455] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.409122] pinctrl core: initialized pinctrl subsystem
Jul 27 00:23:57 node-1 kernel: [    0.409185] regulator-dummy: no parameters
Jul 27 00:23:57 node-1 kernel: [    0.409217] RTC time:  0:23:21, date: 07/27/16
Jul 27 00:23:57 node-1 kernel: [    0.409250] NET: Registered protocol family 16
Jul 27 00:23:57 node-1 kernel: [    0.409338] cpuidle: using governor ladder
Jul 27 00:23:57 node-1 kernel: [    0.409339] cpuidle: using governor menu
Jul 27 00:23:57 node-1 kernel: [    0.409373] ACPI: bus type PCI registered
Jul 27 00:23:57 node-1 kernel: [    0.409375] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 27 00:23:57 node-1 kernel: [    0.409421] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 27 00:23:57 node-1 kernel: [    0.409424] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 27 00:23:57 node-1 kernel: [    0.423154] PCI: Using configuration type 1 for base access
Jul 27 00:23:57 node-1 kernel: [    0.424158] bio: create slab <bio-0> at 0
Jul 27 00:23:57 node-1 kernel: [    0.424435] ACPI: Added _OSI(Module Device)
Jul 27 00:23:57 node-1 kernel: [    0.424437] ACPI: Added _OSI(Processor Device)
Jul 27 00:23:57 node-1 kernel: [    0.424438] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 27 00:23:57 node-1 kernel: [    0.424439] ACPI: Added _OSI(Processor Aggregator Device)
Jul 27 00:23:57 node-1 kernel: [    0.437066] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 27 00:23:57 node-1 kernel: [    0.447574] ACPI: Interpreter enabled
Jul 27 00:23:57 node-1 kernel: [    0.447580] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 27 00:23:57 node-1 kernel: [    0.447584] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 27 00:23:57 node-1 kernel: [    0.447586] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 27 00:23:57 node-1 kernel: [    0.447593] ACPI: (supports S0 S4 S5)
Jul 27 00:23:57 node-1 kernel: [    0.447594] ACPI: Using IOAPIC for interrupt routing
Jul 27 00:23:57 node-1 kernel: [    0.447635] HEST: Table parsing has been initialized.
Jul 27 00:23:57 node-1 kernel: [    0.447638] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 27 00:23:57 node-1 kernel: [    0.448189] ACPI: No dock devices found.
Jul 27 00:23:57 node-1 kernel: [    0.459653] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 27 00:23:57 node-1 kernel: [    0.459658] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 00:23:57 node-1 kernel: [    0.459662] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 00:23:57 node-1 kernel: [    0.459688] PCI host bridge to bus 0000:ff
Jul 27 00:23:57 node-1 kernel: [    0.459690] pci_bus 0000:ff: root bus resource [bus ff]
Jul 27 00:23:57 node-1 kernel: [    0.459698] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.459737] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.459767] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.459801] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.459829] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.459857] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.459887] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.459915] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.459943] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.459970] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.459996] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460022] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460049] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460074] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460101] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460126] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460155] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460182] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460208] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.460235] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460260] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.460285] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460311] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460340] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.460374] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460404] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460434] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460464] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460494] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460526] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460557] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460588] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460618] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460648] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460680] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460712] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460744] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460772] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460799] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460830] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460861] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460897] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460931] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460963] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.460991] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461020] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461051] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461082] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461114] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461145] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461176] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461205] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461234] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461261] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461290] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461322] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461354] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461410] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 27 00:23:57 node-1 kernel: [    0.461413] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 00:23:57 node-1 kernel: [    0.461416] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 00:23:57 node-1 kernel: [    0.461434] PCI host bridge to bus 0000:7f
Jul 27 00:23:57 node-1 kernel: [    0.461436] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 27 00:23:57 node-1 kernel: [    0.461441] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461468] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.461497] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461526] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461548] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.461573] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.461599] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461626] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461648] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461671] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461693] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461715] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461739] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461761] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461785] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461812] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461834] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461862] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461887] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.461913] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461937] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.461961] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.461986] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462013] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 00:23:57 node-1 kernel: [    0.462047] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462073] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462099] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462125] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462150] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462178] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462205] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462236] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462262] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462290] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462318] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462346] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462375] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462402] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462427] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462455] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462480] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462506] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462534] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462560] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462585] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462612] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462637] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462663] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462691] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462718] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462746] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462771] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462794] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462819] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462844] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462874] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.462900] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.464153] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 27 00:23:57 node-1 kernel: [    0.464157] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 00:23:57 node-1 kernel: [    0.465284] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 00:23:57 node-1 kernel: [    0.465788] PCI host bridge to bus 0000:00
Jul 27 00:23:57 node-1 kernel: [    0.465791] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 27 00:23:57 node-1 kernel: [    0.465792] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 27 00:23:57 node-1 kernel: [    0.465794] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 27 00:23:57 node-1 kernel: [    0.465795] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 27 00:23:57 node-1 kernel: [    0.465796] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 27 00:23:57 node-1 kernel: [    0.465798] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 27 00:23:57 node-1 kernel: [    0.465799] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 27 00:23:57 node-1 kernel: [    0.465805] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 27 00:23:57 node-1 kernel: [    0.465892] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.465923] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.465964] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 27 00:23:57 node-1 kernel: [    0.465984] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.466013] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.466053] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 27 00:23:57 node-1 kernel: [    0.466072] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.466101] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.466144] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 27 00:23:57 node-1 kernel: [    0.466162] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.466232] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.466309] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.466385] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 00:23:57 node-1 kernel: [    0.466390] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 27 00:23:57 node-1 kernel: [    0.466475] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 27 00:23:57 node-1 kernel: [    0.466622] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 27 00:23:57 node-1 kernel: [    0.466639] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 27 00:23:57 node-1 kernel: [    0.466717] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.466772] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 27 00:23:57 node-1 kernel: [    0.466794] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.466850] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.466893] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 27 00:23:57 node-1 kernel: [    0.466921] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.466978] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.467020] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 27 00:23:57 node-1 kernel: [    0.467043] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 27 00:23:57 node-1 kernel: [    0.467061] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 27 00:23:57 node-1 kernel: [    0.467138] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.467187] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 27 00:23:57 node-1 kernel: [    0.467217] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 27 00:23:57 node-1 kernel: [    0.467466] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 27 00:23:57 node-1 kernel: [    0.467472] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 27 00:23:57 node-1 kernel: [    0.467478] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.467483] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.467491] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 27 00:23:57 node-1 kernel: [    0.467521] pci 0000:01:00.0: supports D1 D2
Jul 27 00:23:57 node-1 kernel: [    0.473874] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 00:23:57 node-1 kernel: [    0.473881] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 00:23:57 node-1 kernel: [    0.473885] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 00:23:57 node-1 kernel: [    0.474011] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.474044] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 27 00:23:57 node-1 kernel: [    0.481871] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 00:23:57 node-1 kernel: [    0.481878] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.481882] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 00:23:57 node-1 kernel: [    0.481975] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.482043] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.482146] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.482191] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 00:23:57 node-1 kernel: [    0.482194] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.482196] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 00:23:57 node-1 kernel: [    0.482248] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.482370] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.482423] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 00:23:57 node-1 kernel: [    0.482426] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.482428] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.482477] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.482596] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.482633] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.482752] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.482788] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.482908] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.482943] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 27 00:23:57 node-1 kernel: [    0.483079] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 27 00:23:57 node-1 kernel: [    0.483120] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 00:23:57 node-1 kernel: [    0.483123] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.483125] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.483184] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 27 00:23:57 node-1 kernel: [    0.483247] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.483299] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.483340] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 27 00:23:57 node-1 kernel: [    0.483425] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 27 00:23:57 node-1 kernel: [    0.483530] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 00:23:57 node-1 kernel: [    0.483532] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.483534] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.483590] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 27 00:23:57 node-1 kernel: [    0.483643] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.483691] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.483903] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 00:23:57 node-1 kernel: [    0.483907] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 00:23:57 node-1 kernel: [    0.483970] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 27 00:23:57 node-1 kernel: [    0.484022] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.484095] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.484304] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 00:23:57 node-1 kernel: [    0.484307] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 00:23:57 node-1 kernel: [    0.484366] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 27 00:23:57 node-1 kernel: [    0.484427] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.484482] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 27 00:23:57 node-1 kernel: [    0.484703] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 00:23:57 node-1 kernel: [    0.484707] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 00:23:57 node-1 kernel: [    0.484880] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 00:23:57 node-1 kernel: [    0.484919] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 00:23:57 node-1 kernel: [    0.484993] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 27 00:23:57 node-1 kernel: [    0.485012] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 27 00:23:57 node-1 kernel: [    0.485025] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 27 00:23:57 node-1 kernel: [    0.485038] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 27 00:23:57 node-1 kernel: [    0.485088] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 27 00:23:57 node-1 kernel: [    0.489881] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 00:23:57 node-1 kernel: [    0.489890] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 00:23:57 node-1 kernel: [    0.489942] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 27 00:23:57 node-1 kernel: [    0.490671] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 27 00:23:57 node-1 kernel: [    0.490674] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 00:23:57 node-1 kernel: [    0.490797] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 00:23:57 node-1 kernel: [    0.490902] PCI host bridge to bus 0000:80
Jul 27 00:23:57 node-1 kernel: [    0.490904] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 27 00:23:57 node-1 kernel: [    0.490906] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 27 00:23:57 node-1 kernel: [    0.490907] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 27 00:23:57 node-1 kernel: [    0.490915] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.490977] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.491044] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 00:23:57 node-1 kernel: [    0.491105] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 00:23:57 node-1 kernel: [    0.491111] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 27 00:23:57 node-1 kernel: [    0.491182] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 27 00:23:57 node-1 kernel: [    0.491481] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 27 00:23:57 node-1 kernel: [    0.491512] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 27 00:23:57 node-1 kernel: [    0.491542] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 27 00:23:57 node-1 kernel: [    0.491570] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 27 00:23:57 node-1 kernel: [    0.491600] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 00:23:57 node-1 kernel: [    0.491630] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 00:23:57 node-1 kernel: [    0.491659] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 00:23:57 node-1 kernel: [    0.491689] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 00:23:57 node-1 kernel: [    0.491773] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 27 00:23:57 node-1 kernel: [    0.491777] ACPI: \_SB_.UNC1: notify handler is installed
Jul 27 00:23:57 node-1 kernel: [    0.491778] ACPI: \_SB_.UNC0: notify handler is installed
Jul 27 00:23:57 node-1 kernel: [    0.491793] ACPI: \_SB_.PCI0: notify handler is installed
Jul 27 00:23:57 node-1 kernel: [    0.491846] ACPI: \_SB_.PCI1: notify handler is installed
Jul 27 00:23:57 node-1 kernel: [    0.491926] Found 4 acpi root devices
Jul 27 00:23:57 node-1 kernel: [    0.492032] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 27 00:23:57 node-1 kernel: [    0.492034] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 27 00:23:57 node-1 kernel: [    0.492036] vgaarb: loaded
Jul 27 00:23:57 node-1 kernel: [    0.492037] vgaarb: bridge control possible 0000:0c:00.0
Jul 27 00:23:57 node-1 kernel: [    0.492145] SCSI subsystem initialized
Jul 27 00:23:57 node-1 kernel: [    0.492209] libata version 3.00 loaded.
Jul 27 00:23:57 node-1 kernel: [    0.492223] ACPI: bus type USB registered
Jul 27 00:23:57 node-1 kernel: [    0.492233] usbcore: registered new interface driver usbfs
Jul 27 00:23:57 node-1 kernel: [    0.492238] usbcore: registered new interface driver hub
Jul 27 00:23:57 node-1 kernel: [    0.492273] usbcore: registered new device driver usb
Jul 27 00:23:57 node-1 kernel: [    0.492430] PCI: Using ACPI for IRQ routing
Jul 27 00:23:57 node-1 kernel: [    0.496041] PCI: pci_cache_line_size set to 64 bytes
Jul 27 00:23:57 node-1 kernel: [    0.496245] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 27 00:23:57 node-1 kernel: [    0.496246] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 27 00:23:57 node-1 kernel: [    0.496247] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 27 00:23:57 node-1 kernel: [    0.496311] NetLabel: Initializing
Jul 27 00:23:57 node-1 kernel: [    0.496312] NetLabel:  domain hash size = 128
Jul 27 00:23:57 node-1 kernel: [    0.496313] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 27 00:23:57 node-1 kernel: [    0.496323] NetLabel:  unlabeled traffic allowed by default
Jul 27 00:23:57 node-1 kernel: [    0.496378] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 27 00:23:57 node-1 kernel: [    0.496382] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 27 00:23:57 node-1 kernel: [    0.498449] Switched to clocksource hpet
Jul 27 00:23:57 node-1 kernel: [    0.502865] AppArmor: AppArmor Filesystem Enabled
Jul 27 00:23:57 node-1 kernel: [    0.502903] pnp: PnP ACPI init
Jul 27 00:23:57 node-1 kernel: [    0.502915] ACPI: bus type PNP registered
Jul 27 00:23:57 node-1 kernel: [    0.503093] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503105] pnp 00:01: [dma 4]
Jul 27 00:23:57 node-1 kernel: [    0.503123] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503157] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503181] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503202] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503249] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503359] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503362] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 27 00:23:57 node-1 kernel: [    0.503364] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503365] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503367] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503368] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503371] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 27 00:23:57 node-1 kernel: [    0.503373] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503375] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503377] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503378] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503380] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503381] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 27 00:23:57 node-1 kernel: [    0.503384] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503485] pnp 00:07: [dma 0 disabled]
Jul 27 00:23:57 node-1 kernel: [    0.503517] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503599] pnp 00:08: [dma 0 disabled]
Jul 27 00:23:57 node-1 kernel: [    0.503635] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 00:23:57 node-1 kernel: [    0.503693] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 27 00:23:57 node-1 kernel: [    0.504134] pnp: PnP ACPI: found 10 devices
Jul 27 00:23:57 node-1 kernel: [    0.504136] ACPI: bus type PNP unregistered
Jul 27 00:23:57 node-1 kernel: [    0.510149] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 00:23:57 node-1 kernel: [    0.510152] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 00:23:57 node-1 kernel: [    0.510155] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 00:23:57 node-1 kernel: [    0.510160] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 00:23:57 node-1 kernel: [    0.510162] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510177] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510206] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 00:23:57 node-1 kernel: [    0.510221] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510250] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 00:23:57 node-1 kernel: [    0.510265] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 00:23:57 node-1 kernel: [    0.510293] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 00:23:57 node-1 kernel: [    0.510311] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 00:23:57 node-1 kernel: [    0.510340] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 00:23:57 node-1 kernel: [    0.510342] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510357] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510386] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 00:23:57 node-1 kernel: [    0.510388] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510403] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510436] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 00:23:57 node-1 kernel: [    0.510438] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510440] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510445] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 00:23:57 node-1 kernel: [    0.510447] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510450] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510454] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 00:23:57 node-1 kernel: [    0.510460] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 00:23:57 node-1 kernel: [    0.510469] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 00:23:57 node-1 kernel: [    0.510473] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 00:23:57 node-1 kernel: [    0.510480] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 27 00:23:57 node-1 kernel: [    0.510481] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 27 00:23:57 node-1 kernel: [    0.510482] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 27 00:23:57 node-1 kernel: [    0.510482] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 27 00:23:57 node-1 kernel: [    0.510483] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 27 00:23:57 node-1 kernel: [    0.510484] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 27 00:23:57 node-1 kernel: [    0.510485] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 27 00:23:57 node-1 kernel: [    0.510486] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 27 00:23:57 node-1 kernel: [    0.510488] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510489] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510490] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510491] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510492] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510493] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510494] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510494] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510495] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 27 00:23:57 node-1 kernel: [    0.510496] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510498] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 27 00:23:57 node-1 kernel: [    0.510499] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 27 00:23:57 node-1 kernel: [    0.510500] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 27 00:23:57 node-1 kernel: [    0.510501] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 27 00:23:57 node-1 kernel: [    0.510504] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 27 00:23:57 node-1 kernel: [    0.510505] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 27 00:23:57 node-1 kernel: [    0.510544] NET: Registered protocol family 2
Jul 27 00:23:57 node-1 kernel: [    0.510835] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.511207] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.511383] TCP: Hash tables configured (established 262144 bind 65536)
Jul 27 00:23:57 node-1 kernel: [    0.511425] TCP: reno registered
Jul 27 00:23:57 node-1 kernel: [    0.511456] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.511563] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.511723] NET: Registered protocol family 1
Jul 27 00:23:57 node-1 kernel: [    0.546542] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 27 00:23:57 node-1 kernel: [    0.546556] PCI: CLS 64 bytes, default 64
Jul 27 00:23:57 node-1 kernel: [    0.546641] Trying to unpack rootfs image as initramfs...
Jul 27 00:23:57 node-1 kernel: [    0.768366] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 27 00:23:57 node-1 kernel: [    0.768424] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 27 00:23:57 node-1 kernel: [    0.768434] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 27 00:23:57 node-1 kernel: [    0.768873] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768879] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768887] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768894] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768903] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768911] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768922] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768930] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768938] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768945] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768952] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768959] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768966] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768973] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768980] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.768986] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 00:23:57 node-1 kernel: [    0.769041] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 27 00:23:57 node-1 kernel: [    0.769045] Scanning for low memory corruption every 60 seconds
Jul 27 00:23:57 node-1 kernel: [    0.769353] Initialise system trusted keyring
Jul 27 00:23:57 node-1 kernel: [    0.769402] audit: initializing netlink socket (disabled)
Jul 27 00:23:57 node-1 kernel: [    0.769415] type=2000 audit(1469579001.716:1): initialized
Jul 27 00:23:57 node-1 kernel: [    0.787342] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 27 00:23:57 node-1 kernel: [    0.788843] zbud: loaded
Jul 27 00:23:57 node-1 kernel: [    0.788962] VFS: Disk quotas dquot_6.5.2
Jul 27 00:23:57 node-1 kernel: [    0.788996] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 27 00:23:57 node-1 kernel: [    0.789369] fuse init (API version 7.22)
Jul 27 00:23:57 node-1 kernel: [    0.789427] msgmni has been set to 32768
Jul 27 00:23:57 node-1 kernel: [    0.789474] Key type big_key registered
Jul 27 00:23:57 node-1 kernel: [    0.789978] Key type asymmetric registered
Jul 27 00:23:57 node-1 kernel: [    0.789980] Asymmetric key parser 'x509' registered
Jul 27 00:23:57 node-1 kernel: [    0.790001] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 27 00:23:57 node-1 kernel: [    0.790060] io scheduler noop registered
Jul 27 00:23:57 node-1 kernel: [    0.790062] io scheduler deadline registered (default)
Jul 27 00:23:57 node-1 kernel: [    0.790080] io scheduler cfq registered
Jul 27 00:23:57 node-1 kernel: [    0.790405] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    0.790507] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    0.790600] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    0.790690] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    0.790789] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    0.790856] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    0.791118] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 27 00:23:57 node-1 kernel: [    0.791138] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 27 00:23:57 node-1 kernel: [    0.791160] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 27 00:23:57 node-1 kernel: [    0.791171] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791173] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791176] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 27 00:23:57 node-1 kernel: [    0.791180] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791181] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791182] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791184] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791185] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791187] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791188] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791189] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791191] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791192] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791193] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791195] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791197] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 27 00:23:57 node-1 kernel: [    0.791201] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791203] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 27 00:23:57 node-1 kernel: [    0.791214] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791216] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 27 00:23:57 node-1 kernel: [    0.791230] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791231] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 27 00:23:57 node-1 kernel: [    0.791234] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 27 00:23:57 node-1 kernel: [    0.791247] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 27 00:23:57 node-1 kernel: [    0.791269] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 27 00:23:57 node-1 kernel: [    0.791273] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 27 00:23:57 node-1 kernel: [    0.791282] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 27 00:23:57 node-1 kernel: [    0.791319] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 27 00:23:57 node-1 kernel: [    0.791321] vesafb: scrolling: redraw
Jul 27 00:23:57 node-1 kernel: [    0.791322] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 27 00:23:57 node-1 kernel: [    0.812547] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 27 00:23:57 node-1 kernel: [    0.821071] Console: switching to colour frame buffer device 80x30
Jul 27 00:23:57 node-1 kernel: [    0.829763] fb0: VESA VGA frame buffer device
Jul 27 00:23:57 node-1 kernel: [    0.829962] intel_idle: MWAIT substates: 0x2120
Jul 27 00:23:57 node-1 kernel: [    0.829963] intel_idle: v0.4 model 0x3F
Jul 27 00:23:57 node-1 kernel: [    0.829963] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 27 00:23:57 node-1 kernel: [    0.830199] ipmi message handler version 39.2
Jul 27 00:23:57 node-1 kernel: [    0.830454] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 27 00:23:57 node-1 kernel: [    0.830889] ACPI: AC Adapter [P111] (on-line)
Jul 27 00:23:57 node-1 kernel: [    0.836167] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 27 00:23:57 node-1 kernel: [    0.847273] ACPI: Power Button [PWRB]
Jul 27 00:23:57 node-1 kernel: [    0.853106] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 27 00:23:57 node-1 kernel: [    0.864837] ACPI: Power Button [PWRF]
Jul 27 00:23:57 node-1 kernel: [    0.891951] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 27 00:23:57 node-1 kernel: [    0.903825] pstore: Registered erst as persistent store backend
Jul 27 00:23:57 node-1 kernel: [    0.910114] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 27 00:23:57 node-1 kernel: [    0.922169] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 27 00:23:57 node-1 kernel: [    0.948932] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 27 00:23:57 node-1 kernel: [    0.982254] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 27 00:23:57 node-1 kernel: [    0.996354] Linux agpgart interface v0.103
Jul 27 00:23:57 node-1 kernel: [    1.003997] brd: module loaded
Jul 27 00:23:57 node-1 kernel: [    1.011181] loop: module loaded
Jul 27 00:23:57 node-1 kernel: [    1.017918] libphy: Fixed MDIO Bus: probed
Jul 27 00:23:57 node-1 kernel: [    1.024391] tun: Universal TUN/TAP device driver, 1.6
Jul 27 00:23:57 node-1 kernel: [    1.030877] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 27 00:23:57 node-1 kernel: [    1.037412] PPP generic driver version 2.4.2
Jul 27 00:23:57 node-1 kernel: [    1.043826] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 27 00:23:57 node-1 kernel: [    1.050279] ehci-pci: EHCI PCI platform driver
Jul 27 00:23:57 node-1 kernel: [    1.056812] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 27 00:23:57 node-1 kernel: [    1.063237] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 27 00:23:57 node-1 kernel: [    1.075814] ehci-pci 0000:00:1a.0: debug port 2
Jul 27 00:23:57 node-1 kernel: [    1.086116] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 27 00:23:57 node-1 kernel: [    1.086140] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 27 00:23:57 node-1 kernel: [    1.101930] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 27 00:23:57 node-1 kernel: [    1.108016] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 00:23:57 node-1 kernel: [    1.114198] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 00:23:57 node-1 kernel: [    1.126124] usb usb1: Product: EHCI Host Controller
Jul 27 00:23:57 node-1 kernel: [    1.132199] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 00:23:57 node-1 kernel: [    1.138314] usb usb1: SerialNumber: 0000:00:1a.0
Jul 27 00:23:57 node-1 kernel: [    1.144377] hub 1-0:1.0: USB hub found
Jul 27 00:23:57 node-1 kernel: [    1.150159] hub 1-0:1.0: 2 ports detected
Jul 27 00:23:57 node-1 kernel: [    1.155960] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 27 00:23:57 node-1 kernel: [    1.161574] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 27 00:23:57 node-1 kernel: [    1.172593] ehci-pci 0000:00:1d.0: debug port 2
Jul 27 00:23:57 node-1 kernel: [    1.181888] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 27 00:23:57 node-1 kernel: [    1.181891] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 27 00:23:57 node-1 kernel: [    1.197848] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 27 00:23:57 node-1 kernel: [    1.203064] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 00:23:57 node-1 kernel: [    1.208384] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 00:23:57 node-1 kernel: [    1.218965] usb usb2: Product: EHCI Host Controller
Jul 27 00:23:57 node-1 kernel: [    1.224442] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 00:23:57 node-1 kernel: [    1.229994] usb usb2: SerialNumber: 0000:00:1d.0
Jul 27 00:23:57 node-1 kernel: [    1.235534] hub 2-0:1.0: USB hub found
Jul 27 00:23:57 node-1 kernel: [    1.240889] hub 2-0:1.0: 2 ports detected
Jul 27 00:23:57 node-1 kernel: [    1.246188] ehci-platform: EHCI generic platform driver
Jul 27 00:23:57 node-1 kernel: [    1.251431] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 27 00:23:57 node-1 kernel: [    1.256805] ohci-pci: OHCI PCI platform driver
Jul 27 00:23:57 node-1 kernel: [    1.262162] ohci-platform: OHCI generic platform driver
Jul 27 00:23:57 node-1 kernel: [    1.267414] uhci_hcd: USB Universal Host Controller Interface driver
Jul 27 00:23:57 node-1 kernel: [    1.272797] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 27 00:23:57 node-1 kernel: [    1.465628] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 27 00:23:57 node-1 kernel: [    1.625819] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 27 00:23:57 node-1 kernel: [    1.631377] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 00:23:57 node-1 kernel: [    1.637088] hub 1-1:1.0: USB hub found
Jul 27 00:23:57 node-1 kernel: [    1.642555] hub 1-1:1.0: 6 ports detected
Jul 27 00:23:57 node-1 kernel: [    1.757372] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 27 00:23:57 node-1 kernel: [    1.797336] tsc: Refined TSC clocksource calibration: 3491.914 MHz
Jul 27 00:23:57 node-1 kernel: [    2.025481] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 27 00:23:57 node-1 kernel: [    2.031059] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 00:23:57 node-1 kernel: [    2.037001] hub 2-1:1.0: USB hub found
Jul 27 00:23:57 node-1 kernel: [    2.042717] hub 2-1:1.0: 8 ports detected
Jul 27 00:23:57 node-1 kernel: [    2.314589] i8042: No controller found
Jul 27 00:23:57 node-1 kernel: [    2.320010] mousedev: PS/2 mouse device common for all mice
Jul 27 00:23:57 node-1 kernel: [    2.320960] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 27 00:23:57 node-1 kernel: [    2.331101] rtc_cmos 00:02: RTC can wake from S4
Jul 27 00:23:57 node-1 kernel: [    2.336849] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 27 00:23:57 node-1 kernel: [    2.342457] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 27 00:23:57 node-1 kernel: [    2.353546] device-mapper: uevent: version 1.0.3
Jul 27 00:23:57 node-1 kernel: [    2.359168] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 27 00:23:57 node-1 kernel: [    2.370400] ledtrig-cpu: registered to indicate activity on CPUs
Jul 27 00:23:57 node-1 kernel: [    2.376323] TCP: cubic registered
Jul 27 00:23:57 node-1 kernel: [    2.382232] NET: Registered protocol family 10
Jul 27 00:23:57 node-1 kernel: [    2.388217] NET: Registered protocol family 17
Jul 27 00:23:57 node-1 kernel: [    2.393899] Key type dns_resolver registered
Jul 27 00:23:57 node-1 kernel: [    2.399894] Loading compiled-in X.509 certificates
Jul 27 00:23:57 node-1 kernel: [    2.406041] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 27 00:23:57 node-1 kernel: [    2.417420] registered taskstats version 1
Jul 27 00:23:57 node-1 kernel: [    2.425653] Key type trusted registered
Jul 27 00:23:57 node-1 kernel: [    2.433338] Key type encrypted registered
Jul 27 00:23:57 node-1 kernel: [    2.438784] AppArmor: AppArmor sha1 policy hashing enabled
Jul 27 00:23:57 node-1 kernel: [    2.444266] IMA: No TPM chip found, activating TPM-bypass!
Jul 27 00:23:57 node-1 kernel: [    2.450398] regulator-dummy: disabling
Jul 27 00:23:57 node-1 kernel: [    2.455954]   Magic number: 8:853:355
Jul 27 00:23:57 node-1 kernel: [    2.457442] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 27 00:23:57 node-1 kernel: [    2.457443] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 27 00:23:57 node-1 kernel: [    2.457444] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 27 00:23:57 node-1 kernel: [    2.457445] usb 2-1.4: Manufacturer: Avocent
Jul 27 00:23:57 node-1 kernel: [    2.457446] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 27 00:23:57 node-1 kernel: [    2.494505] machinecheck machinecheck11: hash matches
Jul 27 00:23:57 node-1 kernel: [    2.499997] input event1: hash matches
Jul 27 00:23:57 node-1 kernel: [    2.505675] rtc_cmos 00:02: setting system clock to 2016-07-27 00:23:23 UTC (1469579003)
Jul 27 00:23:57 node-1 kernel: [    2.518187] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 27 00:23:57 node-1 kernel: [    2.523793] EDD information not available.
Jul 27 00:23:57 node-1 kernel: [    2.529375] PM: Hibernation image not present or could not be loaded.
Jul 27 00:23:57 node-1 kernel: [    2.530248] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 27 00:23:57 node-1 kernel: [    2.541433] Write protecting the kernel read-only data: 12288k
Jul 27 00:23:57 node-1 kernel: [    2.547571] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 27 00:23:57 node-1 kernel: [    2.560032] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 27 00:23:57 node-1 kernel: [    2.591655] device-mapper: multipath: version 1.6.0 loaded
Jul 27 00:23:57 node-1 kernel: [    2.599623] systemd-udevd[217]: starting version 204
Jul 27 00:23:57 node-1 kernel: [    2.628112] md: linear personality registered for level -1
Jul 27 00:23:57 node-1 kernel: [    2.643366] md: multipath personality registered for level -4
Jul 27 00:23:57 node-1 kernel: [    2.651583] md: raid0 personality registered for level 0
Jul 27 00:23:57 node-1 kernel: [    2.659910] md: raid1 personality registered for level 1
Jul 27 00:23:57 node-1 kernel: [    2.666285] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 27 00:23:57 node-1 kernel: [    2.672529] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 27 00:23:57 node-1 kernel: [    2.679070] hidraw: raw HID events driver (C) Jiri Kosina
Jul 27 00:23:57 node-1 kernel: [    2.681786] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 27 00:23:57 node-1 kernel: [    2.683393] megasas: FW now in Ready state
Jul 27 00:23:57 node-1 kernel: [    2.683785] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.683951] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.684116] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.684233] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.684390] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.684484] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.684903] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.685087] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.685241] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.685398] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.685554] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.685660] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.685730] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.685887] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.686014] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.686084] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.686772] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 27 00:23:57 node-1 kernel: [    2.690671] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 27 00:23:57 node-1 kernel: [    2.690673] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 00:23:57 node-1 kernel: [    2.690674] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 00:23:57 node-1 kernel: [    2.691083] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.691215] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.691334] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.691490] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.691884] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.706582] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 27 00:23:57 node-1 kernel: [    2.706596] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 00:23:57 node-1 kernel: [    2.706618] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 00:23:57 node-1 kernel: [    2.706838] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.706961] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.707105] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.707229] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.707487] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.722153] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 27 00:23:57 node-1 kernel: [    2.722160] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 00:23:57 node-1 kernel: [    2.722176] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 00:23:57 node-1 kernel: [    2.722541] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.722656] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.722788] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.722895] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.723070] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.736665] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 27 00:23:57 node-1 kernel: [    2.736696] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 27 00:23:57 node-1 kernel: [    2.736718] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 00:23:57 node-1 kernel: [    2.737030] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.737137] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.737223] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.737328] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.737566] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 00:23:57 node-1 kernel: [    2.744627] raid6: sse2x1   11111 MB/s
Jul 27 00:23:57 node-1 kernel: [    2.812807] raid6: sse2x2   12579 MB/s
Jul 27 00:23:57 node-1 kernel: [    2.880685] raid6: sse2x4    9544 MB/s
Jul 27 00:23:57 node-1 kernel: [    2.948379] raid6: avx2x1   14461 MB/s
Jul 27 00:23:57 node-1 kernel: [    3.020318] raid6: avx2x2   18878 MB/s
Jul 27 00:23:57 node-1 kernel: [    3.092249] raid6: avx2x4   21316 MB/s
Jul 27 00:23:57 node-1 kernel: [    3.098074] raid6: using algorithm avx2x4 (21316 MB/s)
Jul 27 00:23:57 node-1 kernel: [    3.104052] raid6: using avx2x2 recovery algorithm
Jul 27 00:23:57 node-1 kernel: [    3.109910] Switched to clocksource tsc
Jul 27 00:23:57 node-1 kernel: [    3.109911] megasas:IOC Init cmd success
Jul 27 00:23:57 node-1 kernel: [    3.121886] xor: automatically using best checksumming function:
Jul 27 00:23:57 node-1 kernel: [    3.130132] usbcore: registered new interface driver usbhid
Jul 27 00:23:57 node-1 kernel: [    3.132716] megasas: INIT adapter done
Jul 27 00:23:57 node-1 kernel: [    3.141041] usbhid: USB HID core driver
Jul 27 00:23:57 node-1 kernel: [    3.147676] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 27 00:23:57 node-1 kernel: [    3.158781] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 27 00:23:57 node-1 kernel: [    3.169846]    avx       : 72542.000 MB/sec
Jul 27 00:23:57 node-1 kernel: [    3.170455] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 27 00:23:57 node-1 kernel: [    3.171328] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 27 00:23:57 node-1 kernel: [    3.172310] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 27 00:23:57 node-1 kernel: [    3.172828] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 27 00:23:57 node-1 kernel: [    3.204139] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 27 00:23:57 node-1 kernel: [    3.204463] scsi0 : LSI SAS based MegaRAID driver
Jul 27 00:23:57 node-1 kernel: [    3.211510] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 00:23:57 node-1 kernel: [    3.222485] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 00:23:57 node-1 kernel: [    3.226673] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 27 00:23:57 node-1 kernel: [    3.226985] sd 0:2:0:0: [sda] Write Protect is off
Jul 27 00:23:57 node-1 kernel: [    3.226986] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 27 00:23:57 node-1 kernel: [    3.227050] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 27 00:23:57 node-1 kernel: [    3.227231] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 27 00:23:57 node-1 kernel: [    3.257793]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 27 00:23:57 node-1 kernel: [    3.259279] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 27 00:23:57 node-1 kernel: [    3.314875] async_tx: api initialized (async)
Jul 27 00:23:57 node-1 kernel: [    3.325789] md: raid6 personality registered for level 6
Jul 27 00:23:57 node-1 kernel: [    3.333032] md: raid5 personality registered for level 5
Jul 27 00:23:57 node-1 kernel: [    3.340072] md: raid4 personality registered for level 4
Jul 27 00:23:57 node-1 kernel: [    3.349851] md: raid10 personality registered for level 10
Jul 27 00:23:57 node-1 kernel: [    3.403930] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Jul 27 00:23:57 node-1 kernel: [    3.443130] random: lvm urandom read with 31 bits of entropy available
Jul 27 00:23:57 node-1 kernel: [    3.638600] bio: create slab <bio-1> at 1
Jul 27 00:23:57 node-1 kernel: [    4.440839] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 00:23:57 node-1 kernel: [    4.976169] init: plymouth-upstart-bridge main process (550) terminated with status 1
Jul 27 00:23:57 node-1 kernel: [    4.988335] init: plymouth-upstart-bridge main process ended, respawning
Jul 27 00:23:57 node-1 kernel: [    5.063561] random: nonblocking pool is initialized
Jul 27 00:23:57 node-1 kernel: [    5.134399] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 27 00:23:57 node-1 kernel: [    5.167819] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 27 00:23:57 node-1 kernel: [    5.293369] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 27 00:23:57 node-1 kernel: [    5.323314] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 27 00:23:57 node-1 kernel: [    5.404601] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 00:23:57 node-1 kernel: [    5.624373] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 27 00:23:57 node-1 kernel: [    5.677087] XFS (dm-0): Mounting Filesystem
Jul 27 00:23:57 node-1 kernel: [    5.822086] XFS (dm-0): Ending clean mount
Jul 27 00:23:57 node-1 kernel: [    5.895663] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 00:23:57 node-1 kernel: [    5.946363] XFS (dm-1): Mounting Filesystem
Jul 27 00:23:57 node-1 kernel: [    6.051374] XFS (dm-1): Ending clean mount
Jul 27 00:23:57 node-1 kernel: [    7.858234] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 00:23:57 node-1 kernel: [    7.881069] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 00:23:57 node-1 kernel: [    8.043199] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 27 00:23:57 node-1 kernel: [    8.043205] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 27 00:23:57 node-1 kernel: [    8.043208] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 27 00:23:57 node-1 kernel: [    8.043212] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 27 00:23:57 node-1 kernel: [    8.076779] systemd-udevd[774]: starting version 204
Jul 27 00:23:57 node-1 kernel: [    8.330542] power_meter ACPI000D:00: Found ACPI power meter.
Jul 27 00:23:57 node-1 kernel: [    8.330600] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 27 00:23:57 node-1 kernel: [    8.352823] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 27 00:23:57 node-1 kernel: [    8.352828] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 00:23:57 node-1 kernel: [    8.352831] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 27 00:23:57 node-1 kernel: [    8.352832] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 00:23:57 node-1 kernel: [    8.352910] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 27 00:23:57 node-1 kernel: [    8.358993] wmi: Mapper loaded
Jul 27 00:23:57 node-1 kernel: [    8.366933] IPMI System Interface driver.
Jul 27 00:23:57 node-1 kernel: [    8.366966] ipmi_si: probing via ACPI
Jul 27 00:23:57 node-1 kernel: [    8.366981] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 27 00:23:57 node-1 kernel: [    8.366982] ipmi_si: Adding ACPI-specified kcs state machine
Jul 27 00:23:57 node-1 kernel: [    8.366988] ipmi_si: probing via SMBIOS
Jul 27 00:23:57 node-1 kernel: [    8.366989] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 00:23:57 node-1 kernel: [    8.366990] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 27 00:23:57 node-1 kernel: [    8.366991] ipmi_si: probing via SPMI
Jul 27 00:23:57 node-1 kernel: [    8.366992] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 00:23:57 node-1 kernel: [    8.366993] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 27 00:23:57 node-1 kernel: [    8.366994] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 27 00:23:57 node-1 kernel: [    8.376366] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 27 00:23:57 node-1 kernel: [    8.448184] systemd-udevd[793]: renamed network interface eth0 to enp6s0
Jul 27 00:23:57 node-1 kernel: [    8.472082] systemd-udevd[795]: renamed network interface eth3 to enp9s0
Jul 27 00:23:57 node-1 kernel: [    8.496049] systemd-udevd[803]: renamed network interface eth1 to enp7s0
Jul 27 00:23:57 node-1 kernel: [    8.501440] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 27 00:23:57 node-1 kernel: [    8.501444] ipmi_si 00:09: IPMI kcs interface initialized
Jul 27 00:23:57 node-1 kernel: [    8.528028] systemd-udevd[791]: renamed network interface eth2 to enp8s0
Jul 27 00:23:57 node-1 kernel: [    8.893163] type=1400 audit(1469579009.890:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.893315] type=1400 audit(1469579009.890:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.893442] type=1400 audit(1469579009.890:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.893955] type=1400 audit(1469579009.890:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.894115] type=1400 audit(1469579009.890:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.894234] type=1400 audit(1469579009.890:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.908705] type=1400 audit(1469579009.906:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.908924] type=1400 audit(1469579009.906:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1064 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.909118] type=1400 audit(1469579009.906:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1064 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    8.918666] type=1400 audit(1469579009.914:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Jul 27 00:23:57 node-1 kernel: [    9.518676] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 00:23:57 node-1 kernel: [    9.520947] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 00:23:57 node-1 kernel: [    9.695589] enic 0000:06:00.0 enp6s0: Link UP
Jul 27 00:23:57 node-1 kernel: [    9.696001] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 27 00:23:57 node-1 kernel: [    9.696010] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 27 00:23:57 node-1 kernel: [   19.071062] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 27 00:23:57 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 27 00:23:59 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 27 00:23:59 node-1 kernel: [   37.595273] init: failsafe main process (8394) killed by TERM signal
Jul 27 00:23:59 node-1 dbus[8427]: [system] AppArmor D-Bus mediation is enabled
Jul 27 00:23:59 node-1 kernel: [   37.836587] audit_printk_skb: 30 callbacks suppressed
Jul 27 00:23:59 node-1 kernel: [   37.836589] type=1400 audit(1469579039.282:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8517 comm="apparmor_parser"
Jul 27 00:23:59 node-1 kernel: [   37.836593] type=1400 audit(1469579039.282:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8517 comm="apparmor_parser"
Jul 27 00:23:59 node-1 kernel: [   37.836595] type=1400 audit(1469579039.282:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8517 comm="apparmor_parser"
Jul 27 00:23:59 node-1 kernel: [   37.836850] type=1400 audit(1469579039.282:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8518 comm="apparmor_parser"
Jul 27 00:23:59 node-1 kernel: [   37.836909] type=1400 audit(1469579039.282:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8517 comm="apparmor_parser"
Jul 27 00:23:59 node-1 kernel: [   37.836913] type=1400 audit(1469579039.282:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8517 comm="apparmor_parser"
Jul 27 00:23:59 node-1 kernel: [   37.837094] type=1400 audit(1469579039.282:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8517 comm="apparmor_parser"
Jul 27 00:23:59 node-1 kernel: [   37.896248] type=1400 audit(1469579039.342:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8520 comm="apparmor_parser"
Jul 27 00:23:59 node-1 anacron[8586]: Anacron 2.3 started on 2016-07-27
Jul 27 00:23:59 node-1 cron[8550]: (CRON) INFO (pidfile fd = 3)
Jul 27 00:23:59 node-1 anacron[8586]: Will run job `cron.daily' in 5 min.
Jul 27 00:23:59 node-1 anacron[8586]: Will run job `cron.weekly' in 10 min.
Jul 27 00:23:59 node-1 anacron[8586]: Will run job `cron.monthly' in 15 min.
Jul 27 00:23:59 node-1 anacron[8586]: Jobs will be executed sequentially
Jul 27 00:23:59 node-1 cron[8594]: (CRON) STARTUP (fork ok)
Jul 27 00:23:59 node-1 multipathd: path checkers start up
Jul 27 00:23:59 node-1 cron[8594]: (CRON) INFO (Running @reboot jobs)
Jul 27 00:23:59 node-1 postfix/master[8730]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 27 00:24:01 node-1 CRON[8867]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 27 00:24:01 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 00:24:01 node-1 nailgun-agent: D, [2016-07-27T00:24:01.711744 #8870] DEBUG -- : Sleep for 0 seconds before sending request
Jul 27 00:24:01 node-1 nailgun-agent: I, [2016-07-27T00:24:01.753097 #8870]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 00:24:02 node-1 nailgun-agent: D, [2016-07-27T00:24:02.906461 #8870] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 27 00:24:03 node-1 puppet-agent[9057]: Reopening log files
Jul 27 00:24:04 node-1 puppet-agent[9057]: Could not request certificate: Connection refused - connect(2)
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.895109 #8870] DEBUG -- : Trying to find block devices
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.895198 #8870] DEBUG -- : Found block device: sda
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.895268 #8870] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.895287 #8870] DEBUG -- : Trying to get list of physical devices
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.895443 #8870] DEBUG -- : Getting udev properties for device: sda
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.897244 #8870] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Jul 27 00:24:14 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11176", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.897272 #8870] DEBUG -- : Trying to find out if device sda is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.897350 #8870] DEBUG -- : Device sda removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.897367 #8870] DEBUG -- : Device sda seems to be appropriate
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.897723 #8870] DEBUG -- : Getting udev properties for device: dm-0
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.899409 #8870] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-HejMMy4d2fwwcO19j9LgVx0b4MFLOCMYoUvuLXiRp8m1QVgP4mkMzpCBgG4u0Z3E /dev/disk/by-uuid/101d2b8d-5118-4e77-9719-57201f750aea /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-HejMMy4d2fwwcO19j9LgVx0b4MFLOCMYoUvuLXiRp8m1QVgP4mkMzpCBgG4u0Z3E", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"101d2b8d-5118-4e77-9719-57201f750aea", "ID_FS_UUID_ENC"=>"101d2b8d-5118-4e77-9719-57201f750aea", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90538", "nomdmonddf"=>"1", "nomd
Jul 27 00:24:14 node-1 nailgun-agent: monisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.899439 #8870] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.899495 #8870] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.899508 #8870] DEBUG -- : Device dm-0 seems to be appropriate
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.899520 #8870] DEBUG -- : Getting udev properties for device: dm-1
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.901067 #8870] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-eDXpCkVOOgE6JEL6ki8qYdlxLoE4p6508IV3CrXlj5ImUa1ONStevowSkZEcrGju /dev/disk/by-uuid/0d5c7ac5-4eb6-4c9e-be4d-90675bf2fda5 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-eDXpCkVOOgE6JEL6ki8qYdlxLoE4p6508IV3CrXlj5ImUa1ONStevowSkZEcrGju", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0d5c7ac5-4eb6-4c9e-be4d-90675bf2fda5", "ID_FS_UUID_ENC"=>"0d5c7ac5-4eb6-4c9e-be4d-90675bf2fda5", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51
Jul 27 00:24:14 node-1 nailgun-agent: 779", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.901093 #8870] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.901168 #8870] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.901182 #8870] DEBUG -- : Device dm-1 seems to be appropriate
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.901195 #8870] DEBUG -- : Getting udev properties for device: dm-2
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.902749 #8870] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-elgaQQDwJtw2JeZWIBmzUmWTRlIxAio4BxaPfDE3avO2LSsBEH3QgdR4POmaVhLX /dev/disk/by-uuid/55c8996a-5285-48d3-a8a8-802d0d68accf /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-elgaQQDwJtw2JeZWIBmzUmWTRlIxAio4BxaPfDE3avO2LSsBEH3QgdR4POmaVhLX", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"55c8996a-5285-48d3-a8a8-802d0d68accf", "ID_FS_UUID_ENC"=>"55c8996a-5285-48d3-a8a8-802d0d68accf", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58866", "nomdmond
Jul 27 00:24:14 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.902774 #8870] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.902836 #8870] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.902849 #8870] DEBUG -- : Device dm-2 seems to be appropriate
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.902862 #8870] DEBUG -- : Getting udev properties for device: dm-3
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.904390 #8870] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-FdlSELqBthaaSjEr6oR9V54dQ9Y6zO41T2NgQ8O4PhaiJDIQ2RE2bTsMsz1jX0YD /dev/disk/by-uuid/0d36f901-6d82-4d47-9299-40d3d1b766ea /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-FdlSELqBthaaSjEr6oR9V54dQ9Y6zO41T2NgQ8O4PhaiJDIQ2RE2bTsMsz1jX0YD", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0d36f901-6d82-4d47-9299-40d3d1b766ea", "ID_FS_UUID_ENC"=>"0d36f901-6d82-4d47-9299-40d3d1b766ea", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"68305", "nomdmonddf"=>"1", 
Jul 27 00:24:14 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.904447 #8870] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.904487 #8870] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.904500 #8870] DEBUG -- : Device dm-3 seems to be appropriate
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.904513 #8870] DEBUG -- : Getting udev properties for device: dm-4
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.906017 #8870] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-5GoweJugW2lPQuiKlfU78LQNS1PI1tspHlr71qeXjmF3tYJgfhk1ISTZnewmYjF1 /dev/disk/by-uuid/621e68c3-1f19-4ce9-9701-f780c68c437d /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-5GoweJugW2lPQuiKlfU78LQNS1PI1tspHlr71qeXjmF3tYJgfhk1ISTZnewmYjF1", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"621e68c3-1f19-4ce9-9701-f780c68c437d", "ID_FS_UUID_ENC"=>"621e68c3-1f19-4ce9-9701-f780c68c437d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"74735", "nomdmonddf"=>"1", "nomd
Jul 27 00:24:14 node-1 nailgun-agent: monisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.906043 #8870] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.906073 #8870] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.906108 #8870] DEBUG -- : Device dm-4 seems to be appropriate
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.906121 #8870] DEBUG -- : Getting udev properties for device: dm-5
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.907647 #8870] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-5GoweJugW2lPQuiKlfU78LQNS1PI1tspyXUSI3piFfDWdedY8jjuG1N4pOIFMym6 /dev/disk/by-uuid/2cfa7bad-9308-4f1b-b2cb-c1909fdef4b1 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-5GoweJugW2lPQuiKlfU78LQNS1PI1tspyXUSI3piFfDWdedY8jjuG1N4pOIFMym6", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"2cfa7bad-9308-4f1b-b2cb-c1909fdef4b1", "ID_FS_UUID_ENC"=>"2cfa7bad-9308-4f1b-b2cb-c1909fdef4b1", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75110", "nomdmonddf"=>"1", "nomdmonisw"
Jul 27 00:24:14 node-1 nailgun-agent: =>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.907674 #8870] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.907718 #8870] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.907731 #8870] DEBUG -- : Device dm-5 seems to be appropriate
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.907745 #8870] DEBUG -- : Getting udev properties for device: ram0
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.909175 #8870] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80032", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.909204 #8870] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.909241 #8870] DEBUG -- : Device ram0 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.909282 #8870] DEBUG -- : Getting udev properties for device: ram1
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.910624 #8870] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80043", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.910649 #8870] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.910680 #8870] DEBUG -- : Device ram1 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.910699 #8870] DEBUG -- : Getting udev properties for device: ram2
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.912073 #8870] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80211", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.912100 #8870] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.912167 #8870] DEBUG -- : Device ram2 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.912184 #8870] DEBUG -- : Getting udev properties for device: ram3
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.913529 #8870] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80229", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.913570 #8870] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.913607 #8870] DEBUG -- : Device ram3 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.913624 #8870] DEBUG -- : Getting udev properties for device: ram4
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.914986 #8870] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80251", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.915006 #8870] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.915041 #8870] DEBUG -- : Device ram4 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.915057 #8870] DEBUG -- : Getting udev properties for device: ram5
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.916446 #8870] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80268", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.916466 #8870] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.916498 #8870] DEBUG -- : Device ram5 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.916516 #8870] DEBUG -- : Getting udev properties for device: ram6
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.917893 #8870] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80284", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.917913 #8870] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.917949 #8870] DEBUG -- : Device ram6 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.917985 #8870] DEBUG -- : Getting udev properties for device: ram7
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.919328 #8870] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80302", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.919348 #8870] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.919376 #8870] DEBUG -- : Device ram7 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.919403 #8870] DEBUG -- : Getting udev properties for device: ram8
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.920765 #8870] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80318", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.920785 #8870] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.920822 #8870] DEBUG -- : Device ram8 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.920852 #8870] DEBUG -- : Getting udev properties for device: ram9
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.922234 #8870] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80332", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.922254 #8870] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.922286 #8870] DEBUG -- : Device ram9 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.922303 #8870] DEBUG -- : Getting udev properties for device: loop0
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.923670 #8870] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79951", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.923690 #8870] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.923732 #8870] DEBUG -- : Device loop0 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.923750 #8870] DEBUG -- : Getting udev properties for device: loop1
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.925085 #8870] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79962", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.925105 #8870] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.925152 #8870] DEBUG -- : Device loop1 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.925169 #8870] DEBUG -- : Getting udev properties for device: loop2
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.926520 #8870] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79970", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.926539 #8870] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.926568 #8870] DEBUG -- : Device loop2 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.926585 #8870] DEBUG -- : Getting udev properties for device: loop3
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.927931 #8870] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79978", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.927951 #8870] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.927992 #8870] DEBUG -- : Device loop3 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.928009 #8870] DEBUG -- : Getting udev properties for device: loop4
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.929339 #8870] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79989", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.929360 #8870] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.929417 #8870] DEBUG -- : Device loop4 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.929433 #8870] DEBUG -- : Getting udev properties for device: loop5
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.930776 #8870] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79996", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.930796 #8870] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.930833 #8870] DEBUG -- : Device loop5 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.930856 #8870] DEBUG -- : Getting udev properties for device: loop6
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.932200 #8870] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80017", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.932220 #8870] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.932257 #8870] DEBUG -- : Device loop6 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.932279 #8870] DEBUG -- : Getting udev properties for device: loop7
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.933652 #8870] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80025", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.933671 #8870] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.933726 #8870] DEBUG -- : Device loop7 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.933742 #8870] DEBUG -- : Getting udev properties for device: ram10
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.935110 #8870] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80057", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.935138 #8870] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.935177 #8870] DEBUG -- : Device ram10 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.935194 #8870] DEBUG -- : Getting udev properties for device: ram11
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.936537 #8870] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80070", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.936556 #8870] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.936584 #8870] DEBUG -- : Device ram11 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.936614 #8870] DEBUG -- : Getting udev properties for device: ram12
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.937970 #8870] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80082", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.937994 #8870] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.938026 #8870] DEBUG -- : Device ram12 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.938043 #8870] DEBUG -- : Getting udev properties for device: ram13
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.939381 #8870] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80163", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.939413 #8870] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.939442 #8870] DEBUG -- : Device ram13 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.939481 #8870] DEBUG -- : Getting udev properties for device: ram14
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.940850 #8870] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80178", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.940872 #8870] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.940899 #8870] DEBUG -- : Device ram14 removable parameter: "0"
Jul 27 00:24:14 node-1 nailgun-agent: D, [2016-07-27T00:24:14.940950 #8870] DEBUG -- : Getting udev properties for device: ram15
Jul 27 00:24:14 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942314 #8870] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80194", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942334 #8870] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942386 #8870] DEBUG -- : Device ram15 removable parameter: "0"
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942422 #8870] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942451 #8870] DEBUG -- : Block device seems to be physical data storage: sda
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942508 #8870] DEBUG -- : Found block device: dm-0
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942542 #8870] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942557 #8870] DEBUG -- : Found block device: dm-1
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942568 #8870] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942601 #8870] DEBUG -- : Found block device: dm-2
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942612 #8870] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942620 #8870] DEBUG -- : Found block device: dm-3
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942630 #8870] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942653 #8870] DEBUG -- : Found block device: dm-4
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942665 #8870] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942692 #8870] DEBUG -- : Found block device: dm-5
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942703 #8870] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942726 #8870] DEBUG -- : Found block device: ram0
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942747 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942764 #8870] DEBUG -- : Found block device: ram1
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942794 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942816 #8870] DEBUG -- : Found block device: ram2
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942827 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.942846 #8870] DEBUG -- : Found block device: ram3
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948787 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948809 #8870] DEBUG -- : Found block device: ram4
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948821 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948830 #8870] DEBUG -- : Found block device: ram5
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948840 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948848 #8870] DEBUG -- : Found block device: ram6
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948857 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948865 #8870] DEBUG -- : Found block device: ram7
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948873 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948920 #8870] DEBUG -- : Found block device: ram8
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948932 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948940 #8870] DEBUG -- : Found block device: ram9
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948950 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948958 #8870] DEBUG -- : Found block device: loop0
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948968 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948976 #8870] DEBUG -- : Found block device: loop1
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948987 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.948994 #8870] DEBUG -- : Found block device: loop2
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949004 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949054 #8870] DEBUG -- : Found block device: loop3
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949064 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949072 #8870] DEBUG -- : Found block device: loop4
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949081 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949088 #8870] DEBUG -- : Found block device: loop5
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949098 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949106 #8870] DEBUG -- : Found block device: loop6
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949117 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949125 #8870] DEBUG -- : Found block device: loop7
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949174 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949182 #8870] DEBUG -- : Found block device: ram10
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949192 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949200 #8870] DEBUG -- : Found block device: ram11
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949209 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949217 #8870] DEBUG -- : Found block device: ram12
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949226 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949233 #8870] DEBUG -- : Found block device: ram13
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949242 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949282 #8870] DEBUG -- : Found block device: ram14
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949292 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949301 #8870] DEBUG -- : Found block device: ram15
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949311 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:14.949342 #8870] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:15.038952 #8870] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 27 00:24:15 node-1 nailgun-agent: D, [2016-07-27T00:24:15.039001 #8870] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 27 00:24:18 node-1 puppet-user[9445]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 27 00:24:18 node-1 puppet-user[9445]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 27 00:24:19 node-1 puppet-user[9445]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 27 00:24:19 node-1 puppet-user[9445]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 27 00:24:19 node-1 puppet-user[9445]: Finished catalog run in 1.01 seconds
Jul 27 00:24:21 node-1 multipathd: uevent trigger error
Jul 27 00:24:21 node-1 puppet-user[10050]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 00:24:21 node-1 puppet-user[10050]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 27 00:24:21 node-1 puppet-user[10050]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 27 00:24:21 node-1 puppet-user[10050]: Finished catalog run in 0.05 seconds
Jul 27 00:24:22 node-1 puppet-user[10525]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 27 00:24:23 node-1 puppet-user[10525]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Jul 27 00:24:23 node-1 puppet-user[10525]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 27 00:24:23 node-1 puppet-user[10525]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 27 00:24:23 node-1 puppet-user[10525]: Finished catalog run in 0.03 seconds
Jul 27 00:24:24 node-1 puppet-user[10992]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 27 00:24:24 node-1 puppet-user[10992]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 27 00:24:25 node-1 puppet-user[10992]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 27 00:24:25 node-1 puppet-user[10992]: Finished catalog run in 0.04 seconds
Jul 27 00:24:26 node-1 puppet-user[11457]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 27 00:24:26 node-1 puppet-user[11457]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Jul 27 00:24:26 node-1 puppet-user[11457]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 27 00:24:27 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 00:24:27 node-1 puppet-user[11457]: (/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 27 00:24:27 node-1 puppet-user[11457]: Finished catalog run in 0.43 seconds
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004023 #8870] DEBUG -- : Trying to find block devices
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004086 #8870] DEBUG -- : Found block device: sda
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004134 #8870] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004151 #8870] DEBUG -- : Block device seems to be physical data storage: sda
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004172 #8870] DEBUG -- : Found block device: dm-0
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004184 #8870] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004195 #8870] DEBUG -- : Found block device: dm-1
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004205 #8870] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004214 #8870] DEBUG -- : Found block device: dm-2
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004223 #8870] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004248 #8870] DEBUG -- : Found block device: dm-3
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004258 #8870] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004265 #8870] DEBUG -- : Found block device: dm-4
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004286 #8870] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004309 #8870] DEBUG -- : Found block device: dm-5
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004318 #8870] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004326 #8870] DEBUG -- : Found block device: ram0
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004336 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004357 #8870] DEBUG -- : Found block device: ram1
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004367 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004375 #8870] DEBUG -- : Found block device: ram2
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004397 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004406 #8870] DEBUG -- : Found block device: ram3
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004415 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004422 #8870] DEBUG -- : Found block device: ram4
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004445 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004453 #8870] DEBUG -- : Found block device: ram5
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004462 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004470 #8870] DEBUG -- : Found block device: ram6
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004478 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004513 #8870] DEBUG -- : Found block device: ram7
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004523 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004531 #8870] DEBUG -- : Found block device: ram8
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004540 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004562 #8870] DEBUG -- : Found block device: ram9
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004572 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004580 #8870] DEBUG -- : Found block device: loop0
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004589 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004625 #8870] DEBUG -- : Found block device: loop1
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004635 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004643 #8870] DEBUG -- : Found block device: loop2
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004651 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004659 #8870] DEBUG -- : Found block device: loop3
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004668 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004676 #8870] DEBUG -- : Found block device: loop4
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004686 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004693 #8870] DEBUG -- : Found block device: loop5
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004703 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004711 #8870] DEBUG -- : Found block device: loop6
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004747 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004756 #8870] DEBUG -- : Found block device: loop7
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004765 #8870] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004773 #8870] DEBUG -- : Found block device: ram10
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004782 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004791 #8870] DEBUG -- : Found block device: ram11
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004800 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004808 #8870] DEBUG -- : Found block device: ram12
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004828 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004856 #8870] DEBUG -- : Found block device: ram13
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004865 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004873 #8870] DEBUG -- : Found block device: ram14
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004882 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004889 #8870] DEBUG -- : Found block device: ram15
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004898 #8870] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.004925 #8870] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 27 00:24:27 node-1 nailgun-agent: D, [2016-07-27T00:24:27.230680 #8870] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 27 00:24:27 node-1 nailgun-agent: I, [2016-07-27T00:24:27.234229 #8870]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 27 00:24:28 node-1 puppet-user[12064]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 27 00:24:28 node-1 puppet-user[12064]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Jul 27 00:24:28 node-1 puppet-user[12064]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 27 00:24:28 node-1 puppet-user[12064]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 27 00:24:28 node-1 puppet-user[12064]: (/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 27 00:24:28 node-1 puppet-user[12064]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 27 00:24:28 node-1 puppet-user[12064]: Finished catalog run in 0.22 seconds
Jul 27 00:24:30 node-1 puppet-user[12541]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 27 00:24:30 node-1 puppet-user[12541]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Jul 27 00:24:30 node-1 puppet-user[12541]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 27 00:24:30 node-1 kernel: [   69.190729] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 27 00:24:30 node-1 kernel: [   69.190783] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 27 00:24:30 node-1 puppet-user[12541]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 27 00:24:30 node-1 puppet-user[12541]: Finished catalog run in 0.05 seconds
Jul 27 00:24:30 node-1 kernel: [   69.252660] init: plymouth-upstart-bridge main process ended, respawning
Jul 27 00:24:30 node-1 puppet-agent[9057]: Could not run: SIGTERM
Jul 27 00:24:31 node-1 kernel: [   69.526389] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 27 00:24:31 node-1 ec2: 
Jul 27 00:24:31 node-1 ec2: #############################################################
Jul 27 00:24:31 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 27 00:24:31 node-1 ec2: 1024 26:0b:59:01:88:c2:fe:8f:a5:c9:76:cd:d0:6c:a6:0b  root@node-1.domain.tld (DSA)
Jul 27 00:24:31 node-1 ec2: 256 e8:cd:60:3c:96:5d:31:73:92:fa:07:a3:8f:7b:3b:c9  root@node-1.domain.tld (ECDSA)
Jul 27 00:24:31 node-1 ec2: 256 dc:e1:1b:55:1e:d5:fd:d8:9a:d6:af:f6:b7:44:95:1e  root@node-1.domain.tld (ED25519)
Jul 27 00:24:31 node-1 ec2: 2048 99:6a:6b:37:d7:4b:b5:4f:1f:98:84:f0:b8:bd:65:94  root@node-1.domain.tld (RSA)
Jul 27 00:24:31 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 27 00:24:31 node-1 ec2: #############################################################
Jul 27 00:24:32 node-1 puppet-user[13175]: (Scope(Class[main])) MODULAR: sync_time
Jul 27 00:24:32 node-1 puppet-user[13175]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 27 00:24:32 node-1 ntpdate[13612]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 27 00:24:38 node-1 ntpdate[13612]: adjust time server 10.20.0.2 offset 0.000349 sec
Jul 27 00:24:38 node-1 puppet-user[13175]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 27 00:24:38 node-1 puppet-user[13175]: Finished catalog run in 6.17 seconds
Jul 27 00:24:43 node-1 puppet-user[13809]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 00:24:43 node-1 puppet-user[13809]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 27 00:24:43 node-1 puppet-user[13809]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 27 00:24:43 node-1 puppet-user[13809]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 27 00:24:43 node-1 puppet-user[13809]: Finished catalog run in 0.07 seconds
Jul 27 00:24:44 node-1 puppet-user[14271]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 27 00:24:45 node-1 puppet-user[14271]: Compiled catalog for node-1.domain.tld in environment production in 0.91 seconds
Jul 27 00:24:45 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 27 00:24:45 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 27 00:24:46 node-1 puppet-user[14271]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 27 00:25:00 node-1 puppet-user[14271]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 27 00:25:00 node-1 puppet-user[14271]: Finished catalog run in 14.64 seconds
Jul 27 00:25:01 node-1 CRON[15269]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 27 00:25:02 node-1 puppet-user[15263]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 27 00:25:02 node-1 puppet-user[15263]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Jul 27 00:25:07 node-1 puppet-user[15263]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 27 00:25:27 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 00:25:27 node-1 nailgun-agent: I, [2016-07-27T00:25:27.409846 #15272]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 00:25:37 node-1 puppet-user[15263]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 27 00:25:37 node-1 puppet-user[15263]: Finished catalog run in 35.10 seconds
Jul 27 00:25:39 node-1 puppet-user[17877]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 27 00:25:40 node-1 puppet-user[17877]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Jul 27 00:25:40 node-1 puppet-user[17877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 27 00:25:40 node-1 puppet-user[17877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 27 00:25:40 node-1 puppet-user[17877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 27 00:25:40 node-1 puppet-user[17877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 27 00:25:40 node-1 puppet-user[17877]: Finished catalog run in 0.08 seconds
Jul 27 00:25:40 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 00:25:40 node-1 nailgun-agent: I, [2016-07-27T00:25:40.837292 #15272]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 27 00:25:42 node-1 puppet-user[18493]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 27 00:25:42 node-1 puppet-user[18493]: Compiled catalog for node-1.domain.tld in environment production in 0.86 seconds
Jul 27 00:25:43 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 27 00:25:43 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 27 00:25:43 node-1 crontab[18942]: (root) LIST (root)
Jul 27 00:25:43 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 27 00:25:43 node-1 crontab[18943]: (root) REPLACE (root)
Jul 27 00:25:45 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 27 00:25:46 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 27 00:25:47 node-1 puppet-user[18493]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 27 00:25:47 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8367" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 00:25:47 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 27 00:25:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:25:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:25:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:25:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:25:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:07 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:26:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:13 node-1 ntpdate[30392]: no servers can be used, exiting
<27>Jul 27 00:27:13 node-1 ntpdate[30608]: no servers can be used, exiting
<27>Jul 27 00:27:13 node-1 ntpdate[30811]: no servers can be used, exiting
<27>Jul 27 00:27:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 00:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 27 00:28:05 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 00:29:16 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 00:29:22 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 00:29:22 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 00:29:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 00:29:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 00:29:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 00:29:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:59 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:59 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:59 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:59 node-1 multipathd: uevent trigger error
<27>Jul 27 00:29:59 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:01 node-1 haproxy[19840]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:01 node-1 haproxy[19840]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:02 node-1 haproxy[19844]: 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 27 00:30:02 node-1 haproxy[19844]: proxy mysqld has no server available!
<27>Jul 27 00:30:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:05 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:05 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:08 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:10 node-1 haproxy[22621]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:11 node-1 haproxy[22625]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:11 node-1 haproxy[22625]: 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 27 00:30:11 node-1 haproxy[22625]: proxy mysqld has no server available!
<129>Jul 27 00:30:11 node-1 haproxy[22625]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:11 node-1 haproxy[22625]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:12 node-1 haproxy[22625]: 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 27 00:30:12 node-1 haproxy[22625]: proxy object-storage has no server available!
<27>Jul 27 00:30:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:13 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:16 node-1 haproxy[24035]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:16 node-1 haproxy[24035]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:16 node-1 haproxy[24035]: 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 27 00:30:16 node-1 haproxy[24035]: proxy neutron has no server available!
<129>Jul 27 00:30:16 node-1 haproxy[24035]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:16 node-1 haproxy[24035]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:16 node-1 haproxy[24035]: 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 27 00:30:16 node-1 haproxy[24035]: proxy mysqld has no server available!
<129>Jul 27 00:30:17 node-1 haproxy[24044]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:17 node-1 haproxy[24044]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:17 node-1 haproxy[24044]: 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 27 00:30:17 node-1 haproxy[24044]: proxy object-storage has no server available!
<27>Jul 27 00:30:18 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:18 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:18 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:18 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:18 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:19 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:21 node-1 haproxy[25655]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:21 node-1 haproxy[25655]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:21 node-1 haproxy[25655]: 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 27 00:30:21 node-1 haproxy[25655]: proxy keystone-1 has no server available!
<129>Jul 27 00:30:21 node-1 haproxy[25655]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:22 node-1 haproxy[25659]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:22 node-1 haproxy[25659]: 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 27 00:30:22 node-1 haproxy[25659]: proxy keystone-2 has no server available!
<129>Jul 27 00:30:22 node-1 haproxy[25659]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:22 node-1 haproxy[25659]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:22 node-1 haproxy[25659]: 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 27 00:30:22 node-1 haproxy[25659]: proxy neutron has no server available!
<129>Jul 27 00:30:22 node-1 haproxy[25659]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:22 node-1 haproxy[25659]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:22 node-1 haproxy[25659]: 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 27 00:30:22 node-1 haproxy[25659]: proxy mysqld has no server available!
<129>Jul 27 00:30:22 node-1 haproxy[25659]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:23 node-1 haproxy[25659]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:23 node-1 haproxy[25659]: 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 27 00:30:23 node-1 haproxy[25659]: proxy object-storage has no server available!
<27>Jul 27 00:30:24 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:24 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:24 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:24 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:24 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:26 node-1 haproxy[27067]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:27 node-1 haproxy[27071]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:27 node-1 haproxy[27071]: 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 27 00:30:27 node-1 haproxy[27071]: proxy keystone-1 has no server available!
<129>Jul 27 00:30:27 node-1 haproxy[27071]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:27 node-1 haproxy[27071]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:27 node-1 haproxy[27071]: 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 27 00:30:27 node-1 haproxy[27071]: proxy keystone-2 has no server available!
<129>Jul 27 00:30:27 node-1 haproxy[27071]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:27 node-1 haproxy[27071]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:27 node-1 haproxy[27071]: 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 27 00:30:27 node-1 haproxy[27071]: proxy neutron has no server available!
<129>Jul 27 00:30:27 node-1 haproxy[27071]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:27 node-1 haproxy[27071]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:28 node-1 haproxy[27071]: 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 27 00:30:28 node-1 haproxy[27071]: proxy mysqld has no server available!
<129>Jul 27 00:30:28 node-1 haproxy[27071]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:28 node-1 haproxy[27071]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:28 node-1 haproxy[27071]: 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 27 00:30:28 node-1 haproxy[27071]: proxy object-storage has no server available!
<129>Jul 27 00:30:28 node-1 haproxy[27071]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:28 node-1 haproxy[27071]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:28 node-1 haproxy[27071]: 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 27 00:30:28 node-1 haproxy[27071]: proxy aodh has no server available!
<27>Jul 27 00:30:30 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:30 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:30 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:30 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:30 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:30 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:32 node-1 haproxy[28475]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:32 node-1 haproxy[28475]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:32 node-1 haproxy[28475]: 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 27 00:30:32 node-1 haproxy[28475]: proxy keystone-1 has no server available!
<129>Jul 27 00:30:32 node-1 haproxy[28475]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:32 node-1 haproxy[28475]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:32 node-1 haproxy[28475]: 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 27 00:30:32 node-1 haproxy[28475]: proxy keystone-2 has no server available!
<129>Jul 27 00:30:32 node-1 haproxy[28475]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: 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 27 00:30:33 node-1 haproxy[28484]: proxy neutron has no server available!
<129>Jul 27 00:30:33 node-1 haproxy[28484]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: 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 27 00:30:33 node-1 haproxy[28484]: proxy mysqld has no server available!
<129>Jul 27 00:30:33 node-1 haproxy[28484]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: 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 27 00:30:33 node-1 haproxy[28484]: proxy object-storage has no server available!
<129>Jul 27 00:30:33 node-1 haproxy[28484]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:33 node-1 haproxy[28484]: 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 27 00:30:33 node-1 haproxy[28484]: proxy aodh has no server available!
<129>Jul 27 00:30:34 node-1 haproxy[28484]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:34 node-1 haproxy[28484]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:34 node-1 haproxy[28484]: 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 27 00:30:34 node-1 haproxy[28484]: proxy ceilometer has no server available!
<27>Jul 27 00:30:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:35 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:37 node-1 haproxy[29879]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:37 node-1 haproxy[29879]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:37 node-1 haproxy[29879]: 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 27 00:30:37 node-1 haproxy[29879]: proxy keystone-1 has no server available!
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: 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 27 00:30:38 node-1 haproxy[29885]: proxy keystone-2 has no server available!
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: 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 27 00:30:38 node-1 haproxy[29885]: proxy neutron has no server available!
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: 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 27 00:30:38 node-1 haproxy[29885]: proxy mysqld has no server available!
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:38 node-1 haproxy[29885]: 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 27 00:30:38 node-1 haproxy[29885]: proxy object-storage has no server available!
<129>Jul 27 00:30:39 node-1 haproxy[29885]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:39 node-1 haproxy[29885]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:39 node-1 haproxy[29885]: 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 27 00:30:39 node-1 haproxy[29885]: proxy aodh has no server available!
<129>Jul 27 00:30:39 node-1 haproxy[29885]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:39 node-1 haproxy[29885]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:39 node-1 haproxy[29885]: 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 27 00:30:39 node-1 haproxy[29885]: proxy ceilometer has no server available!
<27>Jul 27 00:30:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:40 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:43 node-1 haproxy[31309]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:43 node-1 haproxy[31309]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:43 node-1 haproxy[31309]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:43 node-1 haproxy[31309]: 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 27 00:30:43 node-1 haproxy[31309]: proxy keystone-1 has no server available!
<129>Jul 27 00:30:43 node-1 haproxy[31309]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:43 node-1 haproxy[31309]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:43 node-1 haproxy[31309]: 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 27 00:30:43 node-1 haproxy[31309]: proxy keystone-2 has no server available!
<129>Jul 27 00:30:43 node-1 haproxy[31309]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:43 node-1 haproxy[31309]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:43 node-1 haproxy[31309]: 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 27 00:30:43 node-1 haproxy[31309]: proxy neutron has no server available!
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: 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 27 00:30:44 node-1 haproxy[31315]: proxy mysqld has no server available!
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: 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 27 00:30:44 node-1 haproxy[31315]: proxy object-storage has no server available!
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: 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 27 00:30:44 node-1 haproxy[31315]: proxy aodh has no server available!
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:44 node-1 haproxy[31315]: 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 27 00:30:44 node-1 haproxy[31315]: proxy ceilometer has no server available!
<27>Jul 27 00:30:46 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:46 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:46 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:46 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:46 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: 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 27 00:30:49 node-1 haproxy[325]: proxy keystone-1 has no server available!
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: 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 27 00:30:49 node-1 haproxy[325]: proxy keystone-2 has no server available!
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: 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 27 00:30:49 node-1 haproxy[325]: proxy glance-api has no server available!
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: 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 27 00:30:49 node-1 haproxy[325]: proxy glance-glare has no server available!
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:49 node-1 haproxy[325]: 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 27 00:30:49 node-1 haproxy[325]: proxy neutron has no server available!
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: 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 27 00:30:50 node-1 haproxy[330]: proxy glance-registry has no server available!
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: 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 27 00:30:50 node-1 haproxy[330]: proxy mysqld has no server available!
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: 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 27 00:30:50 node-1 haproxy[330]: proxy object-storage has no server available!
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: 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 27 00:30:50 node-1 haproxy[330]: proxy aodh has no server available!
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:50 node-1 haproxy[330]: 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 27 00:30:50 node-1 haproxy[330]: proxy ceilometer has no server available!
<27>Jul 27 00:30:52 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:52 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:52 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:52 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:52 node-1 multipathd: uevent trigger error
<129>Jul 27 00:30:54 node-1 haproxy[1824]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: 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 27 00:30:55 node-1 haproxy[1828]: proxy keystone-1 has no server available!
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: 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 27 00:30:55 node-1 haproxy[1828]: proxy keystone-2 has no server available!
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: 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 27 00:30:55 node-1 haproxy[1828]: proxy nova-api has no server available!
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: 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 27 00:30:55 node-1 haproxy[1828]: proxy nova-metadata-api has no server available!
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: 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 27 00:30:55 node-1 haproxy[1828]: proxy glance-api has no server available!
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: 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 27 00:30:55 node-1 haproxy[1828]: proxy glance-glare has no server available!
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:55 node-1 haproxy[1828]: 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 27 00:30:55 node-1 haproxy[1828]: proxy neutron has no server available!
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: 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 27 00:30:56 node-1 haproxy[1828]: proxy glance-registry has no server available!
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: 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 27 00:30:56 node-1 haproxy[1828]: proxy mysqld has no server available!
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: 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 27 00:30:56 node-1 haproxy[1828]: proxy object-storage has no server available!
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: 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 27 00:30:56 node-1 haproxy[1828]: proxy aodh has no server available!
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: 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 27 00:30:56 node-1 haproxy[1828]: proxy ceilometer has no server available!
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:30:56 node-1 haproxy[1828]: 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 27 00:30:56 node-1 haproxy[1828]: proxy nova-novncproxy has no server available!
<27>Jul 27 00:30:58 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:58 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:58 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:58 node-1 multipathd: uevent trigger error
<27>Jul 27 00:30:58 node-1 multipathd: uevent trigger error
<129>Jul 27 00:31:00 node-1 haproxy[3211]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:00 node-1 haproxy[3211]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:00 node-1 haproxy[3211]: 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 27 00:31:00 node-1 haproxy[3211]: proxy keystone-1 has no server available!
<129>Jul 27 00:31:00 node-1 haproxy[3211]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:00 node-1 haproxy[3211]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:00 node-1 haproxy[3211]: 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 27 00:31:00 node-1 haproxy[3211]: proxy keystone-2 has no server available!
<129>Jul 27 00:31:00 node-1 haproxy[3211]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:00 node-1 haproxy[3211]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:00 node-1 haproxy[3211]: 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 27 00:31:00 node-1 haproxy[3211]: proxy nova-api has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: 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 27 00:31:01 node-1 haproxy[3215]: proxy nova-metadata-api has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: 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 27 00:31:01 node-1 haproxy[3215]: proxy cinder-api has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: 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 27 00:31:01 node-1 haproxy[3215]: proxy glance-api has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: 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 27 00:31:01 node-1 haproxy[3215]: proxy glance-glare has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: 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 27 00:31:01 node-1 haproxy[3215]: proxy neutron has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: 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 27 00:31:01 node-1 haproxy[3215]: proxy glance-registry has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: 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 27 00:31:01 node-1 haproxy[3215]: proxy mysqld has no server available!
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:01 node-1 haproxy[3215]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:02 node-1 haproxy[3215]: 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 27 00:31:02 node-1 haproxy[3215]: proxy object-storage has no server available!
<129>Jul 27 00:31:02 node-1 haproxy[3215]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:02 node-1 haproxy[3215]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:02 node-1 haproxy[3215]: 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 27 00:31:02 node-1 haproxy[3215]: proxy aodh has no server available!
<129>Jul 27 00:31:02 node-1 haproxy[3215]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:02 node-1 haproxy[3215]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:02 node-1 haproxy[3215]: 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 27 00:31:02 node-1 haproxy[3215]: proxy ceilometer has no server available!
<129>Jul 27 00:31:02 node-1 haproxy[3215]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:02 node-1 haproxy[3215]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:02 node-1 haproxy[3215]: 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 27 00:31:02 node-1 haproxy[3215]: proxy nova-novncproxy has no server available!
<27>Jul 27 00:31:03 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:03 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:03 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:03 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:03 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:03 node-1 multipathd: uevent trigger error
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: 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 27 00:31:06 node-1 haproxy[4683]: proxy keystone-1 has no server available!
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: 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 27 00:31:06 node-1 haproxy[4683]: proxy keystone-2 has no server available!
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: 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 27 00:31:06 node-1 haproxy[4683]: proxy nova-api has no server available!
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:06 node-1 haproxy[4683]: 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 27 00:31:06 node-1 haproxy[4683]: proxy nova-metadata-api has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy cinder-api has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy glance-api has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy glance-glare has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy neutron has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy glance-registry has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy mysqld has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy object-storage has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy aodh has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:07 node-1 haproxy[4690]: 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 27 00:31:07 node-1 haproxy[4690]: proxy ceilometer has no server available!
<129>Jul 27 00:31:07 node-1 haproxy[4690]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: 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 27 00:31:08 node-1 haproxy[4690]: proxy heat-api has no server available!
<129>Jul 27 00:31:08 node-1 haproxy[4690]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: 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 27 00:31:08 node-1 haproxy[4690]: proxy heat-api-cfn has no server available!
<129>Jul 27 00:31:08 node-1 haproxy[4690]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: 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 27 00:31:08 node-1 haproxy[4690]: proxy heat-api-cloudwatch has no server available!
<129>Jul 27 00:31:08 node-1 haproxy[4690]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 00:31:08 node-1 haproxy[4690]: 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 27 00:31:08 node-1 haproxy[4690]: proxy nova-novncproxy has no server available!
<27>Jul 27 00:31:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:31:24 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 00:31:49 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 27 00:31:51 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 27 00:32:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 00:32:35 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 00:32:43 node-1 multipathd: uevent trigger error
<27>Jul 27 00:32:43 node-1 multipathd: uevent trigger error
<27>Jul 27 00:32:43 node-1 multipathd: uevent trigger error
<27>Jul 27 00:32:43 node-1 multipathd: uevent trigger error
<27>Jul 27 00:32:43 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:15 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:16 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:16 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:21 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:21 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:21 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:21 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:21 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 27 00:35:38 node-1 apache2_error [Wed Jul 27 00:35:33.700076 2016] [mpm_event:notice] [pid 16200:tid 139676704360320] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 00:35:38 node-1 apache2_error [Wed Jul 27 00:35:33.700155 2016] [core:notice] [pid 16200:tid 139676704360320] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 00:35:38 node-1 apache2_error [Wed Jul 27 00:35:35.782536 2016] [mpm_event:notice] [pid 16200:tid 139676704360320] AH00491: caught SIGTERM, shutting down
<43>Jul 27 00:35:38 node-1 apache2_error [Wed Jul 27 00:35:36.872089 2016] [mpm_worker:notice] [pid 16770:tid 139881954346880] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 00:35:38 node-1 apache2_error [Wed Jul 27 00:35:36.872160 2016] [core:notice] [pid 16770:tid 139881954346880] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 00:35:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:44 node-1 multipathd: uevent trigger error
<27>Jul 27 00:35:44 node-1 multipathd: uevent trigger error
<43>Jul 27 00:36:58 node-1 apache2_error [Wed Jul 27 00:36:53.578133 2016] [mpm_worker:notice] [pid 16770:tid 139881954346880] AH00295: caught SIGTERM, shutting down
<43>Jul 27 00:36:58 node-1 apache2_error [Wed Jul 27 00:36:54.330267 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 00:36:58 node-1 apache2_error [Wed Jul 27 00:36:54.330305 2016] [core:notice] [pid 30674:tid 139806518765440] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 00:37:38 node-1 apache2_error [Wed Jul 27 00:37:38.346009 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 00:37:38 node-1 apache2_error [Wed Jul 27 00:37:38.541848 2016] [mpm_worker:warn] [pid 30674:tid 139806518765440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 00:37:38 node-1 apache2_error [Wed Jul 27 00:37:38.546050 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 00:37:38 node-1 apache2_error [Wed Jul 27 00:37:38.546073 2016] [core:notice] [pid 30674:tid 139806518765440] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 00:38:22 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:22 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:22 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:22 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:22 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:31 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 00:38:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:38:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:09 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:39:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:40:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:40:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:40:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:40:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:40:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:40:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:41:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 00:41:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:41:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:41:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:41:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:41:41 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:42:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:43:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:43:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:43:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:43:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:43:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:43:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:44:34 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 00:45:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:56 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:56 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:56 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:56 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:56 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:56 node-1 multipathd: uevent trigger error
<27>Jul 27 00:45:56 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:23 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:23 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:23 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:23 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:23 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:46:26 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:36 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 00:47:54 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:54 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:54 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:54 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:54 node-1 multipathd: uevent trigger error
<27>Jul 27 00:47:54 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:10 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:48:29 node-1 multipathd: uevent trigger error
<27>Jul 27 00:50:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 00:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:50:53 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:07 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:12 node-1 multipathd: uevent trigger error
<27>Jul 27 00:51:13 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 27 00:52:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:25 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:25 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:25 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:25 node-1 multipathd: uevent trigger error
<27>Jul 27 00:52:25 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:39 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 00:53:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:53:50 node-1 multipathd: uevent trigger error
<27>Jul 27 00:54:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:54:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:54:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:54:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:54:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:55:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:55:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:55:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:55:13 node-1 multipathd: uevent trigger error
<27>Jul 27 00:55:13 node-1 multipathd: uevent trigger error
<11>Jul 27 00:55:27 node-1 liberasurecode[80017]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:27 node-1 liberasurecode[80017]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:27 node-1 liberasurecode[80017]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:27 node-1 liberasurecode[80017]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:27 node-1 liberasurecode[80131]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:27 node-1 liberasurecode[80131]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:27 node-1 liberasurecode[80131]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:27 node-1 liberasurecode[80131]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:30 node-1 liberasurecode[81305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:30 node-1 liberasurecode[81305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:30 node-1 liberasurecode[81305]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:30 node-1 liberasurecode[81305]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82321]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82321]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82321]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82321]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82357]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82357]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82357]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82357]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82401]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82401]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82401]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82401]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82468]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82468]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82468]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:35 node-1 liberasurecode[82468]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82482]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82482]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82482]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82482]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82494]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82494]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82494]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82494]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82511]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:36 node-1 liberasurecode[82511]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:52 node-1 liberasurecode[83384]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:52 node-1 liberasurecode[83384]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:52 node-1 liberasurecode[83384]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 00:55:52 node-1 liberasurecode[83384]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 00:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 00:56:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 27 00:56:50 node-1 apache2_error [Wed Jul 27 00:56:47.125488 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 00:56:50 node-1 apache2_error [Wed Jul 27 00:56:47.509381 2016] [mpm_worker:warn] [pid 30674:tid 139806518765440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 00:56:50 node-1 apache2_error [Wed Jul 27 00:56:47.513682 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 00:56:50 node-1 apache2_error [Wed Jul 27 00:56:47.513698 2016] [core:notice] [pid 30674:tid 139806518765440] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 00:57:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:28 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:28 node-1 multipathd: uevent trigger error
<43>Jul 27 00:57:30 node-1 apache2_error [Wed Jul 27 00:57:24.592718 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 00:57:30 node-1 apache2_error [Wed Jul 27 00:57:24.789551 2016] [mpm_worker:warn] [pid 30674:tid 139806518765440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 00:57:30 node-1 apache2_error [Wed Jul 27 00:57:24.802437 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 00:57:30 node-1 apache2_error [Wed Jul 27 00:57:24.802470 2016] [core:notice] [pid 30674:tid 139806518765440] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 00:57:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:35 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 00:57:42 node-1 multipathd: uevent trigger error
<43>Jul 27 00:58:20 node-1 apache2_error [Wed Jul 27 00:58:16.649372 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 00:58:20 node-1 apache2_error [Wed Jul 27 00:58:16.848215 2016] [mpm_worker:warn] [pid 30674:tid 139806518765440] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 00:58:20 node-1 apache2_error [Wed Jul 27 00:58:16.857557 2016] [mpm_worker:notice] [pid 30674:tid 139806518765440] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 00:58:20 node-1 apache2_error [Wed Jul 27 00:58:16.857592 2016] [core:notice] [pid 30674:tid 139806518765440] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 00:58:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:20 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:27 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:32 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:32 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:32 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:32 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:32 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:38 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:38 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:38 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:38 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:38 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:38 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:58:49 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:02 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:24 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:32 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 27 00:59:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:40 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:45 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:55 node-1 multipathd: uevent trigger error
<27>Jul 27 00:59:55 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:01 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:01 node-1 multipathd: uevent trigger error
<11>Jul 27 01:00:02 node-1 liberasurecode[138511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 01:00:02 node-1 liberasurecode[138511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 01:00:02 node-1 liberasurecode[138511]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 01:00:02 node-1 liberasurecode[138511]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 01:00:14 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:14 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:14 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:14 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:14 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:14 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 01:00:19 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:19 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:19 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:19 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:19 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:19 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:46 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:46 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:46 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:46 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:46 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:59 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:59 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:59 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:59 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:59 node-1 multipathd: uevent trigger error
<27>Jul 27 01:00:59 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:07 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:07 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:07 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:07 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:07 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:11 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:11 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:12 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:12 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:12 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:25 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:25 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:25 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:25 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:25 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:53 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:53 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:54 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:54 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:54 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:58 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:58 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:58 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:58 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:58 node-1 multipathd: uevent trigger error
<27>Jul 27 01:01:58 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:03 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:03 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:03 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:03 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:03 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:08 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:08 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:08 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:08 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:08 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:13 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:18 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:18 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:18 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:18 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:18 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:23 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:23 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:23 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:23 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:23 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:27 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:27 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:27 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:27 node-1 multipathd: uevent trigger error
<27>Jul 27 01:02:27 node-1 multipathd: uevent trigger error
