Sep  9 03:49:48 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8393" x-info="http://www.rsyslog.com"] start
Sep  9 03:49:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep  9 03:49:48 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep  9 03:49:48 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep  9 03:49:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep  9 03:49:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep  9 03:49:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep  9 03:49:48 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep  9 03:49:48 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f9a0d0de-58dc-4e0f-956a-4475bbc94113 nomdmonddf nomdmonisw
Sep  9 03:49:48 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep  9 03:49:48 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep  9 03:49:48 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep  9 03:49:48 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep  9 03:49:48 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep  9 03:49:48 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep  9 03:49:48 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep  9 03:49:48 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Sep  9 03:49:48 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep  9 03:49:48 node-1 kernel: [    0.000000] No AGP bridge found
Sep  9 03:49:48 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep  9 03:49:48 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep  9 03:49:48 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep  9 03:49:48 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep  9 03:49:48 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep  9 03:49:48 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep  9 03:49:48 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep  9 03:49:48 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep  9 03:49:48 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep  9 03:49:48 node-1 kernel: [    0.000000]   2 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000]   3 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000]   4 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000]   5 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000]   6 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000]   7 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000]   8 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000]   9 disabled
Sep  9 03:49:48 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep  9 03:49:48 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep  9 03:49:48 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep  9 03:49:48 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep  9 03:49:48 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep  9 03:49:48 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep  9 03:49:48 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep  9 03:49:48 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep  9 03:49:48 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep  9 03:49:48 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep  9 03:49:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep  9 03:49:48 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep  9 03:49:48 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep  9 03:49:48 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep  9 03:49:48 node-1 kernel: [    0.000000] Zone ranges:
Sep  9 03:49:48 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] Movable zone start for each node
Sep  9 03:49:48 node-1 kernel: [    0.000000] Early memory node ranges
Sep  9 03:49:48 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep  9 03:49:48 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep  9 03:49:48 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep  9 03:49:48 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep  9 03:49:48 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep  9 03:49:48 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep  9 03:49:48 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep  9 03:49:48 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep  9 03:49:48 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep  9 03:49:48 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep  9 03:49:48 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep  9 03:49:48 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep  9 03:49:48 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep  9 03:49:48 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep  9 03:49:48 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep  9 03:49:48 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep  9 03:49:48 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep  9 03:49:48 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep  9 03:49:48 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep  9 03:49:48 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep  9 03:49:48 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep  9 03:49:48 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep  9 03:49:48 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep  9 03:49:48 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Sep  9 03:49:48 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep  9 03:49:48 node-1 kernel: [    0.000000] Policy zone: Normal
Sep  9 03:49:48 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f9a0d0de-58dc-4e0f-956a-4475bbc94113 nomdmonddf nomdmonisw
Sep  9 03:49:48 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep  9 03:49:48 node-1 kernel: [    0.000000] Checking aperture...
Sep  9 03:49:48 node-1 kernel: [    0.000000] No AGP bridge found
Sep  9 03:49:48 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep  9 03:49:48 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep  9 03:49:48 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep  9 03:49:48 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep  9 03:49:48 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep  9 03:49:48 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep  9 03:49:48 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep  9 03:49:48 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep  9 03:49:48 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep  9 03:49:48 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep  9 03:49:48 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep  9 03:49:48 node-1 kernel: [    0.000000] console [tty0] enabled
Sep  9 03:49:48 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep  9 03:49:48 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep  9 03:49:48 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep  9 03:49:48 node-1 kernel: [    0.000000] hpet clockevent registered
Sep  9 03:49:48 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep  9 03:49:48 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep  9 03:49:48 node-1 kernel: [    0.004000] tsc: Detected 3491.983 MHz processor
Sep  9 03:49:48 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.96 BogoMIPS (lpj=13967932)
Sep  9 03:49:48 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep  9 03:49:48 node-1 kernel: [    0.000048] Security Framework initialized
Sep  9 03:49:48 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Sep  9 03:49:48 node-1 kernel: [    0.000068] Yama: becoming mindful.
Sep  9 03:49:48 node-1 kernel: [    0.001461] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.006403] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.008326] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.008353] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.008644] Initializing cgroup subsys memory
Sep  9 03:49:48 node-1 kernel: [    0.008652] Initializing cgroup subsys devices
Sep  9 03:49:48 node-1 kernel: [    0.008654] Initializing cgroup subsys freezer
Sep  9 03:49:48 node-1 kernel: [    0.008656] Initializing cgroup subsys blkio
Sep  9 03:49:48 node-1 kernel: [    0.008657] Initializing cgroup subsys perf_event
Sep  9 03:49:48 node-1 kernel: [    0.008660] Initializing cgroup subsys hugetlb
Sep  9 03:49:48 node-1 kernel: [    0.008680] CPU: Physical Processor ID: 0
Sep  9 03:49:48 node-1 kernel: [    0.008681] CPU: Processor Core ID: 0
Sep  9 03:49:48 node-1 kernel: [    0.008684] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep  9 03:49:48 node-1 kernel: [    0.008684] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep  9 03:49:48 node-1 kernel: [    0.009378] mce: CPU supports 22 MCE banks
Sep  9 03:49:48 node-1 kernel: [    0.009405] CPU0: Thermal monitoring enabled (TM1)
Sep  9 03:49:48 node-1 kernel: [    0.009426] process: using mwait in idle threads
Sep  9 03:49:48 node-1 kernel: [    0.009429] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep  9 03:49:48 node-1 kernel: [    0.009429] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep  9 03:49:48 node-1 kernel: [    0.009429] tlb_flushall_shift: 6
Sep  9 03:49:48 node-1 kernel: [    0.009517] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep  9 03:49:48 node-1 kernel: [    0.010239] ACPI: Core revision 20131115
Sep  9 03:49:48 node-1 kernel: [    0.022922] ACPI: All ACPI Tables successfully acquired
Sep  9 03:49:48 node-1 kernel: [    0.023081] ftrace: allocating 28617 entries in 112 pages
Sep  9 03:49:48 node-1 kernel: [    0.032056] dmar: Host address width 46
Sep  9 03:49:48 node-1 kernel: [    0.032058] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep  9 03:49:48 node-1 kernel: [    0.032064] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  9 03:49:48 node-1 kernel: [    0.032066] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep  9 03:49:48 node-1 kernel: [    0.032069] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  9 03:49:48 node-1 kernel: [    0.032071] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep  9 03:49:48 node-1 kernel: [    0.032072] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep  9 03:49:48 node-1 kernel: [    0.032073] dmar: ATSR flags: 0x0
Sep  9 03:49:48 node-1 kernel: [    0.032074] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep  9 03:49:48 node-1 kernel: [    0.032075] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep  9 03:49:48 node-1 kernel: [    0.032191] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep  9 03:49:48 node-1 kernel: [    0.032192] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep  9 03:49:48 node-1 kernel: [    0.032193] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep  9 03:49:48 node-1 kernel: [    0.032194] HPET id 0 under DRHD base 0xc7ffc000
Sep  9 03:49:48 node-1 kernel: [    0.032195] Your BIOS is broken and requested that x2apic be disabled.
Sep  9 03:49:48 node-1 kernel: [    0.032195] This will slightly decrease performance.
Sep  9 03:49:48 node-1 kernel: [    0.032195] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep  9 03:49:48 node-1 kernel: [    0.032628] Enabled IRQ remapping in xapic mode
Sep  9 03:49:48 node-1 kernel: [    0.032629] x2apic not enabled, IRQ remapping is in xapic mode
Sep  9 03:49:48 node-1 kernel: [    0.032633] Switched APIC routing to physical flat.
Sep  9 03:49:48 node-1 kernel: [    0.033250] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep  9 03:49:48 node-1 kernel: [    0.072901] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep  9 03:49:48 node-1 kernel: [    0.072906] TSC deadline timer enabled
Sep  9 03:49:48 node-1 kernel: [    0.072914] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep  9 03:49:48 node-1 kernel: [    0.072920] ... version:                3
Sep  9 03:49:48 node-1 kernel: [    0.072921] ... bit width:              48
Sep  9 03:49:48 node-1 kernel: [    0.072922] ... generic registers:      4
Sep  9 03:49:48 node-1 kernel: [    0.072923] ... value mask:             0000ffffffffffff
Sep  9 03:49:48 node-1 kernel: [    0.072924] ... max period:             0000ffffffffffff
Sep  9 03:49:48 node-1 kernel: [    0.072925] ... fixed-purpose events:   3
Sep  9 03:49:48 node-1 kernel: [    0.072925] ... event mask:             000000070000000f
Sep  9 03:49:48 node-1 kernel: [    0.074331] x86: Booting SMP configuration:
Sep  9 03:49:48 node-1 kernel: [    0.088437] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep  9 03:49:48 node-1 kernel: [    0.074332] .... node  #0, CPUs:        #1  #2  #3
Sep  9 03:49:48 node-1 kernel: [    0.116344] .... node  #1, CPUs:    #4  #5  #6  #7
Sep  9 03:49:48 node-1 kernel: [    0.270506] .... node  #0, CPUs:    #8  #9 #10 #11
Sep  9 03:49:48 node-1 kernel: [    0.326122] .... node  #1, CPUs:   #12 #13 #14 #15
Sep  9 03:49:48 node-1 kernel: [    0.382980] x86: Booted up 2 nodes, 16 CPUs
Sep  9 03:49:48 node-1 kernel: [    0.382983] smpboot: Total of 16 processors activated (111755.87 BogoMIPS)
Sep  9 03:49:48 node-1 kernel: [    0.406965] devtmpfs: initialized
Sep  9 03:49:48 node-1 kernel: [    0.410072] EVM: security.selinux
Sep  9 03:49:48 node-1 kernel: [    0.410074] EVM: security.SMACK64
Sep  9 03:49:48 node-1 kernel: [    0.410075] EVM: security.ima
Sep  9 03:49:48 node-1 kernel: [    0.410075] EVM: security.capability
Sep  9 03:49:48 node-1 kernel: [    0.410124] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.410812] pinctrl core: initialized pinctrl subsystem
Sep  9 03:49:48 node-1 kernel: [    0.410876] regulator-dummy: no parameters
Sep  9 03:49:48 node-1 kernel: [    0.410908] RTC time:  3:49:12, date: 09/09/16
Sep  9 03:49:48 node-1 kernel: [    0.410943] NET: Registered protocol family 16
Sep  9 03:49:48 node-1 kernel: [    0.411029] cpuidle: using governor ladder
Sep  9 03:49:48 node-1 kernel: [    0.411030] cpuidle: using governor menu
Sep  9 03:49:48 node-1 kernel: [    0.411066] ACPI: bus type PCI registered
Sep  9 03:49:48 node-1 kernel: [    0.411069] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep  9 03:49:48 node-1 kernel: [    0.411114] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep  9 03:49:48 node-1 kernel: [    0.411116] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep  9 03:49:48 node-1 kernel: [    0.424847] PCI: Using configuration type 1 for base access
Sep  9 03:49:48 node-1 kernel: [    0.425838] bio: create slab <bio-0> at 0
Sep  9 03:49:48 node-1 kernel: [    0.426118] ACPI: Added _OSI(Module Device)
Sep  9 03:49:48 node-1 kernel: [    0.426120] ACPI: Added _OSI(Processor Device)
Sep  9 03:49:48 node-1 kernel: [    0.426121] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep  9 03:49:48 node-1 kernel: [    0.426122] ACPI: Added _OSI(Processor Aggregator Device)
Sep  9 03:49:48 node-1 kernel: [    0.438755] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep  9 03:49:48 node-1 kernel: [    0.449228] ACPI: Interpreter enabled
Sep  9 03:49:48 node-1 kernel: [    0.449233] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep  9 03:49:48 node-1 kernel: [    0.449237] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep  9 03:49:48 node-1 kernel: [    0.449240] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep  9 03:49:48 node-1 kernel: [    0.449247] ACPI: (supports S0 S4 S5)
Sep  9 03:49:48 node-1 kernel: [    0.449248] ACPI: Using IOAPIC for interrupt routing
Sep  9 03:49:48 node-1 kernel: [    0.449288] HEST: Table parsing has been initialized.
Sep  9 03:49:48 node-1 kernel: [    0.449291] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep  9 03:49:48 node-1 kernel: [    0.449845] ACPI: No dock devices found.
Sep  9 03:49:48 node-1 kernel: [    0.461472] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep  9 03:49:48 node-1 kernel: [    0.461477] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  9 03:49:48 node-1 kernel: [    0.461480] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  9 03:49:48 node-1 kernel: [    0.461507] PCI host bridge to bus 0000:ff
Sep  9 03:49:48 node-1 kernel: [    0.461509] pci_bus 0000:ff: root bus resource [bus ff]
Sep  9 03:49:48 node-1 kernel: [    0.461517] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461554] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.461585] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461620] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461649] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.461678] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.461708] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461737] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461766] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461794] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461821] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461847] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461875] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461901] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461928] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461954] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.461982] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462010] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462036] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.462064] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462090] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.462115] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462141] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462171] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.462206] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462238] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462267] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462299] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462330] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462361] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462394] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462427] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462459] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462490] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462521] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462552] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462584] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462615] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462643] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462674] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462708] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462746] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462782] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462815] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462844] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462873] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462903] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462936] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462968] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.462999] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463031] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463061] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463090] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463119] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463148] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463179] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463210] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463267] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep  9 03:49:48 node-1 kernel: [    0.463270] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  9 03:49:48 node-1 kernel: [    0.463273] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  9 03:49:48 node-1 kernel: [    0.463290] PCI host bridge to bus 0000:7f
Sep  9 03:49:48 node-1 kernel: [    0.463292] pci_bus 0000:7f: root bus resource [bus 7f]
Sep  9 03:49:48 node-1 kernel: [    0.463297] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463324] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.463352] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463381] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463403] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.463428] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.463454] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463479] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463502] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463524] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463552] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463577] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463602] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463626] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463650] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463675] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463697] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463719] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463742] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.463765] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463787] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.463810] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463833] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463859] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep  9 03:49:48 node-1 kernel: [    0.463892] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463918] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463944] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463972] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.463997] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464024] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464050] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464078] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464102] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464128] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464156] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464184] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464212] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464238] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464262] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464290] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464315] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464343] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464373] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464399] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464426] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464451] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464479] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464508] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464536] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464566] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464596] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464622] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464645] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464672] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464698] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464729] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.464756] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.466015] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep  9 03:49:48 node-1 kernel: [    0.466018] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  9 03:49:48 node-1 kernel: [    0.467144] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  9 03:49:48 node-1 kernel: [    0.467663] PCI host bridge to bus 0000:00
Sep  9 03:49:48 node-1 kernel: [    0.467665] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep  9 03:49:48 node-1 kernel: [    0.467667] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep  9 03:49:48 node-1 kernel: [    0.467668] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep  9 03:49:48 node-1 kernel: [    0.467669] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep  9 03:49:48 node-1 kernel: [    0.467671] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep  9 03:49:48 node-1 kernel: [    0.467672] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep  9 03:49:48 node-1 kernel: [    0.467674] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep  9 03:49:48 node-1 kernel: [    0.467679] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep  9 03:49:48 node-1 kernel: [    0.467763] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.467794] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.467835] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep  9 03:49:48 node-1 kernel: [    0.467855] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.467884] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.467925] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep  9 03:49:48 node-1 kernel: [    0.467942] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.467971] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.468011] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep  9 03:49:48 node-1 kernel: [    0.468029] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.468100] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.468178] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.468253] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep  9 03:49:48 node-1 kernel: [    0.468258] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep  9 03:49:48 node-1 kernel: [    0.468344] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep  9 03:49:48 node-1 kernel: [    0.468487] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep  9 03:49:48 node-1 kernel: [    0.468505] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep  9 03:49:48 node-1 kernel: [    0.468582] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.468635] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep  9 03:49:48 node-1 kernel: [    0.468658] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.468713] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.468756] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep  9 03:49:48 node-1 kernel: [    0.468784] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.468840] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.468883] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep  9 03:49:48 node-1 kernel: [    0.468907] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep  9 03:49:48 node-1 kernel: [    0.468924] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep  9 03:49:48 node-1 kernel: [    0.469002] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.469051] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep  9 03:49:48 node-1 kernel: [    0.469077] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep  9 03:49:48 node-1 kernel: [    0.469324] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep  9 03:49:48 node-1 kernel: [    0.469330] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep  9 03:49:48 node-1 kernel: [    0.469336] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.469341] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.469349] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep  9 03:49:48 node-1 kernel: [    0.469379] pci 0000:01:00.0: supports D1 D2
Sep  9 03:49:48 node-1 kernel: [    0.479546] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  9 03:49:48 node-1 kernel: [    0.479553] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  9 03:49:48 node-1 kernel: [    0.479557] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  9 03:49:48 node-1 kernel: [    0.479734] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.479768] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep  9 03:49:48 node-1 kernel: [    0.491542] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  9 03:49:48 node-1 kernel: [    0.491548] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.491552] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  9 03:49:48 node-1 kernel: [    0.491637] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.491709] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.491804] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.491886] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  9 03:49:48 node-1 kernel: [    0.491894] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.491898] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  9 03:49:48 node-1 kernel: [    0.491977] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.492099] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.492151] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  9 03:49:48 node-1 kernel: [    0.492154] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.492156] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.492205] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.492351] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.492391] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.492510] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.492546] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.492665] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.492703] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep  9 03:49:48 node-1 kernel: [    0.492822] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep  9 03:49:48 node-1 kernel: [    0.492863] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  9 03:49:48 node-1 kernel: [    0.492866] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.492868] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.492930] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep  9 03:49:48 node-1 kernel: [    0.492993] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.493045] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.493087] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep  9 03:49:48 node-1 kernel: [    0.493168] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep  9 03:49:48 node-1 kernel: [    0.493289] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  9 03:49:48 node-1 kernel: [    0.493291] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.493293] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.493350] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep  9 03:49:48 node-1 kernel: [    0.493407] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.493456] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.493669] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  9 03:49:48 node-1 kernel: [    0.493673] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  9 03:49:48 node-1 kernel: [    0.493736] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep  9 03:49:48 node-1 kernel: [    0.493791] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.493840] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.494049] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  9 03:49:48 node-1 kernel: [    0.494053] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  9 03:49:48 node-1 kernel: [    0.494112] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep  9 03:49:48 node-1 kernel: [    0.494171] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.494223] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep  9 03:49:48 node-1 kernel: [    0.494475] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  9 03:49:48 node-1 kernel: [    0.494478] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  9 03:49:48 node-1 kernel: [    0.494654] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  9 03:49:48 node-1 kernel: [    0.494692] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  9 03:49:48 node-1 kernel: [    0.494771] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep  9 03:49:48 node-1 kernel: [    0.494789] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep  9 03:49:48 node-1 kernel: [    0.494802] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep  9 03:49:48 node-1 kernel: [    0.494816] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep  9 03:49:48 node-1 kernel: [    0.494866] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep  9 03:49:48 node-1 kernel: [    0.499549] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  9 03:49:48 node-1 kernel: [    0.499558] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  9 03:49:48 node-1 kernel: [    0.499611] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep  9 03:49:48 node-1 kernel: [    0.500373] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep  9 03:49:48 node-1 kernel: [    0.500376] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  9 03:49:48 node-1 kernel: [    0.500496] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  9 03:49:48 node-1 kernel: [    0.500605] PCI host bridge to bus 0000:80
Sep  9 03:49:48 node-1 kernel: [    0.500607] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep  9 03:49:48 node-1 kernel: [    0.500609] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep  9 03:49:48 node-1 kernel: [    0.500610] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep  9 03:49:48 node-1 kernel: [    0.500618] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.500682] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.500751] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep  9 03:49:48 node-1 kernel: [    0.500813] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep  9 03:49:48 node-1 kernel: [    0.500818] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep  9 03:49:48 node-1 kernel: [    0.500891] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep  9 03:49:48 node-1 kernel: [    0.501188] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep  9 03:49:48 node-1 kernel: [    0.501220] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep  9 03:49:48 node-1 kernel: [    0.501250] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep  9 03:49:48 node-1 kernel: [    0.501279] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  9 03:49:48 node-1 kernel: [    0.501308] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  9 03:49:48 node-1 kernel: [    0.501339] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  9 03:49:48 node-1 kernel: [    0.501369] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  9 03:49:48 node-1 kernel: [    0.501399] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  9 03:49:48 node-1 kernel: [    0.501484] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep  9 03:49:48 node-1 kernel: [    0.501488] ACPI: \_SB_.UNC1: notify handler is installed
Sep  9 03:49:48 node-1 kernel: [    0.501489] ACPI: \_SB_.UNC0: notify handler is installed
Sep  9 03:49:48 node-1 kernel: [    0.501505] ACPI: \_SB_.PCI0: notify handler is installed
Sep  9 03:49:48 node-1 kernel: [    0.501557] ACPI: \_SB_.PCI1: notify handler is installed
Sep  9 03:49:48 node-1 kernel: [    0.501637] Found 4 acpi root devices
Sep  9 03:49:48 node-1 kernel: [    0.501742] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep  9 03:49:48 node-1 kernel: [    0.501744] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep  9 03:49:48 node-1 kernel: [    0.501746] vgaarb: loaded
Sep  9 03:49:48 node-1 kernel: [    0.501747] vgaarb: bridge control possible 0000:0c:00.0
Sep  9 03:49:48 node-1 kernel: [    0.501864] SCSI subsystem initialized
Sep  9 03:49:48 node-1 kernel: [    0.501929] libata version 3.00 loaded.
Sep  9 03:49:48 node-1 kernel: [    0.501944] ACPI: bus type USB registered
Sep  9 03:49:48 node-1 kernel: [    0.501954] usbcore: registered new interface driver usbfs
Sep  9 03:49:48 node-1 kernel: [    0.501959] usbcore: registered new interface driver hub
Sep  9 03:49:48 node-1 kernel: [    0.501983] usbcore: registered new device driver usb
Sep  9 03:49:48 node-1 kernel: [    0.502156] PCI: Using ACPI for IRQ routing
Sep  9 03:49:48 node-1 kernel: [    0.505746] PCI: pci_cache_line_size set to 64 bytes
Sep  9 03:49:48 node-1 kernel: [    0.505957] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep  9 03:49:48 node-1 kernel: [    0.505958] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep  9 03:49:48 node-1 kernel: [    0.505959] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep  9 03:49:48 node-1 kernel: [    0.506022] NetLabel: Initializing
Sep  9 03:49:48 node-1 kernel: [    0.506024] NetLabel:  domain hash size = 128
Sep  9 03:49:48 node-1 kernel: [    0.506025] NetLabel:  protocols = UNLABELED CIPSOv4
Sep  9 03:49:48 node-1 kernel: [    0.506034] NetLabel:  unlabeled traffic allowed by default
Sep  9 03:49:48 node-1 kernel: [    0.506103] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep  9 03:49:48 node-1 kernel: [    0.506107] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep  9 03:49:48 node-1 kernel: [    0.508162] Switched to clocksource hpet
Sep  9 03:49:48 node-1 kernel: [    0.512211] AppArmor: AppArmor Filesystem Enabled
Sep  9 03:49:48 node-1 kernel: [    0.512225] pnp: PnP ACPI init
Sep  9 03:49:48 node-1 kernel: [    0.512232] ACPI: bus type PNP registered
Sep  9 03:49:48 node-1 kernel: [    0.512343] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512351] pnp 00:01: [dma 4]
Sep  9 03:49:48 node-1 kernel: [    0.512363] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512390] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512409] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512427] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512460] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512513] system 00:06: [io  0x0500-0x057f] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512515] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep  9 03:49:48 node-1 kernel: [    0.512517] system 00:06: [io  0x0580-0x059f] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512519] system 00:06: [io  0x0600-0x061f] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512520] system 00:06: [io  0x0880-0x0883] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512525] system 00:06: [io  0x0800-0x081f] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512527] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep  9 03:49:48 node-1 kernel: [    0.512529] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512530] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512532] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512533] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512535] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512536] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep  9 03:49:48 node-1 kernel: [    0.512538] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512621] pnp 00:07: [dma 0 disabled]
Sep  9 03:49:48 node-1 kernel: [    0.512650] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512724] pnp 00:08: [dma 0 disabled]
Sep  9 03:49:48 node-1 kernel: [    0.512757] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  9 03:49:48 node-1 kernel: [    0.512808] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep  9 03:49:48 node-1 kernel: [    0.513158] pnp: PnP ACPI: found 10 devices
Sep  9 03:49:48 node-1 kernel: [    0.513159] ACPI: bus type PNP unregistered
Sep  9 03:49:48 node-1 kernel: [    0.519550] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  9 03:49:48 node-1 kernel: [    0.519553] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  9 03:49:48 node-1 kernel: [    0.519556] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  9 03:49:48 node-1 kernel: [    0.519560] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  9 03:49:48 node-1 kernel: [    0.519562] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519576] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519605] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  9 03:49:48 node-1 kernel: [    0.519620] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519649] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  9 03:49:48 node-1 kernel: [    0.519664] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  9 03:49:48 node-1 kernel: [    0.519692] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  9 03:49:48 node-1 kernel: [    0.519707] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  9 03:49:48 node-1 kernel: [    0.519739] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  9 03:49:48 node-1 kernel: [    0.519741] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519755] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519785] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  9 03:49:48 node-1 kernel: [    0.519786] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519801] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519830] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  9 03:49:48 node-1 kernel: [    0.519831] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519834] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519838] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  9 03:49:48 node-1 kernel: [    0.519840] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519842] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519846] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  9 03:49:48 node-1 kernel: [    0.519851] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  9 03:49:48 node-1 kernel: [    0.519859] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  9 03:49:48 node-1 kernel: [    0.519862] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  9 03:49:48 node-1 kernel: [    0.519868] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep  9 03:49:48 node-1 kernel: [    0.519869] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep  9 03:49:48 node-1 kernel: [    0.519870] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep  9 03:49:48 node-1 kernel: [    0.519871] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep  9 03:49:48 node-1 kernel: [    0.519872] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep  9 03:49:48 node-1 kernel: [    0.519873] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep  9 03:49:48 node-1 kernel: [    0.519874] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep  9 03:49:48 node-1 kernel: [    0.519875] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep  9 03:49:48 node-1 kernel: [    0.519875] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519876] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519877] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519878] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519879] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519880] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519881] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519882] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519883] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep  9 03:49:48 node-1 kernel: [    0.519883] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519884] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep  9 03:49:48 node-1 kernel: [    0.519885] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep  9 03:49:48 node-1 kernel: [    0.519886] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep  9 03:49:48 node-1 kernel: [    0.519887] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep  9 03:49:48 node-1 kernel: [    0.519889] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep  9 03:49:48 node-1 kernel: [    0.519890] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep  9 03:49:48 node-1 kernel: [    0.519929] NET: Registered protocol family 2
Sep  9 03:49:48 node-1 kernel: [    0.520196] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.520522] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.520669] TCP: Hash tables configured (established 262144 bind 65536)
Sep  9 03:49:48 node-1 kernel: [    0.520706] TCP: reno registered
Sep  9 03:49:48 node-1 kernel: [    0.520735] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.520831] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.520980] NET: Registered protocol family 1
Sep  9 03:49:48 node-1 kernel: [    0.560265] pci 0000:0c:00.0: Video device with shadowed ROM
Sep  9 03:49:48 node-1 kernel: [    0.560280] PCI: CLS 64 bytes, default 64
Sep  9 03:49:48 node-1 kernel: [    0.560350] Trying to unpack rootfs image as initramfs...
Sep  9 03:49:48 node-1 kernel: [    0.780334] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep  9 03:49:48 node-1 kernel: [    0.780373] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep  9 03:49:48 node-1 kernel: [    0.780376] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep  9 03:49:48 node-1 kernel: [    0.780802] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780808] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780813] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780819] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780828] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780839] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780848] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780857] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780865] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780873] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780888] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780894] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780902] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780924] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780932] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780939] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep  9 03:49:48 node-1 kernel: [    0.780980] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep  9 03:49:48 node-1 kernel: [    0.780983] Scanning for low memory corruption every 60 seconds
Sep  9 03:49:48 node-1 kernel: [    0.781268] Initialise system trusted keyring
Sep  9 03:49:48 node-1 kernel: [    0.781312] audit: initializing netlink socket (disabled)
Sep  9 03:49:48 node-1 kernel: [    0.781322] type=2000 audit(1473392952.736:1): initialized
Sep  9 03:49:48 node-1 kernel: [    0.799135] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep  9 03:49:48 node-1 kernel: [    0.800616] zbud: loaded
Sep  9 03:49:48 node-1 kernel: [    0.800729] VFS: Disk quotas dquot_6.5.2
Sep  9 03:49:48 node-1 kernel: [    0.800769] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep  9 03:49:48 node-1 kernel: [    0.801144] fuse init (API version 7.22)
Sep  9 03:49:48 node-1 kernel: [    0.801197] msgmni has been set to 32768
Sep  9 03:49:48 node-1 kernel: [    0.801243] Key type big_key registered
Sep  9 03:49:48 node-1 kernel: [    0.801730] Key type asymmetric registered
Sep  9 03:49:48 node-1 kernel: [    0.801731] Asymmetric key parser 'x509' registered
Sep  9 03:49:48 node-1 kernel: [    0.801754] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep  9 03:49:48 node-1 kernel: [    0.801809] io scheduler noop registered
Sep  9 03:49:48 node-1 kernel: [    0.801811] io scheduler deadline registered (default)
Sep  9 03:49:48 node-1 kernel: [    0.801827] io scheduler cfq registered
Sep  9 03:49:48 node-1 kernel: [    0.802157] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    0.802249] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    0.802337] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    0.802424] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    0.802520] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    0.802587] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    0.802847] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep  9 03:49:48 node-1 kernel: [    0.802865] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep  9 03:49:48 node-1 kernel: [    0.802877] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep  9 03:49:48 node-1 kernel: [    0.802886] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802889] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802891] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep  9 03:49:48 node-1 kernel: [    0.802895] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802896] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802897] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802899] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802900] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802902] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802903] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802904] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802906] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802907] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802909] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802910] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802912] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep  9 03:49:48 node-1 kernel: [    0.802916] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802918] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep  9 03:49:48 node-1 kernel: [    0.802927] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802930] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep  9 03:49:48 node-1 kernel: [    0.802939] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802940] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep  9 03:49:48 node-1 kernel: [    0.802943] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep  9 03:49:48 node-1 kernel: [    0.802956] ioapic: probe of 0000:00:05.4 failed with error -22
Sep  9 03:49:48 node-1 kernel: [    0.803042] ioapic: probe of 0000:80:05.4 failed with error -22
Sep  9 03:49:48 node-1 kernel: [    0.803046] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  9 03:49:48 node-1 kernel: [    0.803054] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep  9 03:49:48 node-1 kernel: [    0.803089] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep  9 03:49:48 node-1 kernel: [    0.803091] vesafb: scrolling: redraw
Sep  9 03:49:48 node-1 kernel: [    0.803092] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep  9 03:49:48 node-1 kernel: [    0.823783] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep  9 03:49:48 node-1 kernel: [    0.832408] Console: switching to colour frame buffer device 80x30
Sep  9 03:49:48 node-1 kernel: [    0.841228] fb0: VESA VGA frame buffer device
Sep  9 03:49:48 node-1 kernel: [    0.841429] intel_idle: MWAIT substates: 0x2120
Sep  9 03:49:48 node-1 kernel: [    0.841430] intel_idle: v0.4 model 0x3F
Sep  9 03:49:48 node-1 kernel: [    0.841431] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep  9 03:49:48 node-1 kernel: [    0.841667] ipmi message handler version 39.2
Sep  9 03:49:48 node-1 kernel: [    0.841925] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep  9 03:49:48 node-1 kernel: [    0.842357] ACPI: AC Adapter [P111] (on-line)
Sep  9 03:49:48 node-1 kernel: [    0.847651] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep  9 03:49:48 node-1 kernel: [    0.858778] ACPI: Power Button [PWRB]
Sep  9 03:49:48 node-1 kernel: [    0.864610] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep  9 03:49:48 node-1 kernel: [    0.876365] ACPI: Power Button [PWRF]
Sep  9 03:49:48 node-1 kernel: [    0.901805] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep  9 03:49:48 node-1 kernel: [    0.913588] pstore: Registered erst as persistent store backend
Sep  9 03:49:48 node-1 kernel: [    0.919879] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep  9 03:49:48 node-1 kernel: [    0.931897] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep  9 03:49:48 node-1 kernel: [    0.958678] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep  9 03:49:48 node-1 kernel: [    0.992013] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep  9 03:49:48 node-1 kernel: [    1.006273] Linux agpgart interface v0.103
Sep  9 03:49:48 node-1 kernel: [    1.013974] brd: module loaded
Sep  9 03:49:48 node-1 kernel: [    1.021022] loop: module loaded
Sep  9 03:49:48 node-1 kernel: [    1.027745] libphy: Fixed MDIO Bus: probed
Sep  9 03:49:48 node-1 kernel: [    1.034198] tun: Universal TUN/TAP device driver, 1.6
Sep  9 03:49:48 node-1 kernel: [    1.040645] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep  9 03:49:48 node-1 kernel: [    1.047159] PPP generic driver version 2.4.2
Sep  9 03:49:48 node-1 kernel: [    1.053542] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep  9 03:49:48 node-1 kernel: [    1.059992] ehci-pci: EHCI PCI platform driver
Sep  9 03:49:48 node-1 kernel: [    1.066635] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep  9 03:49:48 node-1 kernel: [    1.073036] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep  9 03:49:48 node-1 kernel: [    1.085558] ehci-pci 0000:00:1a.0: debug port 2
Sep  9 03:49:48 node-1 kernel: [    1.095740] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep  9 03:49:48 node-1 kernel: [    1.095758] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep  9 03:49:48 node-1 kernel: [    1.111655] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep  9 03:49:48 node-1 kernel: [    1.117712] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep  9 03:49:48 node-1 kernel: [    1.123871] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  9 03:49:48 node-1 kernel: [    1.135739] usb usb1: Product: EHCI Host Controller
Sep  9 03:49:48 node-1 kernel: [    1.141788] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  9 03:49:48 node-1 kernel: [    1.147878] usb usb1: SerialNumber: 0000:00:1a.0
Sep  9 03:49:48 node-1 kernel: [    1.153799] hub 1-0:1.0: USB hub found
Sep  9 03:49:48 node-1 kernel: [    1.159551] hub 1-0:1.0: 2 ports detected
Sep  9 03:49:48 node-1 kernel: [    1.165332] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep  9 03:49:48 node-1 kernel: [    1.170902] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep  9 03:49:48 node-1 kernel: [    1.181754] ehci-pci 0000:00:1d.0: debug port 2
Sep  9 03:49:48 node-1 kernel: [    1.191025] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep  9 03:49:48 node-1 kernel: [    1.191028] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep  9 03:49:48 node-1 kernel: [    1.207573] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep  9 03:49:48 node-1 kernel: [    1.212760] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep  9 03:49:48 node-1 kernel: [    1.218051] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  9 03:49:48 node-1 kernel: [    1.228604] usb usb2: Product: EHCI Host Controller
Sep  9 03:49:48 node-1 kernel: [    1.234053] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  9 03:49:48 node-1 kernel: [    1.239580] usb usb2: SerialNumber: 0000:00:1d.0
Sep  9 03:49:48 node-1 kernel: [    1.245088] hub 2-0:1.0: USB hub found
Sep  9 03:49:48 node-1 kernel: [    1.250431] hub 2-0:1.0: 2 ports detected
Sep  9 03:49:48 node-1 kernel: [    1.255715] ehci-platform: EHCI generic platform driver
Sep  9 03:49:48 node-1 kernel: [    1.260934] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep  9 03:49:48 node-1 kernel: [    1.266235] ohci-pci: OHCI PCI platform driver
Sep  9 03:49:48 node-1 kernel: [    1.271525] ohci-platform: OHCI generic platform driver
Sep  9 03:49:48 node-1 kernel: [    1.276723] uhci_hcd: USB Universal Host Controller Interface driver
Sep  9 03:49:48 node-1 kernel: [    1.282045] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep  9 03:49:48 node-1 kernel: [    1.475353] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep  9 03:49:48 node-1 kernel: [    1.635524] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep  9 03:49:48 node-1 kernel: [    1.641034] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  9 03:49:48 node-1 kernel: [    1.646789] hub 1-1:1.0: USB hub found
Sep  9 03:49:48 node-1 kernel: [    1.652260] hub 1-1:1.0: 6 ports detected
Sep  9 03:49:48 node-1 kernel: [    1.767097] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep  9 03:49:48 node-1 kernel: [    1.779120] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep  9 03:49:48 node-1 kernel: [    2.035186] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep  9 03:49:48 node-1 kernel: [    2.040721] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  9 03:49:48 node-1 kernel: [    2.046578] hub 2-1:1.0: USB hub found
Sep  9 03:49:48 node-1 kernel: [    2.052173] hub 2-1:1.0: 8 ports detected
Sep  9 03:49:48 node-1 kernel: [    2.323515] i8042: No controller found
Sep  9 03:49:48 node-1 kernel: [    2.329005] mousedev: PS/2 mouse device common for all mice
Sep  9 03:49:48 node-1 kernel: [    2.330695] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep  9 03:49:48 node-1 kernel: [    2.340239] rtc_cmos 00:02: RTC can wake from S4
Sep  9 03:49:48 node-1 kernel: [    2.346087] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep  9 03:49:48 node-1 kernel: [    2.351750] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep  9 03:49:48 node-1 kernel: [    2.362965] device-mapper: uevent: version 1.0.3
Sep  9 03:49:48 node-1 kernel: [    2.368585] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep  9 03:49:48 node-1 kernel: [    2.379772] ledtrig-cpu: registered to indicate activity on CPUs
Sep  9 03:49:48 node-1 kernel: [    2.385680] TCP: cubic registered
Sep  9 03:49:48 node-1 kernel: [    2.391551] NET: Registered protocol family 10
Sep  9 03:49:48 node-1 kernel: [    2.397504] NET: Registered protocol family 17
Sep  9 03:49:48 node-1 kernel: [    2.403154] Key type dns_resolver registered
Sep  9 03:49:48 node-1 kernel: [    2.409081] Loading compiled-in X.509 certificates
Sep  9 03:49:48 node-1 kernel: [    2.415238] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep  9 03:49:48 node-1 kernel: [    2.426617] registered taskstats version 1
Sep  9 03:49:48 node-1 kernel: [    2.434557] Key type trusted registered
Sep  9 03:49:48 node-1 kernel: [    2.442198] Key type encrypted registered
Sep  9 03:49:48 node-1 kernel: [    2.447646] AppArmor: AppArmor sha1 policy hashing enabled
Sep  9 03:49:48 node-1 kernel: [    2.453133] IMA: No TPM chip found, activating TPM-bypass!
Sep  9 03:49:48 node-1 kernel: [    2.459267] regulator-dummy: disabling
Sep  9 03:49:48 node-1 kernel: [    2.463271] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep  9 03:49:48 node-1 kernel: [    2.463271] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep  9 03:49:48 node-1 kernel: [    2.463272] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep  9 03:49:48 node-1 kernel: [    2.463273] usb 2-1.4: Manufacturer: Avocent
Sep  9 03:49:48 node-1 kernel: [    2.463274] usb 2-1.4: SerialNumber: 20111102-00000001
Sep  9 03:49:48 node-1 kernel: [    2.498179]   Magic number: 0:796:815
Sep  9 03:49:48 node-1 kernel: [    2.503813] acpi device:a4: hash matches
Sep  9 03:49:48 node-1 kernel: [    2.509487] rtc_cmos 00:02: setting system clock to 2016-09-09 03:49:14 UTC (1473392954)
Sep  9 03:49:48 node-1 kernel: [    2.522041] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep  9 03:49:48 node-1 kernel: [    2.527783] EDD information not available.
Sep  9 03:49:48 node-1 kernel: [    2.533389] PM: Hibernation image not present or could not be loaded.
Sep  9 03:49:48 node-1 kernel: [    2.534273] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep  9 03:49:48 node-1 kernel: [    2.545638] Write protecting the kernel read-only data: 12288k
Sep  9 03:49:48 node-1 kernel: [    2.551851] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep  9 03:49:48 node-1 kernel: [    2.564410] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep  9 03:49:48 node-1 kernel: [    2.597103] device-mapper: multipath: version 1.6.0 loaded
Sep  9 03:49:48 node-1 kernel: [    2.605255] systemd-udevd[216]: starting version 204
Sep  9 03:49:48 node-1 kernel: [    2.632596] md: linear personality registered for level -1
Sep  9 03:49:48 node-1 kernel: [    2.646393] md: multipath personality registered for level -4
Sep  9 03:49:48 node-1 kernel: [    2.654355] md: raid0 personality registered for level 0
Sep  9 03:49:48 node-1 kernel: [    2.662539] md: raid1 personality registered for level 1
Sep  9 03:49:48 node-1 kernel: [    2.668865] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep  9 03:49:48 node-1 kernel: [    2.675172] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep  9 03:49:48 node-1 kernel: [    2.676002] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep  9 03:49:48 node-1 kernel: [    2.676320] megasas: FW now in Ready state
Sep  9 03:49:48 node-1 kernel: [    2.676381] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676420] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676458] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676492] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676519] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676557] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676590] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676629] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676641] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676679] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676714] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676750] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676784] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676817] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676854] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.676887] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.677045] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep  9 03:49:48 node-1 kernel: [    2.706989] hidraw: raw HID events driver (C) Jiri Kosina
Sep  9 03:49:48 node-1 kernel: [    2.715089] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep  9 03:49:48 node-1 kernel: [    2.728228] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep  9 03:49:48 node-1 kernel: [    2.741976] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  9 03:49:48 node-1 kernel: [    2.748996] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.749000] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.749004] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.749009] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.749050] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.764028] usbcore: registered new interface driver usbhid
Sep  9 03:49:48 node-1 kernel: [    2.770721] usbhid: USB HID core driver
Sep  9 03:49:48 node-1 kernel: [    2.771879] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep  9 03:49:48 node-1 kernel: [    2.771896] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep  9 03:49:48 node-1 kernel: [    2.771917] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  9 03:49:48 node-1 kernel: [    2.772389] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.772526] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.772636] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.772764] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.773054] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  9 03:49:48 node-1 kernel: [    2.774373] raid6: sse2x1    7069 MB/s
Sep  9 03:49:48 node-1 kernel: [    2.785967] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep  9 03:49:48 node-1 kernel: [    2.785990] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep  9 03:49:48 node-1 kernel: [    2.786021] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  9 03:49:48 node-1 kernel: [    2.842380] raid6: sse2x2    9093 MB/s
Sep  9 03:49:48 node-1 kernel: [    2.910138] raid6: sse2x4    9943 MB/s
Sep  9 03:49:48 node-1 kernel: [    2.982076] raid6: avx2x1   14952 MB/s
Sep  9 03:49:48 node-1 kernel: [    3.054022] raid6: avx2x2   18895 MB/s
Sep  9 03:49:48 node-1 kernel: [    3.125959] raid6: avx2x4   21344 MB/s
Sep  9 03:49:48 node-1 kernel: [    3.132137] raid6: using algorithm avx2x4 (21344 MB/s)
Sep  9 03:49:48 node-1 kernel: [    3.138232] raid6: using avx2x2 recovery algorithm
Sep  9 03:49:48 node-1 kernel: [    3.144235] megasas:IOC Init cmd success
Sep  9 03:49:48 node-1 kernel: [    3.144237] Switched to clocksource tsc
Sep  9 03:49:48 node-1 kernel: [    3.150013] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.150063] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.150104] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.150136] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.150239] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.168129] xor: automatically using best checksumming function:
Sep  9 03:49:48 node-1 kernel: [    3.171833] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep  9 03:49:48 node-1 kernel: [    3.171834] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep  9 03:49:48 node-1 kernel: [    3.171835] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  9 03:49:48 node-1 kernel: [    3.171896] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.171932] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.171962] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.171993] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.172075] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  9 03:49:48 node-1 kernel: [    3.189927] megasas: INIT adapter done
Sep  9 03:49:48 node-1 kernel: [    3.221083] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep  9 03:49:48 node-1 kernel: [    3.232820] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep  9 03:49:48 node-1 kernel: [    3.245036] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep  9 03:49:48 node-1 kernel: [    3.257416] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep  9 03:49:48 node-1 kernel: [    3.257823]    avx       : 35729.000 MB/sec
Sep  9 03:49:48 node-1 kernel: [    3.261942] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep  9 03:49:48 node-1 kernel: [    3.264166] scsi0 : LSI SAS based MegaRAID driver
Sep  9 03:49:48 node-1 kernel: [    3.271768] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  9 03:49:48 node-1 kernel: [    3.301251] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep  9 03:49:48 node-1 kernel: [    3.315056] async_tx: api initialized (async)
Sep  9 03:49:48 node-1 kernel: [    3.315348] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep  9 03:49:48 node-1 kernel: [    3.321203] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  9 03:49:48 node-1 kernel: [    3.325279] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep  9 03:49:48 node-1 kernel: [    3.325594] sd 0:2:0:0: [sda] Write Protect is off
Sep  9 03:49:48 node-1 kernel: [    3.325595] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep  9 03:49:48 node-1 kernel: [    3.325657] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep  9 03:49:48 node-1 kernel: [    3.325728] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep  9 03:49:48 node-1 kernel: [    3.352810]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep  9 03:49:48 node-1 kernel: [    3.354906] sd 0:2:0:0: [sda] Attached SCSI disk
Sep  9 03:49:48 node-1 kernel: [    3.412180] md: raid6 personality registered for level 6
Sep  9 03:49:48 node-1 kernel: [    3.419376] md: raid5 personality registered for level 5
Sep  9 03:49:48 node-1 kernel: [    3.426371] md: raid4 personality registered for level 4
Sep  9 03:49:48 node-1 kernel: [    3.436143] md: raid10 personality registered for level 10
Sep  9 03:49:48 node-1 kernel: [    3.489857] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Sep  9 03:49:48 node-1 kernel: [    3.493298] random: lvm urandom read with 27 bits of entropy available
Sep  9 03:49:48 node-1 kernel: [    3.597496] bio: create slab <bio-1> at 1
Sep  9 03:49:48 node-1 kernel: [    4.331448] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep  9 03:49:48 node-1 kernel: [    4.883690] init: plymouth-upstart-bridge main process (552) terminated with status 1
Sep  9 03:49:48 node-1 kernel: [    4.895908] init: plymouth-upstart-bridge main process ended, respawning
Sep  9 03:49:48 node-1 kernel: [    5.024541] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep  9 03:49:48 node-1 kernel: [    5.047646] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep  9 03:49:48 node-1 kernel: [    5.154378] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep  9 03:49:48 node-1 kernel: [    5.184351] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep  9 03:49:48 node-1 kernel: [    5.236520] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep  9 03:49:48 node-1 kernel: [    5.251756] random: nonblocking pool is initialized
Sep  9 03:49:48 node-1 kernel: [    5.453836] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep  9 03:49:48 node-1 kernel: [    5.504508] XFS (dm-0): Mounting Filesystem
Sep  9 03:49:48 node-1 kernel: [    5.753796] XFS (dm-0): Ending clean mount
Sep  9 03:49:48 node-1 kernel: [    5.809318] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep  9 03:49:48 node-1 kernel: [    5.836582] XFS (dm-1): Mounting Filesystem
Sep  9 03:49:48 node-1 kernel: [    5.979966] XFS (dm-1): Ending clean mount
Sep  9 03:49:48 node-1 kernel: [    7.979888] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep  9 03:49:48 node-1 kernel: [    8.003491] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep  9 03:49:48 node-1 kernel: [    8.131558] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  9 03:49:48 node-1 kernel: [    8.131562] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep  9 03:49:48 node-1 kernel: [    8.131566] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep  9 03:49:48 node-1 kernel: [    8.131569] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep  9 03:49:48 node-1 kernel: [    8.164295] systemd-udevd[774]: starting version 204
Sep  9 03:49:48 node-1 kernel: [    8.368589] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep  9 03:49:48 node-1 kernel: [    8.368594] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  9 03:49:48 node-1 kernel: [    8.368597] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep  9 03:49:48 node-1 kernel: [    8.368599] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  9 03:49:48 node-1 kernel: [    8.368610] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep  9 03:49:48 node-1 kernel: [    8.375617] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  9 03:49:48 node-1 kernel: [    8.384801] wmi: Mapper loaded
Sep  9 03:49:48 node-1 kernel: [    8.389177] IPMI System Interface driver.
Sep  9 03:49:48 node-1 kernel: [    8.389245] ipmi_si: probing via ACPI
Sep  9 03:49:48 node-1 kernel: [    8.389260] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep  9 03:49:48 node-1 kernel: [    8.389261] ipmi_si: Adding ACPI-specified kcs state machine
Sep  9 03:49:48 node-1 kernel: [    8.389279] ipmi_si: probing via SMBIOS
Sep  9 03:49:48 node-1 kernel: [    8.389280] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep  9 03:49:48 node-1 kernel: [    8.389281] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep  9 03:49:48 node-1 kernel: [    8.389283] ipmi_si: probing via SPMI
Sep  9 03:49:48 node-1 kernel: [    8.389284] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep  9 03:49:48 node-1 kernel: [    8.389285] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep  9 03:49:48 node-1 kernel: [    8.389287] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep  9 03:49:48 node-1 kernel: [    8.393113] power_meter ACPI000D:00: Found ACPI power meter.
Sep  9 03:49:48 node-1 kernel: [    8.393148] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep  9 03:49:48 node-1 kernel: [    8.457952] systemd-udevd[800]: renamed network interface eth2 to enp8s0
Sep  9 03:49:48 node-1 kernel: [    8.489787] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Sep  9 03:49:48 node-1 kernel: [    8.525814] systemd-udevd[797]: renamed network interface eth1 to enp7s0
Sep  9 03:49:48 node-1 kernel: [    8.541960] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep  9 03:49:48 node-1 kernel: [    8.541968] ipmi_si 00:09: IPMI kcs interface initialized
Sep  9 03:49:48 node-1 kernel: [    8.557746] systemd-udevd[792]: renamed network interface eth0 to enp6s0
Sep  9 03:49:48 node-1 kernel: [    8.766657] type=1400 audit(1473392960.757:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1056 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.766812] type=1400 audit(1473392960.757:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1056 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.766939] type=1400 audit(1473392960.757:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1056 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.774746] type=1400 audit(1473392960.765:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=983 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.774885] type=1400 audit(1473392960.765:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=983 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.775005] type=1400 audit(1473392960.765:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=983 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.783695] type=1400 audit(1473392960.773:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=977 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.783837] type=1400 audit(1473392960.773:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=977 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.783957] type=1400 audit(1473392960.773:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=977 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    8.785860] type=1400 audit(1473392960.777:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=990 comm="apparmor_parser"
Sep  9 03:49:48 node-1 kernel: [    9.296052] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep  9 03:49:48 node-1 kernel: [    9.297377] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep  9 03:49:48 node-1 kernel: [    9.489601] enic 0000:06:00.0 enp6s0: Link UP
Sep  9 03:49:48 node-1 kernel: [    9.490025] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep  9 03:49:48 node-1 kernel: [    9.490031] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep  9 03:49:48 node-1 kernel: [   18.651627] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep  9 03:49:50 node-1 failsafe: Failsafe of 120 seconds reached.
Sep  9 03:49:50 node-1 kernel: [   37.537127] init: failsafe main process (8420) killed by TERM signal
Sep  9 03:49:50 node-1 dbus[8449]: [system] AppArmor D-Bus mediation is enabled
Sep  9 03:49:50 node-1 kernel: [   37.729630] audit_printk_skb: 30 callbacks suppressed
Sep  9 03:49:50 node-1 kernel: [   37.729632] type=1400 audit(1473392990.406:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8546 comm="apparmor_parser"
Sep  9 03:49:50 node-1 kernel: [   37.729856] type=1400 audit(1473392990.406:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8545 comm="apparmor_parser"
Sep  9 03:49:50 node-1 kernel: [   37.729861] type=1400 audit(1473392990.406:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8545 comm="apparmor_parser"
Sep  9 03:49:50 node-1 kernel: [   37.729864] type=1400 audit(1473392990.406:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Sep  9 03:49:50 node-1 kernel: [   37.730088] type=1400 audit(1473392990.406:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8545 comm="apparmor_parser"
Sep  9 03:49:50 node-1 kernel: [   37.730103] type=1400 audit(1473392990.406:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Sep  9 03:49:50 node-1 kernel: [   37.730217] type=1400 audit(1473392990.406:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Sep  9 03:49:50 node-1 kernel: [   37.795856] type=1400 audit(1473392990.470:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8548 comm="apparmor_parser"
Sep  9 03:49:50 node-1 anacron[8600]: Anacron 2.3 started on 2016-09-09
Sep  9 03:49:50 node-1 anacron[8600]: Will run job `cron.daily' in 5 min.
Sep  9 03:49:50 node-1 anacron[8600]: Will run job `cron.weekly' in 10 min.
Sep  9 03:49:50 node-1 anacron[8600]: Will run job `cron.monthly' in 15 min.
Sep  9 03:49:50 node-1 anacron[8600]: Jobs will be executed sequentially
Sep  9 03:49:50 node-1 cron[8578]: (CRON) INFO (pidfile fd = 3)
Sep  9 03:49:50 node-1 cron[8648]: (CRON) STARTUP (fork ok)
Sep  9 03:49:50 node-1 multipathd: path checkers start up
Sep  9 03:49:50 node-1 cron[8648]: (CRON) INFO (Running @reboot jobs)
Sep  9 03:49:51 node-1 postfix/master[8757]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep  9 03:49:54 node-1 puppet-agent[8941]: Reopening log files
Sep  9 03:49:54 node-1 puppet-agent[8941]: Could not request certificate: Connection refused - connect(2)
Sep  9 03:50:01 node-1 CRON[8972]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep  9 03:50:07 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  9 03:50:07 node-1 nailgun-agent: D, [2016-09-09T03:50:01.865443 #8975] DEBUG -- : Sleep for 6 seconds before sending request
Sep  9 03:50:07 node-1 nailgun-agent: I, [2016-09-09T03:50:07.892253 #8975]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  9 03:50:08 node-1 puppet-user[9031]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep  9 03:50:08 node-1 puppet-user[9031]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Sep  9 03:50:08 node-1 nailgun-agent: D, [2016-09-09T03:50:08.641179 #8975] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep  9 03:50:09 node-1 puppet-user[9031]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep  9 03:50:09 node-1 puppet-user[9031]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep  9 03:50:09 node-1 puppet-user[9031]: Finished catalog run in 0.93 seconds
Sep  9 03:50:10 node-1 multipathd: uevent trigger error
Sep  9 03:50:11 node-1 puppet-user[9590]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  9 03:50:11 node-1 puppet-user[9590]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep  9 03:50:11 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep  9 03:50:11 node-1 puppet-user[9590]: Finished catalog run in 0.06 seconds
Sep  9 03:50:12 node-1 puppet-user[10047]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep  9 03:50:12 node-1 puppet-user[10047]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep  9 03:50:12 node-1 puppet-user[10047]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep  9 03:50:12 node-1 puppet-user[10047]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep  9 03:50:12 node-1 puppet-user[10047]: Finished catalog run in 0.03 seconds
Sep  9 03:50:14 node-1 puppet-user[10510]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep  9 03:50:14 node-1 puppet-user[10510]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep  9 03:50:14 node-1 puppet-user[10510]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep  9 03:50:14 node-1 puppet-user[10510]: Finished catalog run in 0.04 seconds
Sep  9 03:50:15 node-1 puppet-user[10962]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep  9 03:50:16 node-1 puppet-user[10962]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Sep  9 03:50:16 node-1 puppet-user[10962]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep  9 03:50:16 node-1 puppet-user[10962]: (/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
Sep  9 03:50:16 node-1 puppet-user[10962]: Finished catalog run in 0.42 seconds
Sep  9 03:50:17 node-1 puppet-user[11431]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep  9 03:50:17 node-1 puppet-user[11431]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Sep  9 03:50:18 node-1 puppet-user[11431]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep  9 03:50:18 node-1 puppet-user[11431]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep  9 03:50:18 node-1 puppet-user[11431]: (/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
Sep  9 03:50:18 node-1 puppet-user[11431]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep  9 03:50:18 node-1 puppet-user[11431]: Finished catalog run in 0.22 seconds
Sep  9 03:50:19 node-1 puppet-user[11912]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep  9 03:50:19 node-1 puppet-user[11912]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Sep  9 03:50:19 node-1 puppet-user[11912]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep  9 03:50:19 node-1 kernel: [   67.211774] nr_pdflush_threads exported in /proc is scheduled for removal
Sep  9 03:50:19 node-1 kernel: [   67.211822] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep  9 03:50:19 node-1 puppet-user[11912]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep  9 03:50:19 node-1 puppet-user[11912]: Finished catalog run in 0.05 seconds
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.684578 #8975] DEBUG -- : Trying to find block devices
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.684702 #8975] DEBUG -- : Found block device: sda
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.684744 #8975] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.684770 #8975] DEBUG -- : Trying to get list of physical devices
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.684917 #8975] DEBUG -- : Getting udev properties for device: sda
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.687065 #8975] 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
Sep  9 03:50:20 node-1 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13137", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.687088 #8975] DEBUG -- : Trying to find out if device sda is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.687131 #8975] DEBUG -- : Device sda removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.687147 #8975] DEBUG -- : Device sda seems to be appropriate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.687673 #8975] DEBUG -- : Getting udev properties for device: dm-0
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.689324 #8975] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-loLrpDCg1rNaNuFxSm1H2ucjYYXo1u25bYHc5yyd84DOahVwr07dUWzAGWajoGQf /dev/disk/by-uuid/11cc6c31-d3c3-4bb4-8b94-7b5fdfa1f8ea /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-loLrpDCg1rNaNuFxSm1H2ucjYYXo1u25bYHc5yyd84DOahVwr07dUWzAGWajoGQf", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"11cc6c31-d3c3-4bb4-8b94-7b5fdfa1f8ea", "ID_FS_UUID_ENC"=>"11cc6c31-d3c3-4bb4-8b94-7b5fdfa1f8ea", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55904", "nomdmonddf"=>"1", "nomd
Sep  9 03:50:20 node-1 nailgun-agent: monisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.689349 #8975] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.689389 #8975] DEBUG -- : Device dm-0 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.689401 #8975] DEBUG -- : Device dm-0 seems to be appropriate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.689416 #8975] DEBUG -- : Getting udev properties for device: dm-1
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.691157 #8975] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-BhFKddBprUNX8FolKWYtsHkIMi5hWuo0wM1GFo0NCvrpMTnjMQU4yhtVjlkygdEO /dev/disk/by-uuid/508e9578-e56f-45be-bff9-7bebe051828a /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-BhFKddBprUNX8FolKWYtsHkIMi5hWuo0wM1GFo0NCvrpMTnjMQU4yhtVjlkygdEO", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"508e9578-e56f-45be-bff9-7bebe051828a", "ID_FS_UUID_ENC"=>"508e9578-e56f-45be-bff9-7bebe051828a", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93
Sep  9 03:50:20 node-1 nailgun-agent: 977", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.691182 #8975] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.691210 #8975] DEBUG -- : Device dm-1 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.691257 #8975] DEBUG -- : Device dm-1 seems to be appropriate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.691307 #8975] DEBUG -- : Getting udev properties for device: dm-2
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.693189 #8975] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-pYRmxb7E6BYf0cEjKz6prL0BRlWGWu51A4fcsiRmRkr680jjrSHtVNC3nVQ9PVIE /dev/disk/by-uuid/9c333f76-1958-4e63-bf5e-da1f72904b8c /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-pYRmxb7E6BYf0cEjKz6prL0BRlWGWu51A4fcsiRmRkr680jjrSHtVNC3nVQ9PVIE", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9c333f76-1958-4e63-bf5e-da1f72904b8c", "ID_FS_UUID_ENC"=>"9c333f76-1958-4e63-bf5e-da1f72904b8c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90357", "nomdmond
Sep  9 03:50:20 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.693213 #8975] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.693240 #8975] DEBUG -- : Device dm-2 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.693263 #8975] DEBUG -- : Device dm-2 seems to be appropriate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.693277 #8975] DEBUG -- : Getting udev properties for device: dm-3
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.694984 #8975] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Q7jY0qx9segsPrM5QJmKtSk7FltQxuqrDXFdDEpxYnTHaNlBVk6wvdr3gDl4A2pE /dev/disk/by-uuid/06d36821-dd78-4d7a-a12d-27f82f848836 /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-Q7jY0qx9segsPrM5QJmKtSk7FltQxuqrDXFdDEpxYnTHaNlBVk6wvdr3gDl4A2pE", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"06d36821-dd78-4d7a-a12d-27f82f848836", "ID_FS_UUID_ENC"=>"06d36821-dd78-4d7a-a12d-27f82f848836", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88071", "nomdmonddf"=>"1", 
Sep  9 03:50:20 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.695006 #8975] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.695053 #8975] DEBUG -- : Device dm-3 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.695066 #8975] DEBUG -- : Device dm-3 seems to be appropriate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.695089 #8975] DEBUG -- : Getting udev properties for device: dm-4
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.697106 #8975] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-vEakSKguxXWT2TUt9rUd3RqdBvCcYMOAMcbG70gHGWt56qWwa4JXdTj5pxbkH1Qe /dev/disk/by-uuid/f9a0d0de-58dc-4e0f-956a-4475bbc94113 /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-vEakSKguxXWT2TUt9rUd3RqdBvCcYMOAMcbG70gHGWt56qWwa4JXdTj5pxbkH1Qe", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f9a0d0de-58dc-4e0f-956a-4475bbc94113", "ID_FS_UUID_ENC"=>"f9a0d0de-58dc-4e0f-956a-4475bbc94113", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85618", "nomdmonddf"=>"1", "nomd
Sep  9 03:50:20 node-1 nailgun-agent: monisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.697131 #8975] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.697191 #8975] DEBUG -- : Device dm-4 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.697204 #8975] DEBUG -- : Device dm-4 seems to be appropriate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.697219 #8975] DEBUG -- : Getting udev properties for device: dm-5
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.699256 #8975] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-vEakSKguxXWT2TUt9rUd3RqdBvCcYMOAQdJlRz1PyrzRtCUv7chjPp55spLtkPng /dev/disk/by-uuid/778d878f-84e3-4a60-9912-87e307984d90 /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-vEakSKguxXWT2TUt9rUd3RqdBvCcYMOAQdJlRz1PyrzRtCUv7chjPp55spLtkPng", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"778d878f-84e3-4a60-9912-87e307984d90", "ID_FS_UUID_ENC"=>"778d878f-84e3-4a60-9912-87e307984d90", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85954", "nomdmonddf"=>"1", "nomdmonisw"
Sep  9 03:50:20 node-1 nailgun-agent: =>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.699281 #8975] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.699310 #8975] DEBUG -- : Device dm-5 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.699322 #8975] DEBUG -- : Device dm-5 seems to be appropriate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.699336 #8975] DEBUG -- : Getting udev properties for device: ram0
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.701134 #8975] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17989", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.701175 #8975] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.701210 #8975] DEBUG -- : Device ram0 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.701228 #8975] DEBUG -- : Getting udev properties for device: ram1
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.703048 #8975] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18071", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.703069 #8975] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.703099 #8975] DEBUG -- : Device ram1 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.703133 #8975] DEBUG -- : Getting udev properties for device: ram2
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.704607 #8975] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18749", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.704689 #8975] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.704770 #8975] DEBUG -- : Device ram2 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.704791 #8975] DEBUG -- : Getting udev properties for device: ram3
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.706269 #8975] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18837", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.706300 #8975] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.706332 #8975] DEBUG -- : Device ram3 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.706361 #8975] DEBUG -- : Getting udev properties for device: ram4
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.707941 #8975] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18936", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.707967 #8975] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.708012 #8975] DEBUG -- : Device ram4 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.708032 #8975] DEBUG -- : Getting udev properties for device: ram5
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.712034 #8975] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19029", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.712077 #8975] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.712141 #8975] DEBUG -- : Device ram5 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.712204 #8975] DEBUG -- : Getting udev properties for device: ram6
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.714008 #8975] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19142", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.714050 #8975] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.714092 #8975] DEBUG -- : Device ram6 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.714127 #8975] DEBUG -- : Getting udev properties for device: ram7
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.715971 #8975] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19212", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.716000 #8975] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.716037 #8975] DEBUG -- : Device ram7 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.716057 #8975] DEBUG -- : Getting udev properties for device: ram8
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.717680 #8975] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19299", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.717723 #8975] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.717755 #8975] DEBUG -- : Device ram8 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.717773 #8975] DEBUG -- : Getting udev properties for device: ram9
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.719574 #8975] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19373", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.719596 #8975] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.719633 #8975] DEBUG -- : Device ram9 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.719664 #8975] DEBUG -- : Getting udev properties for device: loop0
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.721651 #8975] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17188", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.721698 #8975] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.721742 #8975] DEBUG -- : Device loop0 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.721783 #8975] DEBUG -- : Getting udev properties for device: loop1
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.723661 #8975] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17266", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.723694 #8975] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.723737 #8975] DEBUG -- : Device loop1 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.723772 #8975] DEBUG -- : Getting udev properties for device: loop2
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.725632 #8975] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17365", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.725665 #8975] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.725707 #8975] DEBUG -- : Device loop2 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.725733 #8975] DEBUG -- : Getting udev properties for device: loop3
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.727475 #8975] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17493", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.727518 #8975] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.727559 #8975] DEBUG -- : Device loop3 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.727583 #8975] DEBUG -- : Getting udev properties for device: loop4
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.729286 #8975] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17586", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.729335 #8975] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.729382 #8975] DEBUG -- : Device loop4 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.729407 #8975] DEBUG -- : Getting udev properties for device: loop5
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.731108 #8975] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17675", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.731139 #8975] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.731180 #8975] DEBUG -- : Device loop5 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.731215 #8975] DEBUG -- : Getting udev properties for device: loop6
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.739276 #8975] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17792", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.739312 #8975] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.739359 #8975] DEBUG -- : Device loop6 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.739383 #8975] DEBUG -- : Getting udev properties for device: loop7
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.741096 #8975] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17886", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.741122 #8975] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.741165 #8975] DEBUG -- : Device loop7 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.741187 #8975] DEBUG -- : Getting udev properties for device: ram10
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.742756 #8975] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18165", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.742781 #8975] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.742819 #8975] DEBUG -- : Device ram10 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.742841 #8975] DEBUG -- : Getting udev properties for device: ram11
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.744416 #8975] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18268", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.744476 #8975] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.744521 #8975] DEBUG -- : Device ram11 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.744543 #8975] DEBUG -- : Getting udev properties for device: ram12
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.746052 #8975] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18377", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.746078 #8975] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.746150 #8975] DEBUG -- : Device ram12 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.746172 #8975] DEBUG -- : Getting udev properties for device: ram13
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.747665 #8975] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18479", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.747690 #8975] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.747721 #8975] DEBUG -- : Device ram13 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.747783 #8975] DEBUG -- : Getting udev properties for device: ram14
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.749253 #8975] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18569", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.749277 #8975] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.749309 #8975] DEBUG -- : Device ram14 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.749330 #8975] DEBUG -- : Getting udev properties for device: ram15
Sep  9 03:50:20 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.750836 #8975] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18662", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.750860 #8975] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.750892 #8975] DEBUG -- : Device ram15 removable parameter: "0"
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.750931 #8975] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.750946 #8975] DEBUG -- : Block device seems to be physical data storage: sda
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751009 #8975] DEBUG -- : Found block device: dm-0
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751041 #8975] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751056 #8975] DEBUG -- : Found block device: dm-1
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751068 #8975] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751077 #8975] DEBUG -- : Found block device: dm-2
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751087 #8975] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751096 #8975] DEBUG -- : Found block device: dm-3
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751107 #8975] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751115 #8975] DEBUG -- : Found block device: dm-4
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751125 #8975] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751134 #8975] DEBUG -- : Found block device: dm-5
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751186 #8975] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751196 #8975] DEBUG -- : Found block device: ram0
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751206 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751215 #8975] DEBUG -- : Found block device: ram1
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751225 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751241 #8975] DEBUG -- : Found block device: ram2
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751252 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751262 #8975] DEBUG -- : Found block device: ram3
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751291 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751300 #8975] DEBUG -- : Found block device: ram4
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751339 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751350 #8975] DEBUG -- : Found block device: ram5
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751361 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751371 #8975] DEBUG -- : Found block device: ram6
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751382 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751392 #8975] DEBUG -- : Found block device: ram7
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751403 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751412 #8975] DEBUG -- : Found block device: ram8
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751423 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751432 #8975] DEBUG -- : Found block device: ram9
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751471 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751481 #8975] DEBUG -- : Found block device: loop0
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751492 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751501 #8975] DEBUG -- : Found block device: loop1
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751512 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751520 #8975] DEBUG -- : Found block device: loop2
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751531 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751540 #8975] DEBUG -- : Found block device: loop3
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751550 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751571 #8975] DEBUG -- : Found block device: loop4
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751583 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751632 #8975] DEBUG -- : Found block device: loop5
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751642 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751651 #8975] DEBUG -- : Found block device: loop6
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751662 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751670 #8975] DEBUG -- : Found block device: loop7
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751682 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751691 #8975] DEBUG -- : Found block device: ram10
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751701 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751710 #8975] DEBUG -- : Found block device: ram11
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751757 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751768 #8975] DEBUG -- : Found block device: ram12
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751777 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751786 #8975] DEBUG -- : Found block device: ram13
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751795 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751804 #8975] DEBUG -- : Found block device: ram14
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751814 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751822 #8975] DEBUG -- : Found block device: ram15
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751833 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.751893 #8975] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.815598 #8975] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep  9 03:50:20 node-1 nailgun-agent: D, [2016-09-09T03:50:20.815680 #8975] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep  9 03:50:21 node-1 puppet-user[12506]: (Scope(Class[main])) MODULAR: sync_time
Sep  9 03:50:21 node-1 puppet-user[12506]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep  9 03:50:21 node-1 ntpdate[13094]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep  9 03:50:28 node-1 ntpdate[13094]: adjust time server 10.20.0.2 offset -0.332200 sec
Sep  9 03:50:28 node-1 puppet-user[12506]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep  9 03:50:28 node-1 puppet-user[12506]: Finished catalog run in 6.16 seconds
Sep  9 03:50:32 node-1 puppet-user[13281]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  9 03:50:32 node-1 puppet-user[13281]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Sep  9 03:50:32 node-1 puppet-user[13281]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep  9 03:50:32 node-1 puppet-user[13281]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Sep  9 03:50:32 node-1 puppet-user[13281]: Finished catalog run in 0.07 seconds
Sep  9 03:50:32 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703382 #8975] DEBUG -- : Trying to find block devices
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703448 #8975] DEBUG -- : Found block device: sda
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703482 #8975] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703511 #8975] DEBUG -- : Block device seems to be physical data storage: sda
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703535 #8975] DEBUG -- : Found block device: dm-0
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703548 #8975] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703560 #8975] DEBUG -- : Found block device: dm-1
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703582 #8975] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703592 #8975] DEBUG -- : Found block device: dm-2
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703602 #8975] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703612 #8975] DEBUG -- : Found block device: dm-3
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703655 #8975] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703666 #8975] DEBUG -- : Found block device: dm-4
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703677 #8975] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703687 #8975] DEBUG -- : Found block device: dm-5
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703698 #8975] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703707 #8975] DEBUG -- : Found block device: ram0
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703717 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703726 #8975] DEBUG -- : Found block device: ram1
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703736 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703745 #8975] DEBUG -- : Found block device: ram2
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703754 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703785 #8975] DEBUG -- : Found block device: ram3
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703795 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703804 #8975] DEBUG -- : Found block device: ram4
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703813 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703822 #8975] DEBUG -- : Found block device: ram5
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703832 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703840 #8975] DEBUG -- : Found block device: ram6
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703850 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703859 #8975] DEBUG -- : Found block device: ram7
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703885 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703894 #8975] DEBUG -- : Found block device: ram8
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703905 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703914 #8975] DEBUG -- : Found block device: ram9
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703924 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703932 #8975] DEBUG -- : Found block device: loop0
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703942 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703952 #8975] DEBUG -- : Found block device: loop1
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703962 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703986 #8975] DEBUG -- : Found block device: loop2
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.703997 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704006 #8975] DEBUG -- : Found block device: loop3
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704016 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704025 #8975] DEBUG -- : Found block device: loop4
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704034 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704043 #8975] DEBUG -- : Found block device: loop5
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704053 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704076 #8975] DEBUG -- : Found block device: loop6
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704086 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704094 #8975] DEBUG -- : Found block device: loop7
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704104 #8975] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704113 #8975] DEBUG -- : Found block device: ram10
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704124 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704132 #8975] DEBUG -- : Found block device: ram11
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704142 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704169 #8975] DEBUG -- : Found block device: ram12
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704180 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704189 #8975] DEBUG -- : Found block device: ram13
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704199 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704207 #8975] DEBUG -- : Found block device: ram14
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704217 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704226 #8975] DEBUG -- : Found block device: ram15
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704235 #8975] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.704264 #8975] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Sep  9 03:50:32 node-1 nailgun-agent: D, [2016-09-09T03:50:32.919904 #8975] DEBUG -- : Response: status: 200 body: {"id": 1}
Sep  9 03:50:32 node-1 nailgun-agent: I, [2016-09-09T03:50:32.920172 #8975]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep  9 03:50:34 node-1 puppet-user[13860]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep  9 03:50:35 node-1 puppet-user[13860]: Compiled catalog for node-1.domain.tld in environment production in 1.18 seconds
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Sep  9 03:50:35 node-1 puppet-user[13860]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep  9 03:50:45 node-1 kernel: [   93.044034] init: plymouth-upstart-bridge main process ended, respawning
Sep  9 03:50:45 node-1 puppet-agent[8941]: Could not run: SIGTERM
Sep  9 03:50:46 node-1 kernel: [   93.335020] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep  9 03:50:46 node-1 ec2: 
Sep  9 03:50:46 node-1 ec2: #############################################################
Sep  9 03:50:46 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep  9 03:50:46 node-1 ec2: 1024 fb:cc:71:81:a9:b6:b0:99:98:6c:d0:99:98:1b:21:01  root@node-1.domain.tld (DSA)
Sep  9 03:50:46 node-1 ec2: 256 8b:ef:e3:0d:25:a3:e8:65:0d:e8:dc:7b:86:ef:b2:84  root@node-1.domain.tld (ECDSA)
Sep  9 03:50:46 node-1 ec2: 256 88:25:b4:72:7b:76:f2:ab:01:d2:02:e9:4a:36:d2:7d  root@node-1.domain.tld (ED25519)
Sep  9 03:50:46 node-1 ec2: 2048 98:77:b2:f0:73:42:7f:0a:51:15:92:5f:e8:1b:0d:e7  root@node-1.domain.tld (RSA)
Sep  9 03:50:46 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep  9 03:50:46 node-1 ec2: #############################################################
Sep  9 03:50:52 node-1 puppet-user[13860]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep  9 03:50:52 node-1 puppet-user[13860]: Finished catalog run in 16.65 seconds
Sep  9 03:50:54 node-1 puppet-user[15234]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep  9 03:50:54 node-1 puppet-user[15234]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep  9 03:50:59 node-1 puppet-user[15234]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep  9 03:51:01 node-1 CRON[16237]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep  9 03:51:25 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  9 03:51:25 node-1 nailgun-agent: I, [2016-09-09T03:51:25.105568 #16240]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  9 03:51:28 node-1 puppet-user[15234]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep  9 03:51:28 node-1 puppet-user[15234]: Finished catalog run in 34.25 seconds
Sep  9 03:51:30 node-1 puppet-user[17805]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep  9 03:51:31 node-1 puppet-user[17805]: Compiled catalog for node-1.domain.tld in environment production in 0.51 seconds
Sep  9 03:51:31 node-1 puppet-user[17805]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep  9 03:51:31 node-1 puppet-user[17805]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep  9 03:51:31 node-1 puppet-user[17805]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep  9 03:51:31 node-1 puppet-user[17805]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep  9 03:51:31 node-1 puppet-user[17805]: Finished catalog run in 0.10 seconds
Sep  9 03:51:33 node-1 puppet-user[18263]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep  9 03:51:33 node-1 puppet-user[18263]: Compiled catalog for node-1.domain.tld in environment production in 0.81 seconds
Sep  9 03:51:34 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep  9 03:51:34 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep  9 03:51:34 node-1 crontab[18699]: (root) LIST (root)
Sep  9 03:51:34 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep  9 03:51:34 node-1 crontab[18700]: (root) REPLACE (root)
Sep  9 03:51:36 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep  9 03:51:37 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep  9 03:51:37 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep  9 03:51:38 node-1 nailgun-agent: I, [2016-09-09T03:51:38.072820 #16240]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep  9 03:51:38 node-1 puppet-user[18263]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep  9 03:51:38 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8393" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  9 03:51:38 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep  9 03:51:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:51:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:51:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:51:58 node-1 multipathd: uevent trigger error
<27>Sep  9 03:51:58 node-1 multipathd: uevent trigger error
<27>Sep  9 03:51:58 node-1 multipathd: uevent trigger error
<27>Sep  9 03:51:58 node-1 multipathd: uevent trigger error
<27>Sep  9 03:51:58 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:02 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:02 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:02 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:02 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:04 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:04 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:04 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:04 node-1 multipathd: uevent trigger error
<27>Sep  9 03:52:04 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:03 node-1 ntpdate[30900]: no servers can be used, exiting
<27>Sep  9 03:53:03 node-1 ntpdate[31022]: no servers can be used, exiting
<27>Sep  9 03:53:03 node-1 ntpdate[31259]: no servers can be used, exiting
<27>Sep  9 03:53:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:35 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:35 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:35 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:38 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:38 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:38 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:38 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:38 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:50 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:50 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:50 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:50 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:50 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:53 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:53 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:53 node-1 multipathd: uevent trigger error
<27>Sep  9 03:53:53 node-1 multipathd: uevent trigger error
<27>Sep  9 03:54:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:54:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:54:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:54:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:54:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:54:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:01 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:01 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:01 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:01 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:01 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:01 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:03 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  9 03:55:03 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  9 03:55:09 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  9 03:55:09 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  9 03:55:15 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  9 03:55:21 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  9 03:55:21 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  9 03:55:27 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:27 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:27 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:27 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:27 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:55:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:13 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:13 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:13 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:13 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:13 node-1 multipathd: uevent trigger error
<129>Sep  9 03:56:16 node-1 haproxy[25823]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 56ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:16 node-1 haproxy[25823]: proxy odl-neutron-endpoint has no server available!
<129>Sep  9 03:56:17 node-1 haproxy[25828]: Server odl-jetty/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 2ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:17 node-1 haproxy[25828]: proxy odl-jetty has no server available!
<27>Sep  9 03:56:39 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:39 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:39 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:39 node-1 multipathd: uevent trigger error
<129>Sep  9 03:56:42 node-1 haproxy[28152]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:42 node-1 haproxy[28152]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:42 node-1 haproxy[28152]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:42 node-1 haproxy[28152]: proxy mysqld has no server available!
<27>Sep  9 03:56:45 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:45 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:45 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:45 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:48 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:48 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:48 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:48 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:48 node-1 multipathd: uevent trigger error
<129>Sep  9 03:56:51 node-1 haproxy[30720]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:51 node-1 haproxy[30720]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:51 node-1 haproxy[30720]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:51 node-1 haproxy[30720]: proxy mysqld has no server available!
<129>Sep  9 03:56:52 node-1 haproxy[30724]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:52 node-1 haproxy[30724]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:52 node-1 haproxy[30724]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:52 node-1 haproxy[30724]: proxy object-storage has no server available!
<27>Sep  9 03:56:54 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:54 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:54 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:54 node-1 multipathd: uevent trigger error
<27>Sep  9 03:56:54 node-1 multipathd: uevent trigger error
<129>Sep  9 03:56:56 node-1 haproxy[32074]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:57 node-1 haproxy[32078]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:57 node-1 haproxy[32078]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:57 node-1 haproxy[32078]: proxy neutron has no server available!
<129>Sep  9 03:56:57 node-1 haproxy[32078]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:57 node-1 haproxy[32078]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:57 node-1 haproxy[32078]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:57 node-1 haproxy[32078]: proxy mysqld has no server available!
<129>Sep  9 03:56:58 node-1 haproxy[32078]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:58 node-1 haproxy[32078]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:56:58 node-1 haproxy[32078]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:56:58 node-1 haproxy[32078]: proxy object-storage has no server available!
<27>Sep  9 03:57:00 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:00 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:00 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:00 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:00 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:03 node-1 haproxy[1055]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:03 node-1 haproxy[1055]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:03 node-1 haproxy[1055]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:03 node-1 haproxy[1055]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:03 node-1 haproxy[1055]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:04 node-1 haproxy[1061]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:04 node-1 haproxy[1061]: proxy neutron has no server available!
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:04 node-1 haproxy[1061]: proxy mysqld has no server available!
<129>Sep  9 03:57:04 node-1 haproxy[1061]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:05 node-1 haproxy[1061]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:05 node-1 haproxy[1061]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:05 node-1 haproxy[1061]: proxy object-storage has no server available!
<27>Sep  9 03:57:06 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:06 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:06 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:06 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:09 node-1 haproxy[2398]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:09 node-1 haproxy[2398]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:09 node-1 haproxy[2398]: proxy neutron has no server available!
<129>Sep  9 03:57:09 node-1 haproxy[2398]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:10 node-1 haproxy[2415]: proxy mysqld has no server available!
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:10 node-1 haproxy[2415]: proxy object-storage has no server available!
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:10 node-1 haproxy[2415]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:10 node-1 haproxy[2415]: proxy aodh has no server available!
<27>Sep  9 03:57:12 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:12 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:12 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:12 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:12 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:14 node-1 haproxy[3763]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:14 node-1 haproxy[3763]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:14 node-1 haproxy[3763]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:14 node-1 haproxy[3763]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:14 node-1 haproxy[3763]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:15 node-1 haproxy[3773]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:15 node-1 haproxy[3773]: proxy neutron has no server available!
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:15 node-1 haproxy[3773]: proxy mysqld has no server available!
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:15 node-1 haproxy[3773]: proxy object-storage has no server available!
<129>Sep  9 03:57:15 node-1 haproxy[3773]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:16 node-1 haproxy[3773]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:16 node-1 haproxy[3773]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:16 node-1 haproxy[3773]: proxy aodh has no server available!
<129>Sep  9 03:57:16 node-1 haproxy[3773]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:16 node-1 haproxy[3773]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:16 node-1 haproxy[3773]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:16 node-1 haproxy[3773]: proxy ceilometer has no server available!
<27>Sep  9 03:57:18 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:18 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:18 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:18 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:18 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:20 node-1 haproxy[5127]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:20 node-1 haproxy[5127]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:20 node-1 haproxy[5127]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:21 node-1 haproxy[5131]: proxy neutron has no server available!
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:21 node-1 haproxy[5131]: proxy mysqld has no server available!
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:21 node-1 haproxy[5131]: proxy object-storage has no server available!
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:21 node-1 haproxy[5131]: proxy aodh has no server available!
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:21 node-1 haproxy[5131]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:22 node-1 haproxy[5131]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:22 node-1 haproxy[5131]: proxy ceilometer has no server available!
<27>Sep  9 03:57:23 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:23 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:23 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:23 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:25 node-1 haproxy[6488]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:25 node-1 haproxy[6488]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:26 node-1 haproxy[6497]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:26 node-1 haproxy[6497]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:26 node-1 haproxy[6497]: proxy neutron has no server available!
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:26 node-1 haproxy[6497]: proxy mysqld has no server available!
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:26 node-1 haproxy[6497]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:27 node-1 haproxy[6497]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:27 node-1 haproxy[6497]: proxy object-storage has no server available!
<129>Sep  9 03:57:27 node-1 haproxy[6497]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:27 node-1 haproxy[6497]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:27 node-1 haproxy[6497]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:27 node-1 haproxy[6497]: proxy aodh has no server available!
<129>Sep  9 03:57:27 node-1 haproxy[6497]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:27 node-1 haproxy[6497]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:27 node-1 haproxy[6497]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:27 node-1 haproxy[6497]: proxy ceilometer has no server available!
<27>Sep  9 03:57:28 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:28 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:28 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:28 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:28 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:31 node-1 haproxy[8056]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:31 node-1 haproxy[8056]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:31 node-1 haproxy[8056]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:31 node-1 haproxy[8056]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:31 node-1 haproxy[8056]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:31 node-1 haproxy[8056]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:31 node-1 haproxy[8056]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:31 node-1 haproxy[8056]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:31 node-1 haproxy[8056]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:32 node-1 haproxy[8062]: proxy glance-api has no server available!
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:32 node-1 haproxy[8062]: proxy glance-glare has no server available!
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:32 node-1 haproxy[8062]: proxy neutron has no server available!
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:32 node-1 haproxy[8062]: proxy glance-registry has no server available!
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:32 node-1 haproxy[8062]: proxy mysqld has no server available!
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:32 node-1 haproxy[8062]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:32 node-1 haproxy[8062]: proxy object-storage has no server available!
<129>Sep  9 03:57:33 node-1 haproxy[8062]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:33 node-1 haproxy[8062]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:33 node-1 haproxy[8062]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:33 node-1 haproxy[8062]: proxy aodh has no server available!
<129>Sep  9 03:57:33 node-1 haproxy[8062]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:33 node-1 haproxy[8062]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:33 node-1 haproxy[8062]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:33 node-1 haproxy[8062]: proxy ceilometer has no server available!
<27>Sep  9 03:57:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:34 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:34 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:37 node-1 haproxy[9488]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:37 node-1 haproxy[9488]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:37 node-1 haproxy[9488]: proxy nova-api has no server available!
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:37 node-1 haproxy[9488]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy nova-metadata-api has no server available!
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy glance-api has no server available!
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy glance-glare has no server available!
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy neutron has no server available!
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy glance-registry has no server available!
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy mysqld has no server available!
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy object-storage has no server available!
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:38 node-1 haproxy[9492]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:38 node-1 haproxy[9492]: proxy aodh has no server available!
<129>Sep  9 03:57:39 node-1 haproxy[9492]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:39 node-1 haproxy[9492]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:39 node-1 haproxy[9492]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:39 node-1 haproxy[9492]: proxy ceilometer has no server available!
<129>Sep  9 03:57:39 node-1 haproxy[9492]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:39 node-1 haproxy[9492]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:39 node-1 haproxy[9492]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:39 node-1 haproxy[9492]: proxy nova-novncproxy has no server available!
<27>Sep  9 03:57:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:40 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:40 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:43 node-1 haproxy[11010]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:43 node-1 haproxy[11010]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:43 node-1 haproxy[11010]: proxy nova-api has no server available!
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:43 node-1 haproxy[11010]: proxy nova-metadata-api has no server available!
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:43 node-1 haproxy[11010]: proxy cinder-api has no server available!
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:43 node-1 haproxy[11010]: proxy glance-api has no server available!
<129>Sep  9 03:57:43 node-1 haproxy[11010]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy glance-glare has no server available!
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy neutron has no server available!
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy glance-registry has no server available!
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy mysqld has no server available!
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy object-storage has no server available!
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy aodh has no server available!
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy ceilometer has no server available!
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:44 node-1 haproxy[11014]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:44 node-1 haproxy[11014]: proxy nova-novncproxy has no server available!
<27>Sep  9 03:57:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 03:57:46 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:46 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:46 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:46 node-1 multipathd: uevent trigger error
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:49 node-1 haproxy[12450]: proxy keystone-1 has no server available!
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:49 node-1 haproxy[12450]: proxy keystone-2 has no server available!
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:49 node-1 haproxy[12450]: proxy nova-api has no server available!
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:49 node-1 haproxy[12450]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:49 node-1 haproxy[12450]: proxy nova-metadata-api has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy cinder-api has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy glance-api has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy glance-glare has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy neutron has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy glance-registry has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy mysqld has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy object-storage has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy aodh has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:50 node-1 haproxy[12472]: proxy ceilometer has no server available!
<129>Sep  9 03:57:50 node-1 haproxy[12472]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:51 node-1 haproxy[12472]: proxy heat-api has no server available!
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:51 node-1 haproxy[12472]: proxy heat-api-cfn has no server available!
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:51 node-1 haproxy[12472]: proxy heat-api-cloudwatch has no server available!
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  9 03:57:51 node-1 haproxy[12472]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  9 03:57:51 node-1 haproxy[12472]: proxy nova-novncproxy has no server available!
<27>Sep  9 03:57:52 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  9 03:57:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:52 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:56 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:56 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:56 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:56 node-1 multipathd: uevent trigger error
<27>Sep  9 03:57:56 node-1 multipathd: uevent trigger error
<27>Sep  9 03:58:07 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep  9 03:58:32 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Sep  9 03:58:34 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep  9 03:59:26 node-1 multipathd: uevent trigger error
<27>Sep  9 03:59:26 node-1 multipathd: uevent trigger error
<27>Sep  9 03:59:26 node-1 multipathd: uevent trigger error
<27>Sep  9 03:59:26 node-1 multipathd: uevent trigger error
<27>Sep  9 03:59:26 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 04:01:42 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:42 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:42 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:42 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:42 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:01:49 node-1 multipathd: uevent trigger error
<43>Sep  9 04:02:09 node-1 apache2_error [Fri Sep 09 04:02:02.442711 2016] [mpm_event:notice] [pid 23747:tid 140711545247616] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  9 04:02:09 node-1 apache2_error [Fri Sep 09 04:02:02.442855 2016] [core:notice] [pid 23747:tid 140711545247616] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep  9 04:02:09 node-1 apache2_error [Fri Sep 09 04:02:05.703141 2016] [mpm_event:notice] [pid 23747:tid 140711545247616] AH00491: caught SIGTERM, shutting down
<43>Sep  9 04:02:09 node-1 apache2_error [Fri Sep 09 04:02:06.796821 2016] [mpm_worker:notice] [pid 24561:tid 140036656306048] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  9 04:02:09 node-1 apache2_error [Fri Sep 09 04:02:06.796881 2016] [core:notice] [pid 24561:tid 140036656306048] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  9 04:02:11 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:11 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:11 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:11 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:11 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:11 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:16 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:16 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:16 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:16 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:19 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:19 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:19 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:19 node-1 multipathd: uevent trigger error
<27>Sep  9 04:02:19 node-1 multipathd: uevent trigger error
<43>Sep  9 04:03:29 node-1 apache2_error [Fri Sep 09 04:03:29.200413 2016] [mpm_worker:notice] [pid 24561:tid 140036656306048] AH00295: caught SIGTERM, shutting down
<43>Sep  9 04:03:39 node-1 apache2_error [Fri Sep 09 04:03:29.944688 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  9 04:03:39 node-1 apache2_error [Fri Sep 09 04:03:29.944713 2016] [core:notice] [pid 6511:tid 140499970590592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  9 04:04:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep  9 04:04:19 node-1 apache2_error [Fri Sep 09 04:04:14.107017 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  9 04:04:19 node-1 apache2_error [Fri Sep 09 04:04:14.299436 2016] [mpm_worker:warn] [pid 6511:tid 140499970590592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  9 04:04:19 node-1 apache2_error [Fri Sep 09 04:04:14.302071 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  9 04:04:19 node-1 apache2_error [Fri Sep 09 04:04:14.302086 2016] [core:notice] [pid 6511:tid 140499970590592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  9 04:04:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:04:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:04:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:04:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:00 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:20 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:20 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:20 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:20 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:05:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:06:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:06:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:06:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:06:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:07:06 node-1 multipathd: uevent trigger error
<27>Sep  9 04:07:06 node-1 multipathd: uevent trigger error
<27>Sep  9 04:07:06 node-1 multipathd: uevent trigger error
<27>Sep  9 04:07:06 node-1 multipathd: uevent trigger error
<27>Sep  9 04:07:06 node-1 multipathd: uevent trigger error
<27>Sep  9 04:07:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 04:08:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:08:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:08:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:08:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:08:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:21 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:21 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:21 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:21 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:21 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:09:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:10:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 04:12:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:12:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 04:13:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:13:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:34 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:34 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:34 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:34 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:34 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:14:50 node-1 multipathd: uevent trigger error
<27>Sep  9 04:15:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:15:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:15:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:15:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:15:07 node-1 multipathd: uevent trigger error
<27>Sep  9 04:16:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 04:17:32 node-1 multipathd: uevent trigger error
<27>Sep  9 04:17:32 node-1 multipathd: uevent trigger error
<27>Sep  9 04:17:32 node-1 multipathd: uevent trigger error
<27>Sep  9 04:17:32 node-1 multipathd: uevent trigger error
<27>Sep  9 04:17:32 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:18 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:18:23 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:08 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:08 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:08 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:08 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:08 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 04:19:25 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:25 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:25 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:25 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:25 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:31 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:31 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:31 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:32 node-1 multipathd: uevent trigger error
<27>Sep  9 04:19:32 node-1 multipathd: uevent trigger error
<27>Sep  9 04:20:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:20:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:20:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:20:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:20:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:14 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:14 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:14 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:14 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:21:33 node-1 multipathd: uevent trigger error
<11>Sep  9 04:21:47 node-1 liberasurecode[26254]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:47 node-1 liberasurecode[26254]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:47 node-1 liberasurecode[26254]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:47 node-1 liberasurecode[26254]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:47 node-1 liberasurecode[26279]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:47 node-1 liberasurecode[26279]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:47 node-1 liberasurecode[26279]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:47 node-1 liberasurecode[26279]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:49 node-1 liberasurecode[26789]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:49 node-1 liberasurecode[26789]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:49 node-1 liberasurecode[26789]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:49 node-1 liberasurecode[26789]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27667]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27667]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27667]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27667]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27715]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27715]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27715]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27715]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27756]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27756]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27756]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27756]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27821]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27821]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27821]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27821]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27835]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27835]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27835]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:55 node-1 liberasurecode[27835]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27848]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27848]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27848]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27848]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27860]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27860]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27860]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:21:56 node-1 liberasurecode[27860]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  9 04:22:04 node-1 liberasurecode[29847]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:22:04 node-1 liberasurecode[29847]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:22:04 node-1 liberasurecode[29847]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:22:04 node-1 liberasurecode[29847]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  9 04:22:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:22:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:22:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:22:12 node-1 multipathd: uevent trigger error
<27>Sep  9 04:22:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep  9 04:23:01 node-1 apache2_error [Fri Sep 09 04:22:59.544647 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  9 04:23:01 node-1 apache2_error [Fri Sep 09 04:22:59.929384 2016] [mpm_worker:warn] [pid 6511:tid 140499970590592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  9 04:23:01 node-1 apache2_error [Fri Sep 09 04:22:59.936313 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  9 04:23:01 node-1 apache2_error [Fri Sep 09 04:22:59.936343 2016] [core:notice] [pid 6511:tid 140499970590592] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep  9 04:23:41 node-1 apache2_error [Fri Sep 09 04:23:36.956985 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  9 04:23:41 node-1 apache2_error [Fri Sep 09 04:23:38.469255 2016] [mpm_worker:warn] [pid 6511:tid 140499970590592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  9 04:23:41 node-1 apache2_error [Fri Sep 09 04:23:38.480345 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  9 04:23:41 node-1 apache2_error [Fri Sep 09 04:23:38.480395 2016] [core:notice] [pid 6511:tid 140499970590592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  9 04:23:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:48 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:48 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:48 node-1 multipathd: uevent trigger error
<27>Sep  9 04:23:48 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:26 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:26 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:27 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:27 node-1 multipathd: uevent trigger error
<43>Sep  9 04:24:31 node-1 apache2_error [Fri Sep 09 04:24:22.993639 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  9 04:24:31 node-1 apache2_error [Fri Sep 09 04:24:23.190241 2016] [mpm_worker:warn] [pid 6511:tid 140499970590592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  9 04:24:31 node-1 apache2_error [Fri Sep 09 04:24:23.200386 2016] [mpm_worker:notice] [pid 6511:tid 140499970590592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  9 04:24:31 node-1 apache2_error [Fri Sep 09 04:24:23.200419 2016] [core:notice] [pid 6511:tid 140499970590592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  9 04:24:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:33 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:39 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:46 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:46 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:46 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:46 node-1 multipathd: uevent trigger error
<27>Sep  9 04:24:46 node-1 multipathd: uevent trigger error
<11>Sep  9 04:25:01 node-1 liberasurecode[30012]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:25:01 node-1 liberasurecode[30012]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:25:01 node-1 liberasurecode[30012]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:25:01 node-1 liberasurecode[30012]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  9 04:25:03 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:03 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:03 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:03 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  9 04:25:24 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:32 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep  9 04:25:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:41 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:51 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:51 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:51 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:51 node-1 multipathd: uevent trigger error
<27>Sep  9 04:25:51 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:26 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  9 04:26:37 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:37 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:37 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:37 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:45 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:52 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:52 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:52 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:52 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:52 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:57 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:57 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:57 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:57 node-1 multipathd: uevent trigger error
<27>Sep  9 04:26:57 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:09 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:40 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:40 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:40 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:40 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:44 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:49 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:54 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:54 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:54 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:54 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:54 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:27:59 node-1 multipathd: uevent trigger error
<27>Sep  9 04:28:03 node-1 multipathd: uevent trigger error
<27>Sep  9 04:28:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:28:04 node-1 multipathd: uevent trigger error
<27>Sep  9 04:28:04 node-1 multipathd: uevent trigger error
<11>Sep  9 04:30:02 node-1 liberasurecode[29296]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:30:02 node-1 liberasurecode[29296]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:30:02 node-1 liberasurecode[29296]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  9 04:30:02 node-1 liberasurecode[29296]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
