Oct 19 08:36:53 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] start
Oct 19 08:36:53 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 19 08:36:53 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 19 08:36:53 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 19 08:36:53 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 19 08:36:53 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 19 08:36:53 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 19 08:36:53 node-1 kernel: [    0.000000] Linux version 3.13.0-98-generic (buildd@lgw01-45) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #145-Ubuntu SMP Sat Oct 8 20:13:07 UTC 2016 (Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39)
Oct 19 08:36:53 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=d29e9f03-d2a4-4797-ba7f-617d312250f1 nomdmonddf nomdmonisw
Oct 19 08:36:53 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 19 08:36:53 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 19 08:36:53 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 19 08:36:53 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 19 08:36:53 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 19 08:36:53 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 19 08:36:53 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 19 08:36:53 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 19 08:36:53 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 19 08:36:53 node-1 kernel: [    0.000000] No AGP bridge found
Oct 19 08:36:53 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 19 08:36:53 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 19 08:36:53 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 19 08:36:53 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 19 08:36:53 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 19 08:36:53 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 19 08:36:53 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 19 08:36:53 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 19 08:36:53 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 19 08:36:53 node-1 kernel: [    0.000000]   2 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000]   3 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000]   4 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000]   5 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000]   6 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000]   7 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000]   8 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000]   9 disabled
Oct 19 08:36:53 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 19 08:36:53 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 19 08:36:53 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 19 08:36:53 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 19 08:36:53 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 19 08:36:53 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 19 08:36:53 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 19 08:36:53 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 19 08:36:53 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 19 08:36:53 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 19 08:36:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 19 08:36:53 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 19 08:36:53 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 19 08:36:53 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 19 08:36:53 node-1 kernel: [    0.000000] Zone ranges:
Oct 19 08:36:53 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 19 08:36:53 node-1 kernel: [    0.000000] Early memory node ranges
Oct 19 08:36:53 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 19 08:36:53 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 19 08:36:53 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 19 08:36:53 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 19 08:36:53 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 19 08:36:53 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 19 08:36:53 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 19 08:36:53 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 19 08:36:53 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 19 08:36:53 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 19 08:36:53 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 19 08:36:53 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 19 08:36:53 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 19 08:36:53 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 19 08:36:53 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 19 08:36:53 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 19 08:36:53 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 19 08:36:53 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 19 08:36:53 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 19 08:36:53 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 19 08:36:53 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 19 08:36:53 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 19 08:36:53 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 19 08:36:53 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 19 08:36:53 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 19 08:36:53 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 19 08:36:53 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=d29e9f03-d2a4-4797-ba7f-617d312250f1 nomdmonddf nomdmonisw
Oct 19 08:36:53 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 19 08:36:53 node-1 kernel: [    0.000000] Checking aperture...
Oct 19 08:36:53 node-1 kernel: [    0.000000] No AGP bridge found
Oct 19 08:36:53 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 19 08:36:53 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 19 08:36:53 node-1 kernel: [    0.000000] Memory: 32653312K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct 19 08:36:53 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 19 08:36:53 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 19 08:36:53 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 19 08:36:53 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 19 08:36:53 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 19 08:36:53 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 19 08:36:53 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 19 08:36:53 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 19 08:36:53 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 19 08:36:53 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 19 08:36:53 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 19 08:36:53 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 19 08:36:53 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 19 08:36:53 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 19 08:36:53 node-1 kernel: [    0.004000] tsc: Detected 3492.236 MHz processor
Oct 19 08:36:53 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.47 BogoMIPS (lpj=13968944)
Oct 19 08:36:53 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 19 08:36:53 node-1 kernel: [    0.000042] Security Framework initialized
Oct 19 08:36:53 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Oct 19 08:36:53 node-1 kernel: [    0.000061] Yama: becoming mindful.
Oct 19 08:36:53 node-1 kernel: [    0.001473] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.006361] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.008292] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.008321] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.008609] Initializing cgroup subsys memory
Oct 19 08:36:53 node-1 kernel: [    0.008617] Initializing cgroup subsys devices
Oct 19 08:36:53 node-1 kernel: [    0.008618] Initializing cgroup subsys freezer
Oct 19 08:36:53 node-1 kernel: [    0.008620] Initializing cgroup subsys blkio
Oct 19 08:36:53 node-1 kernel: [    0.008622] Initializing cgroup subsys perf_event
Oct 19 08:36:53 node-1 kernel: [    0.008624] Initializing cgroup subsys hugetlb
Oct 19 08:36:53 node-1 kernel: [    0.008643] CPU: Physical Processor ID: 0
Oct 19 08:36:53 node-1 kernel: [    0.008644] CPU: Processor Core ID: 0
Oct 19 08:36:53 node-1 kernel: [    0.008648] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 19 08:36:53 node-1 kernel: [    0.008648] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 19 08:36:53 node-1 kernel: [    0.009341] mce: CPU supports 22 MCE banks
Oct 19 08:36:53 node-1 kernel: [    0.009369] CPU0: Thermal monitoring enabled (TM1)
Oct 19 08:36:53 node-1 kernel: [    0.009389] process: using mwait in idle threads
Oct 19 08:36:53 node-1 kernel: [    0.009392] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 19 08:36:53 node-1 kernel: [    0.009392] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 19 08:36:53 node-1 kernel: [    0.009392] tlb_flushall_shift: 6
Oct 19 08:36:53 node-1 kernel: [    0.009481] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 19 08:36:53 node-1 kernel: [    0.010205] ACPI: Core revision 20131115
Oct 19 08:36:53 node-1 kernel: [    0.023001] ACPI: All ACPI Tables successfully acquired
Oct 19 08:36:53 node-1 kernel: [    0.023161] ftrace: allocating 28622 entries in 112 pages
Oct 19 08:36:53 node-1 kernel: [    0.031924] dmar: Host address width 46
Oct 19 08:36:53 node-1 kernel: [    0.031926] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 19 08:36:53 node-1 kernel: [    0.031932] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 19 08:36:53 node-1 kernel: [    0.031934] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 19 08:36:53 node-1 kernel: [    0.031938] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 19 08:36:53 node-1 kernel: [    0.031940] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 19 08:36:53 node-1 kernel: [    0.031941] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 19 08:36:53 node-1 kernel: [    0.031942] dmar: ATSR flags: 0x0
Oct 19 08:36:53 node-1 kernel: [    0.031943] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 19 08:36:53 node-1 kernel: [    0.031944] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 19 08:36:53 node-1 kernel: [    0.032060] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 19 08:36:53 node-1 kernel: [    0.032061] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 19 08:36:53 node-1 kernel: [    0.032062] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 19 08:36:53 node-1 kernel: [    0.032063] HPET id 0 under DRHD base 0xc7ffc000
Oct 19 08:36:53 node-1 kernel: [    0.032064] Your BIOS is broken and requested that x2apic be disabled.
Oct 19 08:36:53 node-1 kernel: [    0.032064] This will slightly decrease performance.
Oct 19 08:36:53 node-1 kernel: [    0.032064] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 19 08:36:53 node-1 kernel: [    0.032498] Enabled IRQ remapping in xapic mode
Oct 19 08:36:53 node-1 kernel: [    0.032499] x2apic not enabled, IRQ remapping is in xapic mode
Oct 19 08:36:53 node-1 kernel: [    0.032503] Switched APIC routing to physical flat.
Oct 19 08:36:53 node-1 kernel: [    0.033119] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 19 08:36:53 node-1 kernel: [    0.072773] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 19 08:36:53 node-1 kernel: [    0.072778] TSC deadline timer enabled
Oct 19 08:36:53 node-1 kernel: [    0.072785] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 19 08:36:53 node-1 kernel: [    0.072791] ... version:                3
Oct 19 08:36:53 node-1 kernel: [    0.072792] ... bit width:              48
Oct 19 08:36:53 node-1 kernel: [    0.072793] ... generic registers:      4
Oct 19 08:36:53 node-1 kernel: [    0.072794] ... value mask:             0000ffffffffffff
Oct 19 08:36:53 node-1 kernel: [    0.072795] ... max period:             0000ffffffffffff
Oct 19 08:36:53 node-1 kernel: [    0.072796] ... fixed-purpose events:   3
Oct 19 08:36:53 node-1 kernel: [    0.072797] ... event mask:             000000070000000f
Oct 19 08:36:53 node-1 kernel: [    0.074211] x86: Booting SMP configuration:
Oct 19 08:36:53 node-1 kernel: [    0.088317] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 19 08:36:53 node-1 kernel: [    0.074213] .... node  #0, CPUs:        #1  #2  #3
Oct 19 08:36:53 node-1 kernel: [    0.116226] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 19 08:36:53 node-1 kernel: [    0.270403] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 19 08:36:53 node-1 kernel: [    0.326081] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 19 08:36:53 node-1 kernel: [    0.382941] x86: Booted up 2 nodes, 16 CPUs
Oct 19 08:36:53 node-1 kernel: [    0.382945] smpboot: Total of 16 processors activated (111763.86 BogoMIPS)
Oct 19 08:36:53 node-1 kernel: [    0.406745] devtmpfs: initialized
Oct 19 08:36:53 node-1 kernel: [    0.409247] EVM: security.selinux
Oct 19 08:36:53 node-1 kernel: [    0.409249] EVM: security.SMACK64
Oct 19 08:36:53 node-1 kernel: [    0.409250] EVM: security.ima
Oct 19 08:36:53 node-1 kernel: [    0.409251] EVM: security.capability
Oct 19 08:36:53 node-1 kernel: [    0.409299] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.409949] pinctrl core: initialized pinctrl subsystem
Oct 19 08:36:53 node-1 kernel: [    0.410011] regulator-dummy: no parameters
Oct 19 08:36:53 node-1 kernel: [    0.410043] RTC time:  8:36:17, date: 10/19/16
Oct 19 08:36:53 node-1 kernel: [    0.410078] NET: Registered protocol family 16
Oct 19 08:36:53 node-1 kernel: [    0.410162] cpuidle: using governor ladder
Oct 19 08:36:53 node-1 kernel: [    0.410164] cpuidle: using governor menu
Oct 19 08:36:53 node-1 kernel: [    0.410197] ACPI: bus type PCI registered
Oct 19 08:36:53 node-1 kernel: [    0.410199] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 19 08:36:53 node-1 kernel: [    0.410248] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 19 08:36:53 node-1 kernel: [    0.410250] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 19 08:36:53 node-1 kernel: [    0.423992] PCI: Using configuration type 1 for base access
Oct 19 08:36:53 node-1 kernel: [    0.424990] bio: create slab <bio-0> at 0
Oct 19 08:36:53 node-1 kernel: [    0.425296] ACPI: Added _OSI(Module Device)
Oct 19 08:36:53 node-1 kernel: [    0.425298] ACPI: Added _OSI(Processor Device)
Oct 19 08:36:53 node-1 kernel: [    0.425299] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 19 08:36:53 node-1 kernel: [    0.425300] ACPI: Added _OSI(Processor Aggregator Device)
Oct 19 08:36:53 node-1 kernel: [    0.438052] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 19 08:36:53 node-1 kernel: [    0.448713] ACPI: Interpreter enabled
Oct 19 08:36:53 node-1 kernel: [    0.448719] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 19 08:36:53 node-1 kernel: [    0.448723] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 19 08:36:53 node-1 kernel: [    0.448725] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 19 08:36:53 node-1 kernel: [    0.448732] ACPI: (supports S0 S4 S5)
Oct 19 08:36:53 node-1 kernel: [    0.448734] ACPI: Using IOAPIC for interrupt routing
Oct 19 08:36:53 node-1 kernel: [    0.448777] HEST: Table parsing has been initialized.
Oct 19 08:36:53 node-1 kernel: [    0.448780] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 19 08:36:53 node-1 kernel: [    0.449336] ACPI: No dock devices found.
Oct 19 08:36:53 node-1 kernel: [    0.460918] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 19 08:36:53 node-1 kernel: [    0.460923] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 08:36:53 node-1 kernel: [    0.460926] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 19 08:36:53 node-1 kernel: [    0.460952] PCI host bridge to bus 0000:ff
Oct 19 08:36:53 node-1 kernel: [    0.460955] pci_bus 0000:ff: root bus resource [bus ff]
Oct 19 08:36:53 node-1 kernel: [    0.460963] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461000] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.461031] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461065] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461094] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.461123] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.461153] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461181] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461211] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461242] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461269] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461295] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461323] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461349] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461375] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461402] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461430] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461457] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461483] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.461511] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461536] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.461562] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461587] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461617] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.461652] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461683] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461712] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461743] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461774] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461805] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461838] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461869] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461900] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461931] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461964] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.461997] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462031] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462060] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462087] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462120] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462155] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462192] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462228] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462262] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462293] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462322] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462351] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462382] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462416] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462448] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462479] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462509] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462538] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462568] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462598] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462632] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462665] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462723] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 19 08:36:53 node-1 kernel: [    0.462725] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 08:36:53 node-1 kernel: [    0.462728] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 19 08:36:53 node-1 kernel: [    0.462746] PCI host bridge to bus 0000:7f
Oct 19 08:36:53 node-1 kernel: [    0.462748] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 19 08:36:53 node-1 kernel: [    0.462753] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462781] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.462808] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462839] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462861] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.462886] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.462912] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462939] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462962] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.462985] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463007] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463030] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463054] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463076] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463100] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463125] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463146] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463169] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463192] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.463215] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463237] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.463258] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463282] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463309] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 19 08:36:53 node-1 kernel: [    0.463343] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463371] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463400] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463429] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463454] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463483] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463511] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463542] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463568] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463596] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463624] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463653] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463682] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463709] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463734] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463762] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463787] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463813] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463841] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463868] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463892] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463917] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463943] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463972] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.463999] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464027] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464056] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464082] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464104] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464129] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464152] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464183] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.464209] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.465464] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 19 08:36:53 node-1 kernel: [    0.465468] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 08:36:53 node-1 kernel: [    0.466589] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 19 08:36:53 node-1 kernel: [    0.467101] PCI host bridge to bus 0000:00
Oct 19 08:36:53 node-1 kernel: [    0.467104] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 19 08:36:53 node-1 kernel: [    0.467105] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 19 08:36:53 node-1 kernel: [    0.467107] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 19 08:36:53 node-1 kernel: [    0.467108] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 19 08:36:53 node-1 kernel: [    0.467109] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 19 08:36:53 node-1 kernel: [    0.467111] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 19 08:36:53 node-1 kernel: [    0.467112] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 19 08:36:53 node-1 kernel: [    0.467118] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 19 08:36:53 node-1 kernel: [    0.467201] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.467231] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.467273] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 19 08:36:53 node-1 kernel: [    0.467293] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.467322] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.467362] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 19 08:36:53 node-1 kernel: [    0.467379] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.467409] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.467452] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 19 08:36:53 node-1 kernel: [    0.467470] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.467541] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.467621] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.467699] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 19 08:36:53 node-1 kernel: [    0.467704] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 19 08:36:53 node-1 kernel: [    0.467789] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 19 08:36:53 node-1 kernel: [    0.467936] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 19 08:36:53 node-1 kernel: [    0.467954] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 19 08:36:53 node-1 kernel: [    0.468031] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.468085] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 19 08:36:53 node-1 kernel: [    0.468107] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.468163] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.468206] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 19 08:36:53 node-1 kernel: [    0.468234] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.468290] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.468333] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 19 08:36:53 node-1 kernel: [    0.468358] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 19 08:36:53 node-1 kernel: [    0.468375] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 19 08:36:53 node-1 kernel: [    0.468453] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.468503] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 19 08:36:53 node-1 kernel: [    0.468527] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 19 08:36:53 node-1 kernel: [    0.468775] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 19 08:36:53 node-1 kernel: [    0.468781] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 19 08:36:53 node-1 kernel: [    0.468787] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.468793] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.468800] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 19 08:36:53 node-1 kernel: [    0.468830] pci 0000:01:00.0: supports D1 D2
Oct 19 08:36:53 node-1 kernel: [    0.478847] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 19 08:36:53 node-1 kernel: [    0.478854] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 19 08:36:53 node-1 kernel: [    0.478858] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 19 08:36:53 node-1 kernel: [    0.479100] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.479133] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 19 08:36:53 node-1 kernel: [    0.490843] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 19 08:36:53 node-1 kernel: [    0.490849] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.490853] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 08:36:53 node-1 kernel: [    0.490937] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.491010] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.491104] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.491192] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 19 08:36:53 node-1 kernel: [    0.491195] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.491197] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 08:36:53 node-1 kernel: [    0.491250] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.491390] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.491449] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 19 08:36:53 node-1 kernel: [    0.491452] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.491454] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.491503] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.491622] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.491665] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.491784] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.491823] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.491945] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.491983] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 19 08:36:53 node-1 kernel: [    0.492102] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 19 08:36:53 node-1 kernel: [    0.492145] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 19 08:36:53 node-1 kernel: [    0.492148] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.492150] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.492210] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 19 08:36:53 node-1 kernel: [    0.492273] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.492325] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.492395] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 19 08:36:53 node-1 kernel: [    0.492474] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 19 08:36:53 node-1 kernel: [    0.492581] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 19 08:36:53 node-1 kernel: [    0.492584] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.492586] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.492642] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 19 08:36:53 node-1 kernel: [    0.492696] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.492744] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.492958] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 19 08:36:53 node-1 kernel: [    0.492961] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 19 08:36:53 node-1 kernel: [    0.493023] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 19 08:36:53 node-1 kernel: [    0.493076] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.493124] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.493350] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 19 08:36:53 node-1 kernel: [    0.493353] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 19 08:36:53 node-1 kernel: [    0.493413] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 19 08:36:53 node-1 kernel: [    0.493480] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.493532] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 19 08:36:53 node-1 kernel: [    0.493754] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 19 08:36:53 node-1 kernel: [    0.493758] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 19 08:36:53 node-1 kernel: [    0.493932] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 19 08:36:53 node-1 kernel: [    0.493970] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 19 08:36:53 node-1 kernel: [    0.494044] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 19 08:36:53 node-1 kernel: [    0.494062] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 19 08:36:53 node-1 kernel: [    0.494076] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 19 08:36:53 node-1 kernel: [    0.494089] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 19 08:36:53 node-1 kernel: [    0.494139] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 19 08:36:53 node-1 kernel: [    0.498851] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 19 08:36:53 node-1 kernel: [    0.498860] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 19 08:36:53 node-1 kernel: [    0.498912] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 19 08:36:53 node-1 kernel: [    0.499624] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 19 08:36:53 node-1 kernel: [    0.499627] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 08:36:53 node-1 kernel: [    0.499751] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 19 08:36:53 node-1 kernel: [    0.499858] PCI host bridge to bus 0000:80
Oct 19 08:36:53 node-1 kernel: [    0.499860] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 19 08:36:53 node-1 kernel: [    0.499861] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 19 08:36:53 node-1 kernel: [    0.499863] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 19 08:36:53 node-1 kernel: [    0.499871] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.499934] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.500002] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 19 08:36:53 node-1 kernel: [    0.500064] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 19 08:36:53 node-1 kernel: [    0.500069] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 19 08:36:53 node-1 kernel: [    0.500139] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 19 08:36:53 node-1 kernel: [    0.500438] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 19 08:36:53 node-1 kernel: [    0.500469] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 19 08:36:53 node-1 kernel: [    0.500499] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 19 08:36:53 node-1 kernel: [    0.500528] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 19 08:36:53 node-1 kernel: [    0.500557] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 08:36:53 node-1 kernel: [    0.500587] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 08:36:53 node-1 kernel: [    0.500617] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 08:36:53 node-1 kernel: [    0.500646] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 08:36:53 node-1 kernel: [    0.500730] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 19 08:36:53 node-1 kernel: [    0.500735] ACPI: \_SB_.UNC1: notify handler is installed
Oct 19 08:36:53 node-1 kernel: [    0.500736] ACPI: \_SB_.UNC0: notify handler is installed
Oct 19 08:36:53 node-1 kernel: [    0.500751] ACPI: \_SB_.PCI0: notify handler is installed
Oct 19 08:36:53 node-1 kernel: [    0.500804] ACPI: \_SB_.PCI1: notify handler is installed
Oct 19 08:36:53 node-1 kernel: [    0.500883] Found 4 acpi root devices
Oct 19 08:36:53 node-1 kernel: [    0.500989] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 19 08:36:53 node-1 kernel: [    0.500992] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 19 08:36:53 node-1 kernel: [    0.500993] vgaarb: loaded
Oct 19 08:36:53 node-1 kernel: [    0.500994] vgaarb: bridge control possible 0000:0c:00.0
Oct 19 08:36:53 node-1 kernel: [    0.501111] SCSI subsystem initialized
Oct 19 08:36:53 node-1 kernel: [    0.501176] libata version 3.00 loaded.
Oct 19 08:36:53 node-1 kernel: [    0.501191] ACPI: bus type USB registered
Oct 19 08:36:53 node-1 kernel: [    0.501201] usbcore: registered new interface driver usbfs
Oct 19 08:36:53 node-1 kernel: [    0.501206] usbcore: registered new interface driver hub
Oct 19 08:36:53 node-1 kernel: [    0.501230] usbcore: registered new device driver usb
Oct 19 08:36:53 node-1 kernel: [    0.501396] PCI: Using ACPI for IRQ routing
Oct 19 08:36:53 node-1 kernel: [    0.504988] PCI: pci_cache_line_size set to 64 bytes
Oct 19 08:36:53 node-1 kernel: [    0.505196] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 19 08:36:53 node-1 kernel: [    0.505197] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 19 08:36:53 node-1 kernel: [    0.505198] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 19 08:36:53 node-1 kernel: [    0.505261] NetLabel: Initializing
Oct 19 08:36:53 node-1 kernel: [    0.505263] NetLabel:  domain hash size = 128
Oct 19 08:36:53 node-1 kernel: [    0.505264] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 19 08:36:53 node-1 kernel: [    0.505273] NetLabel:  unlabeled traffic allowed by default
Oct 19 08:36:53 node-1 kernel: [    0.505341] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 19 08:36:53 node-1 kernel: [    0.505345] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 19 08:36:53 node-1 kernel: [    0.507404] Switched to clocksource hpet
Oct 19 08:36:53 node-1 kernel: [    0.511296] AppArmor: AppArmor Filesystem Enabled
Oct 19 08:36:53 node-1 kernel: [    0.511309] pnp: PnP ACPI init
Oct 19 08:36:53 node-1 kernel: [    0.511316] ACPI: bus type PNP registered
Oct 19 08:36:53 node-1 kernel: [    0.511439] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511447] pnp 00:01: [dma 4]
Oct 19 08:36:53 node-1 kernel: [    0.511459] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511484] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511504] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511521] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511554] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511605] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511608] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 19 08:36:53 node-1 kernel: [    0.511609] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511611] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511612] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511616] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511619] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 19 08:36:53 node-1 kernel: [    0.511620] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511622] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511623] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511625] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511626] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511628] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 19 08:36:53 node-1 kernel: [    0.511630] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511713] pnp 00:07: [dma 0 disabled]
Oct 19 08:36:53 node-1 kernel: [    0.511741] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511816] pnp 00:08: [dma 0 disabled]
Oct 19 08:36:53 node-1 kernel: [    0.511847] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 19 08:36:53 node-1 kernel: [    0.511898] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 19 08:36:53 node-1 kernel: [    0.512243] pnp: PnP ACPI: found 10 devices
Oct 19 08:36:53 node-1 kernel: [    0.512245] ACPI: bus type PNP unregistered
Oct 19 08:36:53 node-1 kernel: [    0.518679] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 19 08:36:53 node-1 kernel: [    0.518681] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 19 08:36:53 node-1 kernel: [    0.518684] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 19 08:36:53 node-1 kernel: [    0.518688] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 19 08:36:53 node-1 kernel: [    0.518690] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.518705] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.518734] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 19 08:36:53 node-1 kernel: [    0.518748] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 19 08:36:53 node-1 kernel: [    0.518777] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 19 08:36:53 node-1 kernel: [    0.518794] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 19 08:36:53 node-1 kernel: [    0.518823] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 19 08:36:53 node-1 kernel: [    0.518837] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 19 08:36:53 node-1 kernel: [    0.518866] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 19 08:36:53 node-1 kernel: [    0.518868] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.518883] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.518912] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 19 08:36:53 node-1 kernel: [    0.518913] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.518928] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.518957] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 19 08:36:53 node-1 kernel: [    0.518958] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.518961] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 08:36:53 node-1 kernel: [    0.518965] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 19 08:36:53 node-1 kernel: [    0.518967] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.518969] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 08:36:53 node-1 kernel: [    0.518973] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 19 08:36:53 node-1 kernel: [    0.518978] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 19 08:36:53 node-1 kernel: [    0.518986] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 19 08:36:53 node-1 kernel: [    0.518989] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 19 08:36:53 node-1 kernel: [    0.518995] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 19 08:36:53 node-1 kernel: [    0.518996] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 19 08:36:53 node-1 kernel: [    0.518997] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 19 08:36:53 node-1 kernel: [    0.518998] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 19 08:36:53 node-1 kernel: [    0.518999] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 19 08:36:53 node-1 kernel: [    0.519000] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 19 08:36:53 node-1 kernel: [    0.519001] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 19 08:36:53 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 19 08:36:53 node-1 kernel: [    0.519002] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 19 08:36:53 node-1 kernel: [    0.519003] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.519004] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 19 08:36:53 node-1 kernel: [    0.519004] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.519005] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 19 08:36:53 node-1 kernel: [    0.519006] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.519007] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.519008] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.519009] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.519010] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 19 08:36:53 node-1 kernel: [    0.519010] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 19 08:36:53 node-1 kernel: [    0.519011] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 19 08:36:53 node-1 kernel: [    0.519012] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 19 08:36:53 node-1 kernel: [    0.519013] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 19 08:36:53 node-1 kernel: [    0.519014] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 19 08:36:53 node-1 kernel: [    0.519016] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 19 08:36:53 node-1 kernel: [    0.519017] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 19 08:36:53 node-1 kernel: [    0.519053] NET: Registered protocol family 2
Oct 19 08:36:53 node-1 kernel: [    0.519312] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.519649] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.519796] TCP: Hash tables configured (established 262144 bind 65536)
Oct 19 08:36:53 node-1 kernel: [    0.519832] TCP: reno registered
Oct 19 08:36:53 node-1 kernel: [    0.519862] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.519957] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.520106] NET: Registered protocol family 1
Oct 19 08:36:53 node-1 kernel: [    0.559501] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 19 08:36:53 node-1 kernel: [    0.559514] PCI: CLS 64 bytes, default 64
Oct 19 08:36:53 node-1 kernel: [    0.559591] Trying to unpack rootfs image as initramfs...
Oct 19 08:36:53 node-1 kernel: [    0.779266] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct 19 08:36:53 node-1 kernel: [    0.779299] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 19 08:36:53 node-1 kernel: [    0.779301] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 19 08:36:53 node-1 kernel: [    0.779706] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779712] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779717] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779723] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779735] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779751] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779766] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779781] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779793] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779803] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779809] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779815] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779824] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779836] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779848] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779862] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 08:36:53 node-1 kernel: [    0.779915] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 19 08:36:53 node-1 kernel: [    0.779919] Scanning for low memory corruption every 60 seconds
Oct 19 08:36:53 node-1 kernel: [    0.780223] Initialise system trusted keyring
Oct 19 08:36:53 node-1 kernel: [    0.780268] audit: initializing netlink socket (disabled)
Oct 19 08:36:53 node-1 kernel: [    0.780277] type=2000 audit(1476866177.732:1): initialized
Oct 19 08:36:53 node-1 kernel: [    0.797949] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 19 08:36:53 node-1 kernel: [    0.799402] zbud: loaded
Oct 19 08:36:53 node-1 kernel: [    0.799513] VFS: Disk quotas dquot_6.5.2
Oct 19 08:36:53 node-1 kernel: [    0.799552] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 19 08:36:53 node-1 kernel: [    0.799920] fuse init (API version 7.22)
Oct 19 08:36:53 node-1 kernel: [    0.799991] msgmni has been set to 32768
Oct 19 08:36:53 node-1 kernel: [    0.800033] Key type big_key registered
Oct 19 08:36:53 node-1 kernel: [    0.800537] Key type asymmetric registered
Oct 19 08:36:53 node-1 kernel: [    0.800538] Asymmetric key parser 'x509' registered
Oct 19 08:36:53 node-1 kernel: [    0.800563] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 19 08:36:53 node-1 kernel: [    0.800623] io scheduler noop registered
Oct 19 08:36:53 node-1 kernel: [    0.800624] io scheduler deadline registered (default)
Oct 19 08:36:53 node-1 kernel: [    0.800641] io scheduler cfq registered
Oct 19 08:36:53 node-1 kernel: [    0.800959] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    0.801051] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    0.801138] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    0.801224] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    0.801319] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    0.801385] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    0.801652] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 19 08:36:53 node-1 kernel: [    0.801670] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 19 08:36:53 node-1 kernel: [    0.801682] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 19 08:36:53 node-1 kernel: [    0.801693] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801695] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801697] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 19 08:36:53 node-1 kernel: [    0.801701] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801702] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801703] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801705] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801706] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801708] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801709] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801711] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801712] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801713] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801715] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801716] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801718] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 19 08:36:53 node-1 kernel: [    0.801722] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801724] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 19 08:36:53 node-1 kernel: [    0.801733] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801735] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 19 08:36:53 node-1 kernel: [    0.801744] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801746] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 19 08:36:53 node-1 kernel: [    0.801748] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 19 08:36:53 node-1 kernel: [    0.801761] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 19 08:36:53 node-1 kernel: [    0.801853] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 19 08:36:53 node-1 kernel: [    0.801857] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 19 08:36:53 node-1 kernel: [    0.801865] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 19 08:36:53 node-1 kernel: [    0.801900] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 19 08:36:53 node-1 kernel: [    0.801901] vesafb: scrolling: redraw
Oct 19 08:36:53 node-1 kernel: [    0.801903] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 19 08:36:53 node-1 kernel: [    0.822953] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 19 08:36:53 node-1 kernel: [    0.831471] Console: switching to colour frame buffer device 80x30
Oct 19 08:36:53 node-1 kernel: [    0.840161] fb0: VESA VGA frame buffer device
Oct 19 08:36:53 node-1 kernel: [    0.840365] intel_idle: MWAIT substates: 0x2120
Oct 19 08:36:53 node-1 kernel: [    0.840366] intel_idle: v0.4 model 0x3F
Oct 19 08:36:53 node-1 kernel: [    0.840367] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 19 08:36:53 node-1 kernel: [    0.840594] ipmi message handler version 39.2
Oct 19 08:36:53 node-1 kernel: [    0.840868] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 19 08:36:53 node-1 kernel: [    0.841305] ACPI: AC Adapter [P111] (on-line)
Oct 19 08:36:53 node-1 kernel: [    0.846526] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 19 08:36:53 node-1 kernel: [    0.857576] ACPI: Power Button [PWRB]
Oct 19 08:36:53 node-1 kernel: [    0.863489] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 19 08:36:53 node-1 kernel: [    0.875286] ACPI: Power Button [PWRF]
Oct 19 08:36:53 node-1 kernel: [    0.901074] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 19 08:36:53 node-1 kernel: [    0.912906] pstore: Registered erst as persistent store backend
Oct 19 08:36:53 node-1 kernel: [    0.919207] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 19 08:36:53 node-1 kernel: [    0.931243] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 19 08:36:53 node-1 kernel: [    0.958001] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 19 08:36:53 node-1 kernel: [    0.991279] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 19 08:36:53 node-1 kernel: [    1.005314] Linux agpgart interface v0.103
Oct 19 08:36:53 node-1 kernel: [    1.012950] brd: module loaded
Oct 19 08:36:53 node-1 kernel: [    1.019980] loop: module loaded
Oct 19 08:36:53 node-1 kernel: [    1.026685] libphy: Fixed MDIO Bus: probed
Oct 19 08:36:53 node-1 kernel: [    1.033126] tun: Universal TUN/TAP device driver, 1.6
Oct 19 08:36:53 node-1 kernel: [    1.039582] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 19 08:36:53 node-1 kernel: [    1.046084] PPP generic driver version 2.4.2
Oct 19 08:36:53 node-1 kernel: [    1.052450] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 19 08:36:53 node-1 kernel: [    1.058856] ehci-pci: EHCI PCI platform driver
Oct 19 08:36:53 node-1 kernel: [    1.065426] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 19 08:36:53 node-1 kernel: [    1.071818] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 19 08:36:53 node-1 kernel: [    1.084315] ehci-pci 0000:00:1a.0: debug port 2
Oct 19 08:36:53 node-1 kernel: [    1.094477] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 19 08:36:53 node-1 kernel: [    1.094495] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 19 08:36:53 node-1 kernel: [    1.110897] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 19 08:36:53 node-1 kernel: [    1.116952] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 19 08:36:53 node-1 kernel: [    1.123103] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 19 08:36:53 node-1 kernel: [    1.134959] usb usb1: Product: EHCI Host Controller
Oct 19 08:36:53 node-1 kernel: [    1.140963] usb usb1: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 19 08:36:53 node-1 kernel: [    1.147006] usb usb1: SerialNumber: 0000:00:1a.0
Oct 19 08:36:53 node-1 kernel: [    1.152958] hub 1-0:1.0: USB hub found
Oct 19 08:36:53 node-1 kernel: [    1.158725] hub 1-0:1.0: 2 ports detected
Oct 19 08:36:53 node-1 kernel: [    1.164532] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 19 08:36:53 node-1 kernel: [    1.170113] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 19 08:36:53 node-1 kernel: [    1.181013] ehci-pci 0000:00:1d.0: debug port 2
Oct 19 08:36:53 node-1 kernel: [    1.190341] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 19 08:36:53 node-1 kernel: [    1.190344] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 19 08:36:53 node-1 kernel: [    1.206816] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 19 08:36:53 node-1 kernel: [    1.212085] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 19 08:36:53 node-1 kernel: [    1.217453] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 19 08:36:53 node-1 kernel: [    1.228129] usb usb2: Product: EHCI Host Controller
Oct 19 08:36:53 node-1 kernel: [    1.233655] usb usb2: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 19 08:36:53 node-1 kernel: [    1.239226] usb usb2: SerialNumber: 0000:00:1d.0
Oct 19 08:36:53 node-1 kernel: [    1.244755] hub 2-0:1.0: USB hub found
Oct 19 08:36:53 node-1 kernel: [    1.250119] hub 2-0:1.0: 2 ports detected
Oct 19 08:36:53 node-1 kernel: [    1.255422] ehci-platform: EHCI generic platform driver
Oct 19 08:36:53 node-1 kernel: [    1.260757] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 19 08:36:53 node-1 kernel: [    1.266086] ohci-pci: OHCI PCI platform driver
Oct 19 08:36:53 node-1 kernel: [    1.271384] ohci-platform: OHCI generic platform driver
Oct 19 08:36:53 node-1 kernel: [    1.276592] uhci_hcd: USB Universal Host Controller Interface driver
Oct 19 08:36:53 node-1 kernel: [    1.281933] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 19 08:36:53 node-1 kernel: [    1.474597] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 19 08:36:53 node-1 kernel: [    1.634769] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 19 08:36:53 node-1 kernel: [    1.640359] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 19 08:36:53 node-1 kernel: [    1.646157] hub 1-1:1.0: USB hub found
Oct 19 08:36:53 node-1 kernel: [    1.651631] hub 1-1:1.0: 6 ports detected
Oct 19 08:36:53 node-1 kernel: [    1.766339] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 19 08:36:53 node-1 kernel: [    1.778422] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 19 08:36:53 node-1 kernel: [    2.034430] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 19 08:36:53 node-1 kernel: [    2.039982] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 19 08:36:53 node-1 kernel: [    2.045822] hub 2-1:1.0: USB hub found
Oct 19 08:36:53 node-1 kernel: [    2.051542] hub 2-1:1.0: 8 ports detected
Oct 19 08:36:53 node-1 kernel: [    2.323636] i8042: No controller found
Oct 19 08:36:53 node-1 kernel: [    2.329067] mousedev: PS/2 mouse device common for all mice
Oct 19 08:36:53 node-1 kernel: [    2.329953] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 19 08:36:53 node-1 kernel: [    2.340203] rtc_cmos 00:02: RTC can wake from S4
Oct 19 08:36:53 node-1 kernel: [    2.345959] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 19 08:36:53 node-1 kernel: [    2.351585] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 19 08:36:53 node-1 kernel: [    2.362741] device-mapper: uevent: version 1.0.3
Oct 19 08:36:53 node-1 kernel: [    2.368423] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 19 08:36:53 node-1 kernel: [    2.379774] ledtrig-cpu: registered to indicate activity on CPUs
Oct 19 08:36:53 node-1 kernel: [    2.385751] TCP: cubic registered
Oct 19 08:36:53 node-1 kernel: [    2.391667] NET: Registered protocol family 10
Oct 19 08:36:53 node-1 kernel: [    2.397625] NET: Registered protocol family 17
Oct 19 08:36:53 node-1 kernel: [    2.403283] Key type dns_resolver registered
Oct 19 08:36:53 node-1 kernel: [    2.409213] Loading compiled-in X.509 certificates
Oct 19 08:36:53 node-1 kernel: [    2.415352] Loaded X.509 cert 'Magrathea: Glacier signing key: c29c39823a6b07000b1e1e4c1cabc3708bc09796'
Oct 19 08:36:53 node-1 kernel: [    2.426697] registered taskstats version 1
Oct 19 08:36:53 node-1 kernel: [    2.434641] Key type trusted registered
Oct 19 08:36:53 node-1 kernel: [    2.442172] Key type encrypted registered
Oct 19 08:36:53 node-1 kernel: [    2.447612] AppArmor: AppArmor sha1 policy hashing enabled
Oct 19 08:36:53 node-1 kernel: [    2.453090] IMA: No TPM chip found, activating TPM-bypass!
Oct 19 08:36:53 node-1 kernel: [    2.459200] regulator-dummy: disabling
Oct 19 08:36:53 node-1 kernel: [    2.464746]   Magic number: 4:879:624
Oct 19 08:36:53 node-1 kernel: [    2.466133] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 19 08:36:53 node-1 kernel: [    2.466134] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 19 08:36:53 node-1 kernel: [    2.466135] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 19 08:36:53 node-1 kernel: [    2.466135] usb 2-1.4: Manufacturer: Avocent
Oct 19 08:36:53 node-1 kernel: [    2.466136] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 19 08:36:53 node-1 kernel: [    2.503415] rtc_cmos 00:02: setting system clock to 2016-10-19 08:36:19 UTC (1476866179)
Oct 19 08:36:53 node-1 kernel: [    2.515918] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 19 08:36:53 node-1 kernel: [    2.521650] EDD information not available.
Oct 19 08:36:53 node-1 kernel: [    2.527338] PM: Hibernation image not present or could not be loaded.
Oct 19 08:36:53 node-1 kernel: [    2.528205] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 19 08:36:53 node-1 kernel: [    2.539556] Write protecting the kernel read-only data: 12288k
Oct 19 08:36:53 node-1 kernel: [    2.545869] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 19 08:36:53 node-1 kernel: [    2.558416] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 19 08:36:53 node-1 kernel: [    2.590756] device-mapper: multipath: version 1.6.0 loaded
Oct 19 08:36:53 node-1 kernel: [    2.598787] systemd-udevd[216]: starting version 204
Oct 19 08:36:53 node-1 kernel: [    2.623917] md: linear personality registered for level -1
Oct 19 08:36:53 node-1 kernel: [    2.638745] md: multipath personality registered for level -4
Oct 19 08:36:53 node-1 kernel: [    2.646734] md: raid0 personality registered for level 0
Oct 19 08:36:53 node-1 kernel: [    2.655063] md: raid1 personality registered for level 1
Oct 19 08:36:53 node-1 kernel: [    2.664612] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 19 08:36:53 node-1 kernel: [    2.670996] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 19 08:36:53 node-1 kernel: [    2.671201] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 19 08:36:53 node-1 kernel: [    2.681945] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct 19 08:36:53 node-1 kernel: [    2.681948] 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 19 08:36:53 node-1 kernel: [    2.681957] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 19 08:36:53 node-1 kernel: [    2.682367] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.682429] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.682515] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.682589] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.682901] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.698981] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct 19 08:36:53 node-1 kernel: [    2.698999] 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 19 08:36:53 node-1 kernel: [    2.699015] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 19 08:36:53 node-1 kernel: [    2.699302] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.699369] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.699468] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.699555] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.699609] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.699712] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.700033] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.717720] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct 19 08:36:53 node-1 kernel: [    2.717726] 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 19 08:36:53 node-1 kernel: [    2.717741] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 19 08:36:53 node-1 kernel: [    2.717972] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.718087] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.718165] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.718238] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.718516] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.729593] raid6: sse2x1   11493 MB/s
Oct 19 08:36:53 node-1 kernel: [    2.733795] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct 19 08:36:53 node-1 kernel: [    2.733826] 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 19 08:36:53 node-1 kernel: [    2.733856] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 19 08:36:53 node-1 kernel: [    2.734070] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.734155] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.734240] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.734318] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.734595] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 19 08:36:53 node-1 kernel: [    2.797715] raid6: sse2x2   12561 MB/s
Oct 19 08:36:53 node-1 kernel: [    2.865635] raid6: sse2x4    9545 MB/s
Oct 19 08:36:53 node-1 kernel: [    2.933365] raid6: avx2x1   14636 MB/s
Oct 19 08:36:53 node-1 kernel: [    3.005300] raid6: avx2x2   18871 MB/s
Oct 19 08:36:53 node-1 kernel: [    3.077233] raid6: avx2x4   21416 MB/s
Oct 19 08:36:53 node-1 kernel: [    3.083114] raid6: using algorithm avx2x4 (21416 MB/s)
Oct 19 08:36:53 node-1 kernel: [    3.089155] raid6: using avx2x2 recovery algorithm
Oct 19 08:36:53 node-1 kernel: [    3.095060] Switched to clocksource tsc
Oct 19 08:36:53 node-1 kernel: [    3.095774] megasas: FW now in Ready state
Oct 19 08:36:53 node-1 kernel: [    3.096232] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.096291] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.096440] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.096519] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.096657] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.096765] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.096833] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.096948] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.097065] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.097282] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.097467] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.097560] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.097626] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.097767] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.097933] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.098002] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Oct 19 08:36:53 node-1 kernel: [    3.098606] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 19 08:36:53 node-1 kernel: [    3.100914] hidraw: raw HID events driver (C) Jiri Kosina
Oct 19 08:36:53 node-1 kernel: [    3.123915] xor: automatically using best checksumming function:
Oct 19 08:36:53 node-1 kernel: [    3.131445] usbcore: registered new interface driver usbhid
Oct 19 08:36:53 node-1 kernel: [    3.137123] usbhid: USB HID core driver
Oct 19 08:36:53 node-1 kernel: [    3.148441] 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 19 08:36:53 node-1 kernel: [    3.159700] 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 19 08:36:53 node-1 kernel: [    3.169156]    avx       : 35743.000 MB/sec
Oct 19 08:36:53 node-1 kernel: [    3.176871] 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 19 08:36:53 node-1 kernel: [    3.188847] async_tx: api initialized (async)
Oct 19 08:36:53 node-1 kernel: [    3.189026] 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 19 08:36:53 node-1 kernel: [    3.189080] 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 19 08:36:53 node-1 kernel: [    3.189437] 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 19 08:36:53 node-1 kernel: [    3.234941] md: raid6 personality registered for level 6
Oct 19 08:36:53 node-1 kernel: [    3.241267] md: raid5 personality registered for level 5
Oct 19 08:36:53 node-1 kernel: [    3.247592] md: raid4 personality registered for level 4
Oct 19 08:36:53 node-1 kernel: [    3.256900] md: raid10 personality registered for level 10
Oct 19 08:36:53 node-1 kernel: [    3.311753] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Oct 19 08:36:53 node-1 kernel: [    3.432971] megasas:IOC Init cmd success
Oct 19 08:36:53 node-1 kernel: [    3.484954] megasas: INIT adapter done
Oct 19 08:36:53 node-1 kernel: [    3.560870] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 19 08:36:53 node-1 kernel: [    3.567798] scsi0 : LSI SAS based MegaRAID driver
Oct 19 08:36:53 node-1 kernel: [    3.575245] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 19 08:36:53 node-1 kernel: [    3.597359] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 19 08:36:53 node-1 kernel: [    3.613944] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 19 08:36:53 node-1 kernel: [    3.614799] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 19 08:36:53 node-1 kernel: [    3.615593] sd 0:2:0:0: [sda] Write Protect is off
Oct 19 08:36:53 node-1 kernel: [    3.615598] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 19 08:36:53 node-1 kernel: [    3.615991] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 19 08:36:53 node-1 kernel: [    3.648178]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 19 08:36:53 node-1 kernel: [    3.652361] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 19 08:36:53 node-1 kernel: [    3.786936] random: lvm urandom read with 27 bits of entropy available
Oct 19 08:36:53 node-1 kernel: [    3.915343] bio: create slab <bio-1> at 1
Oct 19 08:36:53 node-1 kernel: [    4.689851] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 08:36:53 node-1 kernel: [    5.180059] init: plymouth-upstart-bridge main process (553) terminated with status 1
Oct 19 08:36:53 node-1 kernel: [    5.192428] init: plymouth-upstart-bridge main process ended, respawning
Oct 19 08:36:53 node-1 kernel: [    5.301022] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 19 08:36:53 node-1 kernel: [    5.345281] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 19 08:36:53 node-1 kernel: [    5.389458] random: nonblocking pool is initialized
Oct 19 08:36:53 node-1 kernel: [    5.472674] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 19 08:36:53 node-1 kernel: [    5.514578] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 19 08:36:53 node-1 kernel: [    5.638569] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 08:36:53 node-1 kernel: [    5.877264] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 19 08:36:53 node-1 kernel: [    5.918398] XFS (dm-0): Mounting Filesystem
Oct 19 08:36:53 node-1 kernel: [    6.179917] XFS (dm-0): Ending clean mount
Oct 19 08:36:53 node-1 kernel: [    6.283215] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 08:36:53 node-1 kernel: [    6.316314] XFS (dm-1): Mounting Filesystem
Oct 19 08:36:53 node-1 kernel: [    6.418851] XFS (dm-1): Ending clean mount
Oct 19 08:36:53 node-1 kernel: [    8.080285] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 19 08:36:53 node-1 kernel: [    8.094202] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 19 08:36:53 node-1 kernel: [    8.309225] systemd-udevd[780]: starting version 204
Oct 19 08:36:53 node-1 kernel: [    8.491335] power_meter ACPI000D:00: Found ACPI power meter.
Oct 19 08:36:53 node-1 kernel: [    8.491369] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 19 08:36:53 node-1 kernel: [    8.506589] wmi: Mapper loaded
Oct 19 08:36:53 node-1 kernel: [    8.508340] IPMI System Interface driver.
Oct 19 08:36:53 node-1 kernel: [    8.508378] ipmi_si: probing via ACPI
Oct 19 08:36:53 node-1 kernel: [    8.508389] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 19 08:36:53 node-1 kernel: [    8.508390] ipmi_si: Adding ACPI-specified kcs state machine
Oct 19 08:36:53 node-1 kernel: [    8.508397] ipmi_si: probing via SMBIOS
Oct 19 08:36:53 node-1 kernel: [    8.508398] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 19 08:36:53 node-1 kernel: [    8.508399] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 19 08:36:53 node-1 kernel: [    8.508401] ipmi_si: probing via SPMI
Oct 19 08:36:53 node-1 kernel: [    8.508401] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 19 08:36:53 node-1 kernel: [    8.508402] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 19 08:36:53 node-1 kernel: [    8.508403] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 19 08:36:53 node-1 kernel: [    8.561291] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 19 08:36:53 node-1 kernel: [    8.574089] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 19 08:36:53 node-1 kernel: [    8.574094] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 19 08:36:53 node-1 kernel: [    8.574097] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 19 08:36:53 node-1 kernel: [    8.574099] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 19 08:36:53 node-1 kernel: [    8.574113] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 19 08:36:53 node-1 kernel: [    8.629038] systemd-udevd[834]: renamed network interface eth3 to enp9s0
Oct 19 08:36:53 node-1 kernel: [    8.641932] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 19 08:36:53 node-1 kernel: [    8.641939] ipmi_si 00:09: IPMI kcs interface initialized
Oct 19 08:36:53 node-1 kernel: [    8.664877] systemd-udevd[809]: renamed network interface eth1 to enp7s0
Oct 19 08:36:53 node-1 kernel: [    8.684965] systemd-udevd[821]: renamed network interface eth2 to enp8s0
Oct 19 08:36:53 node-1 kernel: [    8.712887] systemd-udevd[799]: renamed network interface eth0 to enp6s0
Oct 19 08:36:53 node-1 kernel: [    8.976801] type=1400 audit(1476866185.977:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    8.976962] type=1400 audit(1476866185.977:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1055 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    8.977091] type=1400 audit(1476866185.977:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1055 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.002138] type=1400 audit(1476866186.001:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.002286] type=1400 audit(1476866186.001:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.002410] type=1400 audit(1476866186.001:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.004700] type=1400 audit(1476866186.005:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.004843] type=1400 audit(1476866186.005:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1062 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.004966] type=1400 audit(1476866186.005:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1062 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.009002] type=1400 audit(1476866186.009:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Oct 19 08:36:53 node-1 kernel: [    9.521796] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 19 08:36:53 node-1 kernel: [    9.522556] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 19 08:36:53 node-1 kernel: [    9.753711] enic 0000:06:00.0 enp6s0: Link UP
Oct 19 08:36:53 node-1 kernel: [    9.756024] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 19 08:36:53 node-1 kernel: [    9.756030] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 19 08:36:53 node-1 kernel: [   19.248379] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 19 08:36:54 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 19 08:36:54 node-1 kernel: [   37.560665] init: failsafe main process (8414) killed by TERM signal
Oct 19 08:36:55 node-1 dbus[8446]: [system] AppArmor D-Bus mediation is enabled
Oct 19 08:36:55 node-1 kernel: [   37.883524] audit_printk_skb: 30 callbacks suppressed
Oct 19 08:36:55 node-1 kernel: [   37.883527] type=1400 audit(1476866215.250:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8541 comm="apparmor_parser"
Oct 19 08:36:55 node-1 kernel: [   37.883532] type=1400 audit(1476866215.250:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Oct 19 08:36:55 node-1 kernel: [   37.883535] type=1400 audit(1476866215.250:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Oct 19 08:36:55 node-1 kernel: [   37.883756] type=1400 audit(1476866215.250:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Oct 19 08:36:55 node-1 kernel: [   37.883758] type=1400 audit(1476866215.250:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Oct 19 08:36:55 node-1 kernel: [   37.883873] type=1400 audit(1476866215.250:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Oct 19 08:36:55 node-1 kernel: [   37.887847] type=1400 audit(1476866215.254:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8542 comm="apparmor_parser"
Oct 19 08:36:55 node-1 kernel: [   37.953402] type=1400 audit(1476866215.318:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8544 comm="apparmor_parser"
Oct 19 08:36:55 node-1 cron[8573]: (CRON) INFO (pidfile fd = 3)
Oct 19 08:36:55 node-1 anacron[8612]: Anacron 2.3 started on 2016-10-19
Oct 19 08:36:55 node-1 cron[8614]: (CRON) STARTUP (fork ok)
Oct 19 08:36:55 node-1 anacron[8612]: Will run job `cron.daily' in 5 min.
Oct 19 08:36:55 node-1 anacron[8612]: Will run job `cron.weekly' in 10 min.
Oct 19 08:36:55 node-1 anacron[8612]: Will run job `cron.monthly' in 15 min.
Oct 19 08:36:55 node-1 anacron[8612]: Jobs will be executed sequentially
Oct 19 08:36:55 node-1 multipathd: path checkers start up
Oct 19 08:36:55 node-1 cron[8614]: (CRON) INFO (Running @reboot jobs)
Oct 19 08:36:55 node-1 postfix/master[8752]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 19 08:36:59 node-1 puppet-agent[8937]: Reopening log files
Oct 19 08:37:00 node-1 puppet-agent[8937]: Could not request certificate: Connection refused - connect(2)
Oct 19 08:37:01 node-1 CRON[9097]: (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 19 08:37:13 node-1 puppet-user[9156]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 19 08:37:13 node-1 puppet-user[9156]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 19 08:37:14 node-1 puppet-user[9156]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 19 08:37:14 node-1 puppet-user[9156]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 19 08:37:14 node-1 puppet-user[9156]: Finished catalog run in 0.91 seconds
Oct 19 08:37:15 node-1 multipathd: uevent trigger error
Oct 19 08:37:15 node-1 puppet-user[9761]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 19 08:37:15 node-1 puppet-user[9761]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 19 08:37:16 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 19 08:37:16 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 19 08:37:16 node-1 puppet-user[9761]: (/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 19 08:37:16 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 19 08:37:16 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 19 08:37:16 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 19 08:37:16 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 19 08:37:16 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 19 08:37:16 node-1 puppet-user[9761]: Finished catalog run in 0.05 seconds
Oct 19 08:37:17 node-1 puppet-user[10222]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 19 08:37:17 node-1 puppet-user[10222]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 19 08:37:17 node-1 puppet-user[10222]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 19 08:37:17 node-1 puppet-user[10222]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 19 08:37:17 node-1 puppet-user[10222]: Finished catalog run in 0.03 seconds
Oct 19 08:37:19 node-1 puppet-user[10685]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 19 08:37:19 node-1 puppet-user[10685]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 19 08:37:19 node-1 puppet-user[10685]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 19 08:37:19 node-1 puppet-user[10685]: Finished catalog run in 0.04 seconds
Oct 19 08:37:19 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 19 08:37:19 node-1 nailgun-agent: D, [2016-10-19T08:37:01.710267 #9100] DEBUG -- : Sleep for 18 seconds before sending request
Oct 19 08:37:19 node-1 nailgun-agent: I, [2016-10-19T08:37:19.724275 #9100]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 19 08:37:20 node-1 nailgun-agent: D, [2016-10-19T08:37:20.117604 #9100] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 19 08:37:20 node-1 puppet-user[11178]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 19 08:37:21 node-1 puppet-user[11178]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Oct 19 08:37:21 node-1 puppet-user[11178]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 19 08:37:23 node-1 puppet-user[11178]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Oct 19 08:37:23 node-1 puppet-user[11178]: Finished catalog run in 2.22 seconds
Oct 19 08:37:24 node-1 puppet-user[11806]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 19 08:37:24 node-1 puppet-user[11806]: Compiled catalog for node-1.domain.tld in environment production in 0.25 seconds
Oct 19 08:37:25 node-1 puppet-user[11806]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 19 08:37:25 node-1 puppet-user[11806]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Oct 19 08:37:25 node-1 puppet-user[11806]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 19 08:37:25 node-1 puppet-user[11806]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 19 08:37:25 node-1 puppet-user[11806]: Finished catalog run in 0.22 seconds
Oct 19 08:37:25 node-1 kernel: [   67.870030] init: plymouth-upstart-bridge main process ended, respawning
Oct 19 08:37:25 node-1 puppet-agent[8937]: Could not run: SIGTERM
Oct 19 08:37:25 node-1 kernel: [   68.149859] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 19 08:37:25 node-1 ec2: 
Oct 19 08:37:25 node-1 ec2: #############################################################
Oct 19 08:37:25 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 19 08:37:25 node-1 ec2: 1024 aa:8a:3d:43:81:ff:06:9b:5a:2d:57:2a:7e:35:17:07  root@node-1.domain.tld (DSA)
Oct 19 08:37:25 node-1 ec2: 256 8f:25:92:c6:1e:ec:ae:11:6f:59:4c:13:2c:4c:fe:28  root@node-1.domain.tld (ECDSA)
Oct 19 08:37:25 node-1 ec2: 256 72:98:51:f8:21:ed:04:66:62:95:f5:e9:77:a8:72:68  root@node-1.domain.tld (ED25519)
Oct 19 08:37:25 node-1 ec2: 2048 46:b8:84:14:a9:f2:9e:93:7e:e5:e5:a1:e8:2d:53:78  root@node-1.domain.tld (RSA)
Oct 19 08:37:25 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 19 08:37:25 node-1 ec2: #############################################################
Oct 19 08:37:26 node-1 puppet-user[12444]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 19 08:37:26 node-1 puppet-user[12444]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct 19 08:37:27 node-1 puppet-user[12444]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 19 08:37:27 node-1 kernel: [   69.645874] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 19 08:37:27 node-1 kernel: [   69.645921] 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 19 08:37:27 node-1 puppet-user[12444]: (/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 19 08:37:27 node-1 puppet-user[12444]: Finished catalog run in 0.05 seconds
Oct 19 08:37:28 node-1 puppet-user[12912]: (Scope(Class[main])) MODULAR: sync_time
Oct 19 08:37:28 node-1 puppet-user[12912]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 19 08:37:29 node-1 ntpdate[13328]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.399822 #9100] DEBUG -- : Trying to find block devices
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.399945 #9100] DEBUG -- : Found block device: sda
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.400006 #9100] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.400033 #9100] DEBUG -- : Trying to get list of physical devices
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.400198 #9100] DEBUG -- : Getting udev properties for device: sda
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.402151 #9100] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Oct 19 08:37:32 node-1 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5801", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.402179 #9100] DEBUG -- : Trying to find out if device sda is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.402224 #9100] DEBUG -- : Device sda removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.402240 #9100] DEBUG -- : Device sda seems to be appropriate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.402728 #9100] DEBUG -- : Getting udev properties for device: dm-0
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.404554 #9100] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-k65UZpOTP5WAKm7WWUZ2uzAfiS2QMaINgwZk2HA2D2tglBKZi94YMhdeDtS7HzXf /dev/disk/by-uuid/53e6aa59-2f66-4b2b-a943-ad967b946c39 /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-k65UZpOTP5WAKm7WWUZ2uzAfiS2QMaINgwZk2HA2D2tglBKZi94YMhdeDtS7HzXf", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"53e6aa59-2f66-4b2b-a943-ad967b946c39", "ID_FS_UUID_ENC"=>"53e6aa59-2f66-4b2b-a943-ad967b946c39", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70741", "nomdmonddf"=>"1", "nomd
Oct 19 08:37:32 node-1 nailgun-agent: monisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.404591 #9100] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.404621 #9100] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.404635 #9100] DEBUG -- : Device dm-0 seems to be appropriate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.404650 #9100] DEBUG -- : Getting udev properties for device: dm-1
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.406814 #9100] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-QOWLcH0NWrCVxKb2EQ7Iv3aGlDOuITuX1A6JkIyKzcKDDpDybozgH0yiba6ymdmo /dev/disk/by-uuid/f2a45149-16bb-4f27-bff4-e35d0f01967f /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-QOWLcH0NWrCVxKb2EQ7Iv3aGlDOuITuX1A6JkIyKzcKDDpDybozgH0yiba6ymdmo", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f2a45149-16bb-4f27-bff4-e35d0f01967f", "ID_FS_UUID_ENC"=>"f2a45149-16bb-4f27-bff4-e35d0f01967f", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34
Oct 19 08:37:32 node-1 nailgun-agent: 6", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.406879 #9100] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.406909 #9100] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.406923 #9100] DEBUG -- : Device dm-1 seems to be appropriate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.406939 #9100] DEBUG -- : Getting udev properties for device: dm-2
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.408807 #9100] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-VGC3rIk6lRb7sfZ1CD3gfEefUQlupPcGmWY7Edl2DrCOa15fgcwTKyFakNMVU1i1 /dev/disk/by-uuid/268bb8f2-9332-41bb-9ab0-6477a6d2c7c6 /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-VGC3rIk6lRb7sfZ1CD3gfEefUQlupPcGmWY7Edl2DrCOa15fgcwTKyFakNMVU1i1", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"268bb8f2-9332-41bb-9ab0-6477a6d2c7c6", "ID_FS_UUID_ENC"=>"268bb8f2-9332-41bb-9ab0-6477a6d2c7c6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1044", "nomdmondd
Oct 19 08:37:32 node-1 nailgun-agent: f"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.408846 #9100] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.408888 #9100] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.408903 #9100] DEBUG -- : Device dm-2 seems to be appropriate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.408927 #9100] DEBUG -- : Getting udev properties for device: dm-3
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.410652 #9100] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-d0ZWVpjm4q6wJemfj28mvEVdRMUJDbwU9kGVpKXB5nHMM8tdAWcMx3cWb9ChscnW /dev/disk/by-uuid/d1e5cf29-1a46-48ba-9bbe-a0f707217464 /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-d0ZWVpjm4q6wJemfj28mvEVdRMUJDbwU9kGVpKXB5nHMM8tdAWcMx3cWb9ChscnW", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d1e5cf29-1a46-48ba-9bbe-a0f707217464", "ID_FS_UUID_ENC"=>"d1e5cf29-1a46-48ba-9bbe-a0f707217464", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9985", "nomdmonddf"=>"1", "
Oct 19 08:37:32 node-1 nailgun-agent: nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.410707 #9100] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.410737 #9100] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.410752 #9100] DEBUG -- : Device dm-3 seems to be appropriate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.410775 #9100] DEBUG -- : Getting udev properties for device: dm-4
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.412650 #9100] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-9gX8PvXBNRUnDNEyZPi2RGkg2NwrMS9dTkQgEa2HdoRuxaby4ESMmXRvq8DzsRZY /dev/disk/by-uuid/d29e9f03-d2a4-4797-ba7f-617d312250f1 /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-9gX8PvXBNRUnDNEyZPi2RGkg2NwrMS9dTkQgEa2HdoRuxaby4ESMmXRvq8DzsRZY", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d29e9f03-d2a4-4797-ba7f-617d312250f1", "ID_FS_UUID_ENC"=>"d29e9f03-d2a4-4797-ba7f-617d312250f1", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11779", "nomdmonddf"=>"1", "nomd
Oct 19 08:37:32 node-1 nailgun-agent: monisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.412691 #9100] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.412739 #9100] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.412753 #9100] DEBUG -- : Device dm-4 seems to be appropriate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.412769 #9100] DEBUG -- : Getting udev properties for device: dm-5
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.414567 #9100] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-9gX8PvXBNRUnDNEyZPi2RGkg2NwrMS9dxPMRZ914a5Lp9BOOxdemclBdgRJSo3uM /dev/disk/by-uuid/b1bceb3a-70ab-4e7d-be84-ad85b0b12d1d /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-9gX8PvXBNRUnDNEyZPi2RGkg2NwrMS9dxPMRZ914a5Lp9BOOxdemclBdgRJSo3uM", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"b1bceb3a-70ab-4e7d-be84-ad85b0b12d1d", "ID_FS_UUID_ENC"=>"b1bceb3a-70ab-4e7d-be84-ad85b0b12d1d", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12364", "nomdmonddf"=>"1", "nomdmonisw"
Oct 19 08:37:32 node-1 nailgun-agent: =>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.414601 #9100] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.414645 #9100] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.414658 #9100] DEBUG -- : Device dm-5 seems to be appropriate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.414708 #9100] DEBUG -- : Getting udev properties for device: ram0
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.416589 #9100] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83993", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.416613 #9100] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.416655 #9100] DEBUG -- : Device ram0 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.416676 #9100] DEBUG -- : Getting udev properties for device: ram1
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.418455 #9100] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84008", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.418480 #9100] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.418515 #9100] DEBUG -- : Device ram1 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.418535 #9100] DEBUG -- : Getting udev properties for device: ram2
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.420199 #9100] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84112", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.420224 #9100] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.420292 #9100] DEBUG -- : Device ram2 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.420312 #9100] DEBUG -- : Getting udev properties for device: ram3
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.421983 #9100] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84131", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.422007 #9100] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.422054 #9100] DEBUG -- : Device ram3 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.422074 #9100] DEBUG -- : Getting udev properties for device: ram4
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.428641 #9100] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84146", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.428671 #9100] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.428707 #9100] DEBUG -- : Device ram4 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.428727 #9100] DEBUG -- : Getting udev properties for device: ram5
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.430654 #9100] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84160", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.430679 #9100] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.430715 #9100] DEBUG -- : Device ram5 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.430735 #9100] DEBUG -- : Getting udev properties for device: ram6
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.432257 #9100] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84175", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.432282 #9100] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.432317 #9100] DEBUG -- : Device ram6 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.432336 #9100] DEBUG -- : Getting udev properties for device: ram7
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.433826 #9100] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84187", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.433874 #9100] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.433909 #9100] DEBUG -- : Device ram7 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.433928 #9100] DEBUG -- : Getting udev properties for device: ram8
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.435402 #9100] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84200", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.435429 #9100] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.435506 #9100] DEBUG -- : Device ram8 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.435526 #9100] DEBUG -- : Getting udev properties for device: ram9
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.437057 #9100] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84213", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.437083 #9100] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.437116 #9100] DEBUG -- : Device ram9 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.437165 #9100] DEBUG -- : Getting udev properties for device: loop0
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.438905 #9100] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83910", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.438930 #9100] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.438961 #9100] DEBUG -- : Device loop0 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.438981 #9100] DEBUG -- : Getting udev properties for device: loop1
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.440647 #9100] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83920", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.440673 #9100] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.440704 #9100] DEBUG -- : Device loop1 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.440724 #9100] DEBUG -- : Getting udev properties for device: loop2
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.442723 #9100] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83927", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.442747 #9100] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.442785 #9100] DEBUG -- : Device loop2 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.442805 #9100] DEBUG -- : Getting udev properties for device: loop3
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.444480 #9100] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83934", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.444506 #9100] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.444544 #9100] DEBUG -- : Device loop3 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.444564 #9100] DEBUG -- : Getting udev properties for device: loop4
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.446525 #9100] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83942", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.446549 #9100] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.446587 #9100] DEBUG -- : Device loop4 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.446606 #9100] DEBUG -- : Getting udev properties for device: loop5
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.448159 #9100] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83954", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.448222 #9100] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.448264 #9100] DEBUG -- : Device loop5 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.448283 #9100] DEBUG -- : Getting udev properties for device: loop6
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.449713 #9100] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83966", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.449738 #9100] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.449800 #9100] DEBUG -- : Device loop6 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.449819 #9100] DEBUG -- : Getting udev properties for device: loop7
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.451565 #9100] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83977", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.451590 #9100] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.451622 #9100] DEBUG -- : Device loop7 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.451681 #9100] DEBUG -- : Getting udev properties for device: ram10
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.453183 #9100] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84021", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.453210 #9100] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.453243 #9100] DEBUG -- : Device ram10 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.453262 #9100] DEBUG -- : Getting udev properties for device: ram11
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.455016 #9100] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84034", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.455040 #9100] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.455072 #9100] DEBUG -- : Device ram11 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.455092 #9100] DEBUG -- : Getting udev properties for device: ram12
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.456829 #9100] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84051", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.456853 #9100] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.456888 #9100] DEBUG -- : Device ram12 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.456907 #9100] DEBUG -- : Getting udev properties for device: ram13
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.458620 #9100] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84069", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.458645 #9100] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.458680 #9100] DEBUG -- : Device ram13 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.458699 #9100] DEBUG -- : Getting udev properties for device: ram14
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.460286 #9100] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84084", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.460311 #9100] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.460349 #9100] DEBUG -- : Device ram14 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.460368 #9100] DEBUG -- : Getting udev properties for device: ram15
Oct 19 08:37:32 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462172 #9100] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84098", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462199 #9100] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462236 #9100] DEBUG -- : Device ram15 removable parameter: "0"
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462273 #9100] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462288 #9100] DEBUG -- : Block device seems to be physical data storage: sda
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462336 #9100] DEBUG -- : Found block device: dm-0
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462350 #9100] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462363 #9100] DEBUG -- : Found block device: dm-1
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462373 #9100] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462382 #9100] DEBUG -- : Found block device: dm-2
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462418 #9100] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462428 #9100] DEBUG -- : Found block device: dm-3
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462437 #9100] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462446 #9100] DEBUG -- : Found block device: dm-4
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462456 #9100] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462464 #9100] DEBUG -- : Found block device: dm-5
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462474 #9100] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462483 #9100] DEBUG -- : Found block device: ram0
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462492 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462501 #9100] DEBUG -- : Found block device: ram1
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462533 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462542 #9100] DEBUG -- : Found block device: ram2
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462552 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462560 #9100] DEBUG -- : Found block device: ram3
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462569 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462577 #9100] DEBUG -- : Found block device: ram4
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462586 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462594 #9100] DEBUG -- : Found block device: ram5
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462604 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462612 #9100] DEBUG -- : Found block device: ram6
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462651 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462659 #9100] DEBUG -- : Found block device: ram7
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462670 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462679 #9100] DEBUG -- : Found block device: ram8
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462689 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462697 #9100] DEBUG -- : Found block device: ram9
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462707 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462715 #9100] DEBUG -- : Found block device: loop0
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462725 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462733 #9100] DEBUG -- : Found block device: loop1
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462789 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462799 #9100] DEBUG -- : Found block device: loop2
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462809 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462817 #9100] DEBUG -- : Found block device: loop3
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462826 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462835 #9100] DEBUG -- : Found block device: loop4
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462844 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462852 #9100] DEBUG -- : Found block device: loop5
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462861 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462916 #9100] DEBUG -- : Found block device: loop6
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462926 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462935 #9100] DEBUG -- : Found block device: loop7
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462945 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462953 #9100] DEBUG -- : Found block device: ram10
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462962 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462970 #9100] DEBUG -- : Found block device: ram11
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462979 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.462987 #9100] DEBUG -- : Found block device: ram12
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463045 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463054 #9100] DEBUG -- : Found block device: ram13
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463065 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463073 #9100] DEBUG -- : Found block device: ram14
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463082 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463090 #9100] DEBUG -- : Found block device: ram15
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463099 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.463128 #9100] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.535192 #9100] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 19 08:37:32 node-1 nailgun-agent: D, [2016-10-19T08:37:32.535241 #9100] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 19 08:37:35 node-1 ntpdate[13328]: adjust time server 10.20.0.2 offset -0.171829 sec
Oct 19 08:37:35 node-1 puppet-user[12912]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 19 08:37:35 node-1 puppet-user[12912]: Finished catalog run in 6.16 seconds
Oct 19 08:37:39 node-1 puppet-user[13690]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 19 08:37:40 node-1 puppet-user[13690]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 19 08:37:40 node-1 puppet-user[13690]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 19 08:37:40 node-1 puppet-user[13690]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Oct 19 08:37:40 node-1 puppet-user[13690]: Finished catalog run in 0.07 seconds
Oct 19 08:37:41 node-1 puppet-user[14143]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 19 08:37:41 node-1 puppet-user[14143]: Compiled catalog for node-1.domain.tld in environment production in 0.42 seconds
Oct 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/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 19 08:37:42 node-1 puppet-user[14143]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 19 08:37:42 node-1 puppet-user[14143]: Finished catalog run in 0.73 seconds
Oct 19 08:37:44 node-1 puppet-user[14643]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 19 08:37:44 node-1 puppet-user[14643]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct 19 08:37:44 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.469896 #9100] DEBUG -- : Trying to find block devices
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.469978 #9100] DEBUG -- : Found block device: sda
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470004 #9100] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470022 #9100] DEBUG -- : Block device seems to be physical data storage: sda
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470042 #9100] DEBUG -- : Found block device: dm-0
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470054 #9100] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470065 #9100] DEBUG -- : Found block device: dm-1
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470094 #9100] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470104 #9100] DEBUG -- : Found block device: dm-2
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470114 #9100] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470123 #9100] DEBUG -- : Found block device: dm-3
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470132 #9100] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470141 #9100] DEBUG -- : Found block device: dm-4
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470150 #9100] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470158 #9100] DEBUG -- : Found block device: dm-5
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470167 #9100] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470176 #9100] DEBUG -- : Found block device: ram0
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470212 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470222 #9100] DEBUG -- : Found block device: ram1
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470231 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470240 #9100] DEBUG -- : Found block device: ram2
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470249 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470257 #9100] DEBUG -- : Found block device: ram3
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470265 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470274 #9100] DEBUG -- : Found block device: ram4
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470282 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470290 #9100] DEBUG -- : Found block device: ram5
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470300 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470327 #9100] DEBUG -- : Found block device: ram6
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470336 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470344 #9100] DEBUG -- : Found block device: ram7
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470353 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470362 #9100] DEBUG -- : Found block device: ram8
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470371 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470379 #9100] DEBUG -- : Found block device: ram9
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470388 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470397 #9100] DEBUG -- : Found block device: loop0
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470405 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470413 #9100] DEBUG -- : Found block device: loop1
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470441 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470450 #9100] DEBUG -- : Found block device: loop2
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470459 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470467 #9100] DEBUG -- : Found block device: loop3
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470476 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470484 #9100] DEBUG -- : Found block device: loop4
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470494 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470501 #9100] DEBUG -- : Found block device: loop5
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470510 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470519 #9100] DEBUG -- : Found block device: loop6
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470548 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470557 #9100] DEBUG -- : Found block device: loop7
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470566 #9100] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470574 #9100] DEBUG -- : Found block device: ram10
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470583 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470592 #9100] DEBUG -- : Found block device: ram11
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470601 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470609 #9100] DEBUG -- : Found block device: ram12
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470617 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470625 #9100] DEBUG -- : Found block device: ram13
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470634 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470657 #9100] DEBUG -- : Found block device: ram14
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470666 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470675 #9100] DEBUG -- : Found block device: ram15
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470684 #9100] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.470712 #9100] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct 19 08:37:44 node-1 nailgun-agent: D, [2016-10-19T08:37:44.624556 #9100] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 19 08:37:44 node-1 nailgun-agent: I, [2016-10-19T08:37:44.624717 #9100]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 19 08:37:47 node-1 puppet-user[14643]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 19 08:38:01 node-1 CRON[16322]: (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 19 08:38:15 node-1 puppet-user[14643]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 19 08:38:15 node-1 puppet-user[14643]: Finished catalog run in 30.71 seconds
Oct 19 08:38:17 node-1 puppet-user[17184]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 19 08:38:17 node-1 puppet-user[17184]: Compiled catalog for node-1.domain.tld in environment production in 0.55 seconds
Oct 19 08:38:17 node-1 puppet-user[17184]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 19 08:38:17 node-1 puppet-user[17184]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 19 08:38:17 node-1 puppet-user[17184]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 19 08:38:17 node-1 puppet-user[17184]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 19 08:38:17 node-1 puppet-user[17184]: Finished catalog run in 0.10 seconds
Oct 19 08:38:19 node-1 puppet-user[17642]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 19 08:38:20 node-1 puppet-user[17642]: Compiled catalog for node-1.domain.tld in environment production in 0.81 seconds
Oct 19 08:38:20 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 19 08:38:20 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 19 08:38:20 node-1 crontab[18083]: (root) LIST (root)
Oct 19 08:38:20 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 19 08:38:21 node-1 crontab[18084]: (root) REPLACE (root)
Oct 19 08:38:22 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 19 08:38:22 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 19 08:38:23 node-1 puppet-user[17642]: (/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 19 08:38:23 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 08:38:23 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 19 08:38:25 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:25 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:25 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:25 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:38:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:30 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:30 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:30 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:30 node-1 multipathd: uevent trigger error
<27>Oct 19 08:39:30 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:10 node-1 ntpdate[1554]: no servers can be used, exiting
<27>Oct 19 08:40:41 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:41 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:41 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:41 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:41 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:55 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:55 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:55 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:55 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:55 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:58 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:58 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:58 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:58 node-1 multipathd: uevent trigger error
<27>Oct 19 08:40:58 node-1 multipathd: uevent trigger error
<27>Oct 19 08:41:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:41:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:41:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:41:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:41:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:01 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:01 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:01 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:01 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:03 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 08:42:03 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 08:42:09 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 08:42:09 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 08:42:15 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 08:42:21 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 08:42:21 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 08:42:28 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:28 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:28 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:28 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:28 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:30 node-1 ntpdate[19536]: the NTP socket is in use, exiting
<27>Oct 19 08:42:30 node-1 ntpdate[19588]: the NTP socket is in use, exiting
<27>Oct 19 08:42:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:40 node-1 multipathd: uevent trigger error
<129>Oct 19 08:42:42 node-1 haproxy[21991]: 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 19 08:42:43 node-1 haproxy[21998]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:42:44 node-1 haproxy[21998]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:42:44 node-1 haproxy[21998]: proxy mysqld has no server available!
<27>Oct 19 08:42:45 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:46 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:46 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:46 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:46 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:49 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:49 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:49 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:49 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:49 node-1 multipathd: uevent trigger error
<129>Oct 19 08:42:51 node-1 haproxy[24556]: 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 19 08:42:52 node-1 haproxy[24560]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:42:52 node-1 haproxy[24560]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:42:52 node-1 haproxy[24560]: proxy mysqld has no server available!
<129>Oct 19 08:42:52 node-1 haproxy[24560]: 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 19 08:42:53 node-1 haproxy[24560]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:42:53 node-1 haproxy[24560]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:42:53 node-1 haproxy[24560]: proxy object-storage has no server available!
<27>Oct 19 08:42:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:42:54 node-1 multipathd: uevent trigger error
<129>Oct 19 08:42:57 node-1 haproxy[25909]: 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 19 08:42:57 node-1 haproxy[25909]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:42:57 node-1 haproxy[25909]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:42:57 node-1 haproxy[25909]: proxy neutron has no server available!
<129>Oct 19 08:42:57 node-1 haproxy[25909]: 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 19 08:42:57 node-1 haproxy[25909]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:42:58 node-1 haproxy[25918]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:42:58 node-1 haproxy[25918]: proxy mysqld has no server available!
<129>Oct 19 08:42:58 node-1 haproxy[25918]: 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 19 08:42:58 node-1 haproxy[25918]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:42:58 node-1 haproxy[25918]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:42:58 node-1 haproxy[25918]: proxy object-storage has no server available!
<27>Oct 19 08:43:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:00 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:02 node-1 haproxy[27288]: 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 19 08:43:02 node-1 haproxy[27288]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:02 node-1 haproxy[27288]: Server keystone-1/node-4 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 19 08:43:02 node-1 haproxy[27288]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:03 node-1 haproxy[27292]: 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 19 08:43:03 node-1 haproxy[27292]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:03 node-1 haproxy[27292]: Server keystone-2/node-4 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 19 08:43:03 node-1 haproxy[27292]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:03 node-1 haproxy[27292]: 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 19 08:43:03 node-1 haproxy[27292]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:03 node-1 haproxy[27292]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:03 node-1 haproxy[27292]: proxy neutron has no server available!
<129>Oct 19 08:43:03 node-1 haproxy[27292]: 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 19 08:43:04 node-1 haproxy[27292]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:04 node-1 haproxy[27292]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:04 node-1 haproxy[27292]: proxy mysqld has no server available!
<129>Oct 19 08:43:04 node-1 haproxy[27292]: 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 19 08:43:04 node-1 haproxy[27292]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:04 node-1 haproxy[27292]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:04 node-1 haproxy[27292]: proxy object-storage has no server available!
<27>Oct 19 08:43:06 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:06 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:06 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:06 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:06 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:06 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:08 node-1 haproxy[28772]: 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 19 08:43:08 node-1 haproxy[28772]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:08 node-1 haproxy[28772]: Server keystone-1/node-4 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 19 08:43:08 node-1 haproxy[28772]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:08 node-1 haproxy[28772]: 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 19 08:43:08 node-1 haproxy[28772]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:08 node-1 haproxy[28772]: Server keystone-2/node-4 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 19 08:43:08 node-1 haproxy[28772]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:08 node-1 haproxy[28772]: 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 19 08:43:08 node-1 haproxy[28772]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:09 node-1 haproxy[28776]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:09 node-1 haproxy[28776]: proxy neutron has no server available!
<129>Oct 19 08:43:09 node-1 haproxy[28776]: 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 19 08:43:09 node-1 haproxy[28776]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:09 node-1 haproxy[28776]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:09 node-1 haproxy[28776]: proxy mysqld has no server available!
<129>Oct 19 08:43:09 node-1 haproxy[28776]: 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 19 08:43:09 node-1 haproxy[28776]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:09 node-1 haproxy[28776]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:09 node-1 haproxy[28776]: proxy object-storage has no server available!
<129>Oct 19 08:43:09 node-1 haproxy[28776]: 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 19 08:43:09 node-1 haproxy[28776]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:10 node-1 haproxy[28776]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:10 node-1 haproxy[28776]: proxy aodh has no server available!
<27>Oct 19 08:43:11 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:11 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:11 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:11 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:11 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:13 node-1 haproxy[30146]: 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 19 08:43:13 node-1 haproxy[30146]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:13 node-1 haproxy[30146]: Server keystone-1/node-4 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 19 08:43:13 node-1 haproxy[30146]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:13 node-1 haproxy[30146]: 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 19 08:43:13 node-1 haproxy[30146]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:14 node-1 haproxy[30150]: Server keystone-2/node-4 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 19 08:43:14 node-1 haproxy[30150]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:14 node-1 haproxy[30150]: 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 19 08:43:14 node-1 haproxy[30150]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:14 node-1 haproxy[30150]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:14 node-1 haproxy[30150]: proxy neutron has no server available!
<129>Oct 19 08:43:14 node-1 haproxy[30150]: 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 19 08:43:14 node-1 haproxy[30150]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:14 node-1 haproxy[30150]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:14 node-1 haproxy[30150]: proxy mysqld has no server available!
<129>Oct 19 08:43:14 node-1 haproxy[30150]: 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 19 08:43:14 node-1 haproxy[30150]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:14 node-1 haproxy[30150]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:14 node-1 haproxy[30150]: proxy object-storage has no server available!
<129>Oct 19 08:43:15 node-1 haproxy[30150]: 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 19 08:43:15 node-1 haproxy[30150]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:15 node-1 haproxy[30150]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:15 node-1 haproxy[30150]: proxy aodh has no server available!
<129>Oct 19 08:43:15 node-1 haproxy[30150]: 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 19 08:43:15 node-1 haproxy[30150]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:15 node-1 haproxy[30150]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:15 node-1 haproxy[30150]: proxy ceilometer has no server available!
<27>Oct 19 08:43:16 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:16 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:16 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:16 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:19 node-1 haproxy[31687]: 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 19 08:43:19 node-1 haproxy[31687]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:19 node-1 haproxy[31687]: Server keystone-1/node-4 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 19 08:43:19 node-1 haproxy[31687]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:19 node-1 haproxy[31687]: 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 19 08:43:19 node-1 haproxy[31687]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:19 node-1 haproxy[31687]: Server keystone-2/node-4 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 19 08:43:19 node-1 haproxy[31687]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:19 node-1 haproxy[31687]: 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 19 08:43:19 node-1 haproxy[31687]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:19 node-1 haproxy[31687]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:19 node-1 haproxy[31687]: proxy neutron has no server available!
<129>Oct 19 08:43:19 node-1 haproxy[31687]: 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 19 08:43:19 node-1 haproxy[31687]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:20 node-1 haproxy[31692]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:20 node-1 haproxy[31692]: proxy mysqld has no server available!
<129>Oct 19 08:43:20 node-1 haproxy[31692]: 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 19 08:43:20 node-1 haproxy[31692]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:20 node-1 haproxy[31692]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:20 node-1 haproxy[31692]: proxy object-storage has no server available!
<129>Oct 19 08:43:20 node-1 haproxy[31692]: 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 19 08:43:20 node-1 haproxy[31692]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:20 node-1 haproxy[31692]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:20 node-1 haproxy[31692]: proxy aodh has no server available!
<129>Oct 19 08:43:20 node-1 haproxy[31692]: 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 19 08:43:20 node-1 haproxy[31692]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:20 node-1 haproxy[31692]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:20 node-1 haproxy[31692]: proxy ceilometer has no server available!
<27>Oct 19 08:43:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:22 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:24 node-1 haproxy[564]: 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 19 08:43:24 node-1 haproxy[564]: 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 19 08:43:24 node-1 haproxy[564]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:24 node-1 haproxy[564]: Server keystone-1/node-4 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 19 08:43:24 node-1 haproxy[564]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:24 node-1 haproxy[564]: 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 19 08:43:24 node-1 haproxy[564]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:25 node-1 haproxy[568]: Server keystone-2/node-4 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 19 08:43:25 node-1 haproxy[568]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:25 node-1 haproxy[568]: 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 19 08:43:25 node-1 haproxy[568]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:25 node-1 haproxy[568]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:25 node-1 haproxy[568]: proxy neutron has no server available!
<129>Oct 19 08:43:25 node-1 haproxy[568]: 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 19 08:43:25 node-1 haproxy[568]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:25 node-1 haproxy[568]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:25 node-1 haproxy[568]: proxy mysqld has no server available!
<129>Oct 19 08:43:25 node-1 haproxy[568]: 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 19 08:43:25 node-1 haproxy[568]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:25 node-1 haproxy[568]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:25 node-1 haproxy[568]: proxy object-storage has no server available!
<129>Oct 19 08:43:25 node-1 haproxy[568]: 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 19 08:43:25 node-1 haproxy[568]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:26 node-1 haproxy[568]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:26 node-1 haproxy[568]: proxy aodh has no server available!
<129>Oct 19 08:43:26 node-1 haproxy[568]: 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 19 08:43:26 node-1 haproxy[568]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:26 node-1 haproxy[568]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:26 node-1 haproxy[568]: proxy ceilometer has no server available!
<27>Oct 19 08:43:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:27 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:29 node-1 haproxy[1955]: 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 19 08:43:30 node-1 haproxy[1959]: 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 19 08:43:30 node-1 haproxy[1959]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:30 node-1 haproxy[1959]: Server keystone-1/node-4 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 19 08:43:30 node-1 haproxy[1959]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:30 node-1 haproxy[1959]: 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 19 08:43:30 node-1 haproxy[1959]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:30 node-1 haproxy[1959]: Server keystone-2/node-4 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 19 08:43:30 node-1 haproxy[1959]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:30 node-1 haproxy[1959]: 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 19 08:43:30 node-1 haproxy[1959]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:30 node-1 haproxy[1959]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:30 node-1 haproxy[1959]: proxy glance-api has no server available!
<129>Oct 19 08:43:30 node-1 haproxy[1959]: 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 19 08:43:30 node-1 haproxy[1959]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:30 node-1 haproxy[1959]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:30 node-1 haproxy[1959]: proxy glance-glare has no server available!
<129>Oct 19 08:43:30 node-1 haproxy[1959]: 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 19 08:43:30 node-1 haproxy[1959]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:30 node-1 haproxy[1959]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:30 node-1 haproxy[1959]: proxy neutron has no server available!
<129>Oct 19 08:43:30 node-1 haproxy[1959]: 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 19 08:43:31 node-1 haproxy[1959]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:31 node-1 haproxy[1959]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:31 node-1 haproxy[1959]: proxy glance-registry has no server available!
<129>Oct 19 08:43:31 node-1 haproxy[1959]: 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 19 08:43:31 node-1 haproxy[1959]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:31 node-1 haproxy[1959]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:31 node-1 haproxy[1959]: proxy mysqld has no server available!
<129>Oct 19 08:43:31 node-1 haproxy[1959]: 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 19 08:43:31 node-1 haproxy[1959]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:31 node-1 haproxy[1959]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:31 node-1 haproxy[1959]: proxy object-storage has no server available!
<129>Oct 19 08:43:31 node-1 haproxy[1959]: 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 19 08:43:31 node-1 haproxy[1959]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:31 node-1 haproxy[1959]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:31 node-1 haproxy[1959]: proxy aodh has no server available!
<129>Oct 19 08:43:31 node-1 haproxy[1959]: 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 19 08:43:31 node-1 haproxy[1959]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:31 node-1 haproxy[1959]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:31 node-1 haproxy[1959]: proxy ceilometer has no server available!
<27>Oct 19 08:43:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:33 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:35 node-1 haproxy[3337]: 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 19 08:43:35 node-1 haproxy[3337]: 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 19 08:43:35 node-1 haproxy[3337]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:36 node-1 haproxy[3341]: Server keystone-1/node-4 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 19 08:43:36 node-1 haproxy[3341]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:36 node-1 haproxy[3341]: 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 19 08:43:36 node-1 haproxy[3341]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:36 node-1 haproxy[3341]: Server keystone-2/node-4 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 19 08:43:36 node-1 haproxy[3341]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:36 node-1 haproxy[3341]: 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 19 08:43:36 node-1 haproxy[3341]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:36 node-1 haproxy[3341]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:36 node-1 haproxy[3341]: proxy nova-api has no server available!
<129>Oct 19 08:43:36 node-1 haproxy[3341]: 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 19 08:43:36 node-1 haproxy[3341]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:36 node-1 haproxy[3341]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:36 node-1 haproxy[3341]: proxy nova-metadata-api has no server available!
<129>Oct 19 08:43:36 node-1 haproxy[3341]: 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 19 08:43:36 node-1 haproxy[3341]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:36 node-1 haproxy[3341]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:36 node-1 haproxy[3341]: proxy glance-api has no server available!
<129>Oct 19 08:43:36 node-1 haproxy[3341]: 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 19 08:43:36 node-1 haproxy[3341]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:36 node-1 haproxy[3341]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:36 node-1 haproxy[3341]: proxy glance-glare has no server available!
<129>Oct 19 08:43:36 node-1 haproxy[3341]: 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 19 08:43:36 node-1 haproxy[3341]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:36 node-1 haproxy[3341]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:36 node-1 haproxy[3341]: proxy neutron has no server available!
<129>Oct 19 08:43:36 node-1 haproxy[3341]: 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 19 08:43:36 node-1 haproxy[3341]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:37 node-1 haproxy[3341]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:37 node-1 haproxy[3341]: proxy glance-registry has no server available!
<129>Oct 19 08:43:37 node-1 haproxy[3341]: 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 19 08:43:37 node-1 haproxy[3341]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:37 node-1 haproxy[3341]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:37 node-1 haproxy[3341]: proxy mysqld has no server available!
<129>Oct 19 08:43:37 node-1 haproxy[3341]: 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 19 08:43:37 node-1 haproxy[3341]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:37 node-1 haproxy[3341]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:37 node-1 haproxy[3341]: proxy object-storage has no server available!
<129>Oct 19 08:43:37 node-1 haproxy[3341]: 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 19 08:43:37 node-1 haproxy[3341]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:37 node-1 haproxy[3341]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:37 node-1 haproxy[3341]: proxy aodh has no server available!
<129>Oct 19 08:43:37 node-1 haproxy[3341]: 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 19 08:43:37 node-1 haproxy[3341]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:37 node-1 haproxy[3341]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:37 node-1 haproxy[3341]: proxy ceilometer has no server available!
<129>Oct 19 08:43:37 node-1 haproxy[3341]: 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 19 08:43:37 node-1 haproxy[3341]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:37 node-1 haproxy[3341]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:37 node-1 haproxy[3341]: proxy nova-novncproxy has no server available!
<27>Oct 19 08:43:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:39 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:41 node-1 haproxy[4696]: 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 19 08:43:41 node-1 haproxy[4696]: 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 19 08:43:41 node-1 haproxy[4696]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:41 node-1 haproxy[4696]: Server keystone-1/node-4 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 19 08:43:41 node-1 haproxy[4696]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:41 node-1 haproxy[4696]: 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 19 08:43:41 node-1 haproxy[4696]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:41 node-1 haproxy[4696]: Server keystone-2/node-4 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 19 08:43:41 node-1 haproxy[4696]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:41 node-1 haproxy[4696]: 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 19 08:43:41 node-1 haproxy[4696]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:41 node-1 haproxy[4696]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:41 node-1 haproxy[4696]: proxy nova-api has no server available!
<129>Oct 19 08:43:41 node-1 haproxy[4696]: 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 19 08:43:41 node-1 haproxy[4696]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:41 node-1 haproxy[4696]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:41 node-1 haproxy[4696]: proxy nova-metadata-api has no server available!
<129>Oct 19 08:43:41 node-1 haproxy[4696]: 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 19 08:43:42 node-1 haproxy[4700]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy cinder-api has no server available!
<129>Oct 19 08:43:42 node-1 haproxy[4700]: 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 19 08:43:42 node-1 haproxy[4700]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy glance-api has no server available!
<129>Oct 19 08:43:42 node-1 haproxy[4700]: 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 19 08:43:42 node-1 haproxy[4700]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy glance-glare has no server available!
<129>Oct 19 08:43:42 node-1 haproxy[4700]: 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 19 08:43:42 node-1 haproxy[4700]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy neutron has no server available!
<129>Oct 19 08:43:42 node-1 haproxy[4700]: 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 19 08:43:42 node-1 haproxy[4700]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy glance-registry has no server available!
<129>Oct 19 08:43:42 node-1 haproxy[4700]: 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 19 08:43:42 node-1 haproxy[4700]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy mysqld has no server available!
<129>Oct 19 08:43:42 node-1 haproxy[4700]: 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 19 08:43:42 node-1 haproxy[4700]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy object-storage has no server available!
<129>Oct 19 08:43:42 node-1 haproxy[4700]: 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 19 08:43:42 node-1 haproxy[4700]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:42 node-1 haproxy[4700]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:42 node-1 haproxy[4700]: proxy aodh has no server available!
<129>Oct 19 08:43:43 node-1 haproxy[4700]: 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 19 08:43:43 node-1 haproxy[4700]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:43 node-1 haproxy[4700]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:43 node-1 haproxy[4700]: proxy ceilometer has no server available!
<129>Oct 19 08:43:43 node-1 haproxy[4700]: 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 19 08:43:43 node-1 haproxy[4700]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:43 node-1 haproxy[4700]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:43 node-1 haproxy[4700]: proxy nova-novncproxy has no server available!
<27>Oct 19 08:43:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:44 node-1 multipathd: uevent trigger error
<129>Oct 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:47 node-1 haproxy[6059]: Server keystone-1/node-4 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 19 08:43:47 node-1 haproxy[6059]: proxy keystone-1 has no server available!
<129>Oct 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:47 node-1 haproxy[6059]: Server keystone-2/node-4 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 19 08:43:47 node-1 haproxy[6059]: proxy keystone-2 has no server available!
<129>Oct 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:47 node-1 haproxy[6059]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:47 node-1 haproxy[6059]: proxy nova-api has no server available!
<129>Oct 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:47 node-1 haproxy[6059]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:47 node-1 haproxy[6059]: proxy nova-metadata-api has no server available!
<129>Oct 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:47 node-1 haproxy[6059]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:47 node-1 haproxy[6059]: proxy cinder-api has no server available!
<129>Oct 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:47 node-1 haproxy[6059]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:47 node-1 haproxy[6059]: proxy glance-api has no server available!
<129>Oct 19 08:43:47 node-1 haproxy[6059]: 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 19 08:43:47 node-1 haproxy[6059]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:47 node-1 haproxy[6059]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:47 node-1 haproxy[6059]: proxy glance-glare has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy neutron has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy glance-registry has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy mysqld has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy object-storage has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy aodh has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy ceilometer has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server heat-api/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy heat-api has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy heat-api-cfn has no server available!
<129>Oct 19 08:43:48 node-1 haproxy[6065]: 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 19 08:43:48 node-1 haproxy[6065]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:48 node-1 haproxy[6065]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:48 node-1 haproxy[6065]: proxy heat-api-cloudwatch has no server available!
<129>Oct 19 08:43:49 node-1 haproxy[6065]: 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 19 08:43:49 node-1 haproxy[6065]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 08:43:49 node-1 haproxy[6065]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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 19 08:43:49 node-1 haproxy[6065]: proxy nova-novncproxy has no server available!
<27>Oct 19 08:43:50 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:50 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:50 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:53 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:53 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:53 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:53 node-1 multipathd: uevent trigger error
<27>Oct 19 08:43:53 node-1 multipathd: uevent trigger error
<27>Oct 19 08:44:01 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 19 08:44:25 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 19 08:44:27 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 19 08:44:55 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 08:44:58 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 08:45:24 node-1 multipathd: uevent trigger error
<27>Oct 19 08:45:24 node-1 multipathd: uevent trigger error
<27>Oct 19 08:45:24 node-1 multipathd: uevent trigger error
<27>Oct 19 08:45:24 node-1 multipathd: uevent trigger error
<27>Oct 19 08:45:24 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:36 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:36 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:36 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:36 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:36 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:36 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:47:42 node-1 multipathd: uevent trigger error
<43>Oct 19 08:47:54 node-1 apache2_error [Wed Oct 19 08:47:53.011543 2016] [mpm_event:notice] [pid 13758:tid 139882059466624] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 19 08:47:54 node-1 apache2_error [Wed Oct 19 08:47:53.011690 2016] [core:notice] [pid 13758:tid 139882059466624] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 08:47:57 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 08:48:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:00 node-1 multipathd: uevent trigger error
<43>Oct 19 08:48:04 node-1 apache2_error [Wed Oct 19 08:47:56.112632 2016] [mpm_event:notice] [pid 13758:tid 139882059466624] AH00491: caught SIGTERM, shutting down
<43>Oct 19 08:48:04 node-1 apache2_error [Wed Oct 19 08:47:57.210502 2016] [mpm_worker:notice] [pid 14636:tid 140101257271168] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 19 08:48:04 node-1 apache2_error [Wed Oct 19 08:47:57.210524 2016] [core:notice] [pid 14636:tid 140101257271168] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 08:48:05 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:05 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:05 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:05 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:48:09 node-1 multipathd: uevent trigger error
<43>Oct 19 08:49:14 node-1 apache2_error [Wed Oct 19 08:49:11.510449 2016] [mpm_worker:notice] [pid 14636:tid 140101257271168] AH00295: caught SIGTERM, shutting down
<43>Oct 19 08:49:14 node-1 apache2_error [Wed Oct 19 08:49:12.265815 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 08:49:14 node-1 apache2_error [Wed Oct 19 08:49:12.265863 2016] [core:notice] [pid 28758:tid 140239875397504] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 19 08:50:04 node-1 apache2_error [Wed Oct 19 08:49:55.965588 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 08:50:04 node-1 apache2_error [Wed Oct 19 08:49:56.159636 2016] [mpm_worker:warn] [pid 28758:tid 140239875397504] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 08:50:04 node-1 apache2_error [Wed Oct 19 08:49:56.164545 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 08:50:04 node-1 apache2_error [Wed Oct 19 08:49:56.164572 2016] [core:notice] [pid 28758:tid 140239875397504] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 08:50:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:40 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:50:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 08:51:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:00 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:27 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:51:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:52:32 node-1 multipathd: uevent trigger error
<27>Oct 19 08:52:32 node-1 multipathd: uevent trigger error
<27>Oct 19 08:52:32 node-1 multipathd: uevent trigger error
<27>Oct 19 08:52:32 node-1 multipathd: uevent trigger error
<27>Oct 19 08:52:32 node-1 multipathd: uevent trigger error
<27>Oct 19 08:53:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:53:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:53:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:53:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:53:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:53:42 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 08:54:37 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:37 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:37 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:37 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:37 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:58 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:58 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:59 node-1 multipathd: uevent trigger error
<27>Oct 19 08:54:59 node-1 multipathd: uevent trigger error
<27>Oct 19 08:55:04 node-1 multipathd: uevent trigger error
<27>Oct 19 08:55:04 node-1 multipathd: uevent trigger error
<27>Oct 19 08:55:04 node-1 multipathd: uevent trigger error
<27>Oct 19 08:55:04 node-1 multipathd: uevent trigger error
<27>Oct 19 08:55:04 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 08:57:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:22 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:38 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:57:54 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:33 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:39 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:58:44 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:52 node-1 multipathd: uevent trigger error
<27>Oct 19 08:59:59 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Oct 19 08:59:59 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Oct 19 09:00:00 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Oct 19 09:00:00 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Oct 19 09:00:01 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Oct 19 09:00:01 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:01 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:01 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:01 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:01 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 09:00:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:46 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:46 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:46 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:46 node-1 multipathd: uevent trigger error
<27>Oct 19 09:00:46 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:04 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:04 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:04 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:04 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:04 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 09:03:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:03:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:02 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:02 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:02 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:02 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:02 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:06 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:06 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:06 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:06 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:11 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:11 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:11 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:11 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:22 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:22 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:23 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:23 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:23 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:23 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:04:29 node-1 multipathd: uevent trigger error
<27>Oct 19 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 09:06:20 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:20 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:20 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:20 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:20 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:37 node-1 multipathd: uevent trigger error
<27>Oct 19 09:06:37 node-1 multipathd: uevent trigger error
<11>Oct 19 09:06:49 node-1 liberasurecode[15261]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:49 node-1 liberasurecode[15261]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:49 node-1 liberasurecode[15261]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:49 node-1 liberasurecode[15261]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:49 node-1 liberasurecode[15289]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:49 node-1 liberasurecode[15289]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:49 node-1 liberasurecode[15289]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:49 node-1 liberasurecode[15289]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:51 node-1 liberasurecode[15697]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:51 node-1 liberasurecode[15697]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:51 node-1 liberasurecode[15697]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:51 node-1 liberasurecode[15697]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16228]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16228]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16228]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16228]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16264]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16264]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16264]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16264]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16317]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16317]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16317]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16317]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16417]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16417]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16417]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16417]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16431]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16431]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16431]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16431]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16447]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16447]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16447]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16447]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16463]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16463]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16463]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:06:56 node-1 liberasurecode[16463]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 09:07:13 node-1 liberasurecode[18971]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:07:13 node-1 liberasurecode[18971]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:07:13 node-1 liberasurecode[18971]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:07:13 node-1 liberasurecode[18971]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 19 09:07:22 node-1 multipathd: uevent trigger error
<27>Oct 19 09:07:23 node-1 multipathd: uevent trigger error
<27>Oct 19 09:07:23 node-1 multipathd: uevent trigger error
<27>Oct 19 09:07:23 node-1 multipathd: uevent trigger error
<27>Oct 19 09:07:23 node-1 multipathd: uevent trigger error
<43>Oct 19 09:08:16 node-1 apache2_error [Wed Oct 19 09:08:08.208862 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 09:08:16 node-1 apache2_error [Wed Oct 19 09:08:08.591668 2016] [mpm_worker:warn] [pid 28758:tid 140239875397504] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 09:08:16 node-1 apache2_error [Wed Oct 19 09:08:08.595706 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 09:08:16 node-1 apache2_error [Wed Oct 19 09:08:08.595740 2016] [core:notice] [pid 28758:tid 140239875397504] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 19 09:08:46 node-1 apache2_error [Wed Oct 19 09:08:45.303692 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 09:08:46 node-1 apache2_error [Wed Oct 19 09:08:45.496712 2016] [mpm_worker:warn] [pid 28758:tid 140239875397504] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 09:08:46 node-1 apache2_error [Wed Oct 19 09:08:45.504984 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 09:08:46 node-1 apache2_error [Wed Oct 19 09:08:45.505014 2016] [core:notice] [pid 28758:tid 140239875397504] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 09:08:49 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:49 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:49 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:49 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:49 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:49 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:57 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:57 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:57 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:57 node-1 multipathd: uevent trigger error
<27>Oct 19 09:08:57 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 09:09:36 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:36 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:36 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:36 node-1 multipathd: uevent trigger error
<43>Oct 19 09:09:36 node-1 apache2_error [Wed Oct 19 09:09:31.933409 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 09:09:36 node-1 apache2_error [Wed Oct 19 09:09:32.128527 2016] [mpm_worker:warn] [pid 28758:tid 140239875397504] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 09:09:36 node-1 apache2_error [Wed Oct 19 09:09:32.136793 2016] [mpm_worker:notice] [pid 28758:tid 140239875397504] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 09:09:36 node-1 apache2_error [Wed Oct 19 09:09:32.136816 2016] [core:notice] [pid 28758:tid 140239875397504] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 09:09:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:42 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:48 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:48 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:48 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:48 node-1 multipathd: uevent trigger error
<27>Oct 19 09:09:48 node-1 multipathd: uevent trigger error
<11>Oct 19 09:10:01 node-1 liberasurecode[17811]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:10:01 node-1 liberasurecode[17811]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:10:01 node-1 liberasurecode[17811]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:10:01 node-1 liberasurecode[17811]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 19 09:10:09 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:09 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:09 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:09 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:09 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:28 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:41 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 19 09:10:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:55 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:55 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:55 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:55 node-1 multipathd: uevent trigger error
<27>Oct 19 09:10:55 node-1 multipathd: uevent trigger error
<27>Oct 19 09:11:37 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 09:13:44 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:44 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:44 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:44 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:44 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:50 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:58 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:58 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:59 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:59 node-1 multipathd: uevent trigger error
<27>Oct 19 09:13:59 node-1 multipathd: uevent trigger error
<129>Oct 19 09:14:09 node-1 haproxy[851]: Server neutron/node-3 is DOWN, reason: Layer4 connection 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 19 09:14:09 node-1 haproxy[851]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 19 09:14:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:32 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:32 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:32 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:32 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:32 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:45 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:45 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:45 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:45 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:45 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:53 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:53 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:53 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:53 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:53 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:58 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:58 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:58 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:58 node-1 multipathd: uevent trigger error
<27>Oct 19 09:14:58 node-1 multipathd: uevent trigger error
<11>Oct 19 09:15:01 node-1 liberasurecode[20622]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:15:01 node-1 liberasurecode[20622]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:15:01 node-1 liberasurecode[20622]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 09:15:01 node-1 liberasurecode[20622]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 19 09:15:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:10 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:15:21 node-1 multipathd: uevent trigger error
<129>Oct 19 09:15:29 node-1 haproxy[851]: 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.
<27>Oct 19 09:16:12 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:12 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:12 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:12 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:12 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:12 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:16 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:16 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:16 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:16 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:17 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:21 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:26 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:31 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:31 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:31 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:31 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:31 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:35 node-1 multipathd: uevent trigger error
<27>Oct 19 09:16:35 node-1 multipathd: uevent trigger error
