Jul 26 02:58:50 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] start
Jul 26 02:58:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 26 02:58:50 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 26 02:58:50 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 26 02:58:50 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 26 02:58:50 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 26 02:58:50 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 26 02: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 26 02: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=b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62 nomdmonddf nomdmonisw
Jul 26 02:58:50 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 26 02:58:50 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 26 02:58:50 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 26 02:58:50 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 26 02:58:50 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 26 02:58:50 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 26 02:58:50 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 26 02: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 26 02:58:50 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 26 02:58:50 node-1 kernel: [    0.000000] No AGP bridge found
Jul 26 02:58:50 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 26 02:58:50 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 26 02:58:50 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 26 02:58:50 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 26 02:58:50 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 26 02:58:50 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 26 02:58:50 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 26 02:58:50 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 26 02:58:50 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 26 02:58:50 node-1 kernel: [    0.000000]   2 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000]   3 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000]   4 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000]   5 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000]   6 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000]   7 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000]   8 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000]   9 disabled
Jul 26 02:58:50 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 26 02:58:50 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 26 02:58:50 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 26 02:58:50 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 26 02:58:50 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 26 02:58:50 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 26 02:58:50 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 26 02:58:50 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 26 02:58:50 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 26 02:58:50 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 26 02:58:50 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 26 02:58:50 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 26 02:58:50 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 26 02:58:50 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 26 02:58:50 node-1 kernel: [    0.000000] Zone ranges:
Jul 26 02:58:50 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 26 02:58:50 node-1 kernel: [    0.000000] Early memory node ranges
Jul 26 02:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 26 02:58:50 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 26 02:58:50 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 26 02:58:50 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 26 02:58:50 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 26 02:58:50 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 26 02:58:50 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 26 02:58:50 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 26 02:58:50 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 26 02:58:50 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 26 02:58:50 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 26 02:58:50 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 26 02:58:50 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 26 02:58:50 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 26 02:58:50 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 26 02:58:50 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 26 02:58:50 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 26 02:58:50 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 26 02:58:50 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 26 02:58:50 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 26 02: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 26 02:58:50 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 26 02:58:50 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 26 02: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 26 02:58:50 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 26 02:58:50 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 26 02: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=b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62 nomdmonddf nomdmonisw
Jul 26 02:58:50 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 26 02:58:50 node-1 kernel: [    0.000000] Checking aperture...
Jul 26 02:58:50 node-1 kernel: [    0.000000] No AGP bridge found
Jul 26 02:58:50 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 26 02:58:50 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 26 02:58:50 node-1 kernel: [    0.000000] Memory: 32653324K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Jul 26 02:58:50 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 26 02:58:50 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 26 02:58:50 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 26 02:58:50 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 26 02:58:50 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 26 02:58:50 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 26 02:58:50 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 26 02:58:50 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 26 02:58:50 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 26 02:58:50 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 26 02:58:50 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 26 02:58:50 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 26 02:58:50 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 26 02:58:50 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 26 02:58:50 node-1 kernel: [    0.004000] tsc: Detected 3491.982 MHz processor
Jul 26 02:58:50 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.96 BogoMIPS (lpj=13967928)
Jul 26 02:58:50 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 26 02:58:50 node-1 kernel: [    0.000048] Security Framework initialized
Jul 26 02:58:50 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Jul 26 02:58:50 node-1 kernel: [    0.000068] Yama: becoming mindful.
Jul 26 02:58:50 node-1 kernel: [    0.001461] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.006391] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.008308] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.008336] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.008612] Initializing cgroup subsys memory
Jul 26 02:58:50 node-1 kernel: [    0.008620] Initializing cgroup subsys devices
Jul 26 02:58:50 node-1 kernel: [    0.008622] Initializing cgroup subsys freezer
Jul 26 02:58:50 node-1 kernel: [    0.008624] Initializing cgroup subsys blkio
Jul 26 02:58:50 node-1 kernel: [    0.008625] Initializing cgroup subsys perf_event
Jul 26 02:58:50 node-1 kernel: [    0.008627] Initializing cgroup subsys hugetlb
Jul 26 02:58:50 node-1 kernel: [    0.008646] CPU: Physical Processor ID: 0
Jul 26 02:58:50 node-1 kernel: [    0.008648] CPU: Processor Core ID: 0
Jul 26 02:58:50 node-1 kernel: [    0.008651] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 26 02:58:50 node-1 kernel: [    0.008651] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 26 02:58:50 node-1 kernel: [    0.009345] mce: CPU supports 22 MCE banks
Jul 26 02:58:50 node-1 kernel: [    0.009373] CPU0: Thermal monitoring enabled (TM1)
Jul 26 02:58:50 node-1 kernel: [    0.009394] process: using mwait in idle threads
Jul 26 02:58:50 node-1 kernel: [    0.009397] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 26 02:58:50 node-1 kernel: [    0.009397] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 26 02:58:50 node-1 kernel: [    0.009397] tlb_flushall_shift: 6
Jul 26 02:58:50 node-1 kernel: [    0.009486] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 26 02:58:50 node-1 kernel: [    0.010211] ACPI: Core revision 20131115
Jul 26 02:58:50 node-1 kernel: [    0.022896] ACPI: All ACPI Tables successfully acquired
Jul 26 02:58:50 node-1 kernel: [    0.023048] ftrace: allocating 28617 entries in 112 pages
Jul 26 02:58:50 node-1 kernel: [    0.031853] dmar: Host address width 46
Jul 26 02:58:50 node-1 kernel: [    0.031855] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 26 02:58:50 node-1 kernel: [    0.031861] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 02:58:50 node-1 kernel: [    0.031863] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 26 02:58:50 node-1 kernel: [    0.031867] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 02:58:50 node-1 kernel: [    0.031868] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 26 02:58:50 node-1 kernel: [    0.031870] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 26 02:58:50 node-1 kernel: [    0.031871] dmar: ATSR flags: 0x0
Jul 26 02:58:50 node-1 kernel: [    0.031872] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 26 02:58:50 node-1 kernel: [    0.031873] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 26 02:58:50 node-1 kernel: [    0.031990] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 26 02:58:50 node-1 kernel: [    0.031991] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 02:58:50 node-1 kernel: [    0.031992] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 02:58:50 node-1 kernel: [    0.031993] HPET id 0 under DRHD base 0xc7ffc000
Jul 26 02:58:50 node-1 kernel: [    0.031994] Your BIOS is broken and requested that x2apic be disabled.
Jul 26 02:58:50 node-1 kernel: [    0.031994] This will slightly decrease performance.
Jul 26 02:58:50 node-1 kernel: [    0.031994] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 26 02:58:50 node-1 kernel: [    0.032425] Enabled IRQ remapping in xapic mode
Jul 26 02:58:50 node-1 kernel: [    0.032426] x2apic not enabled, IRQ remapping is in xapic mode
Jul 26 02:58:50 node-1 kernel: [    0.032430] Switched APIC routing to physical flat.
Jul 26 02:58:50 node-1 kernel: [    0.033034] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 26 02:58:50 node-1 kernel: [    0.072685] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 26 02:58:50 node-1 kernel: [    0.072690] TSC deadline timer enabled
Jul 26 02:58:50 node-1 kernel: [    0.072697] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 26 02:58:50 node-1 kernel: [    0.072703] ... version:                3
Jul 26 02:58:50 node-1 kernel: [    0.072704] ... bit width:              48
Jul 26 02:58:50 node-1 kernel: [    0.072705] ... generic registers:      4
Jul 26 02:58:50 node-1 kernel: [    0.072706] ... value mask:             0000ffffffffffff
Jul 26 02:58:50 node-1 kernel: [    0.072707] ... max period:             0000ffffffffffff
Jul 26 02:58:50 node-1 kernel: [    0.072708] ... fixed-purpose events:   3
Jul 26 02:58:50 node-1 kernel: [    0.072709] ... event mask:             000000070000000f
Jul 26 02:58:50 node-1 kernel: [    0.074117] x86: Booting SMP configuration:
Jul 26 02:58:50 node-1 kernel: [    0.088219] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 26 02:58:50 node-1 kernel: [    0.074119] .... node  #0, CPUs:        #1  #2  #3
Jul 26 02:58:50 node-1 kernel: [    0.116130] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 26 02:58:50 node-1 kernel: [    0.270279] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 26 02:58:50 node-1 kernel: [    0.325893] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 26 02:58:50 node-1 kernel: [    0.382947] x86: Booted up 2 nodes, 16 CPUs
Jul 26 02:58:50 node-1 kernel: [    0.382951] smpboot: Total of 16 processors activated (111755.81 BogoMIPS)
Jul 26 02:58:50 node-1 kernel: [    0.407320] devtmpfs: initialized
Jul 26 02:58:50 node-1 kernel: [    0.410409] EVM: security.selinux
Jul 26 02:58:50 node-1 kernel: [    0.410411] EVM: security.SMACK64
Jul 26 02:58:50 node-1 kernel: [    0.410412] EVM: security.ima
Jul 26 02:58:50 node-1 kernel: [    0.410413] EVM: security.capability
Jul 26 02:58:50 node-1 kernel: [    0.410463] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.411155] pinctrl core: initialized pinctrl subsystem
Jul 26 02:58:50 node-1 kernel: [    0.411213] regulator-dummy: no parameters
Jul 26 02:58:50 node-1 kernel: [    0.411244] RTC time:  2:58:15, date: 07/26/16
Jul 26 02:58:50 node-1 kernel: [    0.411278] NET: Registered protocol family 16
Jul 26 02:58:50 node-1 kernel: [    0.411360] cpuidle: using governor ladder
Jul 26 02:58:50 node-1 kernel: [    0.411361] cpuidle: using governor menu
Jul 26 02:58:50 node-1 kernel: [    0.411395] ACPI: bus type PCI registered
Jul 26 02:58:50 node-1 kernel: [    0.411397] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 26 02:58:50 node-1 kernel: [    0.411443] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 26 02:58:50 node-1 kernel: [    0.411445] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 26 02:58:50 node-1 kernel: [    0.425187] PCI: Using configuration type 1 for base access
Jul 26 02:58:50 node-1 kernel: [    0.426188] bio: create slab <bio-0> at 0
Jul 26 02:58:50 node-1 kernel: [    0.426466] ACPI: Added _OSI(Module Device)
Jul 26 02:58:50 node-1 kernel: [    0.426467] ACPI: Added _OSI(Processor Device)
Jul 26 02:58:50 node-1 kernel: [    0.426468] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 26 02:58:50 node-1 kernel: [    0.426470] ACPI: Added _OSI(Processor Aggregator Device)
Jul 26 02:58:50 node-1 kernel: [    0.439145] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 26 02:58:50 node-1 kernel: [    0.450869] ACPI: Interpreter enabled
Jul 26 02:58:50 node-1 kernel: [    0.450875] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 26 02:58:50 node-1 kernel: [    0.450879] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 26 02:58:50 node-1 kernel: [    0.450881] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 26 02:58:50 node-1 kernel: [    0.450888] ACPI: (supports S0 S4 S5)
Jul 26 02:58:50 node-1 kernel: [    0.450889] ACPI: Using IOAPIC for interrupt routing
Jul 26 02:58:50 node-1 kernel: [    0.450929] HEST: Table parsing has been initialized.
Jul 26 02:58:50 node-1 kernel: [    0.450932] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 26 02:58:50 node-1 kernel: [    0.451503] ACPI: No dock devices found.
Jul 26 02:58:50 node-1 kernel: [    0.463499] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 26 02:58:50 node-1 kernel: [    0.463504] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:50 node-1 kernel: [    0.463507] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 02:58:50 node-1 kernel: [    0.463535] PCI host bridge to bus 0000:ff
Jul 26 02:58:50 node-1 kernel: [    0.463538] pci_bus 0000:ff: root bus resource [bus ff]
Jul 26 02:58:50 node-1 kernel: [    0.463546] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463585] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.463616] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463651] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463681] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.463711] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.463742] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463771] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463804] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463833] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463860] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463886] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463914] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463940] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463967] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.463994] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464023] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464050] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464077] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.464105] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464131] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.464157] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464183] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464216] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.464251] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464282] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464312] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464343] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464374] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464405] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464436] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464466] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464496] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464528] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464561] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464593] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464627] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464657] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464685] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464716] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464749] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464786] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464821] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464854] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464884] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464913] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464943] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.464978] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465011] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465042] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465074] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465103] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465132] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465161] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465190] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465222] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465253] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465313] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 26 02:58:50 node-1 kernel: [    0.465316] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:50 node-1 kernel: [    0.465319] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 02:58:50 node-1 kernel: [    0.465337] PCI host bridge to bus 0000:7f
Jul 26 02:58:50 node-1 kernel: [    0.465339] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 26 02:58:50 node-1 kernel: [    0.465344] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465371] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.465399] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465430] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465452] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.465476] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.465503] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465530] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465553] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465575] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465598] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465621] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465645] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465668] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465694] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465723] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465745] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465768] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465791] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.465815] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465837] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.465860] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465882] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465908] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 02:58:50 node-1 kernel: [    0.465943] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465969] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.465997] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466025] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466050] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466076] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466102] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466129] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466155] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466183] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466210] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466238] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466264] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466289] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466314] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466344] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466369] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466395] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466425] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466454] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466481] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466506] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466534] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466563] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466591] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466618] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466648] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466673] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466695] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466721] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466748] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466778] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.466804] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.468062] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 26 02:58:50 node-1 kernel: [    0.468065] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:50 node-1 kernel: [    0.469188] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 02:58:50 node-1 kernel: [    0.469693] PCI host bridge to bus 0000:00
Jul 26 02:58:50 node-1 kernel: [    0.469695] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 26 02:58:50 node-1 kernel: [    0.469697] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 26 02:58:50 node-1 kernel: [    0.469698] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 26 02:58:50 node-1 kernel: [    0.469700] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 26 02:58:50 node-1 kernel: [    0.469701] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 26 02:58:50 node-1 kernel: [    0.469702] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 26 02:58:50 node-1 kernel: [    0.469704] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 26 02:58:50 node-1 kernel: [    0.469710] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 26 02:58:50 node-1 kernel: [    0.469792] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.469823] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.469864] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 26 02:58:50 node-1 kernel: [    0.469884] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.469913] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.469953] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 26 02:58:50 node-1 kernel: [    0.469972] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.470002] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.470045] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 26 02:58:50 node-1 kernel: [    0.470063] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.470133] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.470210] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.470288] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 02:58:50 node-1 kernel: [    0.470293] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 26 02:58:50 node-1 kernel: [    0.470382] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 26 02:58:50 node-1 kernel: [    0.470530] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 26 02:58:50 node-1 kernel: [    0.470547] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 26 02:58:50 node-1 kernel: [    0.470625] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.470680] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 26 02:58:50 node-1 kernel: [    0.470702] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.470758] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.470801] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 26 02:58:50 node-1 kernel: [    0.470830] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.470886] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.470929] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 26 02:58:50 node-1 kernel: [    0.470952] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 26 02:58:50 node-1 kernel: [    0.470970] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 26 02:58:50 node-1 kernel: [    0.471048] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.471098] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 26 02:58:50 node-1 kernel: [    0.471125] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 26 02:58:50 node-1 kernel: [    0.471374] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 26 02:58:50 node-1 kernel: [    0.471380] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 26 02:58:50 node-1 kernel: [    0.471386] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.471391] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.471398] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 26 02:58:50 node-1 kernel: [    0.471429] pci 0000:01:00.0: supports D1 D2
Jul 26 02:58:50 node-1 kernel: [    0.476984] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 02:58:50 node-1 kernel: [    0.476990] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 02:58:50 node-1 kernel: [    0.476994] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 02:58:50 node-1 kernel: [    0.477218] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.477251] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 26 02:58:50 node-1 kernel: [    0.484980] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 02:58:50 node-1 kernel: [    0.484986] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.484990] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:50 node-1 kernel: [    0.485074] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.485147] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.485241] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.485322] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 02:58:50 node-1 kernel: [    0.485330] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.485334] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:50 node-1 kernel: [    0.485413] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.485550] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.485603] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 02:58:50 node-1 kernel: [    0.485606] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.485608] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.485657] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.485792] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.485833] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.485955] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.485993] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.486112] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.486148] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:50 node-1 kernel: [    0.486266] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:50 node-1 kernel: [    0.486308] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 02:58:50 node-1 kernel: [    0.486311] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.486313] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.486372] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:50 node-1 kernel: [    0.486435] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.486487] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.486528] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 26 02:58:50 node-1 kernel: [    0.486610] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 26 02:58:50 node-1 kernel: [    0.486715] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 02:58:50 node-1 kernel: [    0.486718] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.486720] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.486786] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:50 node-1 kernel: [    0.486844] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.486896] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.487108] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 02:58:50 node-1 kernel: [    0.487112] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 02:58:50 node-1 kernel: [    0.487175] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:50 node-1 kernel: [    0.487228] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.487276] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.487487] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 02:58:50 node-1 kernel: [    0.487491] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 02:58:50 node-1 kernel: [    0.487550] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:50 node-1 kernel: [    0.487610] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.487662] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 26 02:58:50 node-1 kernel: [    0.487911] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 02:58:50 node-1 kernel: [    0.487914] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 02:58:50 node-1 kernel: [    0.488090] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 02:58:50 node-1 kernel: [    0.488128] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 02:58:50 node-1 kernel: [    0.488204] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 26 02:58:50 node-1 kernel: [    0.488223] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 26 02:58:50 node-1 kernel: [    0.488237] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 26 02:58:50 node-1 kernel: [    0.488250] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 26 02:58:50 node-1 kernel: [    0.488300] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 26 02:58:50 node-1 kernel: [    0.492986] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 02:58:50 node-1 kernel: [    0.492995] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 02:58:50 node-1 kernel: [    0.493047] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 26 02:58:50 node-1 kernel: [    0.493653] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 26 02:58:50 node-1 kernel: [    0.493656] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:50 node-1 kernel: [    0.493779] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 02:58:50 node-1 kernel: [    0.493885] PCI host bridge to bus 0000:80
Jul 26 02:58:50 node-1 kernel: [    0.493887] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 26 02:58:50 node-1 kernel: [    0.493889] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 26 02:58:50 node-1 kernel: [    0.493891] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 26 02:58:50 node-1 kernel: [    0.493899] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.493961] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.494028] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 02:58:50 node-1 kernel: [    0.494089] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 02:58:50 node-1 kernel: [    0.494094] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 26 02:58:50 node-1 kernel: [    0.494166] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 26 02:58:50 node-1 kernel: [    0.494465] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 26 02:58:50 node-1 kernel: [    0.494496] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 26 02:58:50 node-1 kernel: [    0.494526] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 26 02:58:50 node-1 kernel: [    0.494555] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 26 02:58:50 node-1 kernel: [    0.494584] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:50 node-1 kernel: [    0.494614] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:50 node-1 kernel: [    0.494643] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:50 node-1 kernel: [    0.494672] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:50 node-1 kernel: [    0.494757] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 26 02:58:50 node-1 kernel: [    0.494761] ACPI: \_SB_.UNC1: notify handler is installed
Jul 26 02:58:50 node-1 kernel: [    0.494762] ACPI: \_SB_.UNC0: notify handler is installed
Jul 26 02:58:50 node-1 kernel: [    0.494777] ACPI: \_SB_.PCI0: notify handler is installed
Jul 26 02:58:50 node-1 kernel: [    0.494830] ACPI: \_SB_.PCI1: notify handler is installed
Jul 26 02:58:50 node-1 kernel: [    0.494909] Found 4 acpi root devices
Jul 26 02:58:50 node-1 kernel: [    0.495014] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 26 02:58:50 node-1 kernel: [    0.495016] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 26 02:58:50 node-1 kernel: [    0.495018] vgaarb: loaded
Jul 26 02:58:50 node-1 kernel: [    0.495019] vgaarb: bridge control possible 0000:0c:00.0
Jul 26 02:58:50 node-1 kernel: [    0.495132] SCSI subsystem initialized
Jul 26 02:58:50 node-1 kernel: [    0.495196] libata version 3.00 loaded.
Jul 26 02:58:50 node-1 kernel: [    0.495210] ACPI: bus type USB registered
Jul 26 02:58:50 node-1 kernel: [    0.495220] usbcore: registered new interface driver usbfs
Jul 26 02:58:50 node-1 kernel: [    0.495225] usbcore: registered new interface driver hub
Jul 26 02:58:50 node-1 kernel: [    0.495248] usbcore: registered new device driver usb
Jul 26 02:58:50 node-1 kernel: [    0.495411] PCI: Using ACPI for IRQ routing
Jul 26 02:58:50 node-1 kernel: [    0.499027] PCI: pci_cache_line_size set to 64 bytes
Jul 26 02:58:50 node-1 kernel: [    0.499228] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 26 02:58:50 node-1 kernel: [    0.499229] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 26 02:58:50 node-1 kernel: [    0.499230] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 26 02:58:50 node-1 kernel: [    0.499294] NetLabel: Initializing
Jul 26 02:58:50 node-1 kernel: [    0.499295] NetLabel:  domain hash size = 128
Jul 26 02:58:50 node-1 kernel: [    0.499296] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 26 02:58:50 node-1 kernel: [    0.499306] NetLabel:  unlabeled traffic allowed by default
Jul 26 02:58:50 node-1 kernel: [    0.499361] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 26 02:58:50 node-1 kernel: [    0.499366] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 26 02:58:50 node-1 kernel: [    0.501422] Switched to clocksource hpet
Jul 26 02:58:50 node-1 kernel: [    0.505355] AppArmor: AppArmor Filesystem Enabled
Jul 26 02:58:50 node-1 kernel: [    0.505377] pnp: PnP ACPI init
Jul 26 02:58:50 node-1 kernel: [    0.505383] ACPI: bus type PNP registered
Jul 26 02:58:50 node-1 kernel: [    0.505497] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505504] pnp 00:01: [dma 4]
Jul 26 02:58:50 node-1 kernel: [    0.505516] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505541] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505560] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505578] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505610] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505660] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505663] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 26 02:58:50 node-1 kernel: [    0.505664] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505666] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505668] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505672] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505674] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 26 02:58:50 node-1 kernel: [    0.505676] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505677] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505679] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505680] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505682] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505683] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 26 02:58:50 node-1 kernel: [    0.505685] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505768] pnp 00:07: [dma 0 disabled]
Jul 26 02:58:50 node-1 kernel: [    0.505796] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505870] pnp 00:08: [dma 0 disabled]
Jul 26 02:58:50 node-1 kernel: [    0.505901] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 02:58:50 node-1 kernel: [    0.505951] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 26 02:58:50 node-1 kernel: [    0.506295] pnp: PnP ACPI: found 10 devices
Jul 26 02:58:50 node-1 kernel: [    0.506297] ACPI: bus type PNP unregistered
Jul 26 02:58:50 node-1 kernel: [    0.512616] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 02:58:50 node-1 kernel: [    0.512619] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 02:58:50 node-1 kernel: [    0.512622] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 02:58:50 node-1 kernel: [    0.512626] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 02:58:50 node-1 kernel: [    0.512628] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512642] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512671] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 02:58:50 node-1 kernel: [    0.512686] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512715] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 02:58:50 node-1 kernel: [    0.512729] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 02:58:50 node-1 kernel: [    0.512773] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 02:58:50 node-1 kernel: [    0.512787] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 02:58:50 node-1 kernel: [    0.512816] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 02:58:50 node-1 kernel: [    0.512818] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512833] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512861] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 02:58:50 node-1 kernel: [    0.512863] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512878] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512906] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 02:58:50 node-1 kernel: [    0.512908] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512911] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512915] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 02:58:50 node-1 kernel: [    0.512917] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512919] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512923] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 02:58:50 node-1 kernel: [    0.512928] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 02:58:50 node-1 kernel: [    0.512936] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 02:58:50 node-1 kernel: [    0.512939] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 02:58:50 node-1 kernel: [    0.512945] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 26 02:58:50 node-1 kernel: [    0.512946] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 26 02:58:50 node-1 kernel: [    0.512947] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 26 02:58:50 node-1 kernel: [    0.512948] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 26 02:58:50 node-1 kernel: [    0.512949] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 26 02:58:50 node-1 kernel: [    0.512950] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 26 02:58:50 node-1 kernel: [    0.512951] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 26 02:58:50 node-1 kernel: [    0.512952] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 26 02:58:50 node-1 kernel: [    0.512953] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512953] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512954] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512955] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512956] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512957] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512958] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512959] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512960] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:50 node-1 kernel: [    0.512960] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512961] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 26 02:58:50 node-1 kernel: [    0.512963] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 26 02:58:50 node-1 kernel: [    0.512963] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 26 02:58:50 node-1 kernel: [    0.512965] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 26 02:58:50 node-1 kernel: [    0.512966] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 26 02:58:50 node-1 kernel: [    0.512967] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 26 02:58:50 node-1 kernel: [    0.513007] NET: Registered protocol family 2
Jul 26 02:58:50 node-1 kernel: [    0.513259] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.513592] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.513735] TCP: Hash tables configured (established 262144 bind 65536)
Jul 26 02:58:50 node-1 kernel: [    0.513777] TCP: reno registered
Jul 26 02:58:50 node-1 kernel: [    0.513810] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.513904] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.514049] NET: Registered protocol family 1
Jul 26 02:58:50 node-1 kernel: [    0.549521] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 26 02:58:50 node-1 kernel: [    0.549535] PCI: CLS 64 bytes, default 64
Jul 26 02:58:50 node-1 kernel: [    0.549622] Trying to unpack rootfs image as initramfs...
Jul 26 02:58:50 node-1 kernel: [    0.768685] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Jul 26 02:58:50 node-1 kernel: [    0.768729] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 26 02:58:50 node-1 kernel: [    0.768732] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 26 02:58:50 node-1 kernel: [    0.769149] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769156] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769161] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769167] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769176] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769187] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769204] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769213] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769222] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769231] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769238] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769244] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769261] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769283] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769290] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769298] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:50 node-1 kernel: [    0.769377] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 26 02:58:50 node-1 kernel: [    0.769380] Scanning for low memory corruption every 60 seconds
Jul 26 02:58:50 node-1 kernel: [    0.769756] Initialise system trusted keyring
Jul 26 02:58:50 node-1 kernel: [    0.769808] audit: initializing netlink socket (disabled)
Jul 26 02:58:50 node-1 kernel: [    0.769825] type=2000 audit(1469501894.724:1): initialized
Jul 26 02:58:50 node-1 kernel: [    0.787725] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 26 02:58:50 node-1 kernel: [    0.789292] zbud: loaded
Jul 26 02:58:50 node-1 kernel: [    0.789419] VFS: Disk quotas dquot_6.5.2
Jul 26 02:58:50 node-1 kernel: [    0.789456] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 26 02:58:50 node-1 kernel: [    0.789827] fuse init (API version 7.22)
Jul 26 02:58:50 node-1 kernel: [    0.789887] msgmni has been set to 32768
Jul 26 02:58:50 node-1 kernel: [    0.789936] Key type big_key registered
Jul 26 02:58:50 node-1 kernel: [    0.790468] Key type asymmetric registered
Jul 26 02:58:50 node-1 kernel: [    0.790470] Asymmetric key parser 'x509' registered
Jul 26 02:58:50 node-1 kernel: [    0.790492] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 26 02:58:50 node-1 kernel: [    0.790561] io scheduler noop registered
Jul 26 02:58:50 node-1 kernel: [    0.790563] io scheduler deadline registered (default)
Jul 26 02:58:50 node-1 kernel: [    0.790580] io scheduler cfq registered
Jul 26 02:58:50 node-1 kernel: [    0.790972] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    0.791091] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    0.791212] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    0.791333] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    0.791445] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    0.791536] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    0.791929] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 26 02:58:50 node-1 kernel: [    0.791955] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 26 02:58:50 node-1 kernel: [    0.791979] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 26 02:58:50 node-1 kernel: [    0.791988] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.791990] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.791993] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:50 node-1 kernel: [    0.791998] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792000] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792001] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792003] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792004] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792006] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792007] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792009] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792010] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792012] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792013] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792014] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792017] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:50 node-1 kernel: [    0.792022] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792025] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:50 node-1 kernel: [    0.792040] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792043] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:50 node-1 kernel: [    0.792053] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792055] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:50 node-1 kernel: [    0.792058] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 26 02:58:50 node-1 kernel: [    0.792097] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 26 02:58:50 node-1 kernel: [    0.792103] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 26 02:58:50 node-1 kernel: [    0.792107] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 26 02:58:50 node-1 kernel: [    0.792117] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 26 02:58:50 node-1 kernel: [    0.792158] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 26 02:58:50 node-1 kernel: [    0.792159] vesafb: scrolling: redraw
Jul 26 02:58:50 node-1 kernel: [    0.792161] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 26 02:58:50 node-1 kernel: [    0.812732] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 26 02:58:50 node-1 kernel: [    0.821256] Console: switching to colour frame buffer device 80x30
Jul 26 02:58:50 node-1 kernel: [    0.829928] fb0: VESA VGA frame buffer device
Jul 26 02:58:50 node-1 kernel: [    0.830125] intel_idle: MWAIT substates: 0x2120
Jul 26 02:58:50 node-1 kernel: [    0.830126] intel_idle: v0.4 model 0x3F
Jul 26 02:58:50 node-1 kernel: [    0.830127] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 26 02:58:50 node-1 kernel: [    0.830363] ipmi message handler version 39.2
Jul 26 02:58:50 node-1 kernel: [    0.830643] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 26 02:58:50 node-1 kernel: [    0.831079] ACPI: AC Adapter [P111] (on-line)
Jul 26 02:58:50 node-1 kernel: [    0.836344] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 26 02:58:50 node-1 kernel: [    0.847339] ACPI: Power Button [PWRB]
Jul 26 02:58:50 node-1 kernel: [    0.853101] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 26 02:58:50 node-1 kernel: [    0.864728] ACPI: Power Button [PWRF]
Jul 26 02:58:50 node-1 kernel: [    0.882936] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 26 02:58:50 node-1 kernel: [    0.894593] pstore: Registered erst as persistent store backend
Jul 26 02:58:50 node-1 kernel: [    0.900776] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 26 02:58:50 node-1 kernel: [    0.912724] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 26 02:58:50 node-1 kernel: [    0.939473] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 26 02:58:50 node-1 kernel: [    0.972944] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 26 02:58:50 node-1 kernel: [    0.987241] Linux agpgart interface v0.103
Jul 26 02:58:50 node-1 kernel: [    0.994995] brd: module loaded
Jul 26 02:58:50 node-1 kernel: [    1.002168] loop: module loaded
Jul 26 02:58:50 node-1 kernel: [    1.008971] libphy: Fixed MDIO Bus: probed
Jul 26 02:58:50 node-1 kernel: [    1.015538] tun: Universal TUN/TAP device driver, 1.6
Jul 26 02:58:50 node-1 kernel: [    1.022088] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 26 02:58:50 node-1 kernel: [    1.028684] PPP generic driver version 2.4.2
Jul 26 02:58:50 node-1 kernel: [    1.035111] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 26 02:58:50 node-1 kernel: [    1.041609] ehci-pci: EHCI PCI platform driver
Jul 26 02:58:50 node-1 kernel: [    1.048283] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 26 02:58:50 node-1 kernel: [    1.054773] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 26 02:58:50 node-1 kernel: [    1.067303] ehci-pci 0000:00:1a.0: debug port 2
Jul 26 02:58:50 node-1 kernel: [    1.077499] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 26 02:58:50 node-1 kernel: [    1.077518] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 26 02:58:50 node-1 kernel: [    1.092924] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 26 02:58:50 node-1 kernel: [    1.098989] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 02:58:50 node-1 kernel: [    1.105192] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 02:58:50 node-1 kernel: [    1.117108] usb usb1: Product: EHCI Host Controller
Jul 26 02:58:50 node-1 kernel: [    1.123151] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 02:58:50 node-1 kernel: [    1.129202] usb usb1: SerialNumber: 0000:00:1a.0
Jul 26 02:58:50 node-1 kernel: [    1.135248] hub 1-0:1.0: USB hub found
Jul 26 02:58:50 node-1 kernel: [    1.141112] hub 1-0:1.0: 2 ports detected
Jul 26 02:58:50 node-1 kernel: [    1.146902] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 26 02:58:50 node-1 kernel: [    1.152477] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 26 02:58:50 node-1 kernel: [    1.163368] ehci-pci 0000:00:1d.0: debug port 2
Jul 26 02:58:50 node-1 kernel: [    1.172660] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 26 02:58:50 node-1 kernel: [    1.172663] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 26 02:58:50 node-1 kernel: [    1.188843] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 26 02:58:50 node-1 kernel: [    1.194039] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 02:58:50 node-1 kernel: [    1.199332] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 02:58:50 node-1 kernel: [    1.209886] usb usb2: Product: EHCI Host Controller
Jul 26 02:58:50 node-1 kernel: [    1.215343] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 02:58:50 node-1 kernel: [    1.220865] usb usb2: SerialNumber: 0000:00:1d.0
Jul 26 02:58:50 node-1 kernel: [    1.226386] hub 2-0:1.0: USB hub found
Jul 26 02:58:50 node-1 kernel: [    1.231734] hub 2-0:1.0: 2 ports detected
Jul 26 02:58:50 node-1 kernel: [    1.237024] ehci-platform: EHCI generic platform driver
Jul 26 02:58:50 node-1 kernel: [    1.242239] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 26 02:58:50 node-1 kernel: [    1.247538] ohci-pci: OHCI PCI platform driver
Jul 26 02:58:50 node-1 kernel: [    1.252817] ohci-platform: OHCI generic platform driver
Jul 26 02:58:50 node-1 kernel: [    1.258009] uhci_hcd: USB Universal Host Controller Interface driver
Jul 26 02:58:50 node-1 kernel: [    1.263339] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 26 02:58:50 node-1 kernel: [    1.456623] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 26 02:58:50 node-1 kernel: [    1.764393] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 26 02:58:50 node-1 kernel: [    1.780660] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 26 02:58:50 node-1 kernel: [    1.786292] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 02:58:50 node-1 kernel: [    1.792053] hub 1-1:1.0: USB hub found
Jul 26 02:58:50 node-1 kernel: [    1.797648] hub 1-1:1.0: 6 ports detected
Jul 26 02:58:50 node-1 kernel: [    1.912254] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 26 02:58:50 node-1 kernel: [    2.302189] i8042: No controller found
Jul 26 02:58:50 node-1 kernel: [    2.307715] mousedev: PS/2 mouse device common for all mice
Jul 26 02:58:50 node-1 kernel: [    2.313445] rtc_cmos 00:02: RTC can wake from S4
Jul 26 02:58:50 node-1 kernel: [    2.316649] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 26 02:58:50 node-1 kernel: [    2.316649] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 02:58:50 node-1 kernel: [    2.317404] hub 2-1:1.0: USB hub found
Jul 26 02:58:50 node-1 kernel: [    2.317652] hub 2-1:1.0: 8 ports detected
Jul 26 02:58:50 node-1 kernel: [    2.341642] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 26 02:58:50 node-1 kernel: [    2.347375] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 26 02:58:50 node-1 kernel: [    2.358641] device-mapper: uevent: version 1.0.3
Jul 26 02:58:50 node-1 kernel: [    2.364324] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 26 02:58:50 node-1 kernel: [    2.375671] ledtrig-cpu: registered to indicate activity on CPUs
Jul 26 02:58:50 node-1 kernel: [    2.381636] TCP: cubic registered
Jul 26 02:58:50 node-1 kernel: [    2.387487] NET: Registered protocol family 10
Jul 26 02:58:50 node-1 kernel: [    2.393508] NET: Registered protocol family 17
Jul 26 02:58:50 node-1 kernel: [    2.399263] Key type dns_resolver registered
Jul 26 02:58:50 node-1 kernel: [    2.405327] Loading compiled-in X.509 certificates
Jul 26 02:58:50 node-1 kernel: [    2.411509] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 26 02:58:50 node-1 kernel: [    2.423118] registered taskstats version 1
Jul 26 02:58:50 node-1 kernel: [    2.431176] Key type trusted registered
Jul 26 02:58:50 node-1 kernel: [    2.438775] Key type encrypted registered
Jul 26 02:58:50 node-1 kernel: [    2.444261] AppArmor: AppArmor sha1 policy hashing enabled
Jul 26 02:58:50 node-1 kernel: [    2.449757] IMA: No TPM chip found, activating TPM-bypass!
Jul 26 02:58:50 node-1 kernel: [    2.455837] regulator-dummy: disabling
Jul 26 02:58:50 node-1 kernel: [    2.461291]   Magic number: 8:611:966
Jul 26 02:58:50 node-1 kernel: [    2.467025] rtc_cmos 00:02: setting system clock to 2016-07-26 02:58:17 UTC (1469501897)
Jul 26 02:58:50 node-1 kernel: [    2.479527] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 26 02:58:50 node-1 kernel: [    2.485186] EDD information not available.
Jul 26 02:58:50 node-1 kernel: [    2.490824] PM: Hibernation image not present or could not be loaded.
Jul 26 02:58:50 node-1 kernel: [    2.491684] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 26 02:58:50 node-1 kernel: [    2.503015] Write protecting the kernel read-only data: 12288k
Jul 26 02:58:50 node-1 kernel: [    2.509338] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 26 02:58:50 node-1 kernel: [    2.522345] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 26 02:58:50 node-1 kernel: [    2.555626] device-mapper: multipath: version 1.6.0 loaded
Jul 26 02:58:50 node-1 kernel: [    2.563870] systemd-udevd[215]: starting version 204
Jul 26 02:58:50 node-1 kernel: [    2.587567] md: linear personality registered for level -1
Jul 26 02:58:50 node-1 kernel: [    2.591849] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 26 02:58:50 node-1 kernel: [    2.607552] md: multipath personality registered for level -4
Jul 26 02:58:50 node-1 kernel: [    2.615764] md: raid0 personality registered for level 0
Jul 26 02:58:50 node-1 kernel: [    2.624032] md: raid1 personality registered for level 1
Jul 26 02:58:50 node-1 kernel: [    2.632815] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 26 02:58:50 node-1 kernel: [    2.639249] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 26 02:58:50 node-1 kernel: [    2.639245] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 26 02:58:50 node-1 kernel: [    2.658062] megasas: FW now in Ready state
Jul 26 02:58:50 node-1 kernel: [    2.664434] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664438] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664442] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664447] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664453] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664457] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664462] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664466] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664470] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664474] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664478] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664483] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664487] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664492] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664497] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664501] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.664554] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 26 02:58:50 node-1 kernel: [    2.684635] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 26 02:58:50 node-1 kernel: [    2.697887] 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 26 02:58:50 node-1 kernel: [    2.699664] raid6: sse2x1    5630 MB/s
Jul 26 02:58:50 node-1 kernel: [    2.718263] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:50 node-1 kernel: [    2.725171] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.725175] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.725180] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.725183] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.725220] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:50 node-1 kernel: [    2.745226] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 26 02:58:50 node-1 kernel: [    2.758393] 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 26 02:58:50 node-1 kernel: [    2.767697] raid6: sse2x2   13857 MB/s
Jul 26 02:58:50 node-1 kernel: [    2.778256] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:50 node-1 kernel: [    2.835464] raid6: sse2x4    9978 MB/s
Jul 26 02:58:50 node-1 kernel: [    2.907402] raid6: avx2x1   14940 MB/s
Jul 26 02:58:50 node-1 kernel: [    2.979334] raid6: avx2x2   18883 MB/s
Jul 26 02:58:50 node-1 kernel: [    3.051276] raid6: avx2x4   21253 MB/s
Jul 26 02:58:50 node-1 kernel: [    3.057377] raid6: using algorithm avx2x4 (21253 MB/s)
Jul 26 02:58:50 node-1 kernel: [    3.063426] raid6: using avx2x2 recovery algorithm
Jul 26 02:58:50 node-1 kernel: [    3.069357] megasas:IOC Init cmd success
Jul 26 02:58:50 node-1 kernel: [    3.069360] Switched to clocksource tsc
Jul 26 02:58:50 node-1 kernel: [    3.069520] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.069547] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.069583] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.069613] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.069700] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.077212] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 26 02:58:50 node-1 kernel: [    3.077214] 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 26 02:58:50 node-1 kernel: [    3.077214] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:50 node-1 kernel: [    3.077276] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.077291] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.077328] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.077365] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.077445] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.084099] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 26 02:58:50 node-1 kernel: [    3.084100] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 26 02:58:50 node-1 kernel: [    3.084101] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 26 02:58:50 node-1 kernel: [    3.084101] usb 2-1.4: Manufacturer: Avocent
Jul 26 02:58:50 node-1 kernel: [    3.084102] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 26 02:58:50 node-1 kernel: [    3.084971] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 26 02:58:50 node-1 kernel: [    3.084972] 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 26 02:58:50 node-1 kernel: [    3.084972] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:50 node-1 kernel: [    3.085033] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.085072] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.085106] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.085145] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.085276] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:50 node-1 kernel: [    3.091260] megasas: INIT adapter done
Jul 26 02:58:50 node-1 kernel: [    3.163209] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 26 02:58:50 node-1 kernel: [    3.163580] scsi0 : LSI SAS based MegaRAID driver
Jul 26 02:58:50 node-1 kernel: [    3.166534] xor: automatically using best checksumming function:
Jul 26 02:58:50 node-1 kernel: [    3.170567] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 02:58:50 node-1 kernel: [    3.181639] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 02:58:50 node-1 kernel: [    3.184157] hidraw: raw HID events driver (C) Jiri Kosina
Jul 26 02:58:50 node-1 kernel: [    3.186028] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 26 02:58:50 node-1 kernel: [    3.186108] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 26 02:58:50 node-1 kernel: [    3.186352] sd 0:2:0:0: [sda] Write Protect is off
Jul 26 02:58:50 node-1 kernel: [    3.186353] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 26 02:58:50 node-1 kernel: [    3.186412] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 26 02:58:50 node-1 kernel: [    3.203174]    avx       : 34938.000 MB/sec
Jul 26 02:58:50 node-1 kernel: [    3.213592]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 26 02:58:50 node-1 kernel: [    3.214811] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 26 02:58:50 node-1 kernel: [    3.297681] usbcore: registered new interface driver usbhid
Jul 26 02:58:50 node-1 kernel: [    3.297681] usbhid: USB HID core driver
Jul 26 02:58:50 node-1 kernel: [    3.307363] async_tx: api initialized (async)
Jul 26 02:58:50 node-1 kernel: [    3.344052] 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 26 02:58:50 node-1 kernel: [    3.356629] 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 26 02:58:50 node-1 kernel: [    3.369342] 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 26 02:58:50 node-1 kernel: [    3.382034] 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 26 02:58:50 node-1 kernel: [    3.395293] 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 26 02:58:50 node-1 kernel: [    3.395731] md: raid6 personality registered for level 6
Jul 26 02:58:50 node-1 kernel: [    3.395732] md: raid5 personality registered for level 5
Jul 26 02:58:50 node-1 kernel: [    3.395732] md: raid4 personality registered for level 4
Jul 26 02:58:50 node-1 kernel: [    3.411415] random: lvm urandom read with 30 bits of entropy available
Jul 26 02:58:50 node-1 kernel: [    3.435352] 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 26 02:58:50 node-1 kernel: [    3.450481] md: raid10 personality registered for level 10
Jul 26 02:58:50 node-1 kernel: [    3.504990] multipathd (375): /proc/375/oom_adj is deprecated, please use /proc/375/oom_score_adj instead.
Jul 26 02:58:50 node-1 kernel: [    3.553386] bio: create slab <bio-1> at 1
Jul 26 02:58:50 node-1 kernel: [    4.317671] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 02:58:50 node-1 kernel: [    4.941240] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 26 02:58:50 node-1 kernel: [    5.013492] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 26 02:58:50 node-1 kernel: [    5.118653] random: nonblocking pool is initialized
Jul 26 02:58:50 node-1 kernel: [    5.166845] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 26 02:58:50 node-1 kernel: [    5.196739] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 26 02:58:50 node-1 kernel: [    5.291053] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 02:58:50 node-1 kernel: [    5.436684] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 26 02:58:50 node-1 kernel: [    5.484881] XFS (dm-0): Mounting Filesystem
Jul 26 02:58:50 node-1 kernel: [    5.670493] XFS (dm-0): Ending clean mount
Jul 26 02:58:50 node-1 kernel: [    5.719815] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 02:58:50 node-1 kernel: [    5.763104] XFS (dm-1): Mounting Filesystem
Jul 26 02:58:50 node-1 kernel: [    5.884687] XFS (dm-1): Ending clean mount
Jul 26 02:58:50 node-1 kernel: [    7.947422] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 26 02:58:50 node-1 kernel: [    7.974037] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 26 02:58:50 node-1 kernel: [    8.116806] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 26 02:58:50 node-1 kernel: [    8.116812] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 26 02:58:50 node-1 kernel: [    8.116816] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 26 02:58:50 node-1 kernel: [    8.116820] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 26 02:58:50 node-1 kernel: [    8.165717] systemd-udevd[779]: starting version 204
Jul 26 02:58:50 node-1 kernel: [    8.347568] wmi: Mapper loaded
Jul 26 02:58:50 node-1 kernel: [    8.351984] power_meter ACPI000D:00: Found ACPI power meter.
Jul 26 02:58:50 node-1 kernel: [    8.352011] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 26 02:58:50 node-1 kernel: [    8.374497] IPMI System Interface driver.
Jul 26 02:58:50 node-1 kernel: [    8.374619] ipmi_si: probing via ACPI
Jul 26 02:58:50 node-1 kernel: [    8.374632] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 26 02:58:50 node-1 kernel: [    8.374633] ipmi_si: Adding ACPI-specified kcs state machine
Jul 26 02:58:50 node-1 kernel: [    8.374649] ipmi_si: probing via SMBIOS
Jul 26 02:58:50 node-1 kernel: [    8.374651] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 02:58:50 node-1 kernel: [    8.374652] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 26 02:58:50 node-1 kernel: [    8.374654] ipmi_si: probing via SPMI
Jul 26 02:58:50 node-1 kernel: [    8.374655] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 02:58:50 node-1 kernel: [    8.374655] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 26 02:58:50 node-1 kernel: [    8.374657] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 26 02:58:50 node-1 kernel: [    8.391474] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 26 02:58:50 node-1 kernel: [    8.441637] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 26 02:58:50 node-1 kernel: [    8.441642] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 02:58:50 node-1 kernel: [    8.441645] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 26 02:58:50 node-1 kernel: [    8.441646] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 02:58:50 node-1 kernel: [    8.441659] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 26 02:58:50 node-1 kernel: [    8.471179] systemd-udevd[822]: renamed network interface eth0 to enp6s0
Jul 26 02:58:50 node-1 kernel: [    8.495042] systemd-udevd[798]: renamed network interface eth1 to enp7s0
Jul 26 02:58:50 node-1 kernel: [    8.519186] systemd-udevd[810]: renamed network interface eth2 to enp8s0
Jul 26 02:58:50 node-1 kernel: [    8.525369] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 26 02:58:50 node-1 kernel: [    8.525377] ipmi_si 00:09: IPMI kcs interface initialized
Jul 26 02:58:50 node-1 kernel: [    8.538986] systemd-udevd[799]: renamed network interface eth3 to enp9s0
Jul 26 02:58:50 node-1 kernel: [    8.872068] type=1400 audit(1469501903.905:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1046 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.872232] type=1400 audit(1469501903.905:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1046 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.872369] type=1400 audit(1469501903.905:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1046 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.874480] type=1400 audit(1469501903.909:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1065 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.874625] type=1400 audit(1469501903.909:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1065 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.874750] type=1400 audit(1469501903.909:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1065 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.881097] type=1400 audit(1469501903.913:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.881241] type=1400 audit(1469501903.913:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1048 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.881366] type=1400 audit(1469501903.913:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1048 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    8.888091] type=1400 audit(1469501903.921:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1047 comm="apparmor_parser"
Jul 26 02:58:50 node-1 kernel: [    9.365585] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 26 02:58:50 node-1 kernel: [    9.366390] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 26 02:58:50 node-1 kernel: [    9.590618] enic 0000:06:00.0 enp6s0: Link UP
Jul 26 02:58:50 node-1 kernel: [    9.591835] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 26 02:58:50 node-1 kernel: [    9.591840] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 26 02:58:50 node-1 kernel: [   18.687817] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 26 02: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 26 02:58:51 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 26 02:58:51 node-1 kernel: [   37.468658] init: failsafe main process (8407) killed by TERM signal
Jul 26 02:58:51 node-1 dbus[8438]: [system] AppArmor D-Bus mediation is enabled
Jul 26 02:58:51 node-1 kernel: [   37.663926] audit_printk_skb: 30 callbacks suppressed
Jul 26 02:58:51 node-1 kernel: [   37.663927] type=1400 audit(1469501931.937:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8533 comm="apparmor_parser"
Jul 26 02:58:51 node-1 kernel: [   37.667618] type=1400 audit(1469501931.941:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8532 comm="apparmor_parser"
Jul 26 02:58:51 node-1 kernel: [   37.667623] type=1400 audit(1469501931.941:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8532 comm="apparmor_parser"
Jul 26 02:58:51 node-1 kernel: [   37.667625] type=1400 audit(1469501931.941:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8532 comm="apparmor_parser"
Jul 26 02:58:51 node-1 kernel: [   37.667843] type=1400 audit(1469501931.941:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8532 comm="apparmor_parser"
Jul 26 02:58:51 node-1 kernel: [   37.667845] type=1400 audit(1469501931.941:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8532 comm="apparmor_parser"
Jul 26 02:58:51 node-1 kernel: [   37.667956] type=1400 audit(1469501931.941:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8532 comm="apparmor_parser"
Jul 26 02:58:52 node-1 kernel: [   37.741240] type=1400 audit(1469501932.013:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8535 comm="apparmor_parser"
Jul 26 02:58:52 node-1 cron[8565]: (CRON) INFO (pidfile fd = 3)
Jul 26 02:58:52 node-1 anacron[8599]: Anacron 2.3 started on 2016-07-26
Jul 26 02:58:52 node-1 cron[8606]: (CRON) STARTUP (fork ok)
Jul 26 02:58:52 node-1 anacron[8599]: Will run job `cron.daily' in 5 min.
Jul 26 02:58:52 node-1 anacron[8599]: Will run job `cron.weekly' in 10 min.
Jul 26 02:58:52 node-1 anacron[8599]: Will run job `cron.monthly' in 15 min.
Jul 26 02:58:52 node-1 anacron[8599]: Jobs will be executed sequentially
Jul 26 02:58:52 node-1 cron[8606]: (CRON) INFO (Running @reboot jobs)
Jul 26 02:58:52 node-1 multipathd: path checkers start up
Jul 26 02:58:52 node-1 postfix/master[8744]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 26 02:58:55 node-1 puppet-agent[8929]: Reopening log files
Jul 26 02:58:58 node-1 puppet-agent[8929]: Could not request certificate: Connection refused - connect(2)
Jul 26 02:59:01 node-1 CRON[8960]: (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 26 02:59:03 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 02:59:03 node-1 nailgun-agent: D, [2016-07-26T02:59:01.772738 #8963] DEBUG -- : Sleep for 2 seconds before sending request
Jul 26 02:59:03 node-1 nailgun-agent: I, [2016-07-26T02:59:03.813040 #8963]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 02:59:04 node-1 nailgun-agent: D, [2016-07-26T02:59:04.626713 #8963] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 26 02:59:12 node-1 puppet-user[9277]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 26 02:59:12 node-1 puppet-user[9277]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 26 02:59:13 node-1 puppet-user[9277]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 26 02:59:13 node-1 puppet-user[9277]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 26 02:59:13 node-1 puppet-user[9277]: Finished catalog run in 0.96 seconds
Jul 26 02:59:14 node-1 multipathd: uevent trigger error
Jul 26 02:59:15 node-1 puppet-user[9707]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 02:59:15 node-1 puppet-user[9707]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Jul 26 02:59:15 node-1 puppet-user[9707]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 26 02:59:15 node-1 puppet-user[9707]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 26 02:59:15 node-1 puppet-user[9707]: (/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 26 02:59:15 node-1 puppet-user[9707]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 26 02:59:15 node-1 puppet-user[9707]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 26 02:59:15 node-1 puppet-user[9707]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 26 02:59:15 node-1 puppet-user[9707]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 26 02:59:15 node-1 puppet-user[9707]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 26 02:59:15 node-1 puppet-user[9707]: Finished catalog run in 0.06 seconds
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.668234 #8963] DEBUG -- : Trying to find block devices
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.668303 #8963] DEBUG -- : Found block device: sda
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.668346 #8963] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.668369 #8963] DEBUG -- : Trying to get list of physical devices
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.668557 #8963] DEBUG -- : Getting udev properties for device: sda
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.670315 #8963] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Jul 26 02:59:16 node-1 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71394", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.670342 #8963] DEBUG -- : Trying to find out if device sda is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.670388 #8963] DEBUG -- : Device sda removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.670406 #8963] DEBUG -- : Device sda seems to be appropriate
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.670833 #8963] DEBUG -- : Getting udev properties for device: dm-0
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.672513 #8963] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-wPjjozS3OntSj38hB0nukWJrAr6x1xHUe2U4YIfxpDlvssJ7exTSsbdOCD4JWdfp /dev/disk/by-uuid/4fdb9a8b-7cc4-4631-b988-02885e15d765 /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-wPjjozS3OntSj38hB0nukWJrAr6x1xHUe2U4YIfxpDlvssJ7exTSsbdOCD4JWdfp", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4fdb9a8b-7cc4-4631-b988-02885e15d765", "ID_FS_UUID_ENC"=>"4fdb9a8b-7cc4-4631-b988-02885e15d765", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10433", "nomdmonddf"=>"1", "nomd
Jul 26 02:59:16 node-1 nailgun-agent: monisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.672539 #8963] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.672600 #8963] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.672614 #8963] DEBUG -- : Device dm-0 seems to be appropriate
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.672629 #8963] DEBUG -- : Getting udev properties for device: dm-1
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.674576 #8963] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-3CFRzlH1RXo1KKZ9fcWCAyJLlzcpymjTxKyKJZg7YbLsQGS8fIog1fmBWxwxJ3k3 /dev/disk/by-uuid/2c2d56b1-2a4d-4fec-a15f-d53c1272e197 /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-3CFRzlH1RXo1KKZ9fcWCAyJLlzcpymjTxKyKJZg7YbLsQGS8fIog1fmBWxwxJ3k3", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2c2d56b1-2a4d-4fec-a15f-d53c1272e197", "ID_FS_UUID_ENC"=>"2c2d56b1-2a4d-4fec-a15f-d53c1272e197", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46
Jul 26 02:59:16 node-1 nailgun-agent: 312", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.674612 #8963] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.674681 #8963] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.674697 #8963] DEBUG -- : Device dm-1 seems to be appropriate
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.674712 #8963] DEBUG -- : Getting udev properties for device: dm-2
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.678505 #8963] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-cTuWnXnaN2yB3kUNwbCwxeZkK7pNEpI779eq8HgG7O4Bf2YzZEIXKv8zBRDOpVOU /dev/disk/by-uuid/e0e26a31-7f62-4794-9790-cf7aec8672a8 /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-cTuWnXnaN2yB3kUNwbCwxeZkK7pNEpI779eq8HgG7O4Bf2YzZEIXKv8zBRDOpVOU", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e0e26a31-7f62-4794-9790-cf7aec8672a8", "ID_FS_UUID_ENC"=>"e0e26a31-7f62-4794-9790-cf7aec8672a8", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47330", "nomdmond
Jul 26 02:59:16 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.678531 #8963] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.678561 #8963] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.678575 #8963] DEBUG -- : Device dm-2 seems to be appropriate
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.678589 #8963] DEBUG -- : Getting udev properties for device: dm-3
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.680201 #8963] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Tz3hRtGaEakNu4JYE5Atu4Iz3UX4a3UAeCe8ACGY749GlCgnbnEcnp48cKOedpgE /dev/disk/by-uuid/4e3e6b98-dfa8-42fc-b4fb-c7f0704b62d0 /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-Tz3hRtGaEakNu4JYE5Atu4Iz3UX4a3UAeCe8ACGY749GlCgnbnEcnp48cKOedpgE", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4e3e6b98-dfa8-42fc-b4fb-c7f0704b62d0", "ID_FS_UUID_ENC"=>"4e3e6b98-dfa8-42fc-b4fb-c7f0704b62d0", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65273", "nomdmonddf"=>"1", 
Jul 26 02:59:16 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.680227 #8963] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.680271 #8963] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.680286 #8963] DEBUG -- : Device dm-3 seems to be appropriate
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.680316 #8963] DEBUG -- : Getting udev properties for device: dm-4
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.682118 #8963] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-shj35aOZ3jfwnMJ3DLnEgCxM3JkhmAno8a0IMIK7sY7lHR5GL9UlC2x801Nt4tbG /dev/disk/by-uuid/b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62 /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-shj35aOZ3jfwnMJ3DLnEgCxM3JkhmAno8a0IMIK7sY7lHR5GL9UlC2x801Nt4tbG", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62", "ID_FS_UUID_ENC"=>"b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73586", "nomdmonddf"=>"1", "nomd
Jul 26 02:59:16 node-1 nailgun-agent: monisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.682152 #8963] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.682196 #8963] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.682211 #8963] DEBUG -- : Device dm-4 seems to be appropriate
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.682243 #8963] DEBUG -- : Getting udev properties for device: dm-5
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.683902 #8963] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-shj35aOZ3jfwnMJ3DLnEgCxM3JkhmAnoq2Z5cODylMCnIb5uPWSYffe62egws8X0 /dev/disk/by-uuid/4873e8c1-fdb5-46e1-ac8a-7ba12ff34840 /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-shj35aOZ3jfwnMJ3DLnEgCxM3JkhmAnoq2Z5cODylMCnIb5uPWSYffe62egws8X0", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"4873e8c1-fdb5-46e1-ac8a-7ba12ff34840", "ID_FS_UUID_ENC"=>"4873e8c1-fdb5-46e1-ac8a-7ba12ff34840", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"74057", "nomdmonddf"=>"1", "nomdmonisw"
Jul 26 02:59:16 node-1 nailgun-agent: =>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.683929 #8963] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.683960 #8963] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.683974 #8963] DEBUG -- : Device dm-5 seems to be appropriate
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.683989 #8963] DEBUG -- : Getting udev properties for device: ram0
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.685448 #8963] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39311", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.685471 #8963] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.685513 #8963] DEBUG -- : Device ram0 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.685545 #8963] DEBUG -- : Getting udev properties for device: ram1
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.686968 #8963] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39330", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.686993 #8963] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.687026 #8963] DEBUG -- : Device ram1 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.687046 #8963] DEBUG -- : Getting udev properties for device: ram2
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.688492 #8963] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39469", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.688548 #8963] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.688595 #8963] DEBUG -- : Device ram2 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.688665 #8963] DEBUG -- : Getting udev properties for device: ram3
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.690309 #8963] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39488", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.690341 #8963] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.690412 #8963] DEBUG -- : Device ram3 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.690451 #8963] DEBUG -- : Getting udev properties for device: ram4
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.692057 #8963] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39508", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.692105 #8963] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.692157 #8963] DEBUG -- : Device ram4 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.692199 #8963] DEBUG -- : Getting udev properties for device: ram5
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.693887 #8963] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39526", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.693919 #8963] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.693987 #8963] DEBUG -- : Device ram5 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.694016 #8963] DEBUG -- : Getting udev properties for device: ram6
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.695595 #8963] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39544", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.695626 #8963] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.695679 #8963] DEBUG -- : Device ram6 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.695718 #8963] DEBUG -- : Getting udev properties for device: ram7
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.697241 #8963] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39562", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.697263 #8963] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.697296 #8963] DEBUG -- : Device ram7 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.697330 #8963] DEBUG -- : Getting udev properties for device: ram8
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.698826 #8963] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39582", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.698868 #8963] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.698901 #8963] DEBUG -- : Device ram8 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.698919 #8963] DEBUG -- : Getting udev properties for device: ram9
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.700350 #8963] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39601", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.700377 #8963] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.700431 #8963] DEBUG -- : Device ram9 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.700451 #8963] DEBUG -- : Getting udev properties for device: loop0
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.701874 #8963] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39165", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.701911 #8963] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.701946 #8963] DEBUG -- : Device loop0 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.701965 #8963] DEBUG -- : Getting udev properties for device: loop1
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.703432 #8963] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39186", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.703468 #8963] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.703540 #8963] DEBUG -- : Device loop1 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.703580 #8963] DEBUG -- : Getting udev properties for device: loop2
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.705181 #8963] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39204", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.705229 #8963] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.705347 #8963] DEBUG -- : Device loop2 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.705375 #8963] DEBUG -- : Getting udev properties for device: loop3
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.706973 #8963] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39230", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.707006 #8963] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.707037 #8963] DEBUG -- : Device loop3 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.707067 #8963] DEBUG -- : Getting udev properties for device: loop4
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.708687 #8963] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39244", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.708727 #8963] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.708764 #8963] DEBUG -- : Device loop4 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.708796 #8963] DEBUG -- : Getting udev properties for device: loop5
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.710195 #8963] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39261", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.710219 #8963] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.710270 #8963] DEBUG -- : Device loop5 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.710287 #8963] DEBUG -- : Getting udev properties for device: loop6
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.711723 #8963] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39278", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.711748 #8963] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.711798 #8963] DEBUG -- : Device loop6 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.711818 #8963] DEBUG -- : Getting udev properties for device: loop7
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.713292 #8963] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39295", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.713317 #8963] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.713350 #8963] DEBUG -- : Device loop7 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.713385 #8963] DEBUG -- : Getting udev properties for device: ram10
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.714860 #8963] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39354", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.714895 #8963] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.714931 #8963] DEBUG -- : Device ram10 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.714949 #8963] DEBUG -- : Getting udev properties for device: ram11
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.716340 #8963] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39371", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.716365 #8963] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.716419 #8963] DEBUG -- : Device ram11 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.716438 #8963] DEBUG -- : Getting udev properties for device: ram12
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.717870 #8963] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39388", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.717895 #8963] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.717942 #8963] DEBUG -- : Device ram12 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.717961 #8963] DEBUG -- : Getting udev properties for device: ram13
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.719369 #8963] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39404", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.719394 #8963] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.719428 #8963] DEBUG -- : Device ram13 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.719448 #8963] DEBUG -- : Getting udev properties for device: ram14
Jul 26 02:59:16 node-1 puppet-user[10173]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.725404 #8963] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39422", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.725431 #8963] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.725470 #8963] DEBUG -- : Device ram14 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.725490 #8963] DEBUG -- : Getting udev properties for device: ram15
Jul 26 02:59:16 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 02:59:16 node-1 puppet-user[10173]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727281 #8963] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39443", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727306 #8963] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727346 #8963] DEBUG -- : Device ram15 removable parameter: "0"
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727381 #8963] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727395 #8963] DEBUG -- : Block device seems to be physical data storage: sda
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727429 #8963] DEBUG -- : Found block device: dm-0
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727454 #8963] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727467 #8963] DEBUG -- : Found block device: dm-1
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727477 #8963] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727530 #8963] DEBUG -- : Found block device: dm-2
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727541 #8963] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727549 #8963] DEBUG -- : Found block device: dm-3
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727558 #8963] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727567 #8963] DEBUG -- : Found block device: dm-4
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727576 #8963] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727586 #8963] DEBUG -- : Found block device: dm-5
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727595 #8963] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727604 #8963] DEBUG -- : Found block device: ram0
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727613 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727659 #8963] DEBUG -- : Found block device: ram1
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727669 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727678 #8963] DEBUG -- : Found block device: ram2
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727687 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727695 #8963] DEBUG -- : Found block device: ram3
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727704 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727712 #8963] DEBUG -- : Found block device: ram4
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727721 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727729 #8963] DEBUG -- : Found block device: ram5
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727778 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727787 #8963] DEBUG -- : Found block device: ram6
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727798 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727806 #8963] DEBUG -- : Found block device: ram7
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727816 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727824 #8963] DEBUG -- : Found block device: ram8
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727833 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727841 #8963] DEBUG -- : Found block device: ram9
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727849 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727895 #8963] DEBUG -- : Found block device: loop0
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727906 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727914 #8963] DEBUG -- : Found block device: loop1
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727923 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727932 #8963] DEBUG -- : Found block device: loop2
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727941 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727949 #8963] DEBUG -- : Found block device: loop3
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727959 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727967 #8963] DEBUG -- : Found block device: loop4
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.727976 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728019 #8963] DEBUG -- : Found block device: loop5
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728029 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728038 #8963] DEBUG -- : Found block device: loop6
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728047 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728055 #8963] DEBUG -- : Found block device: loop7
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728064 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728072 #8963] DEBUG -- : Found block device: ram10
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728083 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728090 #8963] DEBUG -- : Found block device: ram11
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728135 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728144 #8963] DEBUG -- : Found block device: ram12
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728153 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728160 #8963] DEBUG -- : Found block device: ram13
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728171 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728178 #8963] DEBUG -- : Found block device: ram14
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728187 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728196 #8963] DEBUG -- : Found block device: ram15
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728205 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.728271 #8963] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.809416 #8963] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 26 02:59:16 node-1 nailgun-agent: D, [2016-07-26T02:59:16.809501 #8963] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 26 02:59:16 node-1 puppet-user[10173]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 26 02:59:16 node-1 puppet-user[10173]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 26 02:59:16 node-1 puppet-user[10173]: Finished catalog run in 0.03 seconds
Jul 26 02:59:18 node-1 puppet-user[10816]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 26 02:59:18 node-1 puppet-user[10816]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 26 02:59:18 node-1 puppet-user[10816]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 26 02:59:18 node-1 puppet-user[10816]: Finished catalog run in 0.04 seconds
Jul 26 02:59:20 node-1 puppet-user[11448]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 26 02:59:20 node-1 puppet-user[11448]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Jul 26 02:59:20 node-1 puppet-user[11448]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 26 02:59:20 node-1 puppet-user[11448]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 26 02:59:20 node-1 puppet-user[11448]: Finished catalog run in 0.43 seconds
Jul 26 02:59:22 node-1 puppet-user[11926]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 26 02:59:22 node-1 puppet-user[11926]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Jul 26 02:59:22 node-1 puppet-user[11926]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 26 02:59:22 node-1 puppet-user[11926]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 26 02:59:22 node-1 puppet-user[11926]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 26 02:59:22 node-1 puppet-user[11926]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 26 02:59:22 node-1 puppet-user[11926]: Finished catalog run in 0.23 seconds
Jul 26 02:59:24 node-1 puppet-user[12399]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 26 02:59:24 node-1 puppet-user[12399]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Jul 26 02:59:24 node-1 puppet-user[12399]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 26 02:59:24 node-1 kernel: [   69.984122] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 26 02:59:24 node-1 kernel: [   69.984170] 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 26 02:59:24 node-1 puppet-user[12399]: (/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 26 02:59:24 node-1 puppet-user[12399]: Finished catalog run in 0.05 seconds
Jul 26 02:59:26 node-1 puppet-user[12856]: (Scope(Class[main])) MODULAR: sync_time
Jul 26 02:59:26 node-1 puppet-user[12856]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 26 02:59:26 node-1 ntpdate[13277]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 26 02:59:28 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796149 #8963] DEBUG -- : Trying to find block devices
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796227 #8963] DEBUG -- : Found block device: sda
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796253 #8963] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796271 #8963] DEBUG -- : Block device seems to be physical data storage: sda
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796290 #8963] DEBUG -- : Found block device: dm-0
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796302 #8963] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796315 #8963] DEBUG -- : Found block device: dm-1
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796326 #8963] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796355 #8963] DEBUG -- : Found block device: dm-2
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796365 #8963] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796373 #8963] DEBUG -- : Found block device: dm-3
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796382 #8963] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796391 #8963] DEBUG -- : Found block device: dm-4
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796400 #8963] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796408 #8963] DEBUG -- : Found block device: dm-5
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796417 #8963] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796426 #8963] DEBUG -- : Found block device: ram0
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796464 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796473 #8963] DEBUG -- : Found block device: ram1
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796481 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796490 #8963] DEBUG -- : Found block device: ram2
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796499 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796507 #8963] DEBUG -- : Found block device: ram3
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796516 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796524 #8963] DEBUG -- : Found block device: ram4
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796533 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796541 #8963] DEBUG -- : Found block device: ram5
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796570 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796579 #8963] DEBUG -- : Found block device: ram6
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796589 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796596 #8963] DEBUG -- : Found block device: ram7
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796605 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796614 #8963] DEBUG -- : Found block device: ram8
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796623 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796630 #8963] DEBUG -- : Found block device: ram9
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796639 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796648 #8963] DEBUG -- : Found block device: loop0
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796678 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796687 #8963] DEBUG -- : Found block device: loop1
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796696 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796705 #8963] DEBUG -- : Found block device: loop2
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796714 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796722 #8963] DEBUG -- : Found block device: loop3
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796731 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796739 #8963] DEBUG -- : Found block device: loop4
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796765 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796773 #8963] DEBUG -- : Found block device: loop5
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796782 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796791 #8963] DEBUG -- : Found block device: loop6
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796800 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796808 #8963] DEBUG -- : Found block device: loop7
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796843 #8963] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796852 #8963] DEBUG -- : Found block device: ram10
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796861 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796869 #8963] DEBUG -- : Found block device: ram11
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796878 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796886 #8963] DEBUG -- : Found block device: ram12
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796895 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796902 #8963] DEBUG -- : Found block device: ram13
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796911 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796919 #8963] DEBUG -- : Found block device: ram14
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796949 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796957 #8963] DEBUG -- : Found block device: ram15
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796966 #8963] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.796992 #8963] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 26 02:59:28 node-1 nailgun-agent: D, [2016-07-26T02:59:28.949803 #8963] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 26 02:59:28 node-1 nailgun-agent: I, [2016-07-26T02:59:28.949957 #8963]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 26 02:59:30 node-1 kernel: [   76.004481] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 02:59:30 node-1 puppet-agent[8929]: Could not run: SIGTERM
Jul 26 02:59:31 node-1 kernel: [   76.306339] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 26 02:59:31 node-1 ec2: 
Jul 26 02:59:31 node-1 ec2: #############################################################
Jul 26 02:59:31 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 26 02:59:31 node-1 ec2: 1024 4c:01:86:67:00:b5:fb:7c:83:ed:26:6f:b2:e8:96:6a  root@node-1.domain.tld (DSA)
Jul 26 02:59:31 node-1 ec2: 256 ed:58:35:c2:9b:ef:86:a9:01:bf:16:a0:c4:23:af:c7  root@node-1.domain.tld (ECDSA)
Jul 26 02:59:31 node-1 ec2: 256 0a:46:1f:05:a3:b9:fe:e7:e0:26:5f:d8:91:92:9a:7b  root@node-1.domain.tld (ED25519)
Jul 26 02:59:31 node-1 ec2: 2048 c3:14:a2:f4:d3:63:1d:66:73:85:08:3d:29:49:73:1a  root@node-1.domain.tld (RSA)
Jul 26 02:59:31 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 26 02:59:31 node-1 ec2: #############################################################
Jul 26 02:59:32 node-1 ntpdate[13277]: adjust time server 10.20.0.2 offset 0.000538 sec
Jul 26 02:59:32 node-1 puppet-user[12856]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 26 02:59:32 node-1 puppet-user[12856]: Finished catalog run in 6.18 seconds
Jul 26 02:59:37 node-1 puppet-user[13761]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 02:59:38 node-1 puppet-user[13761]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Jul 26 02:59:38 node-1 puppet-user[13761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 26 02:59:38 node-1 puppet-user[13761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 26 02:59:38 node-1 puppet-user[13761]: Finished catalog run in 0.07 seconds
Jul 26 02:59:39 node-1 puppet-user[14219]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 26 02:59:40 node-1 puppet-user[14219]: Compiled catalog for node-1.domain.tld in environment production in 1.39 seconds
Jul 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:41 node-1 puppet-user[14219]: (/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 26 02:59:50 node-1 puppet-user[14219]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 26 02:59:50 node-1 puppet-user[14219]: Finished catalog run in 9.35 seconds
Jul 26 02:59:52 node-1 puppet-user[15061]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 26 02:59:52 node-1 puppet-user[15061]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 26 02:59:56 node-1 puppet-user[15061]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 26 03:00:01 node-1 CRON[16218]: (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 26 03:00:16 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 03:00:16 node-1 nailgun-agent: I, [2016-07-26T03:00:16.124735 #16221]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 03:00:27 node-1 puppet-user[15061]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 26 03:00:27 node-1 puppet-user[15061]: Finished catalog run in 35.25 seconds
Jul 26 03:00:29 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 03:00:29 node-1 nailgun-agent: I, [2016-07-26T03:00:29.506978 #16221]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 26 03:00:29 node-1 puppet-user[17694]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 26 03:00:30 node-1 puppet-user[17694]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Jul 26 03:00:30 node-1 puppet-user[17694]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 26 03:00:30 node-1 puppet-user[17694]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 26 03:00:30 node-1 puppet-user[17694]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 26 03:00:30 node-1 puppet-user[17694]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 26 03:00:30 node-1 puppet-user[17694]: Finished catalog run in 0.08 seconds
Jul 26 03:00:32 node-1 puppet-user[18325]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 26 03:00:33 node-1 puppet-user[18325]: Compiled catalog for node-1.domain.tld in environment production in 0.88 seconds
Jul 26 03:00:33 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 26 03:00:33 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 26 03:00:33 node-1 crontab[18766]: (root) LIST (root)
Jul 26 03:00:33 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 26 03:00:33 node-1 crontab[18767]: (root) REPLACE (root)
Jul 26 03:00:35 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 26 03:00:36 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 26 03:00:37 node-1 puppet-user[18325]: (/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 26 03:00:37 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 26 03:00:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:38 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 26 03:00:39 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:39 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:39 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:39 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:00:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:01:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:03 node-1 ntpdate[29964]: no servers can be used, exiting
<27>Jul 26 03:02:03 node-1 ntpdate[30069]: no servers can be used, exiting
<27>Jul 26 03:02:03 node-1 ntpdate[30265]: no servers can be used, exiting
<27>Jul 26 03:02:35 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:35 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:35 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:35 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:35 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:38 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:38 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:38 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:38 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:38 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:02:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:03:55 node-1 multipathd: uevent trigger error
<27>Jul 26 03:03:55 node-1 multipathd: uevent trigger error
<27>Jul 26 03:03:55 node-1 multipathd: uevent trigger error
<27>Jul 26 03:03:55 node-1 multipathd: uevent trigger error
<27>Jul 26 03:03:55 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:04 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:04 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:04 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:04 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:04 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:06 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 03:04:06 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 03:04:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 03:04:12 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 03:04:18 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 03:04:23 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 03:04:23 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 03:04:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:04:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-1 multipathd: uevent trigger error
<129>Jul 26 03:05:19 node-1 haproxy[24640]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 144ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:05:19 node-1 haproxy[24640]: proxy odl-neutron-endpoint has no server available!
<129>Jul 26 03:05:20 node-1 haproxy[24648]: Server odl-jetty/node-1 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 26 03:05:20 node-1 haproxy[24648]: proxy odl-jetty has no server available!
<27>Jul 26 03:05:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:43 node-1 multipathd: uevent trigger error
<129>Jul 26 03:05:45 node-1 haproxy[27394]: 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 26 03:05:45 node-1 haproxy[27394]: Backup Server mysqld/node-4 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 26 03:05:46 node-1 haproxy[27398]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:05:46 node-1 haproxy[27398]: proxy mysqld has no server available!
<27>Jul 26 03:05:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-1 multipathd: uevent trigger error
<129>Jul 26 03:05:54 node-1 haproxy[30024]: 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 26 03:05:54 node-1 haproxy[30024]: Backup Server mysqld/node-4 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 26 03:05:54 node-1 haproxy[30024]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:05:54 node-1 haproxy[30024]: proxy mysqld has no server available!
<129>Jul 26 03:05:55 node-1 haproxy[30030]: 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 26 03:05:55 node-1 haproxy[30030]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:05:55 node-1 haproxy[30030]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:05:55 node-1 haproxy[30030]: proxy object-storage has no server available!
<27>Jul 26 03:05:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:05:57 node-1 multipathd: uevent trigger error
<129>Jul 26 03:05:59 node-1 haproxy[31415]: 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 26 03:06:00 node-1 haproxy[31419]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:00 node-1 haproxy[31419]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:00 node-1 haproxy[31419]: proxy neutron has no server available!
<129>Jul 26 03:06:00 node-1 haproxy[31419]: 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 26 03:06:00 node-1 haproxy[31419]: Backup Server mysqld/node-4 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 26 03:06:00 node-1 haproxy[31419]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:00 node-1 haproxy[31419]: proxy mysqld has no server available!
<129>Jul 26 03:06:00 node-1 haproxy[31419]: 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 26 03:06:01 node-1 haproxy[31419]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:01 node-1 haproxy[31419]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:01 node-1 haproxy[31419]: proxy object-storage has no server available!
<27>Jul 26 03:06:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:05 node-1 haproxy[384]: 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 26 03:06:05 node-1 haproxy[384]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:05 node-1 haproxy[384]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:05 node-1 haproxy[384]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:05 node-1 haproxy[384]: 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 26 03:06:05 node-1 haproxy[384]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:06 node-1 haproxy[389]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:06 node-1 haproxy[389]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:06 node-1 haproxy[389]: 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 26 03:06:06 node-1 haproxy[389]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:06 node-1 haproxy[389]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:06 node-1 haproxy[389]: proxy neutron has no server available!
<129>Jul 26 03:06:06 node-1 haproxy[389]: 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 26 03:06:06 node-1 haproxy[389]: Backup Server mysqld/node-4 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 26 03:06:06 node-1 haproxy[389]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:06 node-1 haproxy[389]: proxy mysqld has no server available!
<129>Jul 26 03:06:06 node-1 haproxy[389]: 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 26 03:06:07 node-1 haproxy[389]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:07 node-1 haproxy[389]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:07 node-1 haproxy[389]: proxy object-storage has no server available!
<27>Jul 26 03:06:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:08 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:11 node-1 haproxy[1828]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:11 node-1 haproxy[1828]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:11 node-1 haproxy[1828]: proxy neutron has no server available!
<129>Jul 26 03:06:11 node-1 haproxy[1828]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:12 node-1 haproxy[1832]: Backup Server mysqld/node-4 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 26 03:06:12 node-1 haproxy[1832]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:12 node-1 haproxy[1832]: proxy mysqld has no server available!
<129>Jul 26 03:06:12 node-1 haproxy[1832]: 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 26 03:06:12 node-1 haproxy[1832]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:12 node-1 haproxy[1832]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:12 node-1 haproxy[1832]: proxy object-storage has no server available!
<129>Jul 26 03:06:12 node-1 haproxy[1832]: 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 26 03:06:12 node-1 haproxy[1832]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:12 node-1 haproxy[1832]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:12 node-1 haproxy[1832]: proxy aodh has no server available!
<27>Jul 26 03:06:14 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:14 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:14 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:14 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:14 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:16 node-1 haproxy[3256]: 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 26 03:06:16 node-1 haproxy[3256]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:16 node-1 haproxy[3256]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:16 node-1 haproxy[3256]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:16 node-1 haproxy[3256]: 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 26 03:06:17 node-1 haproxy[3260]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:17 node-1 haproxy[3260]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:17 node-1 haproxy[3260]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:17 node-1 haproxy[3260]: 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 26 03:06:17 node-1 haproxy[3260]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:17 node-1 haproxy[3260]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:17 node-1 haproxy[3260]: proxy neutron has no server available!
<129>Jul 26 03:06:17 node-1 haproxy[3260]: 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 26 03:06:17 node-1 haproxy[3260]: Backup Server mysqld/node-4 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 26 03:06:17 node-1 haproxy[3260]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:17 node-1 haproxy[3260]: proxy mysqld has no server available!
<129>Jul 26 03:06:17 node-1 haproxy[3260]: 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 26 03:06:17 node-1 haproxy[3260]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:17 node-1 haproxy[3260]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:17 node-1 haproxy[3260]: proxy object-storage has no server available!
<129>Jul 26 03:06:18 node-1 haproxy[3260]: 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 26 03:06:18 node-1 haproxy[3260]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:18 node-1 haproxy[3260]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:18 node-1 haproxy[3260]: proxy aodh has no server available!
<129>Jul 26 03:06:18 node-1 haproxy[3260]: 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 26 03:06:18 node-1 haproxy[3260]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:18 node-1 haproxy[3260]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:18 node-1 haproxy[3260]: proxy ceilometer has no server available!
<27>Jul 26 03:06:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:20 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:22 node-1 haproxy[4830]: 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 26 03:06:22 node-1 haproxy[4830]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:22 node-1 haproxy[4830]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:22 node-1 haproxy[4830]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:22 node-1 haproxy[4830]: 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 26 03:06:22 node-1 haproxy[4830]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:22 node-1 haproxy[4830]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:22 node-1 haproxy[4830]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:22 node-1 haproxy[4830]: 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 26 03:06:22 node-1 haproxy[4830]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:22 node-1 haproxy[4830]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:22 node-1 haproxy[4830]: proxy neutron has no server available!
<129>Jul 26 03:06:22 node-1 haproxy[4830]: 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 26 03:06:23 node-1 haproxy[4834]: Backup Server mysqld/node-4 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 26 03:06:23 node-1 haproxy[4834]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:23 node-1 haproxy[4834]: proxy mysqld has no server available!
<129>Jul 26 03:06:23 node-1 haproxy[4834]: 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 26 03:06:23 node-1 haproxy[4834]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:23 node-1 haproxy[4834]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:23 node-1 haproxy[4834]: proxy object-storage has no server available!
<129>Jul 26 03:06:23 node-1 haproxy[4834]: 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 26 03:06:23 node-1 haproxy[4834]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:23 node-1 haproxy[4834]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:23 node-1 haproxy[4834]: proxy aodh has no server available!
<129>Jul 26 03:06:23 node-1 haproxy[4834]: 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 26 03:06:23 node-1 haproxy[4834]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:23 node-1 haproxy[4834]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:23 node-1 haproxy[4834]: proxy ceilometer has no server available!
<27>Jul 26 03:06:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:25 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:27 node-1 haproxy[6283]: 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 26 03:06:27 node-1 haproxy[6283]: 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 26 03:06:27 node-1 haproxy[6283]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:27 node-1 haproxy[6283]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:27 node-1 haproxy[6283]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:27 node-1 haproxy[6283]: 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 26 03:06:28 node-1 haproxy[6287]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:28 node-1 haproxy[6287]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:28 node-1 haproxy[6287]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:28 node-1 haproxy[6287]: 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 26 03:06:28 node-1 haproxy[6287]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:28 node-1 haproxy[6287]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:28 node-1 haproxy[6287]: proxy neutron has no server available!
<129>Jul 26 03:06:28 node-1 haproxy[6287]: 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 26 03:06:28 node-1 haproxy[6287]: Backup Server mysqld/node-4 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 26 03:06:28 node-1 haproxy[6287]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:28 node-1 haproxy[6287]: proxy mysqld has no server available!
<129>Jul 26 03:06:28 node-1 haproxy[6287]: 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 26 03:06:28 node-1 haproxy[6287]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:28 node-1 haproxy[6287]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:28 node-1 haproxy[6287]: proxy object-storage has no server available!
<129>Jul 26 03:06:28 node-1 haproxy[6287]: 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 26 03:06:28 node-1 haproxy[6287]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:29 node-1 haproxy[6287]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:29 node-1 haproxy[6287]: proxy aodh has no server available!
<129>Jul 26 03:06:29 node-1 haproxy[6287]: 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 26 03:06:29 node-1 haproxy[6287]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:29 node-1 haproxy[6287]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:29 node-1 haproxy[6287]: proxy ceilometer has no server available!
<27>Jul 26 03:06:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:30 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:33 node-1 haproxy[7935]: 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 26 03:06:33 node-1 haproxy[7935]: 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 26 03:06:33 node-1 haproxy[7935]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:33 node-1 haproxy[7935]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:33 node-1 haproxy[7935]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:33 node-1 haproxy[7935]: 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 26 03:06:33 node-1 haproxy[7935]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:34 node-1 haproxy[7944]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:34 node-1 haproxy[7944]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:34 node-1 haproxy[7944]: 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 26 03:06:34 node-1 haproxy[7944]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:34 node-1 haproxy[7944]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:34 node-1 haproxy[7944]: proxy glance-api has no server available!
<129>Jul 26 03:06:34 node-1 haproxy[7944]: 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 26 03:06:34 node-1 haproxy[7944]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:34 node-1 haproxy[7944]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:34 node-1 haproxy[7944]: proxy glance-glare has no server available!
<129>Jul 26 03:06:34 node-1 haproxy[7944]: 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 26 03:06:34 node-1 haproxy[7944]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:34 node-1 haproxy[7944]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:34 node-1 haproxy[7944]: proxy neutron has no server available!
<129>Jul 26 03:06:34 node-1 haproxy[7944]: 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 26 03:06:34 node-1 haproxy[7944]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:34 node-1 haproxy[7944]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:34 node-1 haproxy[7944]: proxy glance-registry has no server available!
<129>Jul 26 03:06:34 node-1 haproxy[7944]: 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 26 03:06:34 node-1 haproxy[7944]: Backup Server mysqld/node-4 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 26 03:06:34 node-1 haproxy[7944]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:34 node-1 haproxy[7944]: proxy mysqld has no server available!
<129>Jul 26 03:06:34 node-1 haproxy[7944]: 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 26 03:06:35 node-1 haproxy[7944]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:35 node-1 haproxy[7944]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:35 node-1 haproxy[7944]: proxy object-storage has no server available!
<129>Jul 26 03:06:35 node-1 haproxy[7944]: 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 26 03:06:35 node-1 haproxy[7944]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:35 node-1 haproxy[7944]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:35 node-1 haproxy[7944]: proxy aodh has no server available!
<129>Jul 26 03:06:35 node-1 haproxy[7944]: 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 26 03:06:35 node-1 haproxy[7944]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:35 node-1 haproxy[7944]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:35 node-1 haproxy[7944]: proxy ceilometer has no server available!
<27>Jul 26 03:06:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:36 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:39 node-1 haproxy[9439]: 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 26 03:06:39 node-1 haproxy[9439]: 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 26 03:06:39 node-1 haproxy[9439]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:39 node-1 haproxy[9439]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:39 node-1 haproxy[9439]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:39 node-1 haproxy[9439]: 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 26 03:06:39 node-1 haproxy[9439]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:39 node-1 haproxy[9439]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:39 node-1 haproxy[9439]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:40 node-1 haproxy[9443]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:40 node-1 haproxy[9443]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:40 node-1 haproxy[9443]: proxy nova-api has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:40 node-1 haproxy[9443]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:40 node-1 haproxy[9443]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:40 node-1 haproxy[9443]: proxy nova-metadata-api has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:40 node-1 haproxy[9443]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:40 node-1 haproxy[9443]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:40 node-1 haproxy[9443]: proxy glance-api has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:40 node-1 haproxy[9443]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:40 node-1 haproxy[9443]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:40 node-1 haproxy[9443]: proxy glance-glare has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:40 node-1 haproxy[9443]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:40 node-1 haproxy[9443]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:40 node-1 haproxy[9443]: proxy neutron has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:40 node-1 haproxy[9443]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:40 node-1 haproxy[9443]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:40 node-1 haproxy[9443]: proxy glance-registry has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:40 node-1 haproxy[9443]: Backup Server mysqld/node-4 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 26 03:06:40 node-1 haproxy[9443]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:40 node-1 haproxy[9443]: proxy mysqld has no server available!
<129>Jul 26 03:06:40 node-1 haproxy[9443]: 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 26 03:06:41 node-1 haproxy[9443]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:41 node-1 haproxy[9443]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:41 node-1 haproxy[9443]: proxy object-storage has no server available!
<129>Jul 26 03:06:41 node-1 haproxy[9443]: 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 26 03:06:41 node-1 haproxy[9443]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:41 node-1 haproxy[9443]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:41 node-1 haproxy[9443]: proxy aodh has no server available!
<129>Jul 26 03:06:41 node-1 haproxy[9443]: 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 26 03:06:41 node-1 haproxy[9443]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:41 node-1 haproxy[9443]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:41 node-1 haproxy[9443]: proxy ceilometer has no server available!
<129>Jul 26 03:06:41 node-1 haproxy[9443]: 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 26 03:06:41 node-1 haproxy[9443]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:41 node-1 haproxy[9443]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:41 node-1 haproxy[9443]: proxy nova-novncproxy has no server available!
<27>Jul 26 03:06:42 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:42 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:42 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:42 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:43 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:45 node-1 haproxy[10863]: 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 26 03:06:45 node-1 haproxy[10863]: 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 26 03:06:45 node-1 haproxy[10863]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:45 node-1 haproxy[10863]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:45 node-1 haproxy[10863]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:45 node-1 haproxy[10863]: 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 26 03:06:45 node-1 haproxy[10863]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:45 node-1 haproxy[10863]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:45 node-1 haproxy[10863]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:45 node-1 haproxy[10863]: 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 26 03:06:45 node-1 haproxy[10863]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:45 node-1 haproxy[10863]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:45 node-1 haproxy[10863]: proxy nova-api has no server available!
<129>Jul 26 03:06:45 node-1 haproxy[10863]: 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 26 03:06:45 node-1 haproxy[10863]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:45 node-1 haproxy[10863]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:45 node-1 haproxy[10863]: proxy nova-metadata-api has no server available!
<129>Jul 26 03:06:45 node-1 haproxy[10863]: 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 26 03:06:45 node-1 haproxy[10863]: Backup Server cinder-api/node-4 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 26 03:06:45 node-1 haproxy[10863]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:45 node-1 haproxy[10863]: proxy cinder-api has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:46 node-1 haproxy[10867]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:46 node-1 haproxy[10867]: proxy glance-api has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:46 node-1 haproxy[10867]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:46 node-1 haproxy[10867]: proxy glance-glare has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:46 node-1 haproxy[10867]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:46 node-1 haproxy[10867]: proxy neutron has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:46 node-1 haproxy[10867]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:46 node-1 haproxy[10867]: proxy glance-registry has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Backup Server mysqld/node-4 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 26 03:06:46 node-1 haproxy[10867]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:46 node-1 haproxy[10867]: proxy mysqld has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:46 node-1 haproxy[10867]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:46 node-1 haproxy[10867]: proxy object-storage has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:46 node-1 haproxy[10867]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:46 node-1 haproxy[10867]: proxy aodh has no server available!
<129>Jul 26 03:06:46 node-1 haproxy[10867]: 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 26 03:06:46 node-1 haproxy[10867]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:47 node-1 haproxy[10867]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:47 node-1 haproxy[10867]: proxy ceilometer has no server available!
<129>Jul 26 03:06:47 node-1 haproxy[10867]: 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 26 03:06:47 node-1 haproxy[10867]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:47 node-1 haproxy[10867]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:47 node-1 haproxy[10867]: proxy nova-novncproxy has no server available!
<27>Jul 26 03:06:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:48 node-1 multipathd: uevent trigger error
<129>Jul 26 03:06:51 node-1 haproxy[12350]: 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 26 03:06:51 node-1 haproxy[12350]: 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 26 03:06:51 node-1 haproxy[12350]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:51 node-1 haproxy[12350]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:51 node-1 haproxy[12350]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:51 node-1 haproxy[12350]: 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 26 03:06:51 node-1 haproxy[12350]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:51 node-1 haproxy[12350]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:51 node-1 haproxy[12350]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:51 node-1 haproxy[12350]: 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 26 03:06:51 node-1 haproxy[12350]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:51 node-1 haproxy[12350]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:51 node-1 haproxy[12350]: proxy nova-api has no server available!
<129>Jul 26 03:06:51 node-1 haproxy[12350]: 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 26 03:06:51 node-1 haproxy[12350]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:51 node-1 haproxy[12350]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:51 node-1 haproxy[12350]: proxy nova-metadata-api has no server available!
<129>Jul 26 03:06:51 node-1 haproxy[12350]: 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 26 03:06:51 node-1 haproxy[12350]: Backup Server cinder-api/node-4 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 26 03:06:51 node-1 haproxy[12350]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:51 node-1 haproxy[12350]: proxy cinder-api has no server available!
<129>Jul 26 03:06:51 node-1 haproxy[12350]: 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 26 03:06:52 node-1 haproxy[12359]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy glance-api has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy glance-glare has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy neutron has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy glance-registry has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Backup Server mysqld/node-4 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 26 03:06:52 node-1 haproxy[12359]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy mysqld has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy object-storage has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy aodh has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy ceilometer has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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.
<27>Jul 26 03:06:52 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:52 node-1 haproxy[12359]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:52 node-1 haproxy[12359]: proxy heat-api has no server available!
<129>Jul 26 03:06:52 node-1 haproxy[12359]: 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 26 03:06:52 node-1 haproxy[12359]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:53 node-1 haproxy[12359]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:53 node-1 haproxy[12359]: proxy heat-api-cfn has no server available!
<129>Jul 26 03:06:53 node-1 haproxy[12359]: 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 26 03:06:53 node-1 haproxy[12359]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:53 node-1 haproxy[12359]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:53 node-1 haproxy[12359]: proxy heat-api-cloudwatch has no server available!
<129>Jul 26 03:06:53 node-1 haproxy[12359]: 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 26 03:06:53 node-1 haproxy[12359]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:53 node-1 haproxy[12359]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 03:06:53 node-1 haproxy[12359]: proxy nova-novncproxy has no server available!
<27>Jul 26 03:06:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:06:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:07:00 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 03:07:08 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 03:07:33 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 26 03:07:35 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 26 03:08:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 03:10:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:10:54 node-1 multipathd: uevent trigger error
<43>Jul 26 03:11:08 node-1 apache2_error [Tue Jul 26 03:11:07.122869 2016] [mpm_event:notice] [pid 24174:tid 139641754773376] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 03:11:08 node-1 apache2_error [Tue Jul 26 03:11:07.122962 2016] [core:notice] [pid 24174:tid 139641754773376] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:11:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:15 node-1 multipathd: uevent trigger error
<43>Jul 26 03:11:18 node-1 apache2_error [Tue Jul 26 03:11:10.204808 2016] [mpm_event:notice] [pid 24174:tid 139641754773376] AH00491: caught SIGTERM, shutting down
<43>Jul 26 03:11:18 node-1 apache2_error [Tue Jul 26 03:11:11.296367 2016] [mpm_worker:notice] [pid 24967:tid 139935813662592] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 03:11:18 node-1 apache2_error [Tue Jul 26 03:11:11.296435 2016] [core:notice] [pid 24967:tid 139935813662592] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:11:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:20 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:11:24 node-1 multipathd: uevent trigger error
<43>Jul 26 03:12:39 node-1 apache2_error [Tue Jul 26 03:12:32.345141 2016] [mpm_worker:notice] [pid 24967:tid 139935813662592] AH00295: caught SIGTERM, shutting down
<43>Jul 26 03:12:39 node-1 apache2_error [Tue Jul 26 03:12:33.104129 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:12:39 node-1 apache2_error [Tue Jul 26 03:12:33.104153 2016] [core:notice] [pid 6870:tid 140659679876992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:13:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 26 03:13:19 node-1 apache2_error [Tue Jul 26 03:13:16.971716 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:13:19 node-1 apache2_error [Tue Jul 26 03:13:17.169904 2016] [mpm_worker:warn] [pid 6870:tid 140659679876992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:13:19 node-1 apache2_error [Tue Jul 26 03:13:17.172978 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:13:19 node-1 apache2_error [Tue Jul 26 03:13:17.172992 2016] [core:notice] [pid 6870:tid 140659679876992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:14:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:06 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:06 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:06 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:06 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:06 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:06 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:22 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:22 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:22 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:22 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:22 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:40 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:40 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:14:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:00 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:00 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:00 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:00 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:15:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:16:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 03:17:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:17:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:17:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:17:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:17:15 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:18:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:19:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 03:21:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:24 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:30 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:01 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 03:22:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:22:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:29 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:29 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:29 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:29 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:29 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:23:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:25:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 03:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:54 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:59 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:59 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:59 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:59 node-1 multipathd: uevent trigger error
<27>Jul 26 03:26:59 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:48 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:53 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:27:58 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 03:28:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:28:43 node-1 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:08 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:09 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:09 node-1 multipathd: uevent trigger error
<11>Jul 26 03:30:23 node-1 liberasurecode[21323]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:23 node-1 liberasurecode[21323]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:23 node-1 liberasurecode[21323]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:23 node-1 liberasurecode[21323]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:23 node-1 liberasurecode[21353]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:23 node-1 liberasurecode[21353]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:23 node-1 liberasurecode[21353]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:23 node-1 liberasurecode[21353]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:25 node-1 liberasurecode[21779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:25 node-1 liberasurecode[21779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:25 node-1 liberasurecode[21779]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:25 node-1 liberasurecode[21779]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:30 node-1 liberasurecode[22657]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:30 node-1 liberasurecode[22657]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:30 node-1 liberasurecode[22657]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:30 node-1 liberasurecode[22657]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22704]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22704]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22749]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22749]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22749]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22749]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22810]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22810]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22810]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22810]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22827]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22827]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22848]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22848]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22848]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22848]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22867]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22867]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22867]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:31 node-1 liberasurecode[22867]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:48 node-1 liberasurecode[25659]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:48 node-1 liberasurecode[25659]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:48 node-1 liberasurecode[25659]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:30:48 node-1 liberasurecode[25659]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 03:30:56 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:56 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:56 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:56 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:56 node-1 multipathd: uevent trigger error
<27>Jul 26 03:30:56 node-1 multipathd: uevent trigger error
<27>Jul 26 03:31:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 26 03:31:50 node-1 apache2_error [Tue Jul 26 03:31:43.707192 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:31:50 node-1 apache2_error [Tue Jul 26 03:31:44.087666 2016] [mpm_worker:warn] [pid 6870:tid 140659679876992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:31:50 node-1 apache2_error [Tue Jul 26 03:31:44.090545 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:31:50 node-1 apache2_error [Tue Jul 26 03:31:44.090558 2016] [core:notice] [pid 6870:tid 140659679876992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:32:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:25 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:25 node-1 multipathd: uevent trigger error
<43>Jul 26 03:32:30 node-1 apache2_error [Tue Jul 26 03:32:21.219876 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:32:30 node-1 apache2_error [Tue Jul 26 03:32:21.416309 2016] [mpm_worker:warn] [pid 6870:tid 140659679876992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:32:30 node-1 apache2_error [Tue Jul 26 03:32:21.429935 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:32:30 node-1 apache2_error [Tue Jul 26 03:32:21.429968 2016] [core:notice] [pid 6870:tid 140659679876992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:32:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:32:32 node-1 multipathd: uevent trigger error
<43>Jul 26 03:33:10 node-1 apache2_error [Tue Jul 26 03:33:06.909257 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:33:10 node-1 apache2_error [Tue Jul 26 03:33:07.105340 2016] [mpm_worker:warn] [pid 6870:tid 140659679876992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:33:10 node-1 apache2_error [Tue Jul 26 03:33:07.114236 2016] [mpm_worker:notice] [pid 6870:tid 140659679876992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:33:10 node-1 apache2_error [Tue Jul 26 03:33:07.114264 2016] [core:notice] [pid 6870:tid 140659679876992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:33:10 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:11 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:11 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:11 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:11 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:17 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:17 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:17 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:17 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:17 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:31 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:31 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:31 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:31 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:33:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:07 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:14 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 26 03:34:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:23 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-1 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-1 multipathd: uevent trigger error
<11>Jul 26 03:35:01 node-1 liberasurecode[17195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:35:01 node-1 liberasurecode[17195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:35:01 node-1 liberasurecode[17195]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:35:01 node-1 liberasurecode[17195]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 03:35:09 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 03:35:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:19 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:40 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:40 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:40 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:40 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:44 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:45 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:35:57 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:27 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:32 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:36 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:41 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:46 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:50 node-1 multipathd: uevent trigger error
<27>Jul 26 03:36:50 node-1 multipathd: uevent trigger error
