Jul 25 08:58:50 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8374" x-info="http://www.rsyslog.com"] start
Jul 25 08:58:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 25 08:58:50 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 25 08:58:50 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 25 08:58:50 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 25 08:58:50 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 25 08:58:50 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 25 08:58:50 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 25 08:58:50 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=d537cbbd-a9c9-454b-a2c8-30ecb3b357b8 nomdmonddf nomdmonisw
Jul 25 08:58:50 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 25 08:58:50 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 25 08:58:50 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 25 08:58:50 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 25 08:58:50 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 25 08:58:50 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 25 08:58:50 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 25 08:58:50 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 25 08:58:50 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 25 08:58:50 node-1 kernel: [    0.000000] No AGP bridge found
Jul 25 08:58:50 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 25 08:58:50 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 25 08:58:50 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 25 08:58:50 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 25 08:58:50 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 25 08:58:50 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 25 08:58:50 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 25 08:58:50 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 25 08:58:50 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 25 08:58:50 node-1 kernel: [    0.000000]   2 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000]   3 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000]   4 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000]   5 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000]   6 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000]   7 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000]   8 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000]   9 disabled
Jul 25 08:58:50 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 25 08:58:50 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 25 08:58:50 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 25 08:58:50 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 25 08:58:50 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 25 08:58:50 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 25 08:58:50 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 25 08:58:50 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 25 08:58:50 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 25 08:58:50 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 25 08:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 25 08:58:50 node-1 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 25 08:58:50 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 25 08:58:50 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 25 08:58:50 node-1 kernel: [    0.000000] Zone ranges:
Jul 25 08:58:50 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 25 08:58:50 node-1 kernel: [    0.000000] Early memory node ranges
Jul 25 08:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 25 08:58:50 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 25 08:58:50 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 25 08:58:50 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 25 08:58:50 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 25 08:58:50 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 25 08:58:50 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 25 08:58:50 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 25 08:58:50 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 25 08:58:50 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 25 08:58:50 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 25 08:58:50 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 25 08:58:50 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 25 08:58:50 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 25 08:58:50 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 25 08:58:50 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 25 08:58:50 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 25 08:58:50 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 25 08:58:50 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 25 08:58:50 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 25 08:58:50 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 25 08:58:50 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 25 08:58:50 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 25 08:58:50 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 25 08:58:50 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 25 08:58:50 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 25 08:58:50 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=d537cbbd-a9c9-454b-a2c8-30ecb3b357b8 nomdmonddf nomdmonisw
Jul 25 08:58:50 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 25 08:58:50 node-1 kernel: [    0.000000] Checking aperture...
Jul 25 08:58:50 node-1 kernel: [    0.000000] No AGP bridge found
Jul 25 08:58:50 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 25 08:58:50 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 25 08:58:50 node-1 kernel: [    0.000000] Memory: 32653448K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627188K reserved)
Jul 25 08:58:50 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 25 08:58:50 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 25 08:58:50 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 25 08:58:50 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 25 08:58:50 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 25 08:58:50 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 25 08:58:50 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 25 08:58:50 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 25 08:58:50 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 25 08:58:50 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 25 08:58:50 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 25 08:58:50 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 25 08:58:50 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 25 08:58:50 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 25 08:58:50 node-1 kernel: [    0.004000] tsc: Detected 3492.146 MHz processor
Jul 25 08:58:50 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.29 BogoMIPS (lpj=13968584)
Jul 25 08:58:50 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 25 08:58:50 node-1 kernel: [    0.000050] Security Framework initialized
Jul 25 08:58:50 node-1 kernel: [    0.000068] AppArmor: AppArmor initialized
Jul 25 08:58:50 node-1 kernel: [    0.000069] Yama: becoming mindful.
Jul 25 08:58:50 node-1 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.006367] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.008289] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.008316] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.008603] Initializing cgroup subsys memory
Jul 25 08:58:50 node-1 kernel: [    0.008611] Initializing cgroup subsys devices
Jul 25 08:58:50 node-1 kernel: [    0.008613] Initializing cgroup subsys freezer
Jul 25 08:58:50 node-1 kernel: [    0.008614] Initializing cgroup subsys blkio
Jul 25 08:58:50 node-1 kernel: [    0.008616] Initializing cgroup subsys perf_event
Jul 25 08:58:50 node-1 kernel: [    0.008618] Initializing cgroup subsys hugetlb
Jul 25 08:58:50 node-1 kernel: [    0.008638] CPU: Physical Processor ID: 0
Jul 25 08:58:50 node-1 kernel: [    0.008639] CPU: Processor Core ID: 0
Jul 25 08:58:50 node-1 kernel: [    0.008643] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 25 08:58:50 node-1 kernel: [    0.008643] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 25 08:58:50 node-1 kernel: [    0.009336] mce: CPU supports 22 MCE banks
Jul 25 08:58:50 node-1 kernel: [    0.009364] CPU0: Thermal monitoring enabled (TM1)
Jul 25 08:58:50 node-1 kernel: [    0.009385] process: using mwait in idle threads
Jul 25 08:58:50 node-1 kernel: [    0.009388] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 25 08:58:50 node-1 kernel: [    0.009388] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 25 08:58:50 node-1 kernel: [    0.009388] tlb_flushall_shift: 6
Jul 25 08:58:50 node-1 kernel: [    0.009476] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 25 08:58:50 node-1 kernel: [    0.010201] ACPI: Core revision 20131115
Jul 25 08:58:50 node-1 kernel: [    0.022893] ACPI: All ACPI Tables successfully acquired
Jul 25 08:58:50 node-1 kernel: [    0.023052] ftrace: allocating 28617 entries in 112 pages
Jul 25 08:58:50 node-1 kernel: [    0.031860] dmar: Host address width 46
Jul 25 08:58:50 node-1 kernel: [    0.031862] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 25 08:58:50 node-1 kernel: [    0.031868] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 08:58:50 node-1 kernel: [    0.031870] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 25 08:58:50 node-1 kernel: [    0.031873] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 08:58:50 node-1 kernel: [    0.031875] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 25 08:58:50 node-1 kernel: [    0.031876] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 25 08:58:50 node-1 kernel: [    0.031877] dmar: ATSR flags: 0x0
Jul 25 08:58:50 node-1 kernel: [    0.031878] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 25 08:58:50 node-1 kernel: [    0.031879] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 25 08:58:50 node-1 kernel: [    0.031996] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 25 08:58:50 node-1 kernel: [    0.031997] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 08:58:50 node-1 kernel: [    0.031998] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 08:58:50 node-1 kernel: [    0.031999] HPET id 0 under DRHD base 0xc7ffc000
Jul 25 08:58:50 node-1 kernel: [    0.032000] Your BIOS is broken and requested that x2apic be disabled.
Jul 25 08:58:50 node-1 kernel: [    0.032000] This will slightly decrease performance.
Jul 25 08:58:50 node-1 kernel: [    0.032000] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 25 08:58:50 node-1 kernel: [    0.032431] Enabled IRQ remapping in xapic mode
Jul 25 08:58:50 node-1 kernel: [    0.032432] x2apic not enabled, IRQ remapping is in xapic mode
Jul 25 08:58:50 node-1 kernel: [    0.032436] Switched APIC routing to physical flat.
Jul 25 08:58:50 node-1 kernel: [    0.033012] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 25 08:58:50 node-1 kernel: [    0.072665] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 25 08:58:50 node-1 kernel: [    0.072670] TSC deadline timer enabled
Jul 25 08:58:50 node-1 kernel: [    0.072677] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 25 08:58:50 node-1 kernel: [    0.072683] ... version:                3
Jul 25 08:58:50 node-1 kernel: [    0.072684] ... bit width:              48
Jul 25 08:58:50 node-1 kernel: [    0.072685] ... generic registers:      4
Jul 25 08:58:50 node-1 kernel: [    0.072686] ... value mask:             0000ffffffffffff
Jul 25 08:58:50 node-1 kernel: [    0.072687] ... max period:             0000ffffffffffff
Jul 25 08:58:50 node-1 kernel: [    0.072688] ... fixed-purpose events:   3
Jul 25 08:58:50 node-1 kernel: [    0.072689] ... event mask:             000000070000000f
Jul 25 08:58:50 node-1 kernel: [    0.074121] x86: Booting SMP configuration:
Jul 25 08:58:50 node-1 kernel: [    0.088226] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 25 08:58:50 node-1 kernel: [    0.074123] .... node  #0, CPUs:        #1  #2  #3
Jul 25 08:58:50 node-1 kernel: [    0.116139] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 25 08:58:50 node-1 kernel: [    0.270297] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 25 08:58:50 node-1 kernel: [    0.325918] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 25 08:58:50 node-1 kernel: [    0.382773] x86: Booted up 2 nodes, 16 CPUs
Jul 25 08:58:50 node-1 kernel: [    0.382776] smpboot: Total of 16 processors activated (111760.71 BogoMIPS)
Jul 25 08:58:50 node-1 kernel: [    0.406464] devtmpfs: initialized
Jul 25 08:58:50 node-1 kernel: [    0.409522] EVM: security.selinux
Jul 25 08:58:50 node-1 kernel: [    0.409524] EVM: security.SMACK64
Jul 25 08:58:50 node-1 kernel: [    0.409525] EVM: security.ima
Jul 25 08:58:50 node-1 kernel: [    0.409525] EVM: security.capability
Jul 25 08:58:50 node-1 kernel: [    0.409576] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.410243] pinctrl core: initialized pinctrl subsystem
Jul 25 08:58:50 node-1 kernel: [    0.410304] regulator-dummy: no parameters
Jul 25 08:58:50 node-1 kernel: [    0.410336] RTC time:  8:58:14, date: 07/25/16
Jul 25 08:58:50 node-1 kernel: [    0.410369] NET: Registered protocol family 16
Jul 25 08:58:50 node-1 kernel: [    0.410452] cpuidle: using governor ladder
Jul 25 08:58:50 node-1 kernel: [    0.410453] cpuidle: using governor menu
Jul 25 08:58:50 node-1 kernel: [    0.410486] ACPI: bus type PCI registered
Jul 25 08:58:50 node-1 kernel: [    0.410488] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 25 08:58:50 node-1 kernel: [    0.410534] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 25 08:58:50 node-1 kernel: [    0.410537] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 25 08:58:50 node-1 kernel: [    0.424266] PCI: Using configuration type 1 for base access
Jul 25 08:58:50 node-1 kernel: [    0.425263] bio: create slab <bio-0> at 0
Jul 25 08:58:50 node-1 kernel: [    0.425536] ACPI: Added _OSI(Module Device)
Jul 25 08:58:50 node-1 kernel: [    0.425538] ACPI: Added _OSI(Processor Device)
Jul 25 08:58:50 node-1 kernel: [    0.425539] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 25 08:58:50 node-1 kernel: [    0.425540] ACPI: Added _OSI(Processor Aggregator Device)
Jul 25 08:58:50 node-1 kernel: [    0.438221] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 25 08:58:50 node-1 kernel: [    0.449768] ACPI: Interpreter enabled
Jul 25 08:58:50 node-1 kernel: [    0.449774] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 25 08:58:50 node-1 kernel: [    0.449778] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 25 08:58:50 node-1 kernel: [    0.449780] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 25 08:58:50 node-1 kernel: [    0.449787] ACPI: (supports S0 S4 S5)
Jul 25 08:58:50 node-1 kernel: [    0.449788] ACPI: Using IOAPIC for interrupt routing
Jul 25 08:58:50 node-1 kernel: [    0.449828] HEST: Table parsing has been initialized.
Jul 25 08:58:50 node-1 kernel: [    0.449831] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 25 08:58:50 node-1 kernel: [    0.450382] ACPI: No dock devices found.
Jul 25 08:58:50 node-1 kernel: [    0.461988] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 25 08:58:50 node-1 kernel: [    0.461993] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 08:58:50 node-1 kernel: [    0.461997] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 08:58:50 node-1 kernel: [    0.462025] PCI host bridge to bus 0000:ff
Jul 25 08:58:50 node-1 kernel: [    0.462028] pci_bus 0000:ff: root bus resource [bus ff]
Jul 25 08:58:50 node-1 kernel: [    0.462036] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462074] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.462105] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462140] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462170] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.462200] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.462231] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462260] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462291] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462320] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462347] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462375] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462403] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462430] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462456] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462483] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462511] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462538] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462565] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.462593] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462619] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.462644] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462670] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462700] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.462735] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462766] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462796] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462826] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462857] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462888] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462919] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462949] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.462980] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463013] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463045] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463078] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463112] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463143] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463170] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463202] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463235] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463275] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463311] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463344] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463375] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463407] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463439] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463470] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463504] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463535] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463567] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463596] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463625] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463654] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463684] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463716] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463748] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463805] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 25 08:58:50 node-1 kernel: [    0.463808] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 08:58:50 node-1 kernel: [    0.463811] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 08:58:50 node-1 kernel: [    0.463829] PCI host bridge to bus 0000:7f
Jul 25 08:58:50 node-1 kernel: [    0.463830] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 25 08:58:50 node-1 kernel: [    0.463835] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463863] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.463892] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463922] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.463944] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.463969] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.463996] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464023] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464045] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464073] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464097] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464122] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464148] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464173] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464198] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464224] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464246] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464269] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464292] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.464315] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464339] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.464361] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464383] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464410] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 08:58:50 node-1 kernel: [    0.464442] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464469] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464497] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464524] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464549] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464576] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464602] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464629] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464653] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464681] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464708] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464735] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464763] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464789] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464814] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464844] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464869] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464895] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464923] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464951] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.464975] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465002] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465027] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465054] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465080] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465107] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465137] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465161] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465183] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465209] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465235] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465265] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.465291] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.466551] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 25 08:58:50 node-1 kernel: [    0.466555] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 08:58:50 node-1 kernel: [    0.467672] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 08:58:50 node-1 kernel: [    0.468191] PCI host bridge to bus 0000:00
Jul 25 08:58:50 node-1 kernel: [    0.468194] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 25 08:58:50 node-1 kernel: [    0.468195] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 25 08:58:50 node-1 kernel: [    0.468197] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 25 08:58:50 node-1 kernel: [    0.468198] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 25 08:58:50 node-1 kernel: [    0.468199] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 25 08:58:50 node-1 kernel: [    0.468201] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 25 08:58:50 node-1 kernel: [    0.468202] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 25 08:58:50 node-1 kernel: [    0.468208] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 25 08:58:50 node-1 kernel: [    0.468291] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.468322] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.468364] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 25 08:58:50 node-1 kernel: [    0.468384] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.468413] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.468453] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 25 08:58:50 node-1 kernel: [    0.468471] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.468501] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.468541] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 25 08:58:50 node-1 kernel: [    0.468557] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.468627] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.468703] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.468778] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 08:58:50 node-1 kernel: [    0.468783] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 25 08:58:50 node-1 kernel: [    0.468867] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 25 08:58:50 node-1 kernel: [    0.469014] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 25 08:58:50 node-1 kernel: [    0.469031] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 25 08:58:50 node-1 kernel: [    0.469110] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.469164] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 25 08:58:50 node-1 kernel: [    0.469185] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.469241] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.469285] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 25 08:58:50 node-1 kernel: [    0.469311] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.469367] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.469410] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 25 08:58:50 node-1 kernel: [    0.469432] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 25 08:58:50 node-1 kernel: [    0.469450] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 25 08:58:50 node-1 kernel: [    0.469528] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.469578] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 25 08:58:50 node-1 kernel: [    0.469604] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 25 08:58:50 node-1 kernel: [    0.469851] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 25 08:58:50 node-1 kernel: [    0.469857] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 25 08:58:50 node-1 kernel: [    0.469863] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.469869] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.469876] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 25 08:58:50 node-1 kernel: [    0.469906] pci 0000:01:00.0: supports D1 D2
Jul 25 08:58:50 node-1 kernel: [    0.476067] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 08:58:50 node-1 kernel: [    0.476073] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 08:58:50 node-1 kernel: [    0.476078] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 08:58:50 node-1 kernel: [    0.476233] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.476267] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 25 08:58:50 node-1 kernel: [    0.484070] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 08:58:50 node-1 kernel: [    0.484088] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.484090] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 08:58:50 node-1 kernel: [    0.484145] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.484212] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.484289] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.484333] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 08:58:50 node-1 kernel: [    0.484336] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.484338] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 08:58:50 node-1 kernel: [    0.484390] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.484512] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.484565] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 08:58:50 node-1 kernel: [    0.484568] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.484570] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.484619] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.484742] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.484780] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.484898] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.484934] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.485073] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.485111] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 25 08:58:50 node-1 kernel: [    0.485230] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 25 08:58:50 node-1 kernel: [    0.485272] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 08:58:50 node-1 kernel: [    0.485275] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.485277] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.485336] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 25 08:58:50 node-1 kernel: [    0.485399] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.485451] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.485492] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 25 08:58:50 node-1 kernel: [    0.485574] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 25 08:58:50 node-1 kernel: [    0.485680] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 08:58:50 node-1 kernel: [    0.485682] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.485684] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.485740] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 25 08:58:50 node-1 kernel: [    0.485794] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.485842] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.486075] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 08:58:50 node-1 kernel: [    0.486079] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 08:58:50 node-1 kernel: [    0.486140] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 25 08:58:50 node-1 kernel: [    0.486200] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.486249] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.486458] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 08:58:50 node-1 kernel: [    0.486462] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 08:58:50 node-1 kernel: [    0.486520] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 25 08:58:50 node-1 kernel: [    0.486580] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.486632] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 25 08:58:50 node-1 kernel: [    0.486855] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 08:58:50 node-1 kernel: [    0.486859] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 08:58:50 node-1 kernel: [    0.487032] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 08:58:50 node-1 kernel: [    0.487070] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 08:58:50 node-1 kernel: [    0.487144] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 25 08:58:50 node-1 kernel: [    0.487163] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 25 08:58:50 node-1 kernel: [    0.487176] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 25 08:58:50 node-1 kernel: [    0.487189] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 25 08:58:50 node-1 kernel: [    0.487240] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 25 08:58:50 node-1 kernel: [    0.492078] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 08:58:50 node-1 kernel: [    0.492087] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 08:58:50 node-1 kernel: [    0.492140] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 25 08:58:50 node-1 kernel: [    0.492878] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 25 08:58:50 node-1 kernel: [    0.492881] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 08:58:50 node-1 kernel: [    0.493000] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 08:58:50 node-1 kernel: [    0.493106] PCI host bridge to bus 0000:80
Jul 25 08:58:50 node-1 kernel: [    0.493108] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 25 08:58:50 node-1 kernel: [    0.493110] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 25 08:58:50 node-1 kernel: [    0.493111] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 25 08:58:50 node-1 kernel: [    0.493119] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.493181] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.493250] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 08:58:50 node-1 kernel: [    0.493311] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 08:58:50 node-1 kernel: [    0.493316] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 25 08:58:50 node-1 kernel: [    0.493388] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 25 08:58:50 node-1 kernel: [    0.493684] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 25 08:58:50 node-1 kernel: [    0.493716] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 25 08:58:50 node-1 kernel: [    0.493745] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 25 08:58:50 node-1 kernel: [    0.493775] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 25 08:58:50 node-1 kernel: [    0.493804] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 08:58:50 node-1 kernel: [    0.493834] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 08:58:50 node-1 kernel: [    0.493863] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 08:58:50 node-1 kernel: [    0.493893] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 08:58:50 node-1 kernel: [    0.493977] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 25 08:58:50 node-1 kernel: [    0.493981] ACPI: \_SB_.UNC1: notify handler is installed
Jul 25 08:58:50 node-1 kernel: [    0.493982] ACPI: \_SB_.UNC0: notify handler is installed
Jul 25 08:58:50 node-1 kernel: [    0.493997] ACPI: \_SB_.PCI0: notify handler is installed
Jul 25 08:58:50 node-1 kernel: [    0.494050] ACPI: \_SB_.PCI1: notify handler is installed
Jul 25 08:58:50 node-1 kernel: [    0.494129] Found 4 acpi root devices
Jul 25 08:58:50 node-1 kernel: [    0.494235] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 25 08:58:50 node-1 kernel: [    0.494237] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 25 08:58:50 node-1 kernel: [    0.494238] vgaarb: loaded
Jul 25 08:58:50 node-1 kernel: [    0.494239] vgaarb: bridge control possible 0000:0c:00.0
Jul 25 08:58:50 node-1 kernel: [    0.494354] SCSI subsystem initialized
Jul 25 08:58:50 node-1 kernel: [    0.494419] libata version 3.00 loaded.
Jul 25 08:58:50 node-1 kernel: [    0.494433] ACPI: bus type USB registered
Jul 25 08:58:50 node-1 kernel: [    0.494443] usbcore: registered new interface driver usbfs
Jul 25 08:58:50 node-1 kernel: [    0.494448] usbcore: registered new interface driver hub
Jul 25 08:58:50 node-1 kernel: [    0.494472] usbcore: registered new device driver usb
Jul 25 08:58:50 node-1 kernel: [    0.494646] PCI: Using ACPI for IRQ routing
Jul 25 08:58:50 node-1 kernel: [    0.498261] PCI: pci_cache_line_size set to 64 bytes
Jul 25 08:58:50 node-1 kernel: [    0.498472] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 25 08:58:50 node-1 kernel: [    0.498473] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 25 08:58:50 node-1 kernel: [    0.498474] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 25 08:58:50 node-1 kernel: [    0.498538] NetLabel: Initializing
Jul 25 08:58:50 node-1 kernel: [    0.498539] NetLabel:  domain hash size = 128
Jul 25 08:58:50 node-1 kernel: [    0.498540] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 25 08:58:50 node-1 kernel: [    0.498549] NetLabel:  unlabeled traffic allowed by default
Jul 25 08:58:50 node-1 kernel: [    0.498604] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 25 08:58:50 node-1 kernel: [    0.498609] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 25 08:58:50 node-1 kernel: [    0.500663] Switched to clocksource hpet
Jul 25 08:58:50 node-1 kernel: [    0.504746] AppArmor: AppArmor Filesystem Enabled
Jul 25 08:58:50 node-1 kernel: [    0.504759] pnp: PnP ACPI init
Jul 25 08:58:50 node-1 kernel: [    0.504766] ACPI: bus type PNP registered
Jul 25 08:58:50 node-1 kernel: [    0.504876] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 25 08:58:50 node-1 kernel: [    0.504884] pnp 00:01: [dma 4]
Jul 25 08:58:50 node-1 kernel: [    0.504896] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 25 08:58:50 node-1 kernel: [    0.504923] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 25 08:58:50 node-1 kernel: [    0.504942] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 25 08:58:50 node-1 kernel: [    0.504959] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 25 08:58:50 node-1 kernel: [    0.504992] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 25 08:58:50 node-1 kernel: [    0.505044] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505046] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 25 08:58:50 node-1 kernel: [    0.505048] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505050] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505051] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505056] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505058] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 25 08:58:50 node-1 kernel: [    0.505060] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505061] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505063] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505064] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505066] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505067] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 25 08:58:50 node-1 kernel: [    0.505069] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 25 08:58:50 node-1 kernel: [    0.505152] pnp 00:07: [dma 0 disabled]
Jul 25 08:58:50 node-1 kernel: [    0.505180] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 08:58:50 node-1 kernel: [    0.505254] pnp 00:08: [dma 0 disabled]
Jul 25 08:58:50 node-1 kernel: [    0.505286] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 08:58:50 node-1 kernel: [    0.505337] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 25 08:58:50 node-1 kernel: [    0.505682] pnp: PnP ACPI: found 10 devices
Jul 25 08:58:50 node-1 kernel: [    0.505683] ACPI: bus type PNP unregistered
Jul 25 08:58:50 node-1 kernel: [    0.512112] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 08:58:50 node-1 kernel: [    0.512115] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 08:58:50 node-1 kernel: [    0.512118] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 08:58:50 node-1 kernel: [    0.512122] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 08:58:50 node-1 kernel: [    0.512124] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512138] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512167] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 08:58:50 node-1 kernel: [    0.512182] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512211] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 08:58:50 node-1 kernel: [    0.512225] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 08:58:50 node-1 kernel: [    0.512254] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 08:58:50 node-1 kernel: [    0.512269] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 08:58:50 node-1 kernel: [    0.512301] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 08:58:50 node-1 kernel: [    0.512302] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512317] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512346] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 08:58:50 node-1 kernel: [    0.512348] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512363] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512391] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 08:58:50 node-1 kernel: [    0.512393] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512396] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512400] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 08:58:50 node-1 kernel: [    0.512402] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512404] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512408] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 08:58:50 node-1 kernel: [    0.512413] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 08:58:50 node-1 kernel: [    0.512421] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 08:58:50 node-1 kernel: [    0.512424] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 08:58:50 node-1 kernel: [    0.512430] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 25 08:58:50 node-1 kernel: [    0.512431] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 25 08:58:50 node-1 kernel: [    0.512432] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 25 08:58:50 node-1 kernel: [    0.512433] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 25 08:58:50 node-1 kernel: [    0.512434] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 25 08:58:50 node-1 kernel: [    0.512435] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 25 08:58:50 node-1 kernel: [    0.512436] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 25 08:58:50 node-1 kernel: [    0.512437] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 25 08:58:50 node-1 kernel: [    0.512438] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512438] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512439] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512440] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512441] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512442] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512443] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512444] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512445] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 25 08:58:50 node-1 kernel: [    0.512445] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512446] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 25 08:58:50 node-1 kernel: [    0.512448] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 25 08:58:50 node-1 kernel: [    0.512448] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 25 08:58:50 node-1 kernel: [    0.512450] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 25 08:58:50 node-1 kernel: [    0.512451] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 25 08:58:50 node-1 kernel: [    0.512452] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 25 08:58:50 node-1 kernel: [    0.512490] NET: Registered protocol family 2
Jul 25 08:58:50 node-1 kernel: [    0.512755] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.513089] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.513235] TCP: Hash tables configured (established 262144 bind 65536)
Jul 25 08:58:50 node-1 kernel: [    0.513279] TCP: reno registered
Jul 25 08:58:50 node-1 kernel: [    0.513307] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.513405] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.513553] NET: Registered protocol family 1
Jul 25 08:58:50 node-1 kernel: [    0.548762] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 25 08:58:50 node-1 kernel: [    0.548776] PCI: CLS 64 bytes, default 64
Jul 25 08:58:50 node-1 kernel: [    0.548851] Trying to unpack rootfs image as initramfs...
Jul 25 08:58:50 node-1 kernel: [    0.768307] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Jul 25 08:58:50 node-1 kernel: [    0.768350] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 25 08:58:50 node-1 kernel: [    0.768353] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 25 08:58:50 node-1 kernel: [    0.768783] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768790] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768795] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768800] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768825] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768836] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768845] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768854] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768861] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768871] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768877] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768883] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768890] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768897] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768905] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768912] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 08:58:50 node-1 kernel: [    0.768988] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 25 08:58:50 node-1 kernel: [    0.768991] Scanning for low memory corruption every 60 seconds
Jul 25 08:58:50 node-1 kernel: [    0.769364] Initialise system trusted keyring
Jul 25 08:58:50 node-1 kernel: [    0.769418] audit: initializing netlink socket (disabled)
Jul 25 08:58:50 node-1 kernel: [    0.769434] type=2000 audit(1469437093.724:1): initialized
Jul 25 08:58:50 node-1 kernel: [    0.787344] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 25 08:58:50 node-1 kernel: [    0.788877] zbud: loaded
Jul 25 08:58:50 node-1 kernel: [    0.789003] VFS: Disk quotas dquot_6.5.2
Jul 25 08:58:50 node-1 kernel: [    0.789039] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 25 08:58:50 node-1 kernel: [    0.789425] fuse init (API version 7.22)
Jul 25 08:58:50 node-1 kernel: [    0.789486] msgmni has been set to 32768
Jul 25 08:58:50 node-1 kernel: [    0.789535] Key type big_key registered
Jul 25 08:58:50 node-1 kernel: [    0.790059] Key type asymmetric registered
Jul 25 08:58:50 node-1 kernel: [    0.790061] Asymmetric key parser 'x509' registered
Jul 25 08:58:50 node-1 kernel: [    0.790083] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 25 08:58:50 node-1 kernel: [    0.790149] io scheduler noop registered
Jul 25 08:58:50 node-1 kernel: [    0.790151] io scheduler deadline registered (default)
Jul 25 08:58:50 node-1 kernel: [    0.790169] io scheduler cfq registered
Jul 25 08:58:50 node-1 kernel: [    0.790581] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    0.790701] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    0.790812] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    0.790917] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    0.791026] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    0.791119] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    0.791508] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 25 08:58:50 node-1 kernel: [    0.791533] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 25 08:58:50 node-1 kernel: [    0.791549] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 25 08:58:50 node-1 kernel: [    0.791558] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791560] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791563] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 25 08:58:50 node-1 kernel: [    0.791568] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791569] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791571] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791572] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791574] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791576] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791577] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791578] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791580] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791581] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791583] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791584] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791587] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 25 08:58:50 node-1 kernel: [    0.791592] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791594] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 25 08:58:50 node-1 kernel: [    0.791609] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791612] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 25 08:58:50 node-1 kernel: [    0.791622] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791624] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 25 08:58:50 node-1 kernel: [    0.791627] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 25 08:58:50 node-1 kernel: [    0.791662] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 25 08:58:50 node-1 kernel: [    0.791668] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 25 08:58:50 node-1 kernel: [    0.791672] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 25 08:58:50 node-1 kernel: [    0.791681] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 25 08:58:50 node-1 kernel: [    0.791730] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 25 08:58:50 node-1 kernel: [    0.791731] vesafb: scrolling: redraw
Jul 25 08:58:50 node-1 kernel: [    0.791733] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 25 08:58:50 node-1 kernel: [    0.812354] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 25 08:58:50 node-1 kernel: [    0.820893] Console: switching to colour frame buffer device 80x30
Jul 25 08:58:50 node-1 kernel: [    0.829564] fb0: VESA VGA frame buffer device
Jul 25 08:58:50 node-1 kernel: [    0.829759] intel_idle: MWAIT substates: 0x2120
Jul 25 08:58:50 node-1 kernel: [    0.829760] intel_idle: v0.4 model 0x3F
Jul 25 08:58:50 node-1 kernel: [    0.829761] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 25 08:58:50 node-1 kernel: [    0.830009] ipmi message handler version 39.2
Jul 25 08:58:50 node-1 kernel: [    0.830279] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 25 08:58:50 node-1 kernel: [    0.830710] ACPI: AC Adapter [P111] (on-line)
Jul 25 08:58:50 node-1 kernel: [    0.835938] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 25 08:58:50 node-1 kernel: [    0.847002] ACPI: Power Button [PWRB]
Jul 25 08:58:50 node-1 kernel: [    0.852860] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 25 08:58:50 node-1 kernel: [    0.864579] ACPI: Power Button [PWRF]
Jul 25 08:58:50 node-1 kernel: [    0.890215] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 25 08:58:50 node-1 kernel: [    0.901992] pstore: Registered erst as persistent store backend
Jul 25 08:58:50 node-1 kernel: [    0.908270] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 25 08:58:50 node-1 kernel: [    0.920399] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 25 08:58:50 node-1 kernel: [    0.947153] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 25 08:58:50 node-1 kernel: [    0.980439] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 25 08:58:50 node-1 kernel: [    0.994526] Linux agpgart interface v0.103
Jul 25 08:58:50 node-1 kernel: [    1.002173] brd: module loaded
Jul 25 08:58:50 node-1 kernel: [    1.009227] loop: module loaded
Jul 25 08:58:50 node-1 kernel: [    1.015962] libphy: Fixed MDIO Bus: probed
Jul 25 08:58:50 node-1 kernel: [    1.022429] tun: Universal TUN/TAP device driver, 1.6
Jul 25 08:58:50 node-1 kernel: [    1.028901] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 25 08:58:50 node-1 kernel: [    1.035426] PPP generic driver version 2.4.2
Jul 25 08:58:50 node-1 kernel: [    1.041808] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 25 08:58:50 node-1 kernel: [    1.048255] ehci-pci: EHCI PCI platform driver
Jul 25 08:58:50 node-1 kernel: [    1.054796] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 25 08:58:50 node-1 kernel: [    1.061208] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 25 08:58:50 node-1 kernel: [    1.073885] ehci-pci 0000:00:1a.0: debug port 2
Jul 25 08:58:50 node-1 kernel: [    1.084135] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 25 08:58:50 node-1 kernel: [    1.084154] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 25 08:58:50 node-1 kernel: [    1.100160] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 25 08:58:50 node-1 kernel: [    1.106242] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 08:58:50 node-1 kernel: [    1.112429] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 08:58:50 node-1 kernel: [    1.124372] usb usb1: Product: EHCI Host Controller
Jul 25 08:58:50 node-1 kernel: [    1.130408] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 08:58:50 node-1 kernel: [    1.136470] usb usb1: SerialNumber: 0000:00:1a.0
Jul 25 08:58:50 node-1 kernel: [    1.142430] hub 1-0:1.0: USB hub found
Jul 25 08:58:50 node-1 kernel: [    1.148208] hub 1-0:1.0: 2 ports detected
Jul 25 08:58:50 node-1 kernel: [    1.153995] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 25 08:58:50 node-1 kernel: [    1.159585] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 25 08:58:50 node-1 kernel: [    1.170503] ehci-pci 0000:00:1d.0: debug port 2
Jul 25 08:58:50 node-1 kernel: [    1.179816] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 25 08:58:50 node-1 kernel: [    1.179819] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 25 08:58:50 node-1 kernel: [    1.196078] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 25 08:58:50 node-1 kernel: [    1.201283] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 08:58:50 node-1 kernel: [    1.206592] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 08:58:50 node-1 kernel: [    1.217163] usb usb2: Product: EHCI Host Controller
Jul 25 08:58:50 node-1 kernel: [    1.222639] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 08:58:50 node-1 kernel: [    1.228189] usb usb2: SerialNumber: 0000:00:1d.0
Jul 25 08:58:50 node-1 kernel: [    1.233700] hub 2-0:1.0: USB hub found
Jul 25 08:58:50 node-1 kernel: [    1.239055] hub 2-0:1.0: 2 ports detected
Jul 25 08:58:50 node-1 kernel: [    1.244351] ehci-platform: EHCI generic platform driver
Jul 25 08:58:50 node-1 kernel: [    1.249578] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 25 08:58:50 node-1 kernel: [    1.254885] ohci-pci: OHCI PCI platform driver
Jul 25 08:58:50 node-1 kernel: [    1.260187] ohci-platform: OHCI generic platform driver
Jul 25 08:58:50 node-1 kernel: [    1.265386] uhci_hcd: USB Universal Host Controller Interface driver
Jul 25 08:58:50 node-1 kernel: [    1.270721] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 25 08:58:50 node-1 kernel: [    1.463857] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 25 08:58:50 node-1 kernel: [    1.763654] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 25 08:58:50 node-1 kernel: [    1.779927] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 25 08:58:50 node-1 kernel: [    1.785528] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 08:58:50 node-1 kernel: [    1.791194] hub 1-1:1.0: USB hub found
Jul 25 08:58:50 node-1 kernel: [    1.796789] hub 1-1:1.0: 6 ports detected
Jul 25 08:58:50 node-1 kernel: [    1.911497] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 25 08:58:50 node-1 kernel: [    2.309847] i8042: No controller found
Jul 25 08:58:50 node-1 kernel: [    2.315460] mousedev: PS/2 mouse device common for all mice
Jul 25 08:58:50 node-1 kernel: [    2.321263] rtc_cmos 00:02: RTC can wake from S4
Jul 25 08:58:50 node-1 kernel: [    2.323911] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 25 08:58:50 node-1 kernel: [    2.323912] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 08:58:50 node-1 kernel: [    2.324547] hub 2-1:1.0: USB hub found
Jul 25 08:58:50 node-1 kernel: [    2.324782] hub 2-1:1.0: 8 ports detected
Jul 25 08:58:50 node-1 kernel: [    2.349550] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 25 08:58:50 node-1 kernel: [    2.355300] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 25 08:58:50 node-1 kernel: [    2.366670] device-mapper: uevent: version 1.0.3
Jul 25 08:58:50 node-1 kernel: [    2.372376] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 25 08:58:50 node-1 kernel: [    2.383729] ledtrig-cpu: registered to indicate activity on CPUs
Jul 25 08:58:50 node-1 kernel: [    2.389689] TCP: cubic registered
Jul 25 08:58:50 node-1 kernel: [    2.395534] NET: Registered protocol family 10
Jul 25 08:58:50 node-1 kernel: [    2.401588] NET: Registered protocol family 17
Jul 25 08:58:50 node-1 kernel: [    2.407362] Key type dns_resolver registered
Jul 25 08:58:50 node-1 kernel: [    2.413492] Loading compiled-in X.509 certificates
Jul 25 08:58:50 node-1 kernel: [    2.419748] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 25 08:58:50 node-1 kernel: [    2.431591] registered taskstats version 1
Jul 25 08:58:50 node-1 kernel: [    2.439842] Key type trusted registered
Jul 25 08:58:50 node-1 kernel: [    2.447612] Key type encrypted registered
Jul 25 08:58:50 node-1 kernel: [    2.453226] AppArmor: AppArmor sha1 policy hashing enabled
Jul 25 08:58:50 node-1 kernel: [    2.458870] IMA: No TPM chip found, activating TPM-bypass!
Jul 25 08:58:50 node-1 kernel: [    2.465088] regulator-dummy: disabling
Jul 25 08:58:50 node-1 kernel: [    2.470691]   Magic number: 8:175:979
Jul 25 08:58:50 node-1 kernel: [    2.476568] rtc_cmos 00:02: setting system clock to 2016-07-25 08:58:16 UTC (1469437096)
Jul 25 08:58:50 node-1 kernel: [    2.489328] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 25 08:58:50 node-1 kernel: [    2.495135] EDD information not available.
Jul 25 08:58:50 node-1 kernel: [    2.500886] PM: Hibernation image not present or could not be loaded.
Jul 25 08:58:50 node-1 kernel: [    2.501752] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 25 08:58:50 node-1 kernel: [    2.513403] Write protecting the kernel read-only data: 12288k
Jul 25 08:58:50 node-1 kernel: [    2.519815] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 25 08:58:50 node-1 kernel: [    2.533076] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 25 08:58:50 node-1 kernel: [    2.566032] device-mapper: multipath: version 1.6.0 loaded
Jul 25 08:58:50 node-1 kernel: [    2.574233] systemd-udevd[216]: starting version 204
Jul 25 08:58:50 node-1 kernel: [    2.597745] md: linear personality registered for level -1
Jul 25 08:58:50 node-1 kernel: [    2.599380] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 25 08:58:50 node-1 kernel: [    2.618251] md: multipath personality registered for level -4
Jul 25 08:58:50 node-1 kernel: [    2.626272] md: raid0 personality registered for level 0
Jul 25 08:58:50 node-1 kernel: [    2.634769] md: raid1 personality registered for level 1
Jul 25 08:58:50 node-1 kernel: [    2.641219] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 25 08:58:50 node-1 kernel: [    2.647545] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 25 08:58:50 node-1 kernel: [    2.653852] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 25 08:58:50 node-1 kernel: [    2.658231] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 25 08:58:50 node-1 kernel: [    2.658233] 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 25 08:58:50 node-1 kernel: [    2.658239] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 08:58:50 node-1 kernel: [    2.658567] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.658689] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.658776] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.659063] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.659318] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.675223] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 25 08:58:50 node-1 kernel: [    2.675264] 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 25 08:58:50 node-1 kernel: [    2.675264] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 08:58:50 node-1 kernel: [    2.675570] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.675750] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.675903] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.676040] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.676311] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.690378] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 25 08:58:50 node-1 kernel: [    2.690407] 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 25 08:58:50 node-1 kernel: [    2.690444] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 08:58:50 node-1 kernel: [    2.690675] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.690784] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.690975] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.691133] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.691362] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.706676] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 25 08:58:50 node-1 kernel: [    2.706680] 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 25 08:58:50 node-1 kernel: [    2.706681] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 08:58:50 node-1 kernel: [    2.709916] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.710036] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.710154] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.710297] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.710588] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.848458] Switched to clocksource tsc
Jul 25 08:58:50 node-1 kernel: [    2.848627] megasas: FW now in Ready state
Jul 25 08:58:50 node-1 kernel: [    2.848748] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.848857] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.848943] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.848980] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849012] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849050] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849089] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849117] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849153] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849186] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849224] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849271] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849307] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849343] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849377] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849416] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 25 08:58:50 node-1 kernel: [    2.849562] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 25 08:58:50 node-1 kernel: [    2.906218] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 25 08:58:50 node-1 kernel: [    2.913081] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 25 08:58:50 node-1 kernel: [    2.914763] raid6: sse2x1   10378 MB/s
Jul 25 08:58:50 node-1 kernel: [    2.933267] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 25 08:58:50 node-1 kernel: [    2.939978] usb 2-1.4: Manufacturer: Avocent
Jul 25 08:58:50 node-1 kernel: [    2.946531] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 25 08:58:50 node-1 kernel: [    2.955889] hidraw: raw HID events driver (C) Jiri Kosina
Jul 25 08:58:50 node-1 kernel: [    2.964964] usbcore: registered new interface driver usbhid
Jul 25 08:58:50 node-1 kernel: [    2.971251] usbhid: USB HID core driver
Jul 25 08:58:50 node-1 kernel: [    2.978474] 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 25 08:58:50 node-1 kernel: [    2.982593] raid6: sse2x2    2160 MB/s
Jul 25 08:58:50 node-1 kernel: [    2.997703] 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 25 08:58:50 node-1 kernel: [    3.010521] 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 25 08:58:50 node-1 kernel: [    3.023534] 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 25 08:58:50 node-1 kernel: [    3.036905] 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 25 08:58:50 node-1 kernel: [    3.050274] 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 25 08:58:50 node-1 kernel: [    3.050551] raid6: sse2x4    1009 MB/s
Jul 25 08:58:50 node-1 kernel: [    3.118436] raid6: avx2x1   17009 MB/s
Jul 25 08:58:50 node-1 kernel: [    3.190376] raid6: avx2x2   25759 MB/s
Jul 25 08:58:50 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 25 08:58:50 node-1 kernel: [    3.190377] megasas:IOC Init cmd success
Jul 25 08:58:50 node-1 kernel: [    3.238344] megasas: INIT adapter done
Jul 25 08:58:50 node-1 kernel: [    3.270307] raid6: avx2x4   27408 MB/s
Jul 25 08:58:50 node-1 kernel: [    3.276525] raid6: using algorithm avx2x4 (27408 MB/s)
Jul 25 08:58:50 node-1 kernel: [    3.282670] raid6: using avx2x2 recovery algorithm
Jul 25 08:58:50 node-1 kernel: [    3.289448] xor: automatically using best checksumming function:
Jul 25 08:58:50 node-1 kernel: [    3.314272] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 25 08:58:50 node-1 kernel: [    3.320501] scsi0 : LSI SAS based MegaRAID driver
Jul 25 08:58:50 node-1 kernel: [    3.327606] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 08:58:50 node-1 kernel: [    3.334265]    avx       : 35548.000 MB/sec
Jul 25 08:58:50 node-1 kernel: [    3.346850] async_tx: api initialized (async)
Jul 25 08:58:50 node-1 kernel: [    3.356717] md: raid6 personality registered for level 6
Jul 25 08:58:50 node-1 kernel: [    3.362894] md: raid5 personality registered for level 5
Jul 25 08:58:50 node-1 kernel: [    3.366833] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 08:58:50 node-1 kernel: [    3.380626] md: raid4 personality registered for level 4
Jul 25 08:58:50 node-1 kernel: [    3.387900] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 25 08:58:50 node-1 kernel: [    3.393721] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 25 08:58:50 node-1 kernel: [    3.405160] md: raid10 personality registered for level 10
Jul 25 08:58:50 node-1 kernel: [    3.405829] sd 0:2:0:0: [sda] Write Protect is off
Jul 25 08:58:50 node-1 kernel: [    3.405870] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 25 08:58:50 node-1 kernel: [    3.406168] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 25 08:58:50 node-1 kernel: [    3.441056]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 25 08:58:50 node-1 kernel: [    3.446713] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 25 08:58:50 node-1 kernel: [    3.485645] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Jul 25 08:58:50 node-1 kernel: [    3.592303] random: lvm urandom read with 29 bits of entropy available
Jul 25 08:58:50 node-1 kernel: [    3.734508] bio: create slab <bio-1> at 1
Jul 25 08:58:50 node-1 kernel: [    4.403542] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 08:58:50 node-1 kernel: [    4.975769] init: plymouth-upstart-bridge main process (549) terminated with status 1
Jul 25 08:58:50 node-1 kernel: [    4.988613] init: plymouth-upstart-bridge main process ended, respawning
Jul 25 08:58:50 node-1 kernel: [    5.126299] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 25 08:58:50 node-1 kernel: [    5.141780] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 25 08:58:50 node-1 kernel: [    5.231368] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 25 08:58:50 node-1 kernel: [    5.267360] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 25 08:58:50 node-1 kernel: [    5.324548] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 08:58:50 node-1 kernel: [    5.481328] random: nonblocking pool is initialized
Jul 25 08:58:50 node-1 kernel: [    5.519732] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 25 08:58:50 node-1 kernel: [    5.554260] XFS (dm-0): Mounting Filesystem
Jul 25 08:58:50 node-1 kernel: [    5.867860] XFS (dm-0): Ending clean mount
Jul 25 08:58:50 node-1 kernel: [    5.977287] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 08:58:50 node-1 kernel: [    6.003033] XFS (dm-1): Mounting Filesystem
Jul 25 08:58:50 node-1 kernel: [    6.135372] XFS (dm-1): Ending clean mount
Jul 25 08:58:50 node-1 kernel: [    7.915491] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 25 08:58:50 node-1 kernel: [    7.938755] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 25 08:58:50 node-1 kernel: [    8.098968] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 25 08:58:50 node-1 kernel: [    8.098973] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 25 08:58:50 node-1 kernel: [    8.098976] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 25 08:58:50 node-1 kernel: [    8.098980] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 25 08:58:50 node-1 kernel: [    8.151834] systemd-udevd[774]: starting version 204
Jul 25 08:58:50 node-1 kernel: [    8.428053] power_meter ACPI000D:00: Found ACPI power meter.
Jul 25 08:58:50 node-1 kernel: [    8.428062] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 25 08:58:50 node-1 kernel: [    8.435106] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 25 08:58:50 node-1 kernel: [    8.435111] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 08:58:50 node-1 kernel: [    8.435113] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 25 08:58:50 node-1 kernel: [    8.435115] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 08:58:50 node-1 kernel: [    8.435159] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 25 08:58:50 node-1 kernel: [    8.435725] IPMI System Interface driver.
Jul 25 08:58:50 node-1 kernel: [    8.435762] ipmi_si: probing via ACPI
Jul 25 08:58:50 node-1 kernel: [    8.435772] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 25 08:58:50 node-1 kernel: [    8.435773] ipmi_si: Adding ACPI-specified kcs state machine
Jul 25 08:58:50 node-1 kernel: [    8.435781] ipmi_si: probing via SMBIOS
Jul 25 08:58:50 node-1 kernel: [    8.435782] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 08:58:50 node-1 kernel: [    8.435783] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 25 08:58:50 node-1 kernel: [    8.435785] ipmi_si: probing via SPMI
Jul 25 08:58:50 node-1 kernel: [    8.435786] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 08:58:50 node-1 kernel: [    8.435787] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 25 08:58:50 node-1 kernel: [    8.435789] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 25 08:58:50 node-1 kernel: [    8.440480] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 25 08:58:50 node-1 kernel: [    8.453015] wmi: Mapper loaded
Jul 25 08:58:50 node-1 kernel: [    8.570303] systemd-udevd[797]: renamed network interface eth0 to enp6s0
Jul 25 08:58:50 node-1 kernel: [    8.580212] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 25 08:58:50 node-1 kernel: [    8.580220] ipmi_si 00:09: IPMI kcs interface initialized
Jul 25 08:58:50 node-1 kernel: [    8.606226] systemd-udevd[807]: renamed network interface eth1 to enp7s0
Jul 25 08:58:50 node-1 kernel: [    8.644814] systemd-udevd[813]: renamed network interface eth2 to enp8s0
Jul 25 08:58:50 node-1 kernel: [    8.674136] systemd-udevd[816]: renamed network interface eth3 to enp9s0
Jul 25 08:58:50 node-1 kernel: [    8.973238] type=1400 audit(1469437102.996:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1038 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.973391] type=1400 audit(1469437102.996:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1038 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.973526] type=1400 audit(1469437103.000:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1038 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.980387] type=1400 audit(1469437103.004:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1035 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.980528] type=1400 audit(1469437103.004:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1035 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.980648] type=1400 audit(1469437103.004:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1035 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.986706] type=1400 audit(1469437103.012:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1036 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.986822] type=1400 audit(1469437103.012:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1036 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.986931] type=1400 audit(1469437103.012:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1036 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    8.989435] type=1400 audit(1469437103.012:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1037 comm="apparmor_parser"
Jul 25 08:58:50 node-1 kernel: [    9.648189] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 25 08:58:50 node-1 kernel: [    9.649078] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 25 08:58:50 node-1 kernel: [    9.893878] enic 0000:06:00.0 enp6s0: Link UP
Jul 25 08:58:50 node-1 kernel: [    9.894597] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 25 08:58:50 node-1 kernel: [    9.894606] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 25 08:58:50 node-1 kernel: [   19.180690] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 25 08:58:52 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 25 08:58:52 node-1 kernel: [   38.109486] init: failsafe main process (8401) killed by TERM signal
Jul 25 08:58:52 node-1 dbus[8439]: [system] AppArmor D-Bus mediation is enabled
Jul 25 08:58:52 node-1 kernel: [   38.338406] audit_printk_skb: 30 callbacks suppressed
Jul 25 08:58:52 node-1 kernel: [   38.338407] type=1400 audit(1469437132.305:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8526 comm="apparmor_parser"
Jul 25 08:58:52 node-1 kernel: [   38.338411] type=1400 audit(1469437132.305:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8526 comm="apparmor_parser"
Jul 25 08:58:52 node-1 kernel: [   38.338413] type=1400 audit(1469437132.305:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 08:58:52 node-1 kernel: [   38.338631] type=1400 audit(1469437132.305:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8526 comm="apparmor_parser"
Jul 25 08:58:52 node-1 kernel: [   38.338633] type=1400 audit(1469437132.305:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 08:58:52 node-1 kernel: [   38.338746] type=1400 audit(1469437132.305:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 08:58:52 node-1 kernel: [   38.341520] type=1400 audit(1469437132.309:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8527 comm="apparmor_parser"
Jul 25 08:58:52 node-1 kernel: [   38.419600] type=1400 audit(1469437132.385:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8529 comm="apparmor_parser"
Jul 25 08:58:52 node-1 anacron[8593]: Anacron 2.3 started on 2016-07-25
Jul 25 08:58:52 node-1 cron[8559]: (CRON) INFO (pidfile fd = 3)
Jul 25 08:58:52 node-1 anacron[8593]: Will run job `cron.daily' in 5 min.
Jul 25 08:58:52 node-1 anacron[8593]: Will run job `cron.weekly' in 10 min.
Jul 25 08:58:52 node-1 anacron[8593]: Will run job `cron.monthly' in 15 min.
Jul 25 08:58:52 node-1 anacron[8593]: Jobs will be executed sequentially
Jul 25 08:58:52 node-1 cron[8605]: (CRON) STARTUP (fork ok)
Jul 25 08:58:52 node-1 multipathd: path checkers start up
Jul 25 08:58:52 node-1 cron[8605]: (CRON) INFO (Running @reboot jobs)
Jul 25 08:58:52 node-1 postfix/master[8738]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 25 08:58:56 node-1 puppet-agent[8922]: Reopening log files
Jul 25 08:58:56 node-1 puppet-agent[8922]: Could not request certificate: Connection refused - connect(2)
Jul 25 08:59:01 node-1 CRON[9082]: (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 25 08:59:05 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 08:59:05 node-1 nailgun-agent: D, [2016-07-25T08:59:01.769581 #9085] DEBUG -- : Sleep for 4 seconds before sending request
Jul 25 08:59:05 node-1 nailgun-agent: I, [2016-07-25T08:59:05.785262 #9085]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 08:59:06 node-1 nailgun-agent: D, [2016-07-25T08:59:06.204139 #9085] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 25 08:59:11 node-1 puppet-user[9450]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 25 08:59:11 node-1 puppet-user[9450]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 25 08:59:12 node-1 puppet-user[9450]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 25 08:59:12 node-1 puppet-user[9450]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 25 08:59:12 node-1 puppet-user[9450]: Finished catalog run in 1.04 seconds
Jul 25 08:59:14 node-1 multipathd: uevent trigger error
Jul 25 08:59:14 node-1 puppet-user[9880]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 08:59:14 node-1 puppet-user[9880]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 25 08:59:14 node-1 puppet-user[9880]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 25 08:59:14 node-1 puppet-user[9880]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 25 08:59:14 node-1 puppet-user[9880]: (/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 25 08:59:14 node-1 puppet-user[9880]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 25 08:59:14 node-1 puppet-user[9880]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 25 08:59:14 node-1 puppet-user[9880]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 25 08:59:14 node-1 puppet-user[9880]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 25 08:59:14 node-1 puppet-user[9880]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 25 08:59:14 node-1 puppet-user[9880]: Finished catalog run in 0.06 seconds
Jul 25 08:59:15 node-1 puppet-user[10350]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 25 08:59:16 node-1 puppet-user[10350]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 25 08:59:16 node-1 puppet-user[10350]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 25 08:59:16 node-1 puppet-user[10350]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 25 08:59:16 node-1 puppet-user[10350]: Finished catalog run in 0.03 seconds
Jul 25 08:59:17 node-1 puppet-user[10821]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 25 08:59:17 node-1 puppet-user[10821]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 25 08:59:17 node-1 puppet-user[10821]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 25 08:59:17 node-1 puppet-user[10821]: Finished catalog run in 0.04 seconds
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.209321 #9085] DEBUG -- : Trying to find block devices
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.209415 #9085] DEBUG -- : Found block device: sda
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.209462 #9085] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.209515 #9085] DEBUG -- : Trying to get list of physical devices
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.209678 #9085] DEBUG -- : Getting udev properties for device: sda
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.211568 #9085] 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 25 08:59:18 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4390", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.211595 #9085] DEBUG -- : Trying to find out if device sda is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.211635 #9085] DEBUG -- : Device sda removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.211669 #9085] DEBUG -- : Device sda seems to be appropriate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.212099 #9085] DEBUG -- : Getting udev properties for device: dm-0
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.213796 #9085] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-ENkC17PLUOUTQBcl3K1KIWhO6zwD5bzLifypWXR7oOfxVOMLIeAokvivzuUyHApY /dev/disk/by-uuid/cc72082d-af21-447a-b9d9-38391571a06c /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-ENkC17PLUOUTQBcl3K1KIWhO6zwD5bzLifypWXR7oOfxVOMLIeAokvivzuUyHApY", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cc72082d-af21-447a-b9d9-38391571a06c", "ID_FS_UUID_ENC"=>"cc72082d-af21-447a-b9d9-38391571a06c", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"92431", "nomdmonddf"=>"1", "nomd
Jul 25 08:59:18 node-1 nailgun-agent: monisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.213820 #9085] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.213850 #9085] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.213865 #9085] DEBUG -- : Device dm-0 seems to be appropriate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.213879 #9085] DEBUG -- : Getting udev properties for device: dm-1
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.215601 #9085] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-B86bn9E3gffJeRpcMedjNCN9KFwSCZU491dENlWqD2ybLMIf6w4achfzfGdus2En /dev/disk/by-uuid/842563f0-3ff2-4372-bb8b-851dc8221e29 /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-B86bn9E3gffJeRpcMedjNCN9KFwSCZU491dENlWqD2ybLMIf6w4achfzfGdus2En", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"842563f0-3ff2-4372-bb8b-851dc8221e29", "ID_FS_UUID_ENC"=>"842563f0-3ff2-4372-bb8b-851dc8221e29", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22
Jul 25 08:59:18 node-1 nailgun-agent: 247", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.215627 #9085] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.215658 #9085] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.215684 #9085] DEBUG -- : Device dm-1 seems to be appropriate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.215735 #9085] DEBUG -- : Getting udev properties for device: dm-2
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.217240 #9085] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-Imqd3VnJeM9i5ooNAdEZeZnGFmlMUZw0PXdXQgRkdz0GuCzVGF5wrm5NOjHX3EEl /dev/disk/by-uuid/13c06cb7-c0dd-432b-aaa0-e8993a120afc /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-Imqd3VnJeM9i5ooNAdEZeZnGFmlMUZw0PXdXQgRkdz0GuCzVGF5wrm5NOjHX3EEl", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"13c06cb7-c0dd-432b-aaa0-e8993a120afc", "ID_FS_UUID_ENC"=>"13c06cb7-c0dd-432b-aaa0-e8993a120afc", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22166", "nomdmond
Jul 25 08:59:18 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.217287 #9085] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.217315 #9085] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.217327 #9085] DEBUG -- : Device dm-2 seems to be appropriate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.217351 #9085] DEBUG -- : Getting udev properties for device: dm-3
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.218945 #9085] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Lh63Ms3dNvYTCGw4VYZ0Fbten8WEovSk2DFcNdMWkaWFScZUN8nGGcWYq81i9Ix0 /dev/disk/by-uuid/88a54109-1ddb-4d54-92ce-11c5bd3f698f /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-Lh63Ms3dNvYTCGw4VYZ0Fbten8WEovSk2DFcNdMWkaWFScZUN8nGGcWYq81i9Ix0", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"88a54109-1ddb-4d54-92ce-11c5bd3f698f", "ID_FS_UUID_ENC"=>"88a54109-1ddb-4d54-92ce-11c5bd3f698f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21114", "nomdmonddf"=>"1", 
Jul 25 08:59:18 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.218972 #9085] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.219036 #9085] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.219052 #9085] DEBUG -- : Device dm-3 seems to be appropriate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.219067 #9085] DEBUG -- : Getting udev properties for device: dm-4
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.220629 #9085] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-x17TdacPleSMExwpF2nj2fO1XWU5279eLlLm2n69fi8d5Kcz2NSO8tRRObyBeLLl /dev/disk/by-uuid/d537cbbd-a9c9-454b-a2c8-30ecb3b357b8 /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-x17TdacPleSMExwpF2nj2fO1XWU5279eLlLm2n69fi8d5Kcz2NSO8tRRObyBeLLl", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d537cbbd-a9c9-454b-a2c8-30ecb3b357b8", "ID_FS_UUID_ENC"=>"d537cbbd-a9c9-454b-a2c8-30ecb3b357b8", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28097", "nomdmonddf"=>"1", "nomd
Jul 25 08:59:18 node-1 nailgun-agent: monisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.220651 #9085] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.220679 #9085] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.220702 #9085] DEBUG -- : Device dm-4 seems to be appropriate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.220716 #9085] DEBUG -- : Getting udev properties for device: dm-5
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.222365 #9085] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-x17TdacPleSMExwpF2nj2fO1XWU5279eX303CAnHBiiojmrNBpv1ETS7Fm45c7qz /dev/disk/by-uuid/0e69a5e4-2de3-455b-a75c-7ed004afcc9d /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-x17TdacPleSMExwpF2nj2fO1XWU5279eX303CAnHBiiojmrNBpv1ETS7Fm45c7qz", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"0e69a5e4-2de3-455b-a75c-7ed004afcc9d", "ID_FS_UUID_ENC"=>"0e69a5e4-2de3-455b-a75c-7ed004afcc9d", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28439", "nomdmonddf"=>"1", "nomdmonisw"
Jul 25 08:59:18 node-1 nailgun-agent: =>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.222388 #9085] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.222419 #9085] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.222432 #9085] DEBUG -- : Device dm-5 seems to be appropriate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.222474 #9085] DEBUG -- : Getting udev properties for device: ram0
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.224064 #9085] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56442", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.224090 #9085] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.224125 #9085] DEBUG -- : Device ram0 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.224145 #9085] DEBUG -- : Getting udev properties for device: ram1
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.225546 #9085] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56558", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.225581 #9085] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.225616 #9085] DEBUG -- : Device ram1 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.225636 #9085] DEBUG -- : Getting udev properties for device: ram2
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.227060 #9085] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57248", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.227082 #9085] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.227135 #9085] DEBUG -- : Device ram2 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.227170 #9085] DEBUG -- : Getting udev properties for device: ram3
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.228588 #9085] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57285", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.228610 #9085] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.228643 #9085] DEBUG -- : Device ram3 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.228675 #9085] DEBUG -- : Getting udev properties for device: ram4
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.230260 #9085] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57349", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.230303 #9085] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.230345 #9085] DEBUG -- : Device ram4 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.230369 #9085] DEBUG -- : Getting udev properties for device: ram5
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.231924 #9085] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57449", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.231951 #9085] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.231991 #9085] DEBUG -- : Device ram5 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.232040 #9085] DEBUG -- : Getting udev properties for device: ram6
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.233520 #9085] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57528", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.233545 #9085] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.233579 #9085] DEBUG -- : Device ram6 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.233619 #9085] DEBUG -- : Getting udev properties for device: ram7
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.235065 #9085] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57607", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.235088 #9085] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.235135 #9085] DEBUG -- : Device ram7 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.235154 #9085] DEBUG -- : Getting udev properties for device: ram8
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.236776 #9085] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57712", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.236805 #9085] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.236842 #9085] DEBUG -- : Device ram8 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.236862 #9085] DEBUG -- : Getting udev properties for device: ram9
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.238483 #9085] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57783", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.238509 #9085] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.238567 #9085] DEBUG -- : Device ram9 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.238587 #9085] DEBUG -- : Getting udev properties for device: loop0
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.240148 #9085] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55504", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.240185 #9085] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.240221 #9085] DEBUG -- : Device loop0 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.240254 #9085] DEBUG -- : Getting udev properties for device: loop1
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.241851 #9085] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55592", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.241876 #9085] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.241910 #9085] DEBUG -- : Device loop1 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.241931 #9085] DEBUG -- : Getting udev properties for device: loop2
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.243415 #9085] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55687", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.243441 #9085] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.243492 #9085] DEBUG -- : Device loop2 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.243514 #9085] DEBUG -- : Getting udev properties for device: loop3
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.244968 #9085] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55757", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.244991 #9085] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.245038 #9085] DEBUG -- : Device loop3 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.245058 #9085] DEBUG -- : Getting udev properties for device: loop4
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.246460 #9085] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55839", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.246481 #9085] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.246530 #9085] DEBUG -- : Device loop4 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.246549 #9085] DEBUG -- : Getting udev properties for device: loop5
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.248010 #9085] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55914", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.248049 #9085] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.248085 #9085] DEBUG -- : Device loop5 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.248104 #9085] DEBUG -- : Getting udev properties for device: loop6
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.250252 #9085] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56185", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.250329 #9085] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.250392 #9085] DEBUG -- : Device loop6 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.250421 #9085] DEBUG -- : Getting udev properties for device: loop7
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.252800 #9085] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56337", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.252862 #9085] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.252958 #9085] DEBUG -- : Device loop7 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.252988 #9085] DEBUG -- : Getting udev properties for device: ram10
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.255430 #9085] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56659", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.255499 #9085] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.255571 #9085] DEBUG -- : Device ram10 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.255598 #9085] DEBUG -- : Getting udev properties for device: ram11
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.257606 #9085] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56721", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.257638 #9085] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.257680 #9085] DEBUG -- : Device ram11 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.257713 #9085] DEBUG -- : Getting udev properties for device: ram12
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.259862 #9085] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56828", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.259936 #9085] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.259984 #9085] DEBUG -- : Device ram12 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.260026 #9085] DEBUG -- : Getting udev properties for device: ram13
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.262201 #9085] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56931", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.262275 #9085] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.262323 #9085] DEBUG -- : Device ram13 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.262353 #9085] DEBUG -- : Getting udev properties for device: ram14
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.264751 #9085] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57034", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.264807 #9085] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.264873 #9085] DEBUG -- : Device ram14 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.270943 #9085] DEBUG -- : Getting udev properties for device: ram15
Jul 25 08:59:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.272934 #9085] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57150", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.272965 #9085] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.272998 #9085] DEBUG -- : Device ram15 removable parameter: "0"
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273037 #9085] 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 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273097 #9085] DEBUG -- : Block device seems to be physical data storage: sda
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273143 #9085] DEBUG -- : Found block device: dm-0
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273159 #9085] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273172 #9085] DEBUG -- : Found block device: dm-1
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273182 #9085] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273191 #9085] DEBUG -- : Found block device: dm-2
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273202 #9085] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273211 #9085] DEBUG -- : Found block device: dm-3
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273220 #9085] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273260 #9085] DEBUG -- : Found block device: dm-4
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273272 #9085] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273281 #9085] DEBUG -- : Found block device: dm-5
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273292 #9085] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273300 #9085] DEBUG -- : Found block device: ram0
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273310 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273318 #9085] DEBUG -- : Found block device: ram1
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273327 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273335 #9085] DEBUG -- : Found block device: ram2
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273346 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273395 #9085] DEBUG -- : Found block device: ram3
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273405 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273414 #9085] DEBUG -- : Found block device: ram4
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273423 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273431 #9085] DEBUG -- : Found block device: ram5
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273441 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273449 #9085] DEBUG -- : Found block device: ram6
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273459 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273467 #9085] DEBUG -- : Found block device: ram7
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273512 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273521 #9085] DEBUG -- : Found block device: ram8
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273531 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273539 #9085] DEBUG -- : Found block device: ram9
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273549 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273557 #9085] DEBUG -- : Found block device: loop0
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273568 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273576 #9085] DEBUG -- : Found block device: loop1
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273586 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273624 #9085] DEBUG -- : Found block device: loop2
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273634 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273643 #9085] DEBUG -- : Found block device: loop3
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273652 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273660 #9085] DEBUG -- : Found block device: loop4
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273669 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273677 #9085] DEBUG -- : Found block device: loop5
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273686 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273694 #9085] DEBUG -- : Found block device: loop6
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273743 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273753 #9085] DEBUG -- : Found block device: loop7
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273763 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273771 #9085] DEBUG -- : Found block device: ram10
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273782 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273790 #9085] DEBUG -- : Found block device: ram11
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273799 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273807 #9085] DEBUG -- : Found block device: ram12
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273816 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273825 #9085] DEBUG -- : Found block device: ram13
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273867 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273875 #9085] DEBUG -- : Found block device: ram14
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273885 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273893 #9085] DEBUG -- : Found block device: ram15
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273902 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.273932 #9085] 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 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.365913 #9085] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 25 08:59:18 node-1 nailgun-agent: D, [2016-07-25T08:59:18.365972 #9085] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 25 08:59:19 node-1 puppet-user[11291]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 25 08:59:19 node-1 puppet-user[11291]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Jul 25 08:59:19 node-1 puppet-user[11291]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 25 08:59:21 node-1 puppet-user[11291]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Jul 25 08:59:21 node-1 puppet-user[11291]: Finished catalog run in 1.90 seconds
Jul 25 08:59:22 node-1 kernel: [   68.145110] init: plymouth-upstart-bridge main process ended, respawning
Jul 25 08:59:22 node-1 puppet-agent[8922]: Could not run: SIGTERM
Jul 25 08:59:22 node-1 kernel: [   68.426805] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 25 08:59:22 node-1 ec2: 
Jul 25 08:59:22 node-1 ec2: #############################################################
Jul 25 08:59:22 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 25 08:59:22 node-1 ec2: 1024 24:33:4f:97:ab:4e:5d:c8:11:c6:86:01:34:c8:ba:b4  root@node-1.domain.tld (DSA)
Jul 25 08:59:22 node-1 ec2: 256 5f:f7:1b:b5:22:d8:3b:fb:5d:b5:a5:57:c6:43:a9:e3  root@node-1.domain.tld (ECDSA)
Jul 25 08:59:22 node-1 ec2: 256 d9:b9:32:98:d3:61:03:81:f6:b4:60:57:b3:fc:d0:5e  root@node-1.domain.tld (ED25519)
Jul 25 08:59:22 node-1 ec2: 2048 45:19:db:29:af:ba:20:1b:cf:88:69:96:76:5c:b7:6e  root@node-1.domain.tld (RSA)
Jul 25 08:59:22 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 25 08:59:22 node-1 ec2: #############################################################
Jul 25 08:59:22 node-1 puppet-user[12003]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 25 08:59:23 node-1 puppet-user[12003]: Compiled catalog for node-1.domain.tld in environment production in 0.24 seconds
Jul 25 08:59:23 node-1 puppet-user[12003]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 25 08:59:23 node-1 puppet-user[12003]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Jul 25 08:59:23 node-1 puppet-user[12003]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 25 08:59:23 node-1 puppet-user[12003]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 25 08:59:23 node-1 puppet-user[12003]: Finished catalog run in 0.25 seconds
Jul 25 08:59:24 node-1 puppet-user[12666]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 25 08:59:25 node-1 puppet-user[12666]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 25 08:59:25 node-1 puppet-user[12666]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 25 08:59:25 node-1 kernel: [   71.264582] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 25 08:59:25 node-1 kernel: [   71.264632] 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 25 08:59:25 node-1 puppet-user[12666]: (/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 25 08:59:25 node-1 puppet-user[12666]: Finished catalog run in 0.05 seconds
Jul 25 08:59:26 node-1 puppet-user[13132]: (Scope(Class[main])) MODULAR: sync_time
Jul 25 08:59:26 node-1 puppet-user[13132]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 25 08:59:27 node-1 ntpdate[13552]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 25 08:59:30 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535196 #9085] DEBUG -- : Trying to find block devices
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535304 #9085] DEBUG -- : Found block device: sda
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535329 #9085] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535346 #9085] DEBUG -- : Block device seems to be physical data storage: sda
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535367 #9085] DEBUG -- : Found block device: dm-0
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535379 #9085] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535390 #9085] DEBUG -- : Found block device: dm-1
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535399 #9085] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535409 #9085] DEBUG -- : Found block device: dm-2
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535435 #9085] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535445 #9085] DEBUG -- : Found block device: dm-3
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535454 #9085] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535463 #9085] DEBUG -- : Found block device: dm-4
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535473 #9085] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535481 #9085] DEBUG -- : Found block device: dm-5
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535491 #9085] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535500 #9085] DEBUG -- : Found block device: ram0
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535520 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535528 #9085] DEBUG -- : Found block device: ram1
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535555 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535565 #9085] DEBUG -- : Found block device: ram2
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535575 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535583 #9085] DEBUG -- : Found block device: ram3
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535591 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535600 #9085] DEBUG -- : Found block device: ram4
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535609 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535617 #9085] DEBUG -- : Found block device: ram5
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535649 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535659 #9085] DEBUG -- : Found block device: ram6
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535669 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535677 #9085] DEBUG -- : Found block device: ram7
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535686 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535694 #9085] DEBUG -- : Found block device: ram8
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535703 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535712 #9085] DEBUG -- : Found block device: ram9
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535748 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535756 #9085] DEBUG -- : Found block device: loop0
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535766 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535774 #9085] DEBUG -- : Found block device: loop1
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535783 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535791 #9085] DEBUG -- : Found block device: loop2
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535800 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535808 #9085] DEBUG -- : Found block device: loop3
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535817 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535852 #9085] DEBUG -- : Found block device: loop4
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535861 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535869 #9085] DEBUG -- : Found block device: loop5
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535878 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535886 #9085] DEBUG -- : Found block device: loop6
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535895 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535904 #9085] DEBUG -- : Found block device: loop7
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535913 #9085] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535921 #9085] DEBUG -- : Found block device: ram10
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535929 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535938 #9085] DEBUG -- : Found block device: ram11
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535973 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535981 #9085] DEBUG -- : Found block device: ram12
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535990 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.535998 #9085] DEBUG -- : Found block device: ram13
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.536007 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.536015 #9085] DEBUG -- : Found block device: ram14
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.536024 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.536031 #9085] DEBUG -- : Found block device: ram15
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.536040 #9085] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.536095 #9085] 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 25 08:59:30 node-1 nailgun-agent: D, [2016-07-25T08:59:30.753333 #9085] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 25 08:59:30 node-1 nailgun-agent: I, [2016-07-25T08:59:30.753504 #9085]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 25 08:59:33 node-1 ntpdate[13552]: adjust time server 10.20.0.2 offset 0.000540 sec
Jul 25 08:59:33 node-1 puppet-user[13132]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 25 08:59:33 node-1 puppet-user[13132]: Finished catalog run in 6.16 seconds
Jul 25 08:59:39 node-1 puppet-user[13865]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 08:59:39 node-1 puppet-user[13865]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 25 08:59:39 node-1 puppet-user[13865]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 25 08:59:39 node-1 puppet-user[13865]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 25 08:59:39 node-1 puppet-user[13865]: Finished catalog run in 0.07 seconds
Jul 25 08:59:41 node-1 puppet-user[14327]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 25 08:59:42 node-1 puppet-user[14327]: Compiled catalog for node-1.domain.tld in environment production in 1.21 seconds
Jul 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:42 node-1 puppet-user[14327]: (/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 25 08:59:51 node-1 puppet-user[14327]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 25 08:59:51 node-1 puppet-user[14327]: Finished catalog run in 9.00 seconds
Jul 25 08:59:53 node-1 puppet-user[15163]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 25 08:59:53 node-1 puppet-user[15163]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Jul 25 08:59:57 node-1 puppet-user[15163]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 25 09:00:01 node-1 CRON[16224]: (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 25 09:00:24 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 09:00:24 node-1 nailgun-agent: I, [2016-07-25T09:00:24.942326 #16227]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 09:00:29 node-1 puppet-user[15163]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 25 09:00:29 node-1 puppet-user[15163]: Finished catalog run in 36.27 seconds
Jul 25 09:00:31 node-1 puppet-user[17853]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 25 09:00:31 node-1 puppet-user[17853]: Compiled catalog for node-1.domain.tld in environment production in 0.56 seconds
Jul 25 09:00:32 node-1 puppet-user[17853]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 25 09:00:32 node-1 puppet-user[17853]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 25 09:00:32 node-1 puppet-user[17853]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 25 09:00:32 node-1 puppet-user[17853]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 25 09:00:32 node-1 puppet-user[17853]: Finished catalog run in 0.08 seconds
Jul 25 09:00:34 node-1 puppet-user[18320]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 25 09:00:34 node-1 puppet-user[18320]: Compiled catalog for node-1.domain.tld in environment production in 0.93 seconds
Jul 25 09:00:35 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 25 09:00:35 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 25 09:00:35 node-1 crontab[18773]: (root) LIST (root)
Jul 25 09:00:35 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 25 09:00:35 node-1 crontab[18774]: (root) REPLACE (root)
Jul 25 09:00:37 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 25 09:00:37 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 09:00:38 node-1 nailgun-agent: I, [2016-07-25T09:00:38.083304 #16227]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 25 09:00:38 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 25 09:00:39 node-1 puppet-user[18320]: (/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 25 09:00:39 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8374" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 09:00:39 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 25 09:00:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:00:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:00:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:00:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:00:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:00:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:00 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:00 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:00 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:00 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:00 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:00 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:49 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:49 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:49 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:49 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:49 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:49 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:51 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:51 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:51 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:51 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:51 node-1 multipathd: uevent trigger error
<27>Jul 25 09:01:51 node-1 multipathd: uevent trigger error
<27>Jul 25 09:02:34 node-1 ntpdate[2410]: no servers can be used, exiting
<27>Jul 25 09:02:34 node-1 ntpdate[2632]: no servers can be used, exiting
<27>Jul 25 09:03:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:09 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:09 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:09 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:09 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:09 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:23 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:23 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:23 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:23 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:23 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:23 node-1 multipathd: uevent trigger error
<27>Jul 25 09:03:23 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 09:04:34 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 09:04:39 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 09:04:40 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 09:04:45 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 09:04:51 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 09:04:51 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 09:04:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:04:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:11 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:13 node-1 haproxy[22826]: 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 25 09:05:14 node-1 haproxy[22830]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:14 node-1 haproxy[22830]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:14 node-1 haproxy[22830]: proxy mysqld has no server available!
<27>Jul 25 09:05:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:20 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:22 node-1 haproxy[25525]: 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 25 09:05:23 node-1 haproxy[25529]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:23 node-1 haproxy[25529]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:23 node-1 haproxy[25529]: proxy mysqld has no server available!
<129>Jul 25 09:05:23 node-1 haproxy[25529]: 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 25 09:05:24 node-1 haproxy[25529]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:24 node-1 haproxy[25529]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:24 node-1 haproxy[25529]: proxy object-storage has no server available!
<27>Jul 25 09:05:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:25 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:27 node-1 haproxy[26920]: 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 25 09:05:28 node-1 haproxy[26924]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:28 node-1 haproxy[26924]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:28 node-1 haproxy[26924]: proxy neutron has no server available!
<129>Jul 25 09:05:28 node-1 haproxy[26924]: 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 25 09:05:28 node-1 haproxy[26924]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:29 node-1 haproxy[26924]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:29 node-1 haproxy[26924]: proxy mysqld has no server available!
<129>Jul 25 09:05:29 node-1 haproxy[26924]: 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 25 09:05:29 node-1 haproxy[26924]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:29 node-1 haproxy[26924]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:29 node-1 haproxy[26924]: proxy object-storage has no server available!
<27>Jul 25 09:05:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:31 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:31 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:33 node-1 haproxy[28358]: 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 25 09:05:33 node-1 haproxy[28358]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:33 node-1 haproxy[28358]: Server keystone-1/node-3 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 25 09:05:33 node-1 haproxy[28358]: proxy keystone-1 has no server available!
<129>Jul 25 09:05:33 node-1 haproxy[28358]: 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 25 09:05:34 node-1 haproxy[28362]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:34 node-1 haproxy[28362]: Server keystone-2/node-3 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 25 09:05:34 node-1 haproxy[28362]: proxy keystone-2 has no server available!
<129>Jul 25 09:05:34 node-1 haproxy[28362]: 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 25 09:05:34 node-1 haproxy[28362]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:34 node-1 haproxy[28362]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:34 node-1 haproxy[28362]: proxy neutron has no server available!
<129>Jul 25 09:05:34 node-1 haproxy[28362]: 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 25 09:05:34 node-1 haproxy[28362]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:34 node-1 haproxy[28362]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:34 node-1 haproxy[28362]: proxy mysqld has no server available!
<129>Jul 25 09:05:35 node-1 haproxy[28362]: 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 25 09:05:35 node-1 haproxy[28362]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:35 node-1 haproxy[28362]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:35 node-1 haproxy[28362]: proxy object-storage has no server available!
<27>Jul 25 09:05:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:36 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:38 node-1 haproxy[29918]: 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 25 09:05:38 node-1 haproxy[29918]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:39 node-1 haproxy[29932]: Server keystone-1/node-3 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 25 09:05:39 node-1 haproxy[29932]: proxy keystone-1 has no server available!
<129>Jul 25 09:05:39 node-1 haproxy[29932]: 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 25 09:05:39 node-1 haproxy[29932]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:39 node-1 haproxy[29932]: Server keystone-2/node-3 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 25 09:05:39 node-1 haproxy[29932]: proxy keystone-2 has no server available!
<129>Jul 25 09:05:39 node-1 haproxy[29932]: 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 25 09:05:39 node-1 haproxy[29932]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:39 node-1 haproxy[29932]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:39 node-1 haproxy[29932]: proxy neutron has no server available!
<129>Jul 25 09:05:39 node-1 haproxy[29932]: 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 25 09:05:39 node-1 haproxy[29932]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:40 node-1 haproxy[29932]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:40 node-1 haproxy[29932]: proxy mysqld has no server available!
<129>Jul 25 09:05:40 node-1 haproxy[29932]: 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 25 09:05:40 node-1 haproxy[29932]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:40 node-1 haproxy[29932]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:40 node-1 haproxy[29932]: proxy object-storage has no server available!
<129>Jul 25 09:05:40 node-1 haproxy[29932]: 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 25 09:05:40 node-1 haproxy[29932]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:40 node-1 haproxy[29932]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:40 node-1 haproxy[29932]: proxy aodh has no server available!
<27>Jul 25 09:05:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:42 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:44 node-1 haproxy[31297]: 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 25 09:05:44 node-1 haproxy[31297]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:44 node-1 haproxy[31297]: Server keystone-1/node-3 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 25 09:05:44 node-1 haproxy[31297]: proxy keystone-1 has no server available!
<129>Jul 25 09:05:44 node-1 haproxy[31297]: 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 25 09:05:44 node-1 haproxy[31297]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:44 node-1 haproxy[31297]: Server keystone-2/node-3 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 25 09:05:44 node-1 haproxy[31297]: proxy keystone-2 has no server available!
<129>Jul 25 09:05:44 node-1 haproxy[31297]: 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 25 09:05:45 node-1 haproxy[31303]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:45 node-1 haproxy[31303]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:45 node-1 haproxy[31303]: proxy neutron has no server available!
<129>Jul 25 09:05:45 node-1 haproxy[31303]: 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 25 09:05:45 node-1 haproxy[31303]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:45 node-1 haproxy[31303]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:45 node-1 haproxy[31303]: proxy mysqld has no server available!
<129>Jul 25 09:05:45 node-1 haproxy[31303]: 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 25 09:05:45 node-1 haproxy[31303]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:45 node-1 haproxy[31303]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:45 node-1 haproxy[31303]: proxy object-storage has no server available!
<129>Jul 25 09:05:45 node-1 haproxy[31303]: 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 25 09:05:45 node-1 haproxy[31303]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:45 node-1 haproxy[31303]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:45 node-1 haproxy[31303]: proxy aodh has no server available!
<129>Jul 25 09:05:46 node-1 haproxy[31303]: 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 25 09:05:46 node-1 haproxy[31303]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:46 node-1 haproxy[31303]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:46 node-1 haproxy[31303]: proxy ceilometer has no server available!
<27>Jul 25 09:05:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:47 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:49 node-1 haproxy[32667]: 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 25 09:05:50 node-1 haproxy[32671]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:50 node-1 haproxy[32671]: Server keystone-1/node-3 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 25 09:05:50 node-1 haproxy[32671]: proxy keystone-1 has no server available!
<129>Jul 25 09:05:50 node-1 haproxy[32671]: 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 25 09:05:50 node-1 haproxy[32671]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:50 node-1 haproxy[32671]: Server keystone-2/node-3 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 25 09:05:50 node-1 haproxy[32671]: proxy keystone-2 has no server available!
<129>Jul 25 09:05:50 node-1 haproxy[32671]: 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 25 09:05:50 node-1 haproxy[32671]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:50 node-1 haproxy[32671]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:50 node-1 haproxy[32671]: proxy neutron has no server available!
<129>Jul 25 09:05:50 node-1 haproxy[32671]: 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 25 09:05:50 node-1 haproxy[32671]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:51 node-1 haproxy[32671]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:51 node-1 haproxy[32671]: proxy mysqld has no server available!
<129>Jul 25 09:05:51 node-1 haproxy[32671]: 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 25 09:05:51 node-1 haproxy[32671]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:51 node-1 haproxy[32671]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:51 node-1 haproxy[32671]: proxy object-storage has no server available!
<129>Jul 25 09:05:51 node-1 haproxy[32671]: 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 25 09:05:51 node-1 haproxy[32671]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:51 node-1 haproxy[32671]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:51 node-1 haproxy[32671]: proxy aodh has no server available!
<129>Jul 25 09:05:51 node-1 haproxy[32671]: 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 25 09:05:51 node-1 haproxy[32671]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:51 node-1 haproxy[32671]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:51 node-1 haproxy[32671]: proxy ceilometer has no server available!
<27>Jul 25 09:05:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:53 node-1 multipathd: uevent trigger error
<129>Jul 25 09:05:55 node-1 haproxy[1613]: 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 25 09:05:55 node-1 haproxy[1613]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:55 node-1 haproxy[1613]: 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 25 09:05:55 node-1 haproxy[1613]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:55 node-1 haproxy[1613]: Server keystone-1/node-3 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 25 09:05:55 node-1 haproxy[1613]: proxy keystone-1 has no server available!
<129>Jul 25 09:05:55 node-1 haproxy[1613]: 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 25 09:05:55 node-1 haproxy[1613]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:55 node-1 haproxy[1613]: Server keystone-2/node-3 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 25 09:05:55 node-1 haproxy[1613]: proxy keystone-2 has no server available!
<129>Jul 25 09:05:56 node-1 haproxy[1617]: 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 25 09:05:56 node-1 haproxy[1617]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:56 node-1 haproxy[1617]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:56 node-1 haproxy[1617]: proxy neutron has no server available!
<129>Jul 25 09:05:56 node-1 haproxy[1617]: 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 25 09:05:56 node-1 haproxy[1617]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:56 node-1 haproxy[1617]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:56 node-1 haproxy[1617]: proxy mysqld has no server available!
<129>Jul 25 09:05:56 node-1 haproxy[1617]: 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 25 09:05:56 node-1 haproxy[1617]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:56 node-1 haproxy[1617]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:56 node-1 haproxy[1617]: proxy object-storage has no server available!
<129>Jul 25 09:05:56 node-1 haproxy[1617]: 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 25 09:05:56 node-1 haproxy[1617]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:56 node-1 haproxy[1617]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:56 node-1 haproxy[1617]: proxy aodh has no server available!
<129>Jul 25 09:05:57 node-1 haproxy[1617]: 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 25 09:05:57 node-1 haproxy[1617]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:05:57 node-1 haproxy[1617]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 25 09:05:57 node-1 haproxy[1617]: proxy ceilometer has no server available!
<27>Jul 25 09:05:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:58 node-1 multipathd: uevent trigger error
<27>Jul 25 09:05:58 node-1 multipathd: uevent trigger error
<129>Jul 25 09:06:01 node-1 haproxy[3009]: 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 25 09:06:01 node-1 haproxy[3009]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:01 node-1 haproxy[3009]: 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 25 09:06:01 node-1 haproxy[3009]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:01 node-1 haproxy[3009]: Server keystone-1/node-3 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 25 09:06:01 node-1 haproxy[3009]: proxy keystone-1 has no server available!
<129>Jul 25 09:06:01 node-1 haproxy[3009]: 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 25 09:06:01 node-1 haproxy[3009]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:01 node-1 haproxy[3009]: Server keystone-2/node-3 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 25 09:06:01 node-1 haproxy[3009]: proxy keystone-2 has no server available!
<129>Jul 25 09:06:01 node-1 haproxy[3009]: 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 25 09:06:01 node-1 haproxy[3009]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:01 node-1 haproxy[3009]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:01 node-1 haproxy[3009]: proxy glance-api has no server available!
<129>Jul 25 09:06:01 node-1 haproxy[3009]: 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 25 09:06:01 node-1 haproxy[3009]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:01 node-1 haproxy[3009]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:01 node-1 haproxy[3009]: proxy glance-glare has no server available!
<129>Jul 25 09:06:01 node-1 haproxy[3009]: 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 25 09:06:02 node-1 haproxy[3013]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:02 node-1 haproxy[3013]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:02 node-1 haproxy[3013]: proxy neutron has no server available!
<129>Jul 25 09:06:02 node-1 haproxy[3013]: 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 25 09:06:02 node-1 haproxy[3013]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:02 node-1 haproxy[3013]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:02 node-1 haproxy[3013]: proxy glance-registry has no server available!
<129>Jul 25 09:06:02 node-1 haproxy[3013]: 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 25 09:06:02 node-1 haproxy[3013]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:02 node-1 haproxy[3013]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:02 node-1 haproxy[3013]: proxy mysqld has no server available!
<129>Jul 25 09:06:02 node-1 haproxy[3013]: 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 25 09:06:02 node-1 haproxy[3013]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:02 node-1 haproxy[3013]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:02 node-1 haproxy[3013]: proxy object-storage has no server available!
<129>Jul 25 09:06:02 node-1 haproxy[3013]: 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 25 09:06:02 node-1 haproxy[3013]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:02 node-1 haproxy[3013]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:02 node-1 haproxy[3013]: proxy aodh has no server available!
<129>Jul 25 09:06:02 node-1 haproxy[3013]: 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 25 09:06:02 node-1 haproxy[3013]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:03 node-1 haproxy[3013]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:03 node-1 haproxy[3013]: proxy ceilometer has no server available!
<27>Jul 25 09:06:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:04 node-1 multipathd: uevent trigger error
<129>Jul 25 09:06:07 node-1 haproxy[4431]: 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 25 09:06:07 node-1 haproxy[4431]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:07 node-1 haproxy[4431]: 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 25 09:06:07 node-1 haproxy[4431]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:07 node-1 haproxy[4431]: Server keystone-1/node-3 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 25 09:06:07 node-1 haproxy[4431]: proxy keystone-1 has no server available!
<129>Jul 25 09:06:07 node-1 haproxy[4431]: 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 25 09:06:07 node-1 haproxy[4431]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:07 node-1 haproxy[4431]: Server keystone-2/node-3 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 25 09:06:07 node-1 haproxy[4431]: proxy keystone-2 has no server available!
<129>Jul 25 09:06:07 node-1 haproxy[4431]: 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 25 09:06:07 node-1 haproxy[4431]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:07 node-1 haproxy[4431]: Server nova-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:07 node-1 haproxy[4431]: proxy nova-api has no server available!
<129>Jul 25 09:06:07 node-1 haproxy[4431]: 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 25 09:06:07 node-1 haproxy[4431]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:07 node-1 haproxy[4431]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:07 node-1 haproxy[4431]: proxy nova-metadata-api has no server available!
<129>Jul 25 09:06:07 node-1 haproxy[4431]: 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 25 09:06:07 node-1 haproxy[4431]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:07 node-1 haproxy[4431]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:07 node-1 haproxy[4431]: proxy glance-api has no server available!
<129>Jul 25 09:06:07 node-1 haproxy[4431]: 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 25 09:06:07 node-1 haproxy[4431]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:08 node-1 haproxy[4435]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:08 node-1 haproxy[4435]: proxy glance-glare has no server available!
<129>Jul 25 09:06:08 node-1 haproxy[4435]: 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 25 09:06:08 node-1 haproxy[4435]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:08 node-1 haproxy[4435]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:08 node-1 haproxy[4435]: proxy neutron has no server available!
<129>Jul 25 09:06:08 node-1 haproxy[4435]: 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 25 09:06:08 node-1 haproxy[4435]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:08 node-1 haproxy[4435]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:08 node-1 haproxy[4435]: proxy glance-registry has no server available!
<129>Jul 25 09:06:08 node-1 haproxy[4435]: 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 25 09:06:08 node-1 haproxy[4435]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:08 node-1 haproxy[4435]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:08 node-1 haproxy[4435]: proxy mysqld has no server available!
<129>Jul 25 09:06:08 node-1 haproxy[4435]: 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 25 09:06:08 node-1 haproxy[4435]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:08 node-1 haproxy[4435]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:08 node-1 haproxy[4435]: proxy object-storage has no server available!
<129>Jul 25 09:06:08 node-1 haproxy[4435]: 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 25 09:06:08 node-1 haproxy[4435]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:08 node-1 haproxy[4435]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:08 node-1 haproxy[4435]: proxy aodh has no server available!
<129>Jul 25 09:06:08 node-1 haproxy[4435]: 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 25 09:06:08 node-1 haproxy[4435]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:08 node-1 haproxy[4435]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:08 node-1 haproxy[4435]: proxy ceilometer has no server available!
<129>Jul 25 09:06:08 node-1 haproxy[4435]: 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 25 09:06:08 node-1 haproxy[4435]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:09 node-1 haproxy[4435]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:09 node-1 haproxy[4435]: proxy nova-novncproxy has no server available!
<27>Jul 25 09:06:10 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:10 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:10 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:10 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:10 node-1 multipathd: uevent trigger error
<129>Jul 25 09:06:12 node-1 haproxy[5777]: 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 25 09:06:12 node-1 haproxy[5777]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:12 node-1 haproxy[5777]: 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 25 09:06:12 node-1 haproxy[5777]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:12 node-1 haproxy[5777]: Server keystone-1/node-3 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 25 09:06:12 node-1 haproxy[5777]: proxy keystone-1 has no server available!
<129>Jul 25 09:06:12 node-1 haproxy[5777]: 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 25 09:06:12 node-1 haproxy[5777]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:12 node-1 haproxy[5777]: Server keystone-2/node-3 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 25 09:06:12 node-1 haproxy[5777]: proxy keystone-2 has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:13 node-1 haproxy[5781]: Server nova-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:13 node-1 haproxy[5781]: proxy nova-api has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:13 node-1 haproxy[5781]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:13 node-1 haproxy[5781]: proxy nova-metadata-api has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:13 node-1 haproxy[5781]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:13 node-1 haproxy[5781]: proxy cinder-api has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:13 node-1 haproxy[5781]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:13 node-1 haproxy[5781]: proxy glance-api has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:13 node-1 haproxy[5781]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:13 node-1 haproxy[5781]: proxy glance-glare has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:13 node-1 haproxy[5781]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:13 node-1 haproxy[5781]: proxy neutron has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:13 node-1 haproxy[5781]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:13 node-1 haproxy[5781]: proxy glance-registry has no server available!
<129>Jul 25 09:06:13 node-1 haproxy[5781]: 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 25 09:06:13 node-1 haproxy[5781]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:14 node-1 haproxy[5781]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:14 node-1 haproxy[5781]: proxy mysqld has no server available!
<129>Jul 25 09:06:14 node-1 haproxy[5781]: 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 25 09:06:14 node-1 haproxy[5781]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:14 node-1 haproxy[5781]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:14 node-1 haproxy[5781]: proxy object-storage has no server available!
<129>Jul 25 09:06:14 node-1 haproxy[5781]: 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 25 09:06:14 node-1 haproxy[5781]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:14 node-1 haproxy[5781]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:14 node-1 haproxy[5781]: proxy aodh has no server available!
<129>Jul 25 09:06:14 node-1 haproxy[5781]: 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 25 09:06:14 node-1 haproxy[5781]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:14 node-1 haproxy[5781]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:14 node-1 haproxy[5781]: proxy ceilometer has no server available!
<129>Jul 25 09:06:14 node-1 haproxy[5781]: 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 25 09:06:14 node-1 haproxy[5781]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:14 node-1 haproxy[5781]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:14 node-1 haproxy[5781]: proxy nova-novncproxy has no server available!
<27>Jul 25 09:06:15 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:15 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:15 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:15 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:15 node-1 multipathd: uevent trigger error
<129>Jul 25 09:06:18 node-1 haproxy[7138]: 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 25 09:06:18 node-1 haproxy[7138]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:18 node-1 haproxy[7138]: 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 25 09:06:18 node-1 haproxy[7138]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:18 node-1 haproxy[7138]: Server keystone-1/node-3 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 25 09:06:18 node-1 haproxy[7138]: proxy keystone-1 has no server available!
<129>Jul 25 09:06:18 node-1 haproxy[7138]: 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 25 09:06:18 node-1 haproxy[7138]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:18 node-1 haproxy[7138]: Server keystone-2/node-3 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 25 09:06:18 node-1 haproxy[7138]: proxy keystone-2 has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Server nova-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy nova-api has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy nova-metadata-api has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy cinder-api has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Server glance-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy glance-api has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy glance-glare has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy neutron has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy glance-registry has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy mysqld has no server available!
<129>Jul 25 09:06:19 node-1 haproxy[7144]: 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 25 09:06:19 node-1 haproxy[7144]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:19 node-1 haproxy[7144]: Server object-storage/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:19 node-1 haproxy[7144]: proxy object-storage has no server available!
<129>Jul 25 09:06:20 node-1 haproxy[7144]: 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 25 09:06:20 node-1 haproxy[7144]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:20 node-1 haproxy[7144]: Server aodh/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:20 node-1 haproxy[7144]: proxy aodh has no server available!
<129>Jul 25 09:06:20 node-1 haproxy[7144]: 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 25 09:06:20 node-1 haproxy[7144]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:20 node-1 haproxy[7144]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:20 node-1 haproxy[7144]: proxy ceilometer has no server available!
<129>Jul 25 09:06:20 node-1 haproxy[7144]: 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 25 09:06:20 node-1 haproxy[7144]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:20 node-1 haproxy[7144]: Server heat-api/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:20 node-1 haproxy[7144]: proxy heat-api has no server available!
<129>Jul 25 09:06:20 node-1 haproxy[7144]: 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 25 09:06:20 node-1 haproxy[7144]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:20 node-1 haproxy[7144]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:20 node-1 haproxy[7144]: proxy heat-api-cfn has no server available!
<129>Jul 25 09:06:20 node-1 haproxy[7144]: 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 25 09:06:20 node-1 haproxy[7144]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:20 node-1 haproxy[7144]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:20 node-1 haproxy[7144]: proxy heat-api-cloudwatch has no server available!
<129>Jul 25 09:06:20 node-1 haproxy[7144]: 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 25 09:06:20 node-1 haproxy[7144]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:06:20 node-1 haproxy[7144]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection 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 25 09:06:20 node-1 haproxy[7144]: proxy nova-novncproxy has no server available!
<27>Jul 25 09:06:21 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:21 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:21 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:21 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:21 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:25 node-1 multipathd: uevent trigger error
<27>Jul 25 09:06:34 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 25 09:06:59 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 25 09:07:01 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 25 09:07:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:07:37 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 09:07:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:07:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:07:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:07:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:07:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:14 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:14 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:14 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:14 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:14 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:30 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 25 09:10:40 node-1 apache2_error [Mon Jul 25 09:10:33.607339 2016] [mpm_event:notice] [pid 16210:tid 140119475795840] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 09:10:40 node-1 apache2_error [Mon Jul 25 09:10:33.607467 2016] [core:notice] [pid 16210:tid 140119475795840] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 09:10:40 node-1 apache2_error [Mon Jul 25 09:10:36.514022 2016] [mpm_event:notice] [pid 16210:tid 140119475795840] AH00491: caught SIGTERM, shutting down
<43>Jul 25 09:10:40 node-1 apache2_error [Mon Jul 25 09:10:37.616283 2016] [mpm_worker:notice] [pid 16593:tid 139643836278656] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 09:10:40 node-1 apache2_error [Mon Jul 25 09:10:37.616340 2016] [core:notice] [pid 16593:tid 139643836278656] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 09:10:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:10:50 node-1 multipathd: uevent trigger error
<43>Jul 25 09:12:00 node-1 apache2_error [Mon Jul 25 09:11:59.351481 2016] [mpm_worker:notice] [pid 16593:tid 139643836278656] AH00295: caught SIGTERM, shutting down
<43>Jul 25 09:12:00 node-1 apache2_error [Mon Jul 25 09:12:00.113435 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 09:12:00 node-1 apache2_error [Mon Jul 25 09:12:00.113480 2016] [core:notice] [pid 30511:tid 140622043535232] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 09:12:50 node-1 apache2_error [Mon Jul 25 09:12:44.357977 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 09:12:50 node-1 apache2_error [Mon Jul 25 09:12:44.554061 2016] [mpm_worker:warn] [pid 30511:tid 140622043535232] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 09:12:50 node-1 apache2_error [Mon Jul 25 09:12:44.556897 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 09:12:50 node-1 apache2_error [Mon Jul 25 09:12:44.556912 2016] [core:notice] [pid 30511:tid 140622043535232] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 09:13:29 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:29 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:29 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:29 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:29 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:29 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:31 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:13:34 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:34 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:34 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:34 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:34 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:34 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:34 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:13:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:14:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:15:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:15:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:15:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:15:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:15:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:15:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:16:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:16:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:16:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:16:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:16:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:16:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:16:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:16:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:38 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:38 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:38 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:38 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:38 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:38 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:17:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:18:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:18:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:18:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:18:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:18:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:19:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:20:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:53 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:20:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:21:47 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:08 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:08 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:08 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:08 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:08 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:36 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:22:55 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:55 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:55 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:55 node-1 multipathd: uevent trigger error
<27>Jul 25 09:22:55 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:02 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 25 09:23:02 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 25 09:23:03 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 25 09:23:04 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 25 09:23:04 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 25 09:23:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:23:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:25:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:26:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:26:43 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 25 09:27:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:27:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:27:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:27:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:27:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:39 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:28:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:54 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:54 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:54 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:54 node-1 multipathd: uevent trigger error
<27>Jul 25 09:28:54 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:07 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:29:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:30:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:30:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:30:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:30:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:30:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:30:46 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:05 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:05 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:05 node-1 multipathd: uevent trigger error
<11>Jul 25 09:31:18 node-1 liberasurecode[61596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:18 node-1 liberasurecode[61596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:18 node-1 liberasurecode[61596]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:18 node-1 liberasurecode[61596]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:18 node-1 liberasurecode[61634]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:18 node-1 liberasurecode[61634]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:18 node-1 liberasurecode[61634]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:18 node-1 liberasurecode[61634]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:21 node-1 liberasurecode[62054]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:21 node-1 liberasurecode[62054]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:21 node-1 liberasurecode[62054]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:21 node-1 liberasurecode[62054]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62869]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62869]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62869]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62869]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62912]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62912]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62912]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62912]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62954]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62954]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62954]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:26 node-1 liberasurecode[62954]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63020]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63020]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63020]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63020]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63043]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63043]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63043]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63043]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63062]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63062]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63062]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63062]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63074]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63074]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63074]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:27 node-1 liberasurecode[63074]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:35 node-1 liberasurecode[64011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:35 node-1 liberasurecode[64011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:35 node-1 liberasurecode[64011]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:31:35 node-1 liberasurecode[64011]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 09:31:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:31:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:44 node-1 multipathd: uevent trigger error
<27>Jul 25 09:31:44 node-1 multipathd: uevent trigger error
<43>Jul 25 09:32:32 node-1 apache2_error [Mon Jul 25 09:32:31.820378 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 09:32:32 node-1 apache2_error [Mon Jul 25 09:32:32.204422 2016] [mpm_worker:warn] [pid 30511:tid 140622043535232] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 09:32:32 node-1 apache2_error [Mon Jul 25 09:32:32.207784 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 09:32:32 node-1 apache2_error [Mon Jul 25 09:32:32.207802 2016] [core:notice] [pid 30511:tid 140622043535232] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 09:33:12 node-1 apache2_error [Mon Jul 25 09:33:09.087210 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 09:33:12 node-1 apache2_error [Mon Jul 25 09:33:09.471789 2016] [mpm_worker:warn] [pid 30511:tid 140622043535232] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 09:33:12 node-1 apache2_error [Mon Jul 25 09:33:09.481261 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 09:33:12 node-1 apache2_error [Mon Jul 25 09:33:09.481288 2016] [core:notice] [pid 30511:tid 140622043535232] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 09:33:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:13 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:20 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:59 node-1 multipathd: uevent trigger error
<27>Jul 25 09:33:59 node-1 multipathd: uevent trigger error
<43>Jul 25 09:34:02 node-1 apache2_error [Mon Jul 25 09:33:55.310805 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 09:34:02 node-1 apache2_error [Mon Jul 25 09:33:55.511186 2016] [mpm_worker:warn] [pid 30511:tid 140622043535232] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 09:34:02 node-1 apache2_error [Mon Jul 25 09:33:55.520679 2016] [mpm_worker:notice] [pid 30511:tid 140622043535232] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 09:34:02 node-1 apache2_error [Mon Jul 25 09:33:55.520711 2016] [core:notice] [pid 30511:tid 140622043535232] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 09:34:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:06 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:11 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:18 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:18 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:18 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:18 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:18 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:33 node-1 multipathd: uevent trigger error
<27>Jul 25 09:34:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 09:34:55 node-1 multipathd: uevent trigger error
<11>Jul 25 09:35:01 node-1 liberasurecode[107585]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:35:01 node-1 liberasurecode[107585]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:35:01 node-1 liberasurecode[107585]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:35:01 node-1 liberasurecode[107585]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 09:35:03 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 25 09:35:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:12 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:26 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:45 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:45 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:45 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:45 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:45 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:35:50 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:04 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:08 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 09:36:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:17 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:22 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:27 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:32 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:37 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:36:42 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:16 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:24 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:24 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:24 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:24 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:24 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:35 node-1 multipathd: uevent trigger error
<27>Jul 25 09:38:35 node-1 multipathd: uevent trigger error
<129>Jul 25 09:38:45 node-1 haproxy[144692]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 09:38:45 node-1 haproxy[144692]: Server neutron/node-1 is DOWN, reason: Layer4 connection 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 25 09:39:25 node-1 haproxy[144692]: 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.
<27>Jul 25 09:39:30 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:30 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:30 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:30 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:30 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:36 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:40 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:52 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:52 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:52 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:52 node-1 multipathd: uevent trigger error
<27>Jul 25 09:39:52 node-1 multipathd: uevent trigger error
<11>Jul 25 09:40:01 node-1 liberasurecode[165559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:40:01 node-1 liberasurecode[165559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:40:01 node-1 liberasurecode[165559]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 09:40:01 node-1 liberasurecode[165559]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
