Oct  7 00:01:44 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] start
Oct  7 00:01:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  7 00:01:44 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct  7 00:01:44 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct  7 00:01:44 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  7 00:01:44 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  7 00:01:44 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  7 00:01:44 node-1 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Oct  7 00:01:44 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=886bda69-7979-44e6-93aa-44ec4eb07b11 nomdmonddf nomdmonisw
Oct  7 00:01:44 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct  7 00:01:44 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct  7 00:01:44 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct  7 00:01:44 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct  7 00:01:44 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  7 00:01:44 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  7 00:01:44 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  7 00:01:44 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
Oct  7 00:01:44 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  7 00:01:44 node-1 kernel: [    0.000000] No AGP bridge found
Oct  7 00:01:44 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  7 00:01:44 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct  7 00:01:44 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  7 00:01:44 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct  7 00:01:44 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  7 00:01:44 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  7 00:01:44 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  7 00:01:44 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  7 00:01:44 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  7 00:01:44 node-1 kernel: [    0.000000]   2 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000]   3 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000]   4 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000]   5 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000]   6 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000]   7 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000]   8 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000]   9 disabled
Oct  7 00:01:44 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  7 00:01:44 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  7 00:01:44 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  7 00:01:44 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  7 00:01:44 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  7 00:01:44 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  7 00:01:44 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  7 00:01:44 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  7 00:01:44 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  7 00:01:44 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  7 00:01:44 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  7 00:01:44 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  7 00:01:44 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  7 00:01:44 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  7 00:01:44 node-1 kernel: [    0.000000] Zone ranges:
Oct  7 00:01:44 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] Movable zone start for each node
Oct  7 00:01:44 node-1 kernel: [    0.000000] Early memory node ranges
Oct  7 00:01:44 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct  7 00:01:44 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  7 00:01:44 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  7 00:01:44 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  7 00:01:44 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct  7 00:01:44 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct  7 00:01:44 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  7 00:01:44 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  7 00:01:44 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  7 00:01:44 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  7 00:01:44 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  7 00:01:44 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  7 00:01:44 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  7 00:01:44 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  7 00:01:44 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  7 00:01:44 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  7 00:01:44 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  7 00:01:44 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  7 00:01:44 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  7 00:01:44 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  7 00:01:44 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  7 00:01:44 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  7 00:01:44 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  7 00:01:44 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 
Oct  7 00:01:44 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct  7 00:01:44 node-1 kernel: [    0.000000] Policy zone: Normal
Oct  7 00:01:44 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=886bda69-7979-44e6-93aa-44ec4eb07b11 nomdmonddf nomdmonisw
Oct  7 00:01:44 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  7 00:01:44 node-1 kernel: [    0.000000] Checking aperture...
Oct  7 00:01:44 node-1 kernel: [    0.000000] No AGP bridge found
Oct  7 00:01:44 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  7 00:01:44 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  7 00:01:44 node-1 kernel: [    0.000000] Memory: 32653456K/33280636K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Oct  7 00:01:44 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  7 00:01:44 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  7 00:01:44 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  7 00:01:44 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  7 00:01:44 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  7 00:01:44 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  7 00:01:44 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  7 00:01:44 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  7 00:01:44 node-1 kernel: [    0.000000] console [tty0] enabled
Oct  7 00:01:44 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  7 00:01:44 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  7 00:01:44 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  7 00:01:44 node-1 kernel: [    0.000000] hpet clockevent registered
Oct  7 00:01:44 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  7 00:01:44 node-1 kernel: [    0.004000] tsc: Detected 3492.261 MHz processor
Oct  7 00:01:44 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.52 BogoMIPS (lpj=13969044)
Oct  7 00:01:44 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  7 00:01:44 node-1 kernel: [    0.000048] Security Framework initialized
Oct  7 00:01:44 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Oct  7 00:01:44 node-1 kernel: [    0.000067] Yama: becoming mindful.
Oct  7 00:01:44 node-1 kernel: [    0.001449] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.006334] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.008261] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.008288] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.008568] Initializing cgroup subsys memory
Oct  7 00:01:44 node-1 kernel: [    0.008576] Initializing cgroup subsys devices
Oct  7 00:01:44 node-1 kernel: [    0.008578] Initializing cgroup subsys freezer
Oct  7 00:01:44 node-1 kernel: [    0.008580] Initializing cgroup subsys blkio
Oct  7 00:01:44 node-1 kernel: [    0.008582] Initializing cgroup subsys perf_event
Oct  7 00:01:44 node-1 kernel: [    0.008584] Initializing cgroup subsys hugetlb
Oct  7 00:01:44 node-1 kernel: [    0.008603] CPU: Physical Processor ID: 0
Oct  7 00:01:44 node-1 kernel: [    0.008604] CPU: Processor Core ID: 0
Oct  7 00:01:44 node-1 kernel: [    0.008608] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  7 00:01:44 node-1 kernel: [    0.008608] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  7 00:01:44 node-1 kernel: [    0.009302] mce: CPU supports 22 MCE banks
Oct  7 00:01:44 node-1 kernel: [    0.009329] CPU0: Thermal monitoring enabled (TM1)
Oct  7 00:01:44 node-1 kernel: [    0.009350] process: using mwait in idle threads
Oct  7 00:01:44 node-1 kernel: [    0.009353] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  7 00:01:44 node-1 kernel: [    0.009353] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  7 00:01:44 node-1 kernel: [    0.009353] tlb_flushall_shift: 6
Oct  7 00:01:44 node-1 kernel: [    0.009442] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  7 00:01:44 node-1 kernel: [    0.010166] ACPI: Core revision 20131115
Oct  7 00:01:44 node-1 kernel: [    0.022859] ACPI: All ACPI Tables successfully acquired
Oct  7 00:01:44 node-1 kernel: [    0.023032] ftrace: allocating 28614 entries in 112 pages
Oct  7 00:01:44 node-1 kernel: [    0.031742] dmar: Host address width 46
Oct  7 00:01:44 node-1 kernel: [    0.031745] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  7 00:01:44 node-1 kernel: [    0.031751] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  7 00:01:44 node-1 kernel: [    0.031752] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  7 00:01:44 node-1 kernel: [    0.031756] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  7 00:01:44 node-1 kernel: [    0.031758] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  7 00:01:44 node-1 kernel: [    0.031759] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  7 00:01:44 node-1 kernel: [    0.031760] dmar: ATSR flags: 0x0
Oct  7 00:01:44 node-1 kernel: [    0.031761] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  7 00:01:44 node-1 kernel: [    0.031762] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  7 00:01:44 node-1 kernel: [    0.031878] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  7 00:01:44 node-1 kernel: [    0.031879] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  7 00:01:44 node-1 kernel: [    0.031880] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  7 00:01:44 node-1 kernel: [    0.031881] HPET id 0 under DRHD base 0xc7ffc000
Oct  7 00:01:44 node-1 kernel: [    0.031883] Your BIOS is broken and requested that x2apic be disabled.
Oct  7 00:01:44 node-1 kernel: [    0.031883] This will slightly decrease performance.
Oct  7 00:01:44 node-1 kernel: [    0.031883] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  7 00:01:44 node-1 kernel: [    0.032315] Enabled IRQ remapping in xapic mode
Oct  7 00:01:44 node-1 kernel: [    0.032316] x2apic not enabled, IRQ remapping is in xapic mode
Oct  7 00:01:44 node-1 kernel: [    0.032320] Switched APIC routing to physical flat.
Oct  7 00:01:44 node-1 kernel: [    0.032925] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  7 00:01:44 node-1 kernel: [    0.072579] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  7 00:01:44 node-1 kernel: [    0.072585] TSC deadline timer enabled
Oct  7 00:01:44 node-1 kernel: [    0.072592] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  7 00:01:44 node-1 kernel: [    0.072598] ... version:                3
Oct  7 00:01:44 node-1 kernel: [    0.072599] ... bit width:              48
Oct  7 00:01:44 node-1 kernel: [    0.072600] ... generic registers:      4
Oct  7 00:01:44 node-1 kernel: [    0.072601] ... value mask:             0000ffffffffffff
Oct  7 00:01:44 node-1 kernel: [    0.072602] ... max period:             0000ffffffffffff
Oct  7 00:01:44 node-1 kernel: [    0.072603] ... fixed-purpose events:   3
Oct  7 00:01:44 node-1 kernel: [    0.072604] ... event mask:             000000070000000f
Oct  7 00:01:44 node-1 kernel: [    0.074002] x86: Booting SMP configuration:
Oct  7 00:01:44 node-1 kernel: [    0.088205] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  7 00:01:44 node-1 kernel: [    0.074004] .... node  #0, CPUs:        #1  #2  #3
Oct  7 00:01:44 node-1 kernel: [    0.116116] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  7 00:01:44 node-1 kernel: [    0.270282] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  7 00:01:44 node-1 kernel: [    0.325913] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  7 00:01:44 node-1 kernel: [    0.382975] x86: Booted up 2 nodes, 16 CPUs
Oct  7 00:01:44 node-1 kernel: [    0.382978] smpboot: Total of 16 processors activated (111764.22 BogoMIPS)
Oct  7 00:01:44 node-1 kernel: [    0.408041] devtmpfs: initialized
Oct  7 00:01:44 node-1 kernel: [    0.410583] EVM: security.selinux
Oct  7 00:01:44 node-1 kernel: [    0.410585] EVM: security.SMACK64
Oct  7 00:01:44 node-1 kernel: [    0.410586] EVM: security.ima
Oct  7 00:01:44 node-1 kernel: [    0.410587] EVM: security.capability
Oct  7 00:01:44 node-1 kernel: [    0.410637] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.411292] pinctrl core: initialized pinctrl subsystem
Oct  7 00:01:44 node-1 kernel: [    0.411347] regulator-dummy: no parameters
Oct  7 00:01:44 node-1 kernel: [    0.411379] RTC time:  0:01:09, date: 10/07/16
Oct  7 00:01:44 node-1 kernel: [    0.411413] NET: Registered protocol family 16
Oct  7 00:01:44 node-1 kernel: [    0.411496] cpuidle: using governor ladder
Oct  7 00:01:44 node-1 kernel: [    0.411497] cpuidle: using governor menu
Oct  7 00:01:44 node-1 kernel: [    0.411547] ACPI: bus type PCI registered
Oct  7 00:01:44 node-1 kernel: [    0.411549] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  7 00:01:44 node-1 kernel: [    0.411595] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  7 00:01:44 node-1 kernel: [    0.411597] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  7 00:01:44 node-1 kernel: [    0.425305] PCI: Using configuration type 1 for base access
Oct  7 00:01:44 node-1 kernel: [    0.426302] bio: create slab <bio-0> at 0
Oct  7 00:01:44 node-1 kernel: [    0.426586] ACPI: Added _OSI(Module Device)
Oct  7 00:01:44 node-1 kernel: [    0.426588] ACPI: Added _OSI(Processor Device)
Oct  7 00:01:44 node-1 kernel: [    0.426589] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  7 00:01:44 node-1 kernel: [    0.426590] ACPI: Added _OSI(Processor Aggregator Device)
Oct  7 00:01:44 node-1 kernel: [    0.439430] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  7 00:01:44 node-1 kernel: [    0.450933] ACPI: Interpreter enabled
Oct  7 00:01:44 node-1 kernel: [    0.450938] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  7 00:01:44 node-1 kernel: [    0.450942] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  7 00:01:44 node-1 kernel: [    0.450945] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  7 00:01:44 node-1 kernel: [    0.450952] ACPI: (supports S0 S4 S5)
Oct  7 00:01:44 node-1 kernel: [    0.450953] ACPI: Using IOAPIC for interrupt routing
Oct  7 00:01:44 node-1 kernel: [    0.450995] HEST: Table parsing has been initialized.
Oct  7 00:01:44 node-1 kernel: [    0.450997] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  7 00:01:44 node-1 kernel: [    0.451556] ACPI: No dock devices found.
Oct  7 00:01:44 node-1 kernel: [    0.463180] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  7 00:01:44 node-1 kernel: [    0.463185] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  7 00:01:44 node-1 kernel: [    0.463188] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  7 00:01:44 node-1 kernel: [    0.463217] PCI host bridge to bus 0000:ff
Oct  7 00:01:44 node-1 kernel: [    0.463219] pci_bus 0000:ff: root bus resource [bus ff]
Oct  7 00:01:44 node-1 kernel: [    0.463227] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463266] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.463296] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463332] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463361] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.463391] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.463422] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463452] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463483] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463511] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463538] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463565] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463593] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463620] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463646] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463673] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463702] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463729] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463756] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.463784] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463810] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.463836] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463863] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463893] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.463928] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463959] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.463989] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464020] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464054] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464085] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464116] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464147] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464180] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464212] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464245] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464278] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464312] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464341] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464369] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464400] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464433] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464470] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464504] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464537] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464569] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464600] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464630] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464659] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464690] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464721] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464753] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464782] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464812] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464839] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464869] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464901] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464932] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.464989] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  7 00:01:44 node-1 kernel: [    0.464992] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  7 00:01:44 node-1 kernel: [    0.464995] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  7 00:01:44 node-1 kernel: [    0.465013] PCI host bridge to bus 0000:7f
Oct  7 00:01:44 node-1 kernel: [    0.465015] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  7 00:01:44 node-1 kernel: [    0.465020] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465047] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.465076] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465108] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465129] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.465155] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.465181] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465205] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465229] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465258] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465282] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465306] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465331] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465355] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465380] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465409] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465431] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465454] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465476] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.465500] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465521] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.465543] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465565] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465592] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  7 00:01:44 node-1 kernel: [    0.465624] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465650] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465676] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465702] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465728] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465753] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465779] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465807] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465832] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465859] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465887] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465915] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465944] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465969] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.465995] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466023] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466048] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466074] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466102] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466128] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466153] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466177] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466203] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466229] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466255] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466281] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466311] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466334] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466357] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466381] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466406] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466435] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.466460] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.467703] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  7 00:01:44 node-1 kernel: [    0.467706] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  7 00:01:44 node-1 kernel: [    0.468835] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  7 00:01:44 node-1 kernel: [    0.469348] PCI host bridge to bus 0000:00
Oct  7 00:01:44 node-1 kernel: [    0.469350] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  7 00:01:44 node-1 kernel: [    0.469352] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  7 00:01:44 node-1 kernel: [    0.469353] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  7 00:01:44 node-1 kernel: [    0.469355] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  7 00:01:44 node-1 kernel: [    0.469356] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  7 00:01:44 node-1 kernel: [    0.469357] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  7 00:01:44 node-1 kernel: [    0.469359] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  7 00:01:44 node-1 kernel: [    0.469365] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  7 00:01:44 node-1 kernel: [    0.469450] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.469480] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.469522] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  7 00:01:44 node-1 kernel: [    0.469541] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.469571] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.469611] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  7 00:01:44 node-1 kernel: [    0.469630] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.469660] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.469703] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  7 00:01:44 node-1 kernel: [    0.469721] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.469792] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.469869] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.469947] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  7 00:01:44 node-1 kernel: [    0.469952] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  7 00:01:44 node-1 kernel: [    0.470038] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  7 00:01:44 node-1 kernel: [    0.470187] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  7 00:01:44 node-1 kernel: [    0.470204] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  7 00:01:44 node-1 kernel: [    0.470282] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.470337] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  7 00:01:44 node-1 kernel: [    0.470359] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.470415] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.470458] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  7 00:01:44 node-1 kernel: [    0.470487] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.470543] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.470586] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  7 00:01:44 node-1 kernel: [    0.470609] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  7 00:01:44 node-1 kernel: [    0.470626] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  7 00:01:44 node-1 kernel: [    0.470704] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.470754] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  7 00:01:44 node-1 kernel: [    0.470782] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  7 00:01:44 node-1 kernel: [    0.471031] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  7 00:01:44 node-1 kernel: [    0.471037] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  7 00:01:44 node-1 kernel: [    0.471043] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.471048] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.471056] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  7 00:01:44 node-1 kernel: [    0.471086] pci 0000:01:00.0: supports D1 D2
Oct  7 00:01:44 node-1 kernel: [    0.477262] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  7 00:01:44 node-1 kernel: [    0.477269] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  7 00:01:44 node-1 kernel: [    0.477273] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  7 00:01:44 node-1 kernel: [    0.477452] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.477485] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  7 00:01:44 node-1 kernel: [    0.485259] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  7 00:01:44 node-1 kernel: [    0.485262] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.485264] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  7 00:01:44 node-1 kernel: [    0.485319] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.485386] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.485462] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.485508] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  7 00:01:44 node-1 kernel: [    0.485511] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.485513] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  7 00:01:44 node-1 kernel: [    0.485572] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.485699] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.485753] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  7 00:01:44 node-1 kernel: [    0.485756] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.485758] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.485807] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.485926] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.485963] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.486082] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.486121] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.486241] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.486282] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  7 00:01:44 node-1 kernel: [    0.486400] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  7 00:01:44 node-1 kernel: [    0.486444] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  7 00:01:44 node-1 kernel: [    0.486447] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.486449] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.486507] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  7 00:01:44 node-1 kernel: [    0.486591] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.486645] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.486685] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  7 00:01:44 node-1 kernel: [    0.486764] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  7 00:01:44 node-1 kernel: [    0.486880] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  7 00:01:44 node-1 kernel: [    0.486883] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.486885] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.486943] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  7 00:01:44 node-1 kernel: [    0.487002] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.487050] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.487269] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  7 00:01:44 node-1 kernel: [    0.487273] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  7 00:01:44 node-1 kernel: [    0.487342] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  7 00:01:44 node-1 kernel: [    0.487400] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.487447] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.487693] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  7 00:01:44 node-1 kernel: [    0.487697] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  7 00:01:44 node-1 kernel: [    0.487765] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  7 00:01:44 node-1 kernel: [    0.487828] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.487880] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  7 00:01:44 node-1 kernel: [    0.488103] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  7 00:01:44 node-1 kernel: [    0.488106] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  7 00:01:44 node-1 kernel: [    0.488282] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  7 00:01:44 node-1 kernel: [    0.488320] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  7 00:01:44 node-1 kernel: [    0.488395] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  7 00:01:44 node-1 kernel: [    0.488414] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  7 00:01:44 node-1 kernel: [    0.488427] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  7 00:01:44 node-1 kernel: [    0.488440] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  7 00:01:44 node-1 kernel: [    0.488490] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  7 00:01:44 node-1 kernel: [    0.493279] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  7 00:01:44 node-1 kernel: [    0.493288] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  7 00:01:44 node-1 kernel: [    0.493335] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  7 00:01:44 node-1 kernel: [    0.493828] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  7 00:01:44 node-1 kernel: [    0.493831] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  7 00:01:44 node-1 kernel: [    0.493956] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  7 00:01:44 node-1 kernel: [    0.494063] PCI host bridge to bus 0000:80
Oct  7 00:01:44 node-1 kernel: [    0.494065] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  7 00:01:44 node-1 kernel: [    0.494066] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  7 00:01:44 node-1 kernel: [    0.494068] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  7 00:01:44 node-1 kernel: [    0.494076] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.494140] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.494208] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  7 00:01:44 node-1 kernel: [    0.494270] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  7 00:01:44 node-1 kernel: [    0.494275] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  7 00:01:44 node-1 kernel: [    0.494349] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  7 00:01:44 node-1 kernel: [    0.494650] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  7 00:01:44 node-1 kernel: [    0.494682] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  7 00:01:44 node-1 kernel: [    0.494712] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  7 00:01:44 node-1 kernel: [    0.494741] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  7 00:01:44 node-1 kernel: [    0.494770] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  7 00:01:44 node-1 kernel: [    0.494800] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  7 00:01:44 node-1 kernel: [    0.494830] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  7 00:01:44 node-1 kernel: [    0.494860] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  7 00:01:44 node-1 kernel: [    0.494946] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  7 00:01:44 node-1 kernel: [    0.494950] ACPI: \_SB_.UNC1: notify handler is installed
Oct  7 00:01:44 node-1 kernel: [    0.494952] ACPI: \_SB_.UNC0: notify handler is installed
Oct  7 00:01:44 node-1 kernel: [    0.494967] ACPI: \_SB_.PCI0: notify handler is installed
Oct  7 00:01:44 node-1 kernel: [    0.495020] ACPI: \_SB_.PCI1: notify handler is installed
Oct  7 00:01:44 node-1 kernel: [    0.495099] Found 4 acpi root devices
Oct  7 00:01:44 node-1 kernel: [    0.495206] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  7 00:01:44 node-1 kernel: [    0.495209] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  7 00:01:44 node-1 kernel: [    0.495210] vgaarb: loaded
Oct  7 00:01:44 node-1 kernel: [    0.495211] vgaarb: bridge control possible 0000:0c:00.0
Oct  7 00:01:44 node-1 kernel: [    0.495332] SCSI subsystem initialized
Oct  7 00:01:44 node-1 kernel: [    0.495395] libata version 3.00 loaded.
Oct  7 00:01:44 node-1 kernel: [    0.495410] ACPI: bus type USB registered
Oct  7 00:01:44 node-1 kernel: [    0.495420] usbcore: registered new interface driver usbfs
Oct  7 00:01:44 node-1 kernel: [    0.495425] usbcore: registered new interface driver hub
Oct  7 00:01:44 node-1 kernel: [    0.495449] usbcore: registered new device driver usb
Oct  7 00:01:44 node-1 kernel: [    0.495620] PCI: Using ACPI for IRQ routing
Oct  7 00:01:44 node-1 kernel: [    0.499220] PCI: pci_cache_line_size set to 64 bytes
Oct  7 00:01:44 node-1 kernel: [    0.499421] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  7 00:01:44 node-1 kernel: [    0.499422] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct  7 00:01:44 node-1 kernel: [    0.499423] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  7 00:01:44 node-1 kernel: [    0.499491] NetLabel: Initializing
Oct  7 00:01:44 node-1 kernel: [    0.499493] NetLabel:  domain hash size = 128
Oct  7 00:01:44 node-1 kernel: [    0.499494] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  7 00:01:44 node-1 kernel: [    0.499504] NetLabel:  unlabeled traffic allowed by default
Oct  7 00:01:44 node-1 kernel: [    0.499560] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  7 00:01:44 node-1 kernel: [    0.499564] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  7 00:01:44 node-1 kernel: [    0.501619] Switched to clocksource hpet
Oct  7 00:01:44 node-1 kernel: [    0.505541] AppArmor: AppArmor Filesystem Enabled
Oct  7 00:01:44 node-1 kernel: [    0.505555] pnp: PnP ACPI init
Oct  7 00:01:44 node-1 kernel: [    0.505562] ACPI: bus type PNP registered
Oct  7 00:01:44 node-1 kernel: [    0.505686] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  7 00:01:44 node-1 kernel: [    0.505694] pnp 00:01: [dma 4]
Oct  7 00:01:44 node-1 kernel: [    0.505706] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  7 00:01:44 node-1 kernel: [    0.505733] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  7 00:01:44 node-1 kernel: [    0.505753] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  7 00:01:44 node-1 kernel: [    0.505771] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  7 00:01:44 node-1 kernel: [    0.505803] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  7 00:01:44 node-1 kernel: [    0.505856] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505858] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  7 00:01:44 node-1 kernel: [    0.505860] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505861] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505863] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505868] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505870] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  7 00:01:44 node-1 kernel: [    0.505871] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505873] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505874] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505876] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505877] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505879] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  7 00:01:44 node-1 kernel: [    0.505881] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  7 00:01:44 node-1 kernel: [    0.505965] pnp 00:07: [dma 0 disabled]
Oct  7 00:01:44 node-1 kernel: [    0.505993] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  7 00:01:44 node-1 kernel: [    0.506067] pnp 00:08: [dma 0 disabled]
Oct  7 00:01:44 node-1 kernel: [    0.506103] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  7 00:01:44 node-1 kernel: [    0.506153] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  7 00:01:44 node-1 kernel: [    0.506503] pnp: PnP ACPI: found 10 devices
Oct  7 00:01:44 node-1 kernel: [    0.506505] ACPI: bus type PNP unregistered
Oct  7 00:01:44 node-1 kernel: [    0.512738] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  7 00:01:44 node-1 kernel: [    0.512741] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  7 00:01:44 node-1 kernel: [    0.512744] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  7 00:01:44 node-1 kernel: [    0.512748] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  7 00:01:44 node-1 kernel: [    0.512750] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.512764] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.512793] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  7 00:01:44 node-1 kernel: [    0.512810] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  7 00:01:44 node-1 kernel: [    0.512839] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  7 00:01:44 node-1 kernel: [    0.512853] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  7 00:01:44 node-1 kernel: [    0.512882] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  7 00:01:44 node-1 kernel: [    0.512897] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  7 00:01:44 node-1 kernel: [    0.512925] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  7 00:01:44 node-1 kernel: [    0.512927] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.512942] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.512971] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  7 00:01:44 node-1 kernel: [    0.512973] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.512987] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513016] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  7 00:01:44 node-1 kernel: [    0.513017] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.513020] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513024] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  7 00:01:44 node-1 kernel: [    0.513026] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.513028] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513032] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  7 00:01:44 node-1 kernel: [    0.513037] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  7 00:01:44 node-1 kernel: [    0.513045] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  7 00:01:44 node-1 kernel: [    0.513048] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  7 00:01:44 node-1 kernel: [    0.513055] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  7 00:01:44 node-1 kernel: [    0.513055] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  7 00:01:44 node-1 kernel: [    0.513056] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  7 00:01:44 node-1 kernel: [    0.513057] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  7 00:01:44 node-1 kernel: [    0.513058] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  7 00:01:44 node-1 kernel: [    0.513059] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  7 00:01:44 node-1 kernel: [    0.513060] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  7 00:01:44 node-1 kernel: [    0.513061] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  7 00:01:44 node-1 kernel: [    0.513062] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.513063] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513064] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.513064] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513065] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.513066] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513067] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.513068] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513069] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  7 00:01:44 node-1 kernel: [    0.513070] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513071] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  7 00:01:44 node-1 kernel: [    0.513072] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  7 00:01:44 node-1 kernel: [    0.513073] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  7 00:01:44 node-1 kernel: [    0.513074] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  7 00:01:44 node-1 kernel: [    0.513076] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  7 00:01:44 node-1 kernel: [    0.513077] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  7 00:01:44 node-1 kernel: [    0.513113] NET: Registered protocol family 2
Oct  7 00:01:44 node-1 kernel: [    0.513374] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.513711] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.513853] TCP: Hash tables configured (established 262144 bind 65536)
Oct  7 00:01:44 node-1 kernel: [    0.513889] TCP: reno registered
Oct  7 00:01:44 node-1 kernel: [    0.513917] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.514010] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.514156] NET: Registered protocol family 1
Oct  7 00:01:44 node-1 kernel: [    0.553725] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  7 00:01:44 node-1 kernel: [    0.553739] PCI: CLS 64 bytes, default 64
Oct  7 00:01:44 node-1 kernel: [    0.553816] Trying to unpack rootfs image as initramfs...
Oct  7 00:01:44 node-1 kernel: [    0.772643] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Oct  7 00:01:44 node-1 kernel: [    0.772699] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  7 00:01:44 node-1 kernel: [    0.772701] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct  7 00:01:44 node-1 kernel: [    0.773124] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773130] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773135] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773140] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773152] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773169] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773184] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773199] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773211] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773221] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773227] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773234] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773242] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773255] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773268] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773280] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  7 00:01:44 node-1 kernel: [    0.773415] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  7 00:01:44 node-1 kernel: [    0.773421] Scanning for low memory corruption every 60 seconds
Oct  7 00:01:44 node-1 kernel: [    0.773865] Initialise system trusted keyring
Oct  7 00:01:44 node-1 kernel: [    0.773920] audit: initializing netlink socket (disabled)
Oct  7 00:01:44 node-1 kernel: [    0.773936] type=2000 audit(1475798468.724:1): initialized
Oct  7 00:01:44 node-1 kernel: [    0.791657] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  7 00:01:44 node-1 kernel: [    0.793164] zbud: loaded
Oct  7 00:01:44 node-1 kernel: [    0.793290] VFS: Disk quotas dquot_6.5.2
Oct  7 00:01:44 node-1 kernel: [    0.793325] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  7 00:01:44 node-1 kernel: [    0.793705] fuse init (API version 7.22)
Oct  7 00:01:44 node-1 kernel: [    0.793769] msgmni has been set to 32768
Oct  7 00:01:44 node-1 kernel: [    0.793818] Key type big_key registered
Oct  7 00:01:44 node-1 kernel: [    0.794349] Key type asymmetric registered
Oct  7 00:01:44 node-1 kernel: [    0.794351] Asymmetric key parser 'x509' registered
Oct  7 00:01:44 node-1 kernel: [    0.794374] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  7 00:01:44 node-1 kernel: [    0.794444] io scheduler noop registered
Oct  7 00:01:44 node-1 kernel: [    0.794446] io scheduler deadline registered (default)
Oct  7 00:01:44 node-1 kernel: [    0.794466] io scheduler cfq registered
Oct  7 00:01:44 node-1 kernel: [    0.795019] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    0.795169] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    0.795282] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    0.795404] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    0.795515] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    0.795654] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    0.796028] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  7 00:01:44 node-1 kernel: [    0.796054] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  7 00:01:44 node-1 kernel: [    0.796070] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  7 00:01:44 node-1 kernel: [    0.796079] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796081] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796084] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  7 00:01:44 node-1 kernel: [    0.796089] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796090] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796092] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796093] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796095] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796096] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796098] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796099] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796101] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796102] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796103] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796105] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796107] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  7 00:01:44 node-1 kernel: [    0.796112] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796115] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  7 00:01:44 node-1 kernel: [    0.796129] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796132] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  7 00:01:44 node-1 kernel: [    0.796143] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796145] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  7 00:01:44 node-1 kernel: [    0.796152] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  7 00:01:44 node-1 kernel: [    0.796201] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  7 00:01:44 node-1 kernel: [    0.796207] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  7 00:01:44 node-1 kernel: [    0.796212] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  7 00:01:44 node-1 kernel: [    0.796221] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  7 00:01:44 node-1 kernel: [    0.796261] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  7 00:01:44 node-1 kernel: [    0.796262] vesafb: scrolling: redraw
Oct  7 00:01:44 node-1 kernel: [    0.796264] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  7 00:01:44 node-1 kernel: [    0.816850] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  7 00:01:44 node-1 kernel: [    0.825368] Console: switching to colour frame buffer device 80x30
Oct  7 00:01:44 node-1 kernel: [    0.834036] fb0: VESA VGA frame buffer device
Oct  7 00:01:44 node-1 kernel: [    0.834232] intel_idle: MWAIT substates: 0x2120
Oct  7 00:01:44 node-1 kernel: [    0.834233] intel_idle: v0.4 model 0x3F
Oct  7 00:01:44 node-1 kernel: [    0.834234] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  7 00:01:44 node-1 kernel: [    0.834461] ipmi message handler version 39.2
Oct  7 00:01:44 node-1 kernel: [    0.834735] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  7 00:01:44 node-1 kernel: [    0.835167] ACPI: AC Adapter [P111] (on-line)
Oct  7 00:01:44 node-1 kernel: [    0.840385] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  7 00:01:44 node-1 kernel: [    0.851370] ACPI: Power Button [PWRB]
Oct  7 00:01:44 node-1 kernel: [    0.857113] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  7 00:01:44 node-1 kernel: [    0.868724] ACPI: Power Button [PWRF]
Oct  7 00:01:44 node-1 kernel: [    0.895172] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  7 00:01:44 node-1 kernel: [    0.906797] pstore: Registered erst as persistent store backend
Oct  7 00:01:44 node-1 kernel: [    0.912984] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  7 00:01:44 node-1 kernel: [    0.924891] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  7 00:01:44 node-1 kernel: [    0.951618] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  7 00:01:44 node-1 kernel: [    0.984890] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  7 00:01:44 node-1 kernel: [    0.998951] Linux agpgart interface v0.103
Oct  7 00:01:44 node-1 kernel: [    1.006554] brd: module loaded
Oct  7 00:01:44 node-1 kernel: [    1.013613] loop: module loaded
Oct  7 00:01:44 node-1 kernel: [    1.020322] libphy: Fixed MDIO Bus: probed
Oct  7 00:01:44 node-1 kernel: [    1.026779] tun: Universal TUN/TAP device driver, 1.6
Oct  7 00:01:44 node-1 kernel: [    1.033254] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  7 00:01:44 node-1 kernel: [    1.039782] PPP generic driver version 2.4.2
Oct  7 00:01:44 node-1 kernel: [    1.046179] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  7 00:01:44 node-1 kernel: [    1.052613] ehci-pci: EHCI PCI platform driver
Oct  7 00:01:44 node-1 kernel: [    1.059145] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  7 00:01:44 node-1 kernel: [    1.065561] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  7 00:01:44 node-1 kernel: [    1.078106] ehci-pci 0000:00:1a.0: debug port 2
Oct  7 00:01:44 node-1 kernel: [    1.088318] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  7 00:01:44 node-1 kernel: [    1.088336] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  7 00:01:44 node-1 kernel: [    1.105113] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  7 00:01:44 node-1 kernel: [    1.111188] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  7 00:01:44 node-1 kernel: [    1.117376] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  7 00:01:44 node-1 kernel: [    1.129271] usb usb1: Product: EHCI Host Controller
Oct  7 00:01:44 node-1 kernel: [    1.135294] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  7 00:01:44 node-1 kernel: [    1.141343] usb usb1: SerialNumber: 0000:00:1a.0
Oct  7 00:01:44 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  7 00:01:44 node-1 kernel: [    1.147296] hub 1-0:1.0: USB hub found
Oct  7 00:01:44 node-1 kernel: [    1.153070] hub 1-0:1.0: 2 ports detected
Oct  7 00:01:44 node-1 kernel: [    1.158946] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  7 00:01:44 node-1 kernel: [    1.164551] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  7 00:01:44 node-1 kernel: [    1.175464] ehci-pci 0000:00:1d.0: debug port 2
Oct  7 00:01:44 node-1 kernel: [    1.184760] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  7 00:01:44 node-1 kernel: [    1.184763] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  7 00:01:44 node-1 kernel: [    1.201032] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  7 00:01:44 node-1 kernel: [    1.206251] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  7 00:01:44 node-1 kernel: [    1.211574] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  7 00:01:44 node-1 kernel: [    1.222175] usb usb2: Product: EHCI Host Controller
Oct  7 00:01:44 node-1 kernel: [    1.227652] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  7 00:01:44 node-1 kernel: [    1.233197] usb usb2: SerialNumber: 0000:00:1d.0
Oct  7 00:01:44 node-1 kernel: [    1.238721] hub 2-0:1.0: USB hub found
Oct  7 00:01:44 node-1 kernel: [    1.244077] hub 2-0:1.0: 2 ports detected
Oct  7 00:01:44 node-1 kernel: [    1.249384] ehci-platform: EHCI generic platform driver
Oct  7 00:01:44 node-1 kernel: [    1.254621] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  7 00:01:44 node-1 kernel: [    1.259938] ohci-pci: OHCI PCI platform driver
Oct  7 00:01:44 node-1 kernel: [    1.265235] ohci-platform: OHCI generic platform driver
Oct  7 00:01:44 node-1 kernel: [    1.270433] uhci_hcd: USB Universal Host Controller Interface driver
Oct  7 00:01:44 node-1 kernel: [    1.275774] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  7 00:01:44 node-1 kernel: [    1.468812] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  7 00:01:44 node-1 kernel: [    1.768628] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  7 00:01:44 node-1 kernel: [    1.784854] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  7 00:01:44 node-1 kernel: [    1.790473] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  7 00:01:44 node-1 kernel: [    1.796373] hub 1-1:1.0: USB hub found
Oct  7 00:01:44 node-1 kernel: [    1.801967] hub 1-1:1.0: 6 ports detected
Oct  7 00:01:44 node-1 kernel: [    1.916453] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  7 00:01:44 node-1 kernel: [    2.314746] i8042: No controller found
Oct  7 00:01:44 node-1 kernel: [    2.320295] mousedev: PS/2 mouse device common for all mice
Oct  7 00:01:44 node-1 kernel: [    2.326012] rtc_cmos 00:02: RTC can wake from S4
Oct  7 00:01:44 node-1 kernel: [    2.331746] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  7 00:01:44 node-1 kernel: [    2.332835] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  7 00:01:44 node-1 kernel: [    2.332836] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  7 00:01:44 node-1 kernel: [    2.333347] hub 2-1:1.0: USB hub found
Oct  7 00:01:44 node-1 kernel: [    2.333582] hub 2-1:1.0: 8 ports detected
Oct  7 00:01:44 node-1 kernel: [    2.359869] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  7 00:01:44 node-1 kernel: [    2.371148] device-mapper: uevent: version 1.0.3
Oct  7 00:01:44 node-1 kernel: [    2.376845] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  7 00:01:44 node-1 kernel: [    2.388183] ledtrig-cpu: registered to indicate activity on CPUs
Oct  7 00:01:44 node-1 kernel: [    2.394157] TCP: cubic registered
Oct  7 00:01:44 node-1 kernel: [    2.400006] NET: Registered protocol family 10
Oct  7 00:01:44 node-1 kernel: [    2.406053] NET: Registered protocol family 17
Oct  7 00:01:44 node-1 kernel: [    2.411803] Key type dns_resolver registered
Oct  7 00:01:44 node-1 kernel: [    2.417838] Loading compiled-in X.509 certificates
Oct  7 00:01:44 node-1 kernel: [    2.424022] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  7 00:01:44 node-1 kernel: [    2.435607] registered taskstats version 1
Oct  7 00:01:44 node-1 kernel: [    2.443620] Key type trusted registered
Oct  7 00:01:44 node-1 kernel: [    2.451195] Key type encrypted registered
Oct  7 00:01:44 node-1 kernel: [    2.456671] AppArmor: AppArmor sha1 policy hashing enabled
Oct  7 00:01:44 node-1 kernel: [    2.462162] IMA: No TPM chip found, activating TPM-bypass!
Oct  7 00:01:44 node-1 kernel: [    2.468215] regulator-dummy: disabling
Oct  7 00:01:44 node-1 kernel: [    2.473702]   Magic number: 4:507:0
Oct  7 00:01:44 node-1 kernel: [    2.479346] memory memory48: hash matches
Oct  7 00:01:44 node-1 kernel: [    2.484791] rtc_cmos 00:02: setting system clock to 2016-10-07 00:01:11 UTC (1475798471)
Oct  7 00:01:44 node-1 kernel: [    2.497191] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  7 00:01:44 node-1 kernel: [    2.502796] EDD information not available.
Oct  7 00:01:44 node-1 kernel: [    2.508472] PM: Hibernation image not present or could not be loaded.
Oct  7 00:01:44 node-1 kernel: [    2.509330] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  7 00:01:44 node-1 kernel: [    2.520743] Write protecting the kernel read-only data: 12288k
Oct  7 00:01:44 node-1 kernel: [    2.527008] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  7 00:01:44 node-1 kernel: [    2.539889] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  7 00:01:44 node-1 kernel: [    2.573437] device-mapper: multipath: version 1.6.0 loaded
Oct  7 00:01:44 node-1 kernel: [    2.581260] systemd-udevd[216]: starting version 204
Oct  7 00:01:44 node-1 kernel: [    2.603863] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  7 00:01:44 node-1 kernel: [    2.615901] md: linear personality registered for level -1
Oct  7 00:01:44 node-1 kernel: [    2.624574] md: multipath personality registered for level -4
Oct  7 00:01:44 node-1 kernel: [    2.632844] md: raid0 personality registered for level 0
Oct  7 00:01:44 node-1 kernel: [    2.641356] md: raid1 personality registered for level 1
Oct  7 00:01:44 node-1 kernel: [    2.647588] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  7 00:01:44 node-1 kernel: [    2.647588] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  7 00:01:44 node-1 kernel: [    2.657009] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct  7 00:01:44 node-1 kernel: [    2.657011] 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
Oct  7 00:01:44 node-1 kernel: [    2.657012] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  7 00:01:44 node-1 kernel: [    2.657082] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.657119] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.657155] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.657194] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.657273] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.666267] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct  7 00:01:44 node-1 kernel: [    2.666268] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct  7 00:01:44 node-1 kernel: [    2.666269] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  7 00:01:44 node-1 kernel: [    2.666331] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.666370] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.666446] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.666484] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.666522] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.666557] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.666657] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.678629] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct  7 00:01:44 node-1 kernel: [    2.678631] 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
Oct  7 00:01:44 node-1 kernel: [    2.678632] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  7 00:01:44 node-1 kernel: [    2.678694] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.678730] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.678765] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.678804] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.678917] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.686799] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct  7 00:01:44 node-1 kernel: [    2.686800] 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
Oct  7 00:01:44 node-1 kernel: [    2.686801] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  7 00:01:44 node-1 kernel: [    2.686884] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.686916] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.686949] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.686984] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.687044] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.757235] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  7 00:01:44 node-1 kernel: [    2.757236] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  7 00:01:44 node-1 kernel: [    2.757237] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  7 00:01:44 node-1 kernel: [    2.757238] usb 2-1.4: Manufacturer: Avocent
Oct  7 00:01:44 node-1 kernel: [    2.757238] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  7 00:01:44 node-1 kernel: [    2.887816] Switched to clocksource tsc
Oct  7 00:01:44 node-1 kernel: [    2.887932] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  7 00:01:44 node-1 kernel: [    2.889683] megasas: FW now in Ready state
Oct  7 00:01:44 node-1 kernel: [    2.889842] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.889933] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890062] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890196] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890292] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890417] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890477] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890566] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890684] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890818] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.890984] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.891089] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.891184] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.891304] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.891383] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.891460] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Oct  7 00:01:44 node-1 kernel: [    2.892166] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  7 00:01:44 node-1 kernel: [    2.934136] hidraw: raw HID events driver (C) Jiri Kosina
Oct  7 00:01:44 node-1 kernel: [    2.944172] usbcore: registered new interface driver usbhid
Oct  7 00:01:44 node-1 kernel: [    2.950611] usbhid: USB HID core driver
Oct  7 00:01:44 node-1 kernel: [    2.958023] 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
Oct  7 00:01:44 node-1 kernel: [    2.971286] 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
Oct  7 00:01:44 node-1 kernel: [    2.984637] 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
Oct  7 00:01:44 node-1 kernel: [    2.987505] raid6: sse2x1   10934 MB/s
Oct  7 00:01:44 node-1 kernel: [    3.004684] 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
Oct  7 00:01:44 node-1 kernel: [    3.018405] 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
Oct  7 00:01:44 node-1 kernel: [    3.032113] 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
Oct  7 00:01:44 node-1 kernel: [    3.055450] raid6: sse2x2   14491 MB/s
Oct  7 00:01:44 node-1 kernel: [    3.127387] raid6: sse2x4   16845 MB/s
Oct  7 00:01:44 node-1 kernel: [    3.199325] raid6: avx2x1   22374 MB/s
Oct  7 00:01:44 node-1 kernel: [    3.227305] megasas:IOC Init cmd success
Oct  7 00:01:44 node-1 kernel: [    3.255287] megasas: INIT adapter done
Oct  7 00:01:44 node-1 kernel: [    3.271266] raid6: avx2x2   25810 MB/s
Oct  7 00:01:44 node-1 kernel: [    3.331218] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  7 00:01:44 node-1 kernel: [    3.337709] scsi0 : LSI SAS based MegaRAID driver
Oct  7 00:01:44 node-1 kernel: [    3.343202] raid6: avx2x4   30188 MB/s
Oct  7 00:01:44 node-1 kernel: [    3.343203] raid6: using algorithm avx2x4 (30188 MB/s)
Oct  7 00:01:44 node-1 kernel: [    3.343203] raid6: using avx2x2 recovery algorithm
Oct  7 00:01:44 node-1 kernel: [    3.363849] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  7 00:01:44 node-1 kernel: [    3.376342] xor: automatically using best checksumming function:
Oct  7 00:01:44 node-1 kernel: [    3.384798] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  7 00:01:44 node-1 kernel: [    3.400089] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  7 00:01:44 node-1 kernel: [    3.406539] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  7 00:01:44 node-1 kernel: [    3.419157]    avx       : 36469.000 MB/sec
Oct  7 00:01:44 node-1 kernel: [    3.419174] sd 0:2:0:0: [sda] Write Protect is off
Oct  7 00:01:44 node-1 kernel: [    3.419175] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  7 00:01:44 node-1 kernel: [    3.419246] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  7 00:01:44 node-1 kernel: [    3.443440] async_tx: api initialized (async)
Oct  7 00:01:44 node-1 kernel: [    3.446941]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct  7 00:01:44 node-1 kernel: [    3.448632] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  7 00:01:44 node-1 kernel: [    3.464362] md: raid6 personality registered for level 6
Oct  7 00:01:44 node-1 kernel: [    3.469896] md: raid5 personality registered for level 5
Oct  7 00:01:44 node-1 kernel: [    3.475198] md: raid4 personality registered for level 4
Oct  7 00:01:44 node-1 kernel: [    3.483277] md: raid10 personality registered for level 10
Oct  7 00:01:44 node-1 kernel: [    3.528735] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Oct  7 00:01:44 node-1 kernel: [    3.569035] random: lvm urandom read with 25 bits of entropy available
Oct  7 00:01:44 node-1 kernel: [    3.711085] bio: create slab <bio-1> at 1
Oct  7 00:01:44 node-1 kernel: [    4.453465] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  7 00:01:44 node-1 kernel: [    4.972544] init: plymouth-upstart-bridge main process (552) terminated with status 1
Oct  7 00:01:44 node-1 kernel: [    4.984645] init: plymouth-upstart-bridge main process ended, respawning
Oct  7 00:01:44 node-1 kernel: [    5.118220] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  7 00:01:44 node-1 kernel: [    5.145575] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  7 00:01:44 node-1 kernel: [    5.293877] random: nonblocking pool is initialized
Oct  7 00:01:44 node-1 kernel: [    5.342977] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  7 00:01:44 node-1 kernel: [    5.408859] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  7 00:01:44 node-1 kernel: [    5.448030] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  7 00:01:44 node-1 kernel: [    5.698870] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  7 00:01:44 node-1 kernel: [    5.746567] XFS (dm-0): Mounting Filesystem
Oct  7 00:01:44 node-1 kernel: [    6.009285] XFS (dm-0): Ending clean mount
Oct  7 00:01:44 node-1 kernel: [    6.064951] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  7 00:01:44 node-1 kernel: [    6.111588] XFS (dm-1): Mounting Filesystem
Oct  7 00:01:44 node-1 kernel: [    6.247006] XFS (dm-1): Ending clean mount
Oct  7 00:01:44 node-1 kernel: [    7.909891] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  7 00:01:44 node-1 kernel: [    7.923943] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  7 00:01:44 node-1 kernel: [    8.075651] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  7 00:01:44 node-1 kernel: [    8.075657] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  7 00:01:44 node-1 kernel: [    8.075660] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  7 00:01:44 node-1 kernel: [    8.075664] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  7 00:01:44 node-1 kernel: [    8.117269] systemd-udevd[774]: starting version 204
Oct  7 00:01:44 node-1 kernel: [    8.357975] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  7 00:01:44 node-1 kernel: [    8.361846] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  7 00:01:44 node-1 kernel: [    8.361853] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  7 00:01:44 node-1 kernel: [    8.361856] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  7 00:01:44 node-1 kernel: [    8.361858] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  7 00:01:44 node-1 kernel: [    8.361944] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  7 00:01:44 node-1 kernel: [    8.364268] power_meter ACPI000D:00: Found ACPI power meter.
Oct  7 00:01:44 node-1 kernel: [    8.364305] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  7 00:01:44 node-1 kernel: [    8.373015] wmi: Mapper loaded
Oct  7 00:01:44 node-1 kernel: [    8.404724] IPMI System Interface driver.
Oct  7 00:01:44 node-1 kernel: [    8.404781] ipmi_si: probing via ACPI
Oct  7 00:01:44 node-1 kernel: [    8.404792] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  7 00:01:44 node-1 kernel: [    8.404793] ipmi_si: Adding ACPI-specified kcs state machine
Oct  7 00:01:44 node-1 kernel: [    8.404802] ipmi_si: probing via SMBIOS
Oct  7 00:01:44 node-1 kernel: [    8.404803] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  7 00:01:44 node-1 kernel: [    8.404804] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  7 00:01:44 node-1 kernel: [    8.404806] ipmi_si: probing via SPMI
Oct  7 00:01:44 node-1 kernel: [    8.404806] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  7 00:01:44 node-1 kernel: [    8.404807] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  7 00:01:44 node-1 kernel: [    8.404808] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  7 00:01:44 node-1 kernel: [    8.439398] systemd-udevd[792]: renamed network interface eth3 to enp9s0
Oct  7 00:01:44 node-1 kernel: [    8.463251] systemd-udevd[816]: renamed network interface eth1 to enp7s0
Oct  7 00:01:44 node-1 kernel: [    8.495276] systemd-udevd[820]: renamed network interface eth2 to enp8s0
Oct  7 00:01:44 node-1 kernel: [    8.524153] systemd-udevd[809]: renamed network interface eth0 to enp6s0
Oct  7 00:01:44 node-1 kernel: [    8.541450] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  7 00:01:44 node-1 kernel: [    8.541461] ipmi_si 00:09: IPMI kcs interface initialized
Oct  7 00:01:44 node-1 kernel: [    8.731314] type=1400 audit(1475798477.748:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1027 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.731469] type=1400 audit(1475798477.748:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1027 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.731596] type=1400 audit(1475798477.748:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1027 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.750739] type=1400 audit(1475798477.768:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1023 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.750979] type=1400 audit(1475798477.768:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1023 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.751194] type=1400 audit(1475798477.768:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1023 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.780085] type=1400 audit(1475798477.796:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1024 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.780239] type=1400 audit(1475798477.796:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1024 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.780358] type=1400 audit(1475798477.796:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1024 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    8.785155] type=1400 audit(1475798477.800:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1025 comm="apparmor_parser"
Oct  7 00:01:44 node-1 kernel: [    9.299060] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  7 00:01:44 node-1 kernel: [    9.306763] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  7 00:01:44 node-1 kernel: [    9.499409] enic 0000:06:00.0 enp6s0: Link UP
Oct  7 00:01:44 node-1 kernel: [    9.500529] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  7 00:01:44 node-1 kernel: [    9.500534] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  7 00:01:44 node-1 kernel: [   18.452822] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  7 00:01:45 node-1 failsafe: Failsafe of 120 seconds reached.
Oct  7 00:01:45 node-1 kernel: [   36.861453] init: failsafe main process (8418) killed by TERM signal
Oct  7 00:01:46 node-1 dbus[8525]: [system] AppArmor D-Bus mediation is enabled
Oct  7 00:01:46 node-1 kernel: [   37.061670] audit_printk_skb: 30 callbacks suppressed
Oct  7 00:01:46 node-1 kernel: [   37.061671] type=1400 audit(1475798506.134:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8535 comm="apparmor_parser"
Oct  7 00:01:46 node-1 kernel: [   37.065256] type=1400 audit(1475798506.138:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8534 comm="apparmor_parser"
Oct  7 00:01:46 node-1 kernel: [   37.065262] type=1400 audit(1475798506.138:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Oct  7 00:01:46 node-1 kernel: [   37.065265] type=1400 audit(1475798506.138:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Oct  7 00:01:46 node-1 kernel: [   37.065497] type=1400 audit(1475798506.138:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Oct  7 00:01:46 node-1 kernel: [   37.065499] type=1400 audit(1475798506.138:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Oct  7 00:01:46 node-1 kernel: [   37.065622] type=1400 audit(1475798506.138:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Oct  7 00:01:46 node-1 kernel: [   37.128625] type=1400 audit(1475798506.202:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8537 comm="apparmor_parser"
Oct  7 00:01:46 node-1 cron[8576]: (CRON) INFO (pidfile fd = 3)
Oct  7 00:01:46 node-1 anacron[8611]: Anacron 2.3 started on 2016-10-07
Oct  7 00:01:46 node-1 cron[8614]: (CRON) STARTUP (fork ok)
Oct  7 00:01:46 node-1 anacron[8611]: Will run job `cron.daily' in 5 min.
Oct  7 00:01:46 node-1 anacron[8611]: Will run job `cron.weekly' in 10 min.
Oct  7 00:01:46 node-1 anacron[8611]: Will run job `cron.monthly' in 15 min.
Oct  7 00:01:46 node-1 anacron[8611]: Jobs will be executed sequentially
Oct  7 00:01:46 node-1 multipathd: path checkers start up
Oct  7 00:01:46 node-1 cron[8614]: (CRON) INFO (Running @reboot jobs)
Oct  7 00:01:46 node-1 postfix/master[8754]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  7 00:01:49 node-1 puppet-agent[8940]: Reopening log files
Oct  7 00:01:50 node-1 puppet-agent[8940]: Could not request certificate: Connection refused - connect(2)
Oct  7 00:02:01 node-1 CRON[8971]: (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")
Oct  7 00:02:05 node-1 puppet-user[9030]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  7 00:02:05 node-1 puppet-user[9030]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct  7 00:02:06 node-1 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  7 00:02:06 node-1 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  7 00:02:06 node-1 puppet-user[9030]: Finished catalog run in 1.04 seconds
Oct  7 00:02:08 node-1 multipathd: uevent trigger error
Oct  7 00:02:08 node-1 puppet-user[9465]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  7 00:02:08 node-1 puppet-user[9465]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct  7 00:02:08 node-1 puppet-user[9465]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  7 00:02:08 node-1 puppet-user[9465]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  7 00:02:08 node-1 puppet-user[9465]: (/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"]'
Oct  7 00:02:08 node-1 puppet-user[9465]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  7 00:02:08 node-1 puppet-user[9465]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  7 00:02:08 node-1 puppet-user[9465]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  7 00:02:08 node-1 puppet-user[9465]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  7 00:02:08 node-1 puppet-user[9465]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  7 00:02:08 node-1 puppet-user[9465]: Finished catalog run in 0.08 seconds
Oct  7 00:02:09 node-1 puppet-user[9930]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  7 00:02:09 node-1 puppet-user[9930]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct  7 00:02:10 node-1 puppet-user[9930]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  7 00:02:10 node-1 puppet-user[9930]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  7 00:02:10 node-1 puppet-user[9930]: Finished catalog run in 0.02 seconds
Oct  7 00:02:11 node-1 puppet-user[10397]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  7 00:02:11 node-1 puppet-user[10397]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct  7 00:02:12 node-1 puppet-user[10397]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  7 00:02:12 node-1 puppet-user[10397]: Finished catalog run in 0.04 seconds
Oct  7 00:02:13 node-1 puppet-user[10853]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  7 00:02:13 node-1 puppet-user[10853]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Oct  7 00:02:13 node-1 puppet-user[10853]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  7 00:02:14 node-1 puppet-user[10853]: (/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
Oct  7 00:02:14 node-1 puppet-user[10853]: Finished catalog run in 0.48 seconds
Oct  7 00:02:14 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  7 00:02:14 node-1 nailgun-agent: D, [2016-10-07T00:02:01.569682 #8974] DEBUG -- : Sleep for 13 seconds before sending request
Oct  7 00:02:14 node-1 nailgun-agent: I, [2016-10-07T00:02:14.584086 #8974]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  7 00:02:14 node-1 nailgun-agent: D, [2016-10-07T00:02:14.971155 #8974] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct  7 00:02:15 node-1 puppet-user[11456]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  7 00:02:15 node-1 puppet-user[11456]: Compiled catalog for node-1.domain.tld in environment production in 0.25 seconds
Oct  7 00:02:15 node-1 puppet-user[11456]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  7 00:02:15 node-1 puppet-user[11456]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  7 00:02:15 node-1 puppet-user[11456]: (/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
Oct  7 00:02:15 node-1 puppet-user[11456]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  7 00:02:15 node-1 puppet-user[11456]: Finished catalog run in 0.25 seconds
Oct  7 00:02:17 node-1 puppet-user[12075]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  7 00:02:17 node-1 puppet-user[12075]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Oct  7 00:02:17 node-1 puppet-user[12075]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  7 00:02:17 node-1 kernel: [   68.668982] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  7 00:02:17 node-1 kernel: [   68.669031] 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.
Oct  7 00:02:17 node-1 puppet-user[12075]: (/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'
Oct  7 00:02:17 node-1 puppet-user[12075]: Finished catalog run in 0.06 seconds
Oct  7 00:02:19 node-1 puppet-user[12531]: (Scope(Class[main])) MODULAR: sync_time
Oct  7 00:02:19 node-1 puppet-user[12531]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct  7 00:02:19 node-1 ntpdate[12960]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct  7 00:02:25 node-1 ntpdate[12960]: adjust time server 10.20.0.2 offset -0.010098 sec
Oct  7 00:02:25 node-1 puppet-user[12531]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  7 00:02:25 node-1 puppet-user[12531]: Finished catalog run in 6.17 seconds
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.887699 #8974] DEBUG -- : Trying to find block devices
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.887787 #8974] DEBUG -- : Found block device: sda
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.887828 #8974] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.887852 #8974] DEBUG -- : Trying to get list of physical devices
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.887980 #8974] DEBUG -- : Getting udev properties for device: sda
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.889723 #8974] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Oct  7 00:02:26 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1476", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.889748 #8974] DEBUG -- : Trying to find out if device sda is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.889815 #8974] DEBUG -- : Device sda removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.889830 #8974] DEBUG -- : Device sda seems to be appropriate
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.890270 #8974] DEBUG -- : Getting udev properties for device: dm-0
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.891851 #8974] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-OaRdXqVvfm00dEAakI9NOSqVDF4c67FCDKIU2HmX89TIGvptMgdItM3Rm7kJ3xO1 /dev/disk/by-uuid/3263a591-3733-41e8-b497-dd55b518d800 /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-OaRdXqVvfm00dEAakI9NOSqVDF4c67FCDKIU2HmX89TIGvptMgdItM3Rm7kJ3xO1", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3263a591-3733-41e8-b497-dd55b518d800", "ID_FS_UUID_ENC"=>"3263a591-3733-41e8-b497-dd55b518d800", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64192", "nomdmonddf"=>"1", "nomd
Oct  7 00:02:26 node-1 nailgun-agent: monisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.891880 #8974] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.891945 #8974] DEBUG -- : Device dm-0 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.891959 #8974] DEBUG -- : Device dm-0 seems to be appropriate
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.891973 #8974] DEBUG -- : Getting udev properties for device: dm-1
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.893518 #8974] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-KZYzDTQDyMAv0RC62VDHIoNg55CvX0ZSIauC76KIPWzaJMeKLwQ89fjXQRvd7sqy /dev/disk/by-uuid/2335135a-882f-4ebb-8989-1019a36994fb /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-KZYzDTQDyMAv0RC62VDHIoNg55CvX0ZSIauC76KIPWzaJMeKLwQ89fjXQRvd7sqy", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2335135a-882f-4ebb-8989-1019a36994fb", "ID_FS_UUID_ENC"=>"2335135a-882f-4ebb-8989-1019a36994fb", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80
Oct  7 00:02:26 node-1 nailgun-agent: 253", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.893544 #8974] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.893574 #8974] DEBUG -- : Device dm-1 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.893587 #8974] DEBUG -- : Device dm-1 seems to be appropriate
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.893601 #8974] DEBUG -- : Getting udev properties for device: dm-2
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.895084 #8974] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-doenM9VjnQEHvThN9yusteyOC8Ulz2TixN40ahgPAFoj7W0fG5mCDoyXeZdUR4vg /dev/disk/by-uuid/cb64656c-6d22-45d5-aab3-4f000d2b77c0 /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-doenM9VjnQEHvThN9yusteyOC8Ulz2TixN40ahgPAFoj7W0fG5mCDoyXeZdUR4vg", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cb64656c-6d22-45d5-aab3-4f000d2b77c0", "ID_FS_UUID_ENC"=>"cb64656c-6d22-45d5-aab3-4f000d2b77c0", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85344", "nomdmond
Oct  7 00:02:26 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.895110 #8974] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.895171 #8974] DEBUG -- : Device dm-2 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.895184 #8974] DEBUG -- : Device dm-2 seems to be appropriate
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.895198 #8974] DEBUG -- : Getting udev properties for device: dm-3
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.896760 #8974] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-WrzkIti5FBkjXteRsO1FoxTBTTjkT2077HpCM8z3edNGcJJvbnYdAUIMqaWXHYOf /dev/disk/by-uuid/35444bfa-4e50-4c5d-a04d-c53c6ca43699 /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-WrzkIti5FBkjXteRsO1FoxTBTTjkT2077HpCM8z3edNGcJJvbnYdAUIMqaWXHYOf", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"35444bfa-4e50-4c5d-a04d-c53c6ca43699", "ID_FS_UUID_ENC"=>"35444bfa-4e50-4c5d-a04d-c53c6ca43699", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83018", "nomdmonddf"=>"1", 
Oct  7 00:02:26 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.896797 #8974] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.896844 #8974] DEBUG -- : Device dm-3 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.896857 #8974] DEBUG -- : Device dm-3 seems to be appropriate
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.896870 #8974] DEBUG -- : Getting udev properties for device: dm-4
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.898459 #8974] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-1grcueSjpwsEDqk8sbX64VOQkEuF7WkrhW7u1wfyvAPjoGjJt00wqhVenI62h3Td /dev/disk/by-uuid/886bda69-7979-44e6-93aa-44ec4eb07b11 /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-1grcueSjpwsEDqk8sbX64VOQkEuF7WkrhW7u1wfyvAPjoGjJt00wqhVenI62h3Td", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"886bda69-7979-44e6-93aa-44ec4eb07b11", "ID_FS_UUID_ENC"=>"886bda69-7979-44e6-93aa-44ec4eb07b11", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76753", "nomdmonddf"=>"1", "nomd
Oct  7 00:02:26 node-1 nailgun-agent: monisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.898483 #8974] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.898521 #8974] DEBUG -- : Device dm-4 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.898534 #8974] DEBUG -- : Device dm-4 seems to be appropriate
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.898548 #8974] DEBUG -- : Getting udev properties for device: dm-5
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.900060 #8974] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-1grcueSjpwsEDqk8sbX64VOQkEuF7WkroQE8fLUIMg5eT3TR0TsDjfsy3DE4C0vc /dev/disk/by-uuid/250d5e6b-91d3-4c9c-a0bf-f26a51215de0 /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-1grcueSjpwsEDqk8sbX64VOQkEuF7WkroQE8fLUIMg5eT3TR0TsDjfsy3DE4C0vc", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"250d5e6b-91d3-4c9c-a0bf-f26a51215de0", "ID_FS_UUID_ENC"=>"250d5e6b-91d3-4c9c-a0bf-f26a51215de0", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77055", "nomdmonddf"=>"1", "nomdmonisw"
Oct  7 00:02:26 node-1 nailgun-agent: =>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.900083 #8974] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.900110 #8974] DEBUG -- : Device dm-5 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.900133 #8974] DEBUG -- : Device dm-5 seems to be appropriate
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.900146 #8974] DEBUG -- : Getting udev properties for device: ram0
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.901592 #8974] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78397", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.901614 #8974] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.901645 #8974] DEBUG -- : Device ram0 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.901664 #8974] DEBUG -- : Getting udev properties for device: ram1
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.903045 #8974] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78405", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.903068 #8974] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.903113 #8974] DEBUG -- : Device ram1 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.903130 #8974] DEBUG -- : Getting udev properties for device: ram2
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.904527 #8974] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78460", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.904552 #8974] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.904591 #8974] DEBUG -- : Device ram2 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.904623 #8974] DEBUG -- : Getting udev properties for device: ram3
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.906011 #8974] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78468", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.906037 #8974] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.906077 #8974] DEBUG -- : Device ram3 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.906106 #8974] DEBUG -- : Getting udev properties for device: ram4
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.907450 #8974] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78476", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.907475 #8974] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.907516 #8974] DEBUG -- : Device ram4 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.907536 #8974] DEBUG -- : Getting udev properties for device: ram5
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.908909 #8974] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78482", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.908957 #8974] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.908995 #8974] DEBUG -- : Device ram5 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.909015 #8974] DEBUG -- : Getting udev properties for device: ram6
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.910381 #8974] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78492", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.910408 #8974] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.910454 #8974] DEBUG -- : Device ram6 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.910481 #8974] DEBUG -- : Getting udev properties for device: ram7
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.911865 #8974] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78504", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.911894 #8974] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.911924 #8974] DEBUG -- : Device ram7 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.911972 #8974] DEBUG -- : Getting udev properties for device: ram8
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.913314 #8974] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78512", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.913346 #8974] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.913375 #8974] DEBUG -- : Device ram8 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.913404 #8974] DEBUG -- : Getting udev properties for device: ram9
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.914802 #8974] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78522", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.914827 #8974] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.914867 #8974] DEBUG -- : Device ram9 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.914886 #8974] DEBUG -- : Getting udev properties for device: loop0
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.916242 #8974] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78330", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.916267 #8974] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.916300 #8974] DEBUG -- : Device loop0 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.916334 #8974] DEBUG -- : Getting udev properties for device: loop1
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.917694 #8974] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78337", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.917726 #8974] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.917766 #8974] DEBUG -- : Device loop1 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.917783 #8974] DEBUG -- : Getting udev properties for device: loop2
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.924444 #8974] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78343", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.924474 #8974] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.924519 #8974] DEBUG -- : Device loop2 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.924538 #8974] DEBUG -- : Getting udev properties for device: loop3
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.926117 #8974] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78352", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.926180 #8974] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.926224 #8974] DEBUG -- : Device loop3 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.926242 #8974] DEBUG -- : Getting udev properties for device: loop4
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.927638 #8974] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78366", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.927663 #8974] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.927694 #8974] DEBUG -- : Device loop4 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.927748 #8974] DEBUG -- : Getting udev properties for device: loop5
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.929091 #8974] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78375", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.929117 #8974] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.929149 #8974] DEBUG -- : Device loop5 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.929168 #8974] DEBUG -- : Getting udev properties for device: loop6
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.930536 #8974] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78383", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.930557 #8974] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.930588 #8974] DEBUG -- : Device loop6 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.930606 #8974] DEBUG -- : Getting udev properties for device: loop7
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.931971 #8974] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78390", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.931992 #8974] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.932029 #8974] DEBUG -- : Device loop7 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.932045 #8974] DEBUG -- : Getting udev properties for device: ram10
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.933408 #8974] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78414", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.933429 #8974] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.933467 #8974] DEBUG -- : Device ram10 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.933483 #8974] DEBUG -- : Getting udev properties for device: ram11
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.934841 #8974] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78422", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.934861 #8974] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.934896 #8974] DEBUG -- : Device ram11 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.934912 #8974] DEBUG -- : Getting udev properties for device: ram12
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.936260 #8974] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78429", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.936281 #8974] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.936311 #8974] DEBUG -- : Device ram12 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.936328 #8974] DEBUG -- : Getting udev properties for device: ram13
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.937662 #8974] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78436", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.937682 #8974] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.937761 #8974] DEBUG -- : Device ram13 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.937777 #8974] DEBUG -- : Getting udev properties for device: ram14
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.939105 #8974] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78444", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.939125 #8974] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.939154 #8974] DEBUG -- : Device ram14 removable parameter: "0"
Oct  7 00:02:26 node-1 nailgun-agent: D, [2016-10-07T00:02:26.939194 #8974] DEBUG -- : Getting udev properties for device: ram15
Oct  7 00:02:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940506 #8974] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78452", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940528 #8974] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940557 #8974] DEBUG -- : Device ram15 removable parameter: "0"
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940591 #8974] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940604 #8974] DEBUG -- : Block device seems to be physical data storage: sda
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940665 #8974] DEBUG -- : Found block device: dm-0
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940680 #8974] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940693 #8974] DEBUG -- : Found block device: dm-1
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940704 #8974] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940727 #8974] DEBUG -- : Found block device: dm-2
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940738 #8974] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940746 #8974] DEBUG -- : Found block device: dm-3
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940757 #8974] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940765 #8974] DEBUG -- : Found block device: dm-4
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940774 #8974] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940814 #8974] DEBUG -- : Found block device: dm-5
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940825 #8974] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940834 #8974] DEBUG -- : Found block device: ram0
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940842 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940850 #8974] DEBUG -- : Found block device: ram1
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940859 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940866 #8974] DEBUG -- : Found block device: ram2
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940875 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940883 #8974] DEBUG -- : Found block device: ram3
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940915 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940925 #8974] DEBUG -- : Found block device: ram4
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940936 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940944 #8974] DEBUG -- : Found block device: ram5
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940954 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940961 #8974] DEBUG -- : Found block device: ram6
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940971 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940979 #8974] DEBUG -- : Found block device: ram7
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940988 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.940995 #8974] DEBUG -- : Found block device: ram8
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941031 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941040 #8974] DEBUG -- : Found block device: ram9
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941051 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941059 #8974] DEBUG -- : Found block device: loop0
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941068 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941076 #8974] DEBUG -- : Found block device: loop1
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941086 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941094 #8974] DEBUG -- : Found block device: loop2
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941105 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941113 #8974] DEBUG -- : Found block device: loop3
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941123 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941152 #8974] DEBUG -- : Found block device: loop4
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941161 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941170 #8974] DEBUG -- : Found block device: loop5
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941179 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941187 #8974] DEBUG -- : Found block device: loop6
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941196 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941204 #8974] DEBUG -- : Found block device: loop7
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941213 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941221 #8974] DEBUG -- : Found block device: ram10
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941231 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941260 #8974] DEBUG -- : Found block device: ram11
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941270 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941278 #8974] DEBUG -- : Found block device: ram12
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941288 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941295 #8974] DEBUG -- : Found block device: ram13
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941305 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941313 #8974] DEBUG -- : Found block device: ram14
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941323 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941331 #8974] DEBUG -- : Found block device: ram15
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941341 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:26.941392 #8974] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:27.032540 #8974] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct  7 00:02:27 node-1 nailgun-agent: D, [2016-10-07T00:02:27.032587 #8974] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct  7 00:02:31 node-1 puppet-user[13512]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  7 00:02:31 node-1 puppet-user[13512]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct  7 00:02:31 node-1 puppet-user[13512]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  7 00:02:31 node-1 puppet-user[13512]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Oct  7 00:02:31 node-1 puppet-user[13512]: Finished catalog run in 0.07 seconds
Oct  7 00:02:33 node-1 puppet-user[13974]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  7 00:02:33 node-1 puppet-user[13974]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Oct  7 00:02:33 node-1 puppet-user[13974]: (/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
Oct  7 00:02:33 node-1 puppet-user[13974]: (/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
Oct  7 00:02:33 node-1 puppet-user[13974]: (/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
Oct  7 00:02:33 node-1 puppet-user[13974]: (/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
Oct  7 00:02:33 node-1 puppet-user[13974]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  7 00:02:33 node-1 puppet-user[13974]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct  7 00:02:33 node-1 puppet-user[13974]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  7 00:02:33 node-1 puppet-user[13974]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct  7 00:02:34 node-1 puppet-user[13974]: (/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
Oct  7 00:02:34 node-1 puppet-user[13974]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct  7 00:02:34 node-1 puppet-user[13974]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  7 00:02:34 node-1 puppet-user[13974]: Finished catalog run in 0.78 seconds
Oct  7 00:02:36 node-1 puppet-user[14483]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  7 00:02:36 node-1 puppet-user[14483]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct  7 00:02:39 node-1 kernel: [   89.877752] init: plymouth-upstart-bridge main process ended, respawning
Oct  7 00:02:39 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984585 #8974] DEBUG -- : Trying to find block devices
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984655 #8974] DEBUG -- : Found block device: sda
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984685 #8974] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984706 #8974] DEBUG -- : Block device seems to be physical data storage: sda
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984762 #8974] DEBUG -- : Found block device: dm-0
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984775 #8974] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984786 #8974] DEBUG -- : Found block device: dm-1
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984796 #8974] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984804 #8974] DEBUG -- : Found block device: dm-2
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984814 #8974] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984823 #8974] DEBUG -- : Found block device: dm-3
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984832 #8974] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984841 #8974] DEBUG -- : Found block device: dm-4
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984850 #8974] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984878 #8974] DEBUG -- : Found block device: dm-5
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984889 #8974] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984898 #8974] DEBUG -- : Found block device: ram0
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984907 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984915 #8974] DEBUG -- : Found block device: ram1
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984924 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984933 #8974] DEBUG -- : Found block device: ram2
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984943 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984968 #8974] DEBUG -- : Found block device: ram3
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984978 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984987 #8974] DEBUG -- : Found block device: ram4
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.984996 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985004 #8974] DEBUG -- : Found block device: ram5
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985014 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985021 #8974] DEBUG -- : Found block device: ram6
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985030 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985058 #8974] DEBUG -- : Found block device: ram7
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985069 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985077 #8974] DEBUG -- : Found block device: ram8
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985086 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985094 #8974] DEBUG -- : Found block device: ram9
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985103 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985111 #8974] DEBUG -- : Found block device: loop0
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985137 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985146 #8974] DEBUG -- : Found block device: loop1
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985156 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985163 #8974] DEBUG -- : Found block device: loop2
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985172 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985181 #8974] DEBUG -- : Found block device: loop3
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985190 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985213 #8974] DEBUG -- : Found block device: loop4
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985223 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985231 #8974] DEBUG -- : Found block device: loop5
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985240 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985249 #8974] DEBUG -- : Found block device: loop6
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985258 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985266 #8974] DEBUG -- : Found block device: loop7
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985274 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985294 #8974] DEBUG -- : Found block device: ram10
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985323 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985332 #8974] DEBUG -- : Found block device: ram11
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985341 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985350 #8974] DEBUG -- : Found block device: ram12
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985359 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985367 #8974] DEBUG -- : Found block device: ram13
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985376 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985384 #8974] DEBUG -- : Found block device: ram14
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985393 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985401 #8974] DEBUG -- : Found block device: ram15
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985444 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:38.985480 #8974] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct  7 00:02:39 node-1 nailgun-agent: D, [2016-10-07T00:02:39.193296 #8974] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct  7 00:02:39 node-1 nailgun-agent: I, [2016-10-07T00:02:39.193478 #8974]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct  7 00:02:39 node-1 puppet-agent[8940]: Could not run: SIGTERM
Oct  7 00:02:39 node-1 kernel: [   90.169460] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  7 00:02:39 node-1 ec2: 
Oct  7 00:02:39 node-1 ec2: #############################################################
Oct  7 00:02:39 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  7 00:02:39 node-1 ec2: 1024 79:1a:1c:28:09:11:b9:1e:d6:b7:ee:31:0f:56:97:be  root@node-1.domain.tld (DSA)
Oct  7 00:02:39 node-1 ec2: 256 d9:88:0d:8c:47:6a:46:03:5f:b8:13:7c:77:71:dd:84  root@node-1.domain.tld (ECDSA)
Oct  7 00:02:39 node-1 ec2: 256 ec:03:e9:1b:29:40:03:d8:cf:08:80:06:65:0b:9b:fc  root@node-1.domain.tld (ED25519)
Oct  7 00:02:39 node-1 ec2: 2048 3b:76:0b:4d:dc:50:dd:7f:64:5d:75:e3:f3:6e:f8:ec  root@node-1.domain.tld (RSA)
Oct  7 00:02:39 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  7 00:02:39 node-1 ec2: #############################################################
Oct  7 00:02:39 node-1 puppet-user[14483]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  7 00:03:01 node-1 CRON[16876]: (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")
Oct  7 00:03:06 node-1 puppet-user[14483]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  7 00:03:06 node-1 puppet-user[14483]: Finished catalog run in 29.77 seconds
Oct  7 00:03:08 node-1 puppet-user[17182]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  7 00:03:08 node-1 puppet-user[17182]: Compiled catalog for node-1.domain.tld in environment production in 0.53 seconds
Oct  7 00:03:08 node-1 puppet-user[17182]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  7 00:03:08 node-1 puppet-user[17182]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  7 00:03:08 node-1 puppet-user[17182]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  7 00:03:09 node-1 puppet-user[17182]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  7 00:03:09 node-1 puppet-user[17182]: Finished catalog run in 0.08 seconds
Oct  7 00:03:10 node-1 puppet-user[17639]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  7 00:03:11 node-1 puppet-user[17639]: Compiled catalog for node-1.domain.tld in environment production in 0.88 seconds
Oct  7 00:03:11 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  7 00:03:11 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  7 00:03:11 node-1 crontab[18079]: (root) LIST (root)
Oct  7 00:03:11 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  7 00:03:11 node-1 crontab[18082]: (root) REPLACE (root)
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  7 00:03:13 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/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
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  7 00:03:14 node-1 puppet-user[17639]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct  7 00:03:14 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  7 00:03:14 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  7 00:03:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:32 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:03:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:04:29 node-1 ntpdate[30060]: no servers can be used, exiting
<27>Oct  7 00:05:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:05:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:23 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  7 00:06:23 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  7 00:06:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  7 00:06:29 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  7 00:06:34 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  7 00:06:40 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  7 00:06:40 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  7 00:06:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:06:49 node-1 ntpdate[15942]: the NTP socket is in use, exiting
<27>Oct  7 00:06:49 node-1 ntpdate[16001]: the NTP socket is in use, exiting
<27>Oct  7 00:07:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:06 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:08 node-1 haproxy[19763]: 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>Oct  7 00:07:09 node-1 haproxy[19767]: 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>Oct  7 00:07:09 node-1 haproxy[19767]: 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>Oct  7 00:07:09 node-1 haproxy[19767]: proxy mysqld has no server available!
<27>Oct  7 00:07:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:15 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:18 node-1 haproxy[22376]: 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>Oct  7 00:07:18 node-1 haproxy[22376]: 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>Oct  7 00:07:18 node-1 haproxy[22376]: 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>Oct  7 00:07:18 node-1 haproxy[22376]: proxy mysqld has no server available!
<129>Oct  7 00:07:18 node-1 haproxy[22376]: 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>Oct  7 00:07:19 node-1 haproxy[22380]: 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>Oct  7 00:07:19 node-1 haproxy[22380]: 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>Oct  7 00:07:19 node-1 haproxy[22380]: proxy object-storage has no server available!
<27>Oct  7 00:07:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:21 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:23 node-1 haproxy[23862]: 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>Oct  7 00:07:23 node-1 haproxy[23862]: 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>Oct  7 00:07:23 node-1 haproxy[23862]: 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>Oct  7 00:07:23 node-1 haproxy[23862]: proxy neutron has no server available!
<129>Oct  7 00:07:24 node-1 haproxy[23866]: 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>Oct  7 00:07:24 node-1 haproxy[23866]: 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>Oct  7 00:07:24 node-1 haproxy[23866]: 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>Oct  7 00:07:24 node-1 haproxy[23866]: proxy mysqld has no server available!
<129>Oct  7 00:07:24 node-1 haproxy[23866]: 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>Oct  7 00:07:24 node-1 haproxy[23866]: 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>Oct  7 00:07:24 node-1 haproxy[23866]: 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>Oct  7 00:07:24 node-1 haproxy[23866]: proxy object-storage has no server available!
<27>Oct  7 00:07:26 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:26 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:26 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:26 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:26 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:26 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:28 node-1 haproxy[25248]: 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>Oct  7 00:07:29 node-1 haproxy[25252]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:07:29 node-1 haproxy[25252]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:29 node-1 haproxy[25252]: proxy keystone-1 has no server available!
<129>Oct  7 00:07:29 node-1 haproxy[25252]: 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>Oct  7 00:07:29 node-1 haproxy[25252]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:07:29 node-1 haproxy[25252]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:29 node-1 haproxy[25252]: proxy keystone-2 has no server available!
<129>Oct  7 00:07:29 node-1 haproxy[25252]: 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>Oct  7 00:07:29 node-1 haproxy[25252]: 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>Oct  7 00:07:29 node-1 haproxy[25252]: 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>Oct  7 00:07:29 node-1 haproxy[25252]: proxy neutron has no server available!
<129>Oct  7 00:07:29 node-1 haproxy[25252]: 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>Oct  7 00:07:30 node-1 haproxy[25252]: 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>Oct  7 00:07:30 node-1 haproxy[25252]: 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>Oct  7 00:07:30 node-1 haproxy[25252]: proxy mysqld has no server available!
<129>Oct  7 00:07:30 node-1 haproxy[25252]: 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>Oct  7 00:07:30 node-1 haproxy[25252]: 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>Oct  7 00:07:30 node-1 haproxy[25252]: 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>Oct  7 00:07:30 node-1 haproxy[25252]: proxy object-storage has no server available!
<27>Oct  7 00:07:32 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:32 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:32 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:32 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:32 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:32 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:34 node-1 haproxy[26799]: 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>Oct  7 00:07:34 node-1 haproxy[26799]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:07:34 node-1 haproxy[26799]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:34 node-1 haproxy[26799]: proxy keystone-1 has no server available!
<129>Oct  7 00:07:34 node-1 haproxy[26799]: 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>Oct  7 00:07:34 node-1 haproxy[26799]: 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>Oct  7 00:07:34 node-1 haproxy[26799]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:34 node-1 haproxy[26799]: proxy keystone-2 has no server available!
<129>Oct  7 00:07:34 node-1 haproxy[26799]: 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>Oct  7 00:07:34 node-1 haproxy[26799]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: proxy neutron has no server available!
<129>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: proxy mysqld has no server available!
<129>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: proxy object-storage has no server available!
<129>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: 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>Oct  7 00:07:35 node-1 haproxy[26803]: proxy aodh has no server available!
<27>Oct  7 00:07:37 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:37 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:37 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:37 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:37 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:39 node-1 haproxy[28182]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:07:40 node-1 haproxy[28186]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:40 node-1 haproxy[28186]: proxy keystone-1 has no server available!
<129>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: proxy keystone-2 has no server available!
<129>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: proxy neutron has no server available!
<129>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:40 node-1 haproxy[28186]: proxy mysqld has no server available!
<129>Oct  7 00:07:40 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: proxy object-storage has no server available!
<129>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: proxy aodh has no server available!
<129>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: 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>Oct  7 00:07:41 node-1 haproxy[28186]: proxy ceilometer has no server available!
<27>Oct  7 00:07:43 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:43 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:43 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:43 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:43 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:43 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:45 node-1 haproxy[29543]: 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>Oct  7 00:07:45 node-1 haproxy[29543]: 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>Oct  7 00:07:45 node-1 haproxy[29543]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:45 node-1 haproxy[29543]: proxy keystone-1 has no server available!
<129>Oct  7 00:07:45 node-1 haproxy[29543]: 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>Oct  7 00:07:45 node-1 haproxy[29543]: 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>Oct  7 00:07:45 node-1 haproxy[29543]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:45 node-1 haproxy[29543]: proxy keystone-2 has no server available!
<129>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: proxy neutron has no server available!
<129>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: proxy mysqld has no server available!
<129>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: proxy object-storage has no server available!
<129>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: 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>Oct  7 00:07:46 node-1 haproxy[29547]: proxy aodh has no server available!
<129>Oct  7 00:07:47 node-1 haproxy[29547]: 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>Oct  7 00:07:47 node-1 haproxy[29547]: 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>Oct  7 00:07:47 node-1 haproxy[29547]: 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>Oct  7 00:07:47 node-1 haproxy[29547]: proxy ceilometer has no server available!
<27>Oct  7 00:07:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:48 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:50 node-1 haproxy[30896]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:07:51 node-1 haproxy[30900]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:51 node-1 haproxy[30900]: proxy keystone-1 has no server available!
<129>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  7 00:07:51 node-1 haproxy[30900]: proxy keystone-2 has no server available!
<129>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: proxy neutron has no server available!
<129>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: 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>Oct  7 00:07:51 node-1 haproxy[30900]: proxy mysqld has no server available!
<129>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: proxy object-storage has no server available!
<129>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: proxy aodh has no server available!
<129>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: 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>Oct  7 00:07:52 node-1 haproxy[30900]: proxy ceilometer has no server available!
<27>Oct  7 00:07:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:53 node-1 multipathd: uevent trigger error
<129>Oct  7 00:07:56 node-1 haproxy[32322]: 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>Oct  7 00:07:56 node-1 haproxy[32322]: 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>Oct  7 00:07:56 node-1 haproxy[32322]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:07:56 node-1 haproxy[32322]: 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>Oct  7 00:07:56 node-1 haproxy[32322]: proxy keystone-1 has no server available!
<129>Oct  7 00:07:56 node-1 haproxy[32322]: 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>Oct  7 00:07:56 node-1 haproxy[32322]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: proxy keystone-2 has no server available!
<129>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: proxy glance-api has no server available!
<129>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: proxy glance-glare has no server available!
<129>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: proxy neutron has no server available!
<129>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: proxy glance-registry has no server available!
<129>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: proxy mysqld has no server available!
<129>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:57 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: proxy object-storage has no server available!
<129>Oct  7 00:07:58 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: proxy aodh has no server available!
<129>Oct  7 00:07:58 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: 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>Oct  7 00:07:58 node-1 haproxy[32329]: proxy ceilometer has no server available!
<27>Oct  7 00:07:59 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:59 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:59 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:59 node-1 multipathd: uevent trigger error
<27>Oct  7 00:07:59 node-1 multipathd: uevent trigger error
<129>Oct  7 00:08:02 node-1 haproxy[1305]: 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>Oct  7 00:08:02 node-1 haproxy[1305]: 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>Oct  7 00:08:02 node-1 haproxy[1305]: 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>Oct  7 00:08:02 node-1 haproxy[1305]: 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>Oct  7 00:08:02 node-1 haproxy[1305]: proxy keystone-1 has no server available!
<129>Oct  7 00:08:02 node-1 haproxy[1305]: 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>Oct  7 00:08:02 node-1 haproxy[1305]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  7 00:08:02 node-1 haproxy[1305]: 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>Oct  7 00:08:02 node-1 haproxy[1305]: proxy keystone-2 has no server available!
<129>Oct  7 00:08:02 node-1 haproxy[1305]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: proxy nova-api has no server available!
<129>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: proxy nova-metadata-api has no server available!
<129>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: proxy glance-api has no server available!
<129>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: proxy glance-glare has no server available!
<129>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: proxy neutron has no server available!
<129>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: proxy glance-registry has no server available!
<129>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: proxy mysqld has no server available!
<129>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:03 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: proxy object-storage has no server available!
<129>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: proxy aodh has no server available!
<129>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: proxy ceilometer has no server available!
<129>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: 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>Oct  7 00:08:04 node-1 haproxy[1309]: proxy nova-novncproxy has no server available!
<27>Oct  7 00:08:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:06 node-1 multipathd: uevent trigger error
<129>Oct  7 00:08:08 node-1 haproxy[2650]: 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>Oct  7 00:08:08 node-1 haproxy[2650]: 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>Oct  7 00:08:08 node-1 haproxy[2650]: 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>Oct  7 00:08:08 node-1 haproxy[2650]: 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>Oct  7 00:08:08 node-1 haproxy[2650]: proxy keystone-1 has no server available!
<129>Oct  7 00:08:08 node-1 haproxy[2650]: 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>Oct  7 00:08:08 node-1 haproxy[2650]: 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>Oct  7 00:08:08 node-1 haproxy[2650]: 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>Oct  7 00:08:08 node-1 haproxy[2650]: proxy keystone-2 has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: proxy nova-api has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: proxy nova-metadata-api has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: proxy cinder-api has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: proxy glance-api has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: proxy glance-glare has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: proxy neutron has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: proxy glance-registry has no server available!
<129>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:09 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: proxy mysqld has no server available!
<129>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: proxy object-storage has no server available!
<129>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: proxy aodh has no server available!
<129>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: proxy ceilometer has no server available!
<129>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: 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>Oct  7 00:08:10 node-1 haproxy[2654]: proxy nova-novncproxy has no server available!
<27>Oct  7 00:08:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:11 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:11 node-1 multipathd: uevent trigger error
<129>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: proxy keystone-1 has no server available!
<129>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: proxy keystone-2 has no server available!
<129>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:14 node-1 haproxy[4072]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy nova-api has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy nova-metadata-api has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy cinder-api has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy glance-api has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy glance-glare has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy neutron has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy glance-registry has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy mysqld has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy object-storage has no server available!
<129>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: 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>Oct  7 00:08:15 node-1 haproxy[4078]: proxy aodh has no server available!
<129>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: proxy ceilometer has no server available!
<129>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: proxy heat-api has no server available!
<129>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: proxy heat-api-cfn has no server available!
<129>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: proxy heat-api-cloudwatch has no server available!
<129>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: 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>Oct  7 00:08:16 node-1 haproxy[4078]: proxy nova-novncproxy has no server available!
<27>Oct  7 00:08:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:08:28 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  7 00:08:52 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>Oct  7 00:08:54 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  7 00:09:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:09:36 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  7 00:09:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:09:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:09:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:09:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:09:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:09:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:20 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:20 node-1 multipathd: uevent trigger error
<43>Oct  7 00:12:35 node-1 apache2_error [Fri Oct 07 00:12:31.268004 2016] [mpm_event:notice] [pid 14667:tid 139901581051776] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  7 00:12:35 node-1 apache2_error [Fri Oct 07 00:12:31.268068 2016] [core:notice] [pid 14667:tid 139901581051776] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  7 00:12:35 node-1 apache2_error [Fri Oct 07 00:12:34.048751 2016] [mpm_event:notice] [pid 14667:tid 139901581051776] AH00491: caught SIGTERM, shutting down
<43>Oct  7 00:12:35 node-1 apache2_error [Fri Oct 07 00:12:35.133426 2016] [mpm_worker:notice] [pid 15031:tid 140317729302400] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  7 00:12:35 node-1 apache2_error [Fri Oct 07 00:12:35.133543 2016] [core:notice] [pid 15031:tid 140317729302400] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  7 00:12:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:12:39 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:39 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:39 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:39 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:39 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:39 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:42 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:42 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:43 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:43 node-1 multipathd: uevent trigger error
<27>Oct  7 00:12:43 node-1 multipathd: uevent trigger error
<43>Oct  7 00:13:45 node-1 apache2_error [Fri Oct 07 00:13:45.102423 2016] [mpm_worker:notice] [pid 15031:tid 140317729302400] AH00295: caught SIGTERM, shutting down
<43>Oct  7 00:13:45 node-1 apache2_error [Fri Oct 07 00:13:45.861016 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  7 00:13:45 node-1 apache2_error [Fri Oct 07 00:13:45.861064 2016] [core:notice] [pid 26990:tid 140311995737984] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  7 00:14:35 node-1 apache2_error [Fri Oct 07 00:14:29.721161 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  7 00:14:35 node-1 apache2_error [Fri Oct 07 00:14:29.918510 2016] [mpm_worker:warn] [pid 26990:tid 140311995737984] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  7 00:14:35 node-1 apache2_error [Fri Oct 07 00:14:29.922195 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  7 00:14:35 node-1 apache2_error [Fri Oct 07 00:14:29.922209 2016] [core:notice] [pid 26990:tid 140311995737984] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  7 00:15:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:15:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:15:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:16:15 node-1 multipathd: uevent trigger error
<27>Oct  7 00:17:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:17:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:17:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:17:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:17:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:17:04 node-1 multipathd: uevent trigger error
<27>Oct  7 00:18:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:18:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:18:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:18:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:18:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:18:12 node-1 multipathd: uevent trigger error
<27>Oct  7 00:18:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:19:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:41 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:41 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:41 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:41 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:41 node-1 multipathd: uevent trigger error
<27>Oct  7 00:19:41 node-1 multipathd: uevent trigger error
<27>Oct  7 00:21:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:22:02 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:02 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:02 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:02 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:02 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:02 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:16 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:16 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:16 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:16 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:16 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:16 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:27 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:27 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:27 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:27 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:27 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:27 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:22:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:23:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:23:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:23:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:23:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:23:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:23:34 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:24:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:24:50 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:22 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:27:30 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct  7 00:27:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:28:30 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:30 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:30 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:30 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:30 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:28:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:17 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:21 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:36 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:42 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:42 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:42 node-1 multipathd: uevent trigger error
<27>Oct  7 00:29:42 node-1 multipathd: uevent trigger error
<27>Oct  7 00:30:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:30:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:30:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:30:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:30:08 node-1 multipathd: uevent trigger error
<27>Oct  7 00:30:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  7 00:31:13 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:13 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:13 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:13 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:13 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:29 node-1 multipathd: uevent trigger error
<27>Oct  7 00:31:29 node-1 multipathd: uevent trigger error
<11>Oct  7 00:31:42 node-1 liberasurecode[72807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:42 node-1 liberasurecode[72807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:42 node-1 liberasurecode[72807]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:42 node-1 liberasurecode[72807]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:42 node-1 liberasurecode[72831]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:42 node-1 liberasurecode[72831]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:42 node-1 liberasurecode[72831]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:42 node-1 liberasurecode[72831]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:44 node-1 liberasurecode[73245]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:44 node-1 liberasurecode[73245]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:44 node-1 liberasurecode[73245]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:44 node-1 liberasurecode[73245]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73834]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73834]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73872]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73872]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73872]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73872]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73916]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73916]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73916]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:48 node-1 liberasurecode[73916]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73978]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73978]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73978]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73978]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73992]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73992]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73992]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[73992]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74004]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74004]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74004]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74004]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74018]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:49 node-1 liberasurecode[74018]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:58 node-1 liberasurecode[75337]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:58 node-1 liberasurecode[75337]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:58 node-1 liberasurecode[75337]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:31:58 node-1 liberasurecode[75337]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  7 00:32:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:32:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:32:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:32:06 node-1 multipathd: uevent trigger error
<27>Oct  7 00:32:06 node-1 multipathd: uevent trigger error
<43>Oct  7 00:32:57 node-1 apache2_error [Fri Oct 07 00:32:52.075596 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  7 00:32:57 node-1 apache2_error [Fri Oct 07 00:32:52.462248 2016] [mpm_worker:warn] [pid 26990:tid 140311995737984] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  7 00:32:57 node-1 apache2_error [Fri Oct 07 00:32:52.468520 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  7 00:32:57 node-1 apache2_error [Fri Oct 07 00:32:52.468544 2016] [core:notice] [pid 26990:tid 140311995737984] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  7 00:33:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:33 node-1 multipathd: uevent trigger error
<43>Oct  7 00:33:37 node-1 apache2_error [Fri Oct 07 00:33:29.376863 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  7 00:33:37 node-1 apache2_error [Fri Oct 07 00:33:30.887158 2016] [mpm_worker:warn] [pid 26990:tid 140311995737984] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  7 00:33:37 node-1 apache2_error [Fri Oct 07 00:33:30.897694 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  7 00:33:37 node-1 apache2_error [Fri Oct 07 00:33:30.897728 2016] [core:notice] [pid 26990:tid 140311995737984] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  7 00:33:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:33:49 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  7 00:34:17 node-1 apache2_error [Fri Oct 07 00:34:14.934315 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  7 00:34:17 node-1 apache2_error [Fri Oct 07 00:34:15.130107 2016] [mpm_worker:warn] [pid 26990:tid 140311995737984] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  7 00:34:17 node-1 apache2_error [Fri Oct 07 00:34:15.138379 2016] [mpm_worker:notice] [pid 26990:tid 140311995737984] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  7 00:34:17 node-1 apache2_error [Fri Oct 07 00:34:15.138406 2016] [core:notice] [pid 26990:tid 140311995737984] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  7 00:34:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:19 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:25 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:31 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:34:56 node-1 multipathd: uevent trigger error
<11>Oct  7 00:35:01 node-1 liberasurecode[108919]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:35:01 node-1 liberasurecode[108919]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:35:01 node-1 liberasurecode[108919]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:35:01 node-1 liberasurecode[108919]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  7 00:35:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:24 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  7 00:35:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:33 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:38 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:38 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:38 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:38 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:38 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:38 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:48 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:54 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:54 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:54 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:54 node-1 multipathd: uevent trigger error
<27>Oct  7 00:35:54 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:09 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:11 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  7 00:36:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:35 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:40 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:36:53 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:00 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:18 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:47 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:52 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:37:56 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:01 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:05 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:10 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:14 node-1 multipathd: uevent trigger error
<27>Oct  7 00:38:14 node-1 multipathd: uevent trigger error
<11>Oct  7 00:40:01 node-1 liberasurecode[170076]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:40:01 node-1 liberasurecode[170076]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:40:01 node-1 liberasurecode[170076]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  7 00:40:01 node-1 liberasurecode[170076]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
