Oct 28 01:19:57 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8423" x-info="http://www.rsyslog.com"] start
Oct 28 01:19:57 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 28 01:19:57 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 28 01:19:57 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 28 01:19:57 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 28 01:19:57 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 28 01:19:57 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 28 01:19:57 node-1 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Oct 28 01:19:57 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=89357548-6ae6-4bf3-95f6-9fa83c618de3 nomdmonddf nomdmonisw
Oct 28 01:19:57 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 28 01:19:57 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 28 01:19:57 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 28 01:19:57 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 28 01:19:57 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 28 01:19:57 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 28 01:19:57 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 28 01:19:57 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 28 01:19:57 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 28 01:19:57 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 01:19:57 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 28 01:19:57 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 28 01:19:57 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 28 01:19:57 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 28 01:19:57 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 28 01:19:57 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 28 01:19:57 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 28 01:19:57 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 28 01:19:57 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 28 01:19:57 node-1 kernel: [    0.000000]   2 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000]   3 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000]   4 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000]   5 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000]   6 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000]   7 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000]   8 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000]   9 disabled
Oct 28 01:19:57 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 28 01:19:57 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 28 01:19:57 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 28 01:19:57 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 28 01:19:57 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 28 01:19:57 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 28 01:19:57 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 28 01:19:57 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 28 01:19:57 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 28 01:19:57 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 28 01:19:57 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 28 01:19:57 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 28 01:19:57 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 28 01:19:57 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 28 01:19:57 node-1 kernel: [    0.000000] Zone ranges:
Oct 28 01:19:57 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 28 01:19:57 node-1 kernel: [    0.000000] Early memory node ranges
Oct 28 01:19:57 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 28 01:19:57 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 28 01:19:57 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 28 01:19:57 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 28 01:19:57 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 28 01:19:57 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 28 01:19:57 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 28 01:19:57 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 28 01:19:57 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 28 01:19:57 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 28 01:19:57 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 28 01:19:57 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 28 01:19:57 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 28 01:19:57 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 28 01:19:57 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 28 01:19:57 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 28 01:19:57 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 28 01:19:57 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 28 01:19:57 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 28 01:19:57 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 28 01:19:57 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 28 01:19:57 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 28 01:19:57 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 28 01:19:57 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 28 01:19:57 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 28 01:19:57 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 28 01:19:57 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=89357548-6ae6-4bf3-95f6-9fa83c618de3 nomdmonddf nomdmonisw
Oct 28 01:19:57 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 28 01:19:57 node-1 kernel: [    0.000000] Checking aperture...
Oct 28 01:19:57 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 01:19:57 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 28 01:19:57 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 28 01:19:57 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627180K reserved)
Oct 28 01:19:57 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 28 01:19:57 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 28 01:19:57 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 28 01:19:57 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 28 01:19:57 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 28 01:19:57 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 28 01:19:57 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 28 01:19:57 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 28 01:19:57 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 28 01:19:57 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 28 01:19:57 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 28 01:19:57 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 28 01:19:57 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 28 01:19:57 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 28 01:19:57 node-1 kernel: [    0.004000] tsc: Detected 3492.072 MHz processor
Oct 28 01:19:57 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.14 BogoMIPS (lpj=13968288)
Oct 28 01:19:57 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 28 01:19:57 node-1 kernel: [    0.000042] Security Framework initialized
Oct 28 01:19:57 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Oct 28 01:19:57 node-1 kernel: [    0.000061] Yama: becoming mindful.
Oct 28 01:19:57 node-1 kernel: [    0.001473] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.006413] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.008340] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.008368] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.008656] Initializing cgroup subsys memory
Oct 28 01:19:57 node-1 kernel: [    0.008664] Initializing cgroup subsys devices
Oct 28 01:19:57 node-1 kernel: [    0.008666] Initializing cgroup subsys freezer
Oct 28 01:19:57 node-1 kernel: [    0.008668] Initializing cgroup subsys blkio
Oct 28 01:19:57 node-1 kernel: [    0.008669] Initializing cgroup subsys perf_event
Oct 28 01:19:57 node-1 kernel: [    0.008672] Initializing cgroup subsys hugetlb
Oct 28 01:19:57 node-1 kernel: [    0.008691] CPU: Physical Processor ID: 0
Oct 28 01:19:57 node-1 kernel: [    0.008693] CPU: Processor Core ID: 0
Oct 28 01:19:57 node-1 kernel: [    0.008696] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 28 01:19:57 node-1 kernel: [    0.008696] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 28 01:19:57 node-1 kernel: [    0.009390] mce: CPU supports 22 MCE banks
Oct 28 01:19:57 node-1 kernel: [    0.009417] CPU0: Thermal monitoring enabled (TM1)
Oct 28 01:19:57 node-1 kernel: [    0.009438] process: using mwait in idle threads
Oct 28 01:19:57 node-1 kernel: [    0.009441] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 28 01:19:57 node-1 kernel: [    0.009441] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 28 01:19:57 node-1 kernel: [    0.009441] tlb_flushall_shift: 6
Oct 28 01:19:57 node-1 kernel: [    0.009530] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 28 01:19:57 node-1 kernel: [    0.010253] ACPI: Core revision 20131115
Oct 28 01:19:57 node-1 kernel: [    0.023058] ACPI: All ACPI Tables successfully acquired
Oct 28 01:19:57 node-1 kernel: [    0.023220] ftrace: allocating 28622 entries in 112 pages
Oct 28 01:19:57 node-1 kernel: [    0.031982] dmar: Host address width 46
Oct 28 01:19:57 node-1 kernel: [    0.031985] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 28 01:19:57 node-1 kernel: [    0.031991] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 01:19:57 node-1 kernel: [    0.031993] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 28 01:19:57 node-1 kernel: [    0.031997] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 01:19:57 node-1 kernel: [    0.031998] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 28 01:19:57 node-1 kernel: [    0.032000] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 28 01:19:57 node-1 kernel: [    0.032001] dmar: ATSR flags: 0x0
Oct 28 01:19:57 node-1 kernel: [    0.032002] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 28 01:19:57 node-1 kernel: [    0.032003] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 28 01:19:57 node-1 kernel: [    0.032118] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 28 01:19:57 node-1 kernel: [    0.032119] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 01:19:57 node-1 kernel: [    0.032120] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 01:19:57 node-1 kernel: [    0.032121] HPET id 0 under DRHD base 0xc7ffc000
Oct 28 01:19:57 node-1 kernel: [    0.032122] Your BIOS is broken and requested that x2apic be disabled.
Oct 28 01:19:57 node-1 kernel: [    0.032122] This will slightly decrease performance.
Oct 28 01:19:57 node-1 kernel: [    0.032122] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 28 01:19:57 node-1 kernel: [    0.032554] Enabled IRQ remapping in xapic mode
Oct 28 01:19:57 node-1 kernel: [    0.032555] x2apic not enabled, IRQ remapping is in xapic mode
Oct 28 01:19:57 node-1 kernel: [    0.032559] Switched APIC routing to physical flat.
Oct 28 01:19:57 node-1 kernel: [    0.033180] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 28 01:19:57 node-1 kernel: [    0.072831] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 28 01:19:57 node-1 kernel: [    0.072836] TSC deadline timer enabled
Oct 28 01:19:57 node-1 kernel: [    0.072844] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 28 01:19:57 node-1 kernel: [    0.072850] ... version:                3
Oct 28 01:19:57 node-1 kernel: [    0.072851] ... bit width:              48
Oct 28 01:19:57 node-1 kernel: [    0.072852] ... generic registers:      4
Oct 28 01:19:57 node-1 kernel: [    0.072853] ... value mask:             0000ffffffffffff
Oct 28 01:19:57 node-1 kernel: [    0.072854] ... max period:             0000ffffffffffff
Oct 28 01:19:57 node-1 kernel: [    0.072855] ... fixed-purpose events:   3
Oct 28 01:19:57 node-1 kernel: [    0.072856] ... event mask:             000000070000000f
Oct 28 01:19:57 node-1 kernel: [    0.074257] x86: Booting SMP configuration:
Oct 28 01:19:57 node-1 kernel: [    0.088363] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 28 01:19:57 node-1 kernel: [    0.074259] .... node  #0, CPUs:        #1  #2  #3
Oct 28 01:19:57 node-1 kernel: [    0.116271] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 28 01:19:57 node-1 kernel: [    0.270428] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 28 01:19:57 node-1 kernel: [    0.326044] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 28 01:19:57 node-1 kernel: [    0.383098] x86: Booted up 2 nodes, 16 CPUs
Oct 28 01:19:57 node-1 kernel: [    0.383101] smpboot: Total of 16 processors activated (111758.50 BogoMIPS)
Oct 28 01:19:57 node-1 kernel: [    0.407892] devtmpfs: initialized
Oct 28 01:19:57 node-1 kernel: [    0.410339] EVM: security.selinux
Oct 28 01:19:57 node-1 kernel: [    0.410340] EVM: security.SMACK64
Oct 28 01:19:57 node-1 kernel: [    0.410341] EVM: security.ima
Oct 28 01:19:57 node-1 kernel: [    0.410342] EVM: security.capability
Oct 28 01:19:57 node-1 kernel: [    0.410394] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.411056] pinctrl core: initialized pinctrl subsystem
Oct 28 01:19:57 node-1 kernel: [    0.411116] regulator-dummy: no parameters
Oct 28 01:19:57 node-1 kernel: [    0.411148] RTC time:  1:19:19, date: 10/28/16
Oct 28 01:19:57 node-1 kernel: [    0.411182] NET: Registered protocol family 16
Oct 28 01:19:57 node-1 kernel: [    0.411264] cpuidle: using governor ladder
Oct 28 01:19:57 node-1 kernel: [    0.411265] cpuidle: using governor menu
Oct 28 01:19:57 node-1 kernel: [    0.411300] ACPI: bus type PCI registered
Oct 28 01:19:57 node-1 kernel: [    0.411302] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 28 01:19:57 node-1 kernel: [    0.411346] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 28 01:19:57 node-1 kernel: [    0.411348] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 28 01:19:57 node-1 kernel: [    0.425092] PCI: Using configuration type 1 for base access
Oct 28 01:19:57 node-1 kernel: [    0.426082] bio: create slab <bio-0> at 0
Oct 28 01:19:57 node-1 kernel: [    0.426360] ACPI: Added _OSI(Module Device)
Oct 28 01:19:57 node-1 kernel: [    0.426362] ACPI: Added _OSI(Processor Device)
Oct 28 01:19:57 node-1 kernel: [    0.426363] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 28 01:19:57 node-1 kernel: [    0.426364] ACPI: Added _OSI(Processor Aggregator Device)
Oct 28 01:19:57 node-1 kernel: [    0.439017] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 28 01:19:57 node-1 kernel: [    0.449571] ACPI: Interpreter enabled
Oct 28 01:19:57 node-1 kernel: [    0.449577] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 28 01:19:57 node-1 kernel: [    0.449581] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 28 01:19:57 node-1 kernel: [    0.449584] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 28 01:19:57 node-1 kernel: [    0.449591] ACPI: (supports S0 S4 S5)
Oct 28 01:19:57 node-1 kernel: [    0.449592] ACPI: Using IOAPIC for interrupt routing
Oct 28 01:19:57 node-1 kernel: [    0.449635] HEST: Table parsing has been initialized.
Oct 28 01:19:57 node-1 kernel: [    0.449638] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 28 01:19:57 node-1 kernel: [    0.450211] ACPI: No dock devices found.
Oct 28 01:19:57 node-1 kernel: [    0.462212] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 28 01:19:57 node-1 kernel: [    0.462217] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 01:19:57 node-1 kernel: [    0.462220] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 01:19:57 node-1 kernel: [    0.462247] PCI host bridge to bus 0000:ff
Oct 28 01:19:57 node-1 kernel: [    0.462249] pci_bus 0000:ff: root bus resource [bus ff]
Oct 28 01:19:57 node-1 kernel: [    0.462257] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462295] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.462325] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462360] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462389] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.462415] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.462444] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462470] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462498] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462525] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462551] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462577] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462605] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462631] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462658] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462684] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462713] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462740] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462766] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.462794] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462819] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.462845] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462871] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462900] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.462934] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462965] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.462995] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463025] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463056] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463086] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463116] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463147] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463178] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463211] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463243] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463276] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463307] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463335] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463363] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463395] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463429] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463465] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463500] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463532] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463561] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463589] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463619] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463648] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463678] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463708] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463739] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463768] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463800] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463829] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463858] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463889] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463920] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.463977] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 28 01:19:57 node-1 kernel: [    0.463980] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 01:19:57 node-1 kernel: [    0.463983] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 01:19:57 node-1 kernel: [    0.464001] PCI host bridge to bus 0000:7f
Oct 28 01:19:57 node-1 kernel: [    0.464002] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 28 01:19:57 node-1 kernel: [    0.464007] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464034] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.464061] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464088] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464110] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.464134] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.464159] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464185] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464209] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464231] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464253] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464275] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464299] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464320] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464344] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464369] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464390] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464413] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464435] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.464459] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464480] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.464502] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464524] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464550] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 01:19:57 node-1 kernel: [    0.464582] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464608] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464634] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464662] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464687] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464714] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464740] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464768] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464794] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464821] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464848] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464876] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464904] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464930] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464954] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.464981] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465006] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465035] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465065] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465093] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465119] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465143] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465168] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465195] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465222] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465248] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465278] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465304] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465327] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465353] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465379] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465409] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.465436] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.466702] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 28 01:19:57 node-1 kernel: [    0.466705] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 01:19:57 node-1 kernel: [    0.467828] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 01:19:57 node-1 kernel: [    0.468335] PCI host bridge to bus 0000:00
Oct 28 01:19:57 node-1 kernel: [    0.468338] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 28 01:19:57 node-1 kernel: [    0.468339] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 28 01:19:57 node-1 kernel: [    0.468341] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 28 01:19:57 node-1 kernel: [    0.468342] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 28 01:19:57 node-1 kernel: [    0.468343] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 28 01:19:57 node-1 kernel: [    0.468345] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 28 01:19:57 node-1 kernel: [    0.468346] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 28 01:19:57 node-1 kernel: [    0.468352] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 28 01:19:57 node-1 kernel: [    0.468435] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.468465] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.468507] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 28 01:19:57 node-1 kernel: [    0.468527] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.468556] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.468596] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 28 01:19:57 node-1 kernel: [    0.468615] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.468644] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.468688] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 28 01:19:57 node-1 kernel: [    0.468708] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.468778] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.468856] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.468933] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 01:19:57 node-1 kernel: [    0.468938] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 28 01:19:57 node-1 kernel: [    0.469023] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 28 01:19:57 node-1 kernel: [    0.469172] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 28 01:19:57 node-1 kernel: [    0.469189] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 28 01:19:57 node-1 kernel: [    0.469267] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.469322] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 28 01:19:57 node-1 kernel: [    0.469344] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.469399] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.469442] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 28 01:19:57 node-1 kernel: [    0.469470] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.469526] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.469569] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 28 01:19:57 node-1 kernel: [    0.469594] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 28 01:19:57 node-1 kernel: [    0.469611] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 28 01:19:57 node-1 kernel: [    0.469688] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.469738] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 28 01:19:57 node-1 kernel: [    0.469765] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 28 01:19:57 node-1 kernel: [    0.470012] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 28 01:19:57 node-1 kernel: [    0.470018] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 28 01:19:57 node-1 kernel: [    0.470024] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.470030] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.470037] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 28 01:19:57 node-1 kernel: [    0.470067] pci 0000:01:00.0: supports D1 D2
Oct 28 01:19:57 node-1 kernel: [    0.479827] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 01:19:57 node-1 kernel: [    0.479829] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 01:19:57 node-1 kernel: [    0.479831] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 01:19:57 node-1 kernel: [    0.479939] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.479972] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 28 01:19:57 node-1 kernel: [    0.487816] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 01:19:57 node-1 kernel: [    0.487823] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.487827] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 01:19:57 node-1 kernel: [    0.487911] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.487984] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.488110] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.488157] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 01:19:57 node-1 kernel: [    0.488160] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.488162] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 01:19:57 node-1 kernel: [    0.488223] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.488349] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.488406] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 01:19:57 node-1 kernel: [    0.488408] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.488411] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.488463] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.488596] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.488638] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.488758] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.488794] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.488913] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.488953] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 28 01:19:57 node-1 kernel: [    0.489093] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 28 01:19:57 node-1 kernel: [    0.489137] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 01:19:57 node-1 kernel: [    0.489140] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.489142] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.489202] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 28 01:19:57 node-1 kernel: [    0.489266] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.489318] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.489359] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 28 01:19:57 node-1 kernel: [    0.489441] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 28 01:19:57 node-1 kernel: [    0.489551] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 01:19:57 node-1 kernel: [    0.489553] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.489555] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.489611] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 28 01:19:57 node-1 kernel: [    0.489665] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.489713] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.489926] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 01:19:57 node-1 kernel: [    0.489930] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 01:19:57 node-1 kernel: [    0.489997] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 28 01:19:57 node-1 kernel: [    0.490076] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.490126] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.490334] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 01:19:57 node-1 kernel: [    0.490338] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 01:19:57 node-1 kernel: [    0.490397] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 28 01:19:57 node-1 kernel: [    0.490458] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.490510] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 28 01:19:57 node-1 kernel: [    0.490734] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 01:19:57 node-1 kernel: [    0.490737] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 01:19:57 node-1 kernel: [    0.490912] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 01:19:57 node-1 kernel: [    0.490950] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 01:19:57 node-1 kernel: [    0.491025] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 28 01:19:57 node-1 kernel: [    0.491044] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 28 01:19:57 node-1 kernel: [    0.491057] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 28 01:19:57 node-1 kernel: [    0.491070] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 28 01:19:57 node-1 kernel: [    0.491120] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 28 01:19:57 node-1 kernel: [    0.495823] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 01:19:57 node-1 kernel: [    0.495832] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 01:19:57 node-1 kernel: [    0.495885] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 28 01:19:57 node-1 kernel: [    0.496540] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 28 01:19:57 node-1 kernel: [    0.496543] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 01:19:57 node-1 kernel: [    0.496668] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 01:19:57 node-1 kernel: [    0.496775] PCI host bridge to bus 0000:80
Oct 28 01:19:57 node-1 kernel: [    0.496777] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 28 01:19:57 node-1 kernel: [    0.496779] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 28 01:19:57 node-1 kernel: [    0.496780] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 28 01:19:57 node-1 kernel: [    0.496789] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.496852] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.496921] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 01:19:57 node-1 kernel: [    0.496983] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 01:19:57 node-1 kernel: [    0.496989] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 28 01:19:57 node-1 kernel: [    0.497062] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 28 01:19:57 node-1 kernel: [    0.497361] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 28 01:19:57 node-1 kernel: [    0.497392] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 28 01:19:57 node-1 kernel: [    0.497422] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 28 01:19:57 node-1 kernel: [    0.497451] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 28 01:19:57 node-1 kernel: [    0.497480] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 01:19:57 node-1 kernel: [    0.497510] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 01:19:57 node-1 kernel: [    0.497539] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 01:19:57 node-1 kernel: [    0.497569] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 01:19:57 node-1 kernel: [    0.497654] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 28 01:19:57 node-1 kernel: [    0.497658] ACPI: \_SB_.UNC1: notify handler is installed
Oct 28 01:19:57 node-1 kernel: [    0.497659] ACPI: \_SB_.UNC0: notify handler is installed
Oct 28 01:19:57 node-1 kernel: [    0.497674] ACPI: \_SB_.PCI0: notify handler is installed
Oct 28 01:19:57 node-1 kernel: [    0.497727] ACPI: \_SB_.PCI1: notify handler is installed
Oct 28 01:19:57 node-1 kernel: [    0.497807] Found 4 acpi root devices
Oct 28 01:19:57 node-1 kernel: [    0.497912] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 28 01:19:57 node-1 kernel: [    0.497915] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 28 01:19:57 node-1 kernel: [    0.497916] vgaarb: loaded
Oct 28 01:19:57 node-1 kernel: [    0.497917] vgaarb: bridge control possible 0000:0c:00.0
Oct 28 01:19:57 node-1 kernel: [    0.498035] SCSI subsystem initialized
Oct 28 01:19:57 node-1 kernel: [    0.498101] libata version 3.00 loaded.
Oct 28 01:19:57 node-1 kernel: [    0.498116] ACPI: bus type USB registered
Oct 28 01:19:57 node-1 kernel: [    0.498126] usbcore: registered new interface driver usbfs
Oct 28 01:19:57 node-1 kernel: [    0.498131] usbcore: registered new interface driver hub
Oct 28 01:19:57 node-1 kernel: [    0.498155] usbcore: registered new device driver usb
Oct 28 01:19:57 node-1 kernel: [    0.498321] PCI: Using ACPI for IRQ routing
Oct 28 01:19:57 node-1 kernel: [    0.501909] PCI: pci_cache_line_size set to 64 bytes
Oct 28 01:19:57 node-1 kernel: [    0.502118] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 28 01:19:57 node-1 kernel: [    0.502119] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 28 01:19:57 node-1 kernel: [    0.502120] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 28 01:19:57 node-1 kernel: [    0.502184] NetLabel: Initializing
Oct 28 01:19:57 node-1 kernel: [    0.502185] NetLabel:  domain hash size = 128
Oct 28 01:19:57 node-1 kernel: [    0.502186] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 28 01:19:57 node-1 kernel: [    0.502196] NetLabel:  unlabeled traffic allowed by default
Oct 28 01:19:57 node-1 kernel: [    0.502253] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 28 01:19:57 node-1 kernel: [    0.502257] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 28 01:19:57 node-1 kernel: [    0.504316] Switched to clocksource hpet
Oct 28 01:19:57 node-1 kernel: [    0.508258] AppArmor: AppArmor Filesystem Enabled
Oct 28 01:19:57 node-1 kernel: [    0.508281] pnp: PnP ACPI init
Oct 28 01:19:57 node-1 kernel: [    0.508288] ACPI: bus type PNP registered
Oct 28 01:19:57 node-1 kernel: [    0.508402] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508411] pnp 00:01: [dma 4]
Oct 28 01:19:57 node-1 kernel: [    0.508422] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508447] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508467] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508485] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508518] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508570] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508572] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 28 01:19:57 node-1 kernel: [    0.508573] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508575] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508576] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508581] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508583] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 28 01:19:57 node-1 kernel: [    0.508585] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508586] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508588] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508589] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508590] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508592] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 28 01:19:57 node-1 kernel: [    0.508594] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508678] pnp 00:07: [dma 0 disabled]
Oct 28 01:19:57 node-1 kernel: [    0.508706] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508780] pnp 00:08: [dma 0 disabled]
Oct 28 01:19:57 node-1 kernel: [    0.508811] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 01:19:57 node-1 kernel: [    0.508862] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 28 01:19:57 node-1 kernel: [    0.509207] pnp: PnP ACPI: found 10 devices
Oct 28 01:19:57 node-1 kernel: [    0.509208] ACPI: bus type PNP unregistered
Oct 28 01:19:57 node-1 kernel: [    0.515465] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 01:19:57 node-1 kernel: [    0.515468] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 01:19:57 node-1 kernel: [    0.515471] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 01:19:57 node-1 kernel: [    0.515475] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 01:19:57 node-1 kernel: [    0.515477] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515492] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515521] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 01:19:57 node-1 kernel: [    0.515535] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515564] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 01:19:57 node-1 kernel: [    0.515578] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 01:19:57 node-1 kernel: [    0.515607] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 01:19:57 node-1 kernel: [    0.515621] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 01:19:57 node-1 kernel: [    0.515653] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 01:19:57 node-1 kernel: [    0.515655] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515670] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515699] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 01:19:57 node-1 kernel: [    0.515701] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515715] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515744] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 01:19:57 node-1 kernel: [    0.515746] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515749] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515753] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 01:19:57 node-1 kernel: [    0.515755] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515757] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515761] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 01:19:57 node-1 kernel: [    0.515765] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 01:19:57 node-1 kernel: [    0.515773] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 01:19:57 node-1 kernel: [    0.515777] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 01:19:57 node-1 kernel: [    0.515783] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 28 01:19:57 node-1 kernel: [    0.515784] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 28 01:19:57 node-1 kernel: [    0.515785] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 28 01:19:57 node-1 kernel: [    0.515786] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 28 01:19:57 node-1 kernel: [    0.515787] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 28 01:19:57 node-1 kernel: [    0.515788] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 28 01:19:57 node-1 kernel: [    0.515789] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 28 01:19:57 node-1 kernel: [    0.515789] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 28 01:19:57 node-1 kernel: [    0.515790] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515791] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515792] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515793] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515794] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515795] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515796] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515797] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515798] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 28 01:19:57 node-1 kernel: [    0.515799] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515800] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 28 01:19:57 node-1 kernel: [    0.515801] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 28 01:19:57 node-1 kernel: [    0.515802] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 28 01:19:57 node-1 kernel: [    0.515803] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 28 01:19:57 node-1 kernel: [    0.515805] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 28 01:19:57 node-1 kernel: [    0.515806] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 28 01:19:57 node-1 kernel: [    0.515845] NET: Registered protocol family 2
Oct 28 01:19:57 node-1 kernel: [    0.516100] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.516438] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.516582] TCP: Hash tables configured (established 262144 bind 65536)
Oct 28 01:19:57 node-1 kernel: [    0.516618] TCP: reno registered
Oct 28 01:19:57 node-1 kernel: [    0.516647] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.516740] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.516884] NET: Registered protocol family 1
Oct 28 01:19:57 node-1 kernel: [    0.556413] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 28 01:19:57 node-1 kernel: [    0.556427] PCI: CLS 64 bytes, default 64
Oct 28 01:19:57 node-1 kernel: [    0.556503] Trying to unpack rootfs image as initramfs...
Oct 28 01:19:57 node-1 kernel: [    0.776374] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Oct 28 01:19:57 node-1 kernel: [    0.776405] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 28 01:19:57 node-1 kernel: [    0.776407] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 28 01:19:57 node-1 kernel: [    0.776812] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776818] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776823] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776829] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776840] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776857] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776878] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776886] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776894] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776903] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776909] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776916] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776922] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776930] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776936] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776943] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 01:19:57 node-1 kernel: [    0.776982] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 28 01:19:57 node-1 kernel: [    0.776986] Scanning for low memory corruption every 60 seconds
Oct 28 01:19:57 node-1 kernel: [    0.777263] Initialise system trusted keyring
Oct 28 01:19:57 node-1 kernel: [    0.777307] audit: initializing netlink socket (disabled)
Oct 28 01:19:57 node-1 kernel: [    0.777316] type=2000 audit(1477617559.728:1): initialized
Oct 28 01:19:57 node-1 kernel: [    0.794943] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 28 01:19:57 node-1 kernel: [    0.796379] zbud: loaded
Oct 28 01:19:57 node-1 kernel: [    0.796499] VFS: Disk quotas dquot_6.5.2
Oct 28 01:19:57 node-1 kernel: [    0.796539] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 28 01:19:57 node-1 kernel: [    0.796919] fuse init (API version 7.22)
Oct 28 01:19:57 node-1 kernel: [    0.796975] msgmni has been set to 32768
Oct 28 01:19:57 node-1 kernel: [    0.797017] Key type big_key registered
Oct 28 01:19:57 node-1 kernel: [    0.797511] Key type asymmetric registered
Oct 28 01:19:57 node-1 kernel: [    0.797513] Asymmetric key parser 'x509' registered
Oct 28 01:19:57 node-1 kernel: [    0.797534] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 28 01:19:57 node-1 kernel: [    0.797590] io scheduler noop registered
Oct 28 01:19:57 node-1 kernel: [    0.797592] io scheduler deadline registered (default)
Oct 28 01:19:57 node-1 kernel: [    0.797608] io scheduler cfq registered
Oct 28 01:19:57 node-1 kernel: [    0.797895] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    0.797986] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    0.798073] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    0.798159] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    0.798253] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    0.798320] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    0.798582] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 28 01:19:57 node-1 kernel: [    0.798600] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 28 01:19:57 node-1 kernel: [    0.798613] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 28 01:19:57 node-1 kernel: [    0.798622] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798624] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798626] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 28 01:19:57 node-1 kernel: [    0.798630] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798632] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798633] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798634] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798635] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798637] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798639] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798640] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798641] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798643] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798644] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798646] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798648] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 28 01:19:57 node-1 kernel: [    0.798652] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798654] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 28 01:19:57 node-1 kernel: [    0.798662] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798665] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 28 01:19:57 node-1 kernel: [    0.798675] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798676] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 28 01:19:57 node-1 kernel: [    0.798679] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 28 01:19:57 node-1 kernel: [    0.798692] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 28 01:19:57 node-1 kernel: [    0.798780] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 28 01:19:57 node-1 kernel: [    0.798784] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 28 01:19:57 node-1 kernel: [    0.798792] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 28 01:19:57 node-1 kernel: [    0.798827] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 28 01:19:57 node-1 kernel: [    0.798829] vesafb: scrolling: redraw
Oct 28 01:19:57 node-1 kernel: [    0.798830] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 28 01:19:57 node-1 kernel: [    0.819229] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 28 01:19:57 node-1 kernel: [    0.827742] Console: switching to colour frame buffer device 80x30
Oct 28 01:19:57 node-1 kernel: [    0.836428] fb0: VESA VGA frame buffer device
Oct 28 01:19:57 node-1 kernel: [    0.836627] intel_idle: MWAIT substates: 0x2120
Oct 28 01:19:57 node-1 kernel: [    0.836628] intel_idle: v0.4 model 0x3F
Oct 28 01:19:57 node-1 kernel: [    0.836629] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 28 01:19:57 node-1 kernel: [    0.836857] ipmi message handler version 39.2
Oct 28 01:19:57 node-1 kernel: [    0.837117] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 28 01:19:57 node-1 kernel: [    0.837546] ACPI: AC Adapter [P111] (on-line)
Oct 28 01:19:57 node-1 kernel: [    0.842769] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 28 01:19:57 node-1 kernel: [    0.853785] ACPI: Power Button [PWRB]
Oct 28 01:19:57 node-1 kernel: [    0.859601] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 28 01:19:57 node-1 kernel: [    0.871241] ACPI: Power Button [PWRF]
Oct 28 01:19:57 node-1 kernel: [    0.898009] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 28 01:19:57 node-1 kernel: [    0.909677] pstore: Registered erst as persistent store backend
Oct 28 01:19:57 node-1 kernel: [    0.915886] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 28 01:19:57 node-1 kernel: [    0.927859] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 28 01:19:57 node-1 kernel: [    0.954625] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 28 01:19:57 node-1 kernel: [    0.988010] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 28 01:19:57 node-1 kernel: [    1.002110] Linux agpgart interface v0.103
Oct 28 01:19:57 node-1 kernel: [    1.009798] brd: module loaded
Oct 28 01:19:57 node-1 kernel: [    1.016859] loop: module loaded
Oct 28 01:19:57 node-1 kernel: [    1.023607] libphy: Fixed MDIO Bus: probed
Oct 28 01:19:57 node-1 kernel: [    1.030111] tun: Universal TUN/TAP device driver, 1.6
Oct 28 01:19:57 node-1 kernel: [    1.036626] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 28 01:19:57 node-1 kernel: [    1.043167] PPP generic driver version 2.4.2
Oct 28 01:19:57 node-1 kernel: [    1.049577] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 28 01:19:57 node-1 kernel: [    1.056042] ehci-pci: EHCI PCI platform driver
Oct 28 01:19:57 node-1 kernel: [    1.062666] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 28 01:19:57 node-1 kernel: [    1.069126] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 28 01:19:57 node-1 kernel: [    1.081807] ehci-pci 0000:00:1a.0: debug port 2
Oct 28 01:19:57 node-1 kernel: [    1.092096] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 28 01:19:57 node-1 kernel: [    1.092114] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 28 01:19:57 node-1 kernel: [    1.107808] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 28 01:19:57 node-1 kernel: [    1.113877] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 01:19:57 node-1 kernel: [    1.120043] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 01:19:57 node-1 kernel: [    1.131927] usb usb1: Product: EHCI Host Controller
Oct 28 01:19:57 node-1 kernel: [    1.137943] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 01:19:57 node-1 kernel: [    1.143984] usb usb1: SerialNumber: 0000:00:1a.0
Oct 28 01:19:57 node-1 kernel: [    1.149930] hub 1-0:1.0: USB hub found
Oct 28 01:19:57 node-1 kernel: [    1.155704] hub 1-0:1.0: 2 ports detected
Oct 28 01:19:57 node-1 kernel: [    1.161563] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 28 01:19:57 node-1 kernel: [    1.167174] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 28 01:19:57 node-1 kernel: [    1.178067] ehci-pci 0000:00:1d.0: debug port 2
Oct 28 01:19:57 node-1 kernel: [    1.187377] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 28 01:19:57 node-1 kernel: [    1.187380] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 28 01:19:57 node-1 kernel: [    1.203727] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 28 01:19:57 node-1 kernel: [    1.208993] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 01:19:57 node-1 kernel: [    1.214406] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 01:19:57 node-1 kernel: [    1.225024] usb usb2: Product: EHCI Host Controller
Oct 28 01:19:57 node-1 kernel: [    1.230495] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 01:19:57 node-1 kernel: [    1.236046] usb usb2: SerialNumber: 0000:00:1d.0
Oct 28 01:19:57 node-1 kernel: [    1.241569] hub 2-0:1.0: USB hub found
Oct 28 01:19:57 node-1 kernel: [    1.246924] hub 2-0:1.0: 2 ports detected
Oct 28 01:19:57 node-1 kernel: [    1.252238] ehci-platform: EHCI generic platform driver
Oct 28 01:19:57 node-1 kernel: [    1.257486] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 28 01:19:57 node-1 kernel: [    1.262814] ohci-pci: OHCI PCI platform driver
Oct 28 01:19:57 node-1 kernel: [    1.268138] ohci-platform: OHCI generic platform driver
Oct 28 01:19:57 node-1 kernel: [    1.273354] uhci_hcd: USB Universal Host Controller Interface driver
Oct 28 01:19:57 node-1 kernel: [    1.278715] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 28 01:19:57 node-1 kernel: [    1.471508] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 28 01:19:57 node-1 kernel: [    1.631683] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 28 01:19:57 node-1 kernel: [    1.637222] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 01:19:57 node-1 kernel: [    1.642946] hub 1-1:1.0: USB hub found
Oct 28 01:19:57 node-1 kernel: [    1.648420] hub 1-1:1.0: 6 ports detected
Oct 28 01:19:57 node-1 kernel: [    1.763251] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 28 01:19:57 node-1 kernel: [    1.775299] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 28 01:19:57 node-1 kernel: [    2.031344] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 28 01:19:57 node-1 kernel: [    2.036906] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 01:19:57 node-1 kernel: [    2.042742] hub 2-1:1.0: USB hub found
Oct 28 01:19:57 node-1 kernel: [    2.048456] hub 2-1:1.0: 8 ports detected
Oct 28 01:19:57 node-1 kernel: [    2.320295] i8042: No controller found
Oct 28 01:19:57 node-1 kernel: [    2.325701] mousedev: PS/2 mouse device common for all mice
Oct 28 01:19:57 node-1 kernel: [    2.326851] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 28 01:19:57 node-1 kernel: [    2.336823] rtc_cmos 00:02: RTC can wake from S4
Oct 28 01:19:57 node-1 kernel: [    2.342565] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 28 01:19:57 node-1 kernel: [    2.348182] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 28 01:19:57 node-1 kernel: [    2.359288] device-mapper: uevent: version 1.0.3
Oct 28 01:19:57 node-1 kernel: [    2.364918] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 28 01:19:57 node-1 kernel: [    2.376125] ledtrig-cpu: registered to indicate activity on CPUs
Oct 28 01:19:57 node-1 kernel: [    2.382033] TCP: cubic registered
Oct 28 01:19:57 node-1 kernel: [    2.387929] NET: Registered protocol family 10
Oct 28 01:19:57 node-1 kernel: [    2.393901] NET: Registered protocol family 17
Oct 28 01:19:57 node-1 kernel: [    2.399569] Key type dns_resolver registered
Oct 28 01:19:57 node-1 kernel: [    2.405567] Loading compiled-in X.509 certificates
Oct 28 01:19:57 node-1 kernel: [    2.411819] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 28 01:19:57 node-1 kernel: [    2.423184] registered taskstats version 1
Oct 28 01:19:57 node-1 kernel: [    2.431139] Key type trusted registered
Oct 28 01:19:57 node-1 kernel: [    2.438660] Key type encrypted registered
Oct 28 01:19:57 node-1 kernel: [    2.444102] AppArmor: AppArmor sha1 policy hashing enabled
Oct 28 01:19:57 node-1 kernel: [    2.449587] IMA: No TPM chip found, activating TPM-bypass!
Oct 28 01:19:57 node-1 kernel: [    2.455743] regulator-dummy: disabling
Oct 28 01:19:57 node-1 kernel: [    2.461293]   Magic number: 4:503:307
Oct 28 01:19:57 node-1 kernel: [    2.463548] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 28 01:19:57 node-1 kernel: [    2.463549] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 28 01:19:57 node-1 kernel: [    2.463549] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 28 01:19:57 node-1 kernel: [    2.463550] usb 2-1.4: Manufacturer: Avocent
Oct 28 01:19:57 node-1 kernel: [    2.463550] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 28 01:19:57 node-1 kernel: [    2.499770] tty tty36: hash matches
Oct 28 01:19:57 node-1 kernel: [    2.505336] memory memory165: hash matches
Oct 28 01:19:57 node-1 kernel: [    2.510779] rtc_cmos 00:02: setting system clock to 2016-10-28 01:19:21 UTC (1477617561)
Oct 28 01:19:57 node-1 kernel: [    2.523150] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 28 01:19:57 node-1 kernel: [    2.528711] EDD information not available.
Oct 28 01:19:57 node-1 kernel: [    2.534231] PM: Hibernation image not present or could not be loaded.
Oct 28 01:19:57 node-1 kernel: [    2.535089] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 28 01:19:57 node-1 kernel: [    2.546163] Write protecting the kernel read-only data: 12288k
Oct 28 01:19:57 node-1 kernel: [    2.552231] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 28 01:19:57 node-1 kernel: [    2.564557] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 28 01:19:57 node-1 kernel: [    2.596309] device-mapper: multipath: version 1.6.0 loaded
Oct 28 01:19:57 node-1 kernel: [    2.604246] systemd-udevd[217]: starting version 204
Oct 28 01:19:57 node-1 kernel: [    2.629207] md: linear personality registered for level -1
Oct 28 01:19:57 node-1 kernel: [    2.643172] md: multipath personality registered for level -4
Oct 28 01:19:57 node-1 kernel: [    2.651436] md: raid0 personality registered for level 0
Oct 28 01:19:57 node-1 kernel: [    2.659704] md: raid1 personality registered for level 1
Oct 28 01:19:57 node-1 kernel: [    2.669489] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 28 01:19:57 node-1 kernel: [    2.675938] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 28 01:19:57 node-1 kernel: [    2.686808] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct 28 01:19:57 node-1 kernel: [    2.686810] 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 28 01:19:57 node-1 kernel: [    2.686820] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 01:19:57 node-1 kernel: [    2.687464] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.687549] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.687632] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.687691] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.687940] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.703480] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct 28 01:19:57 node-1 kernel: [    2.703482] 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 28 01:19:57 node-1 kernel: [    2.703496] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 28 01:19:57 node-1 kernel: [    2.703812] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.703876] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.703948] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.704050] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.704106] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.704206] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.704468] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.722100] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct 28 01:19:57 node-1 kernel: [    2.722120] 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 28 01:19:57 node-1 kernel: [    2.722132] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 01:19:57 node-1 kernel: [    2.722416] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.722571] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.722650] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.722729] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.722993] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.734533] raid6: sse2x1     977 MB/s
Oct 28 01:19:57 node-1 kernel: [    2.741074] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct 28 01:19:57 node-1 kernel: [    2.741089] 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 28 01:19:57 node-1 kernel: [    2.741106] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 01:19:57 node-1 kernel: [    2.741425] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.741535] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.741600] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.741757] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.742022] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 01:19:57 node-1 kernel: [    2.802596] raid6: sse2x2     791 MB/s
Oct 28 01:19:57 node-1 kernel: [    2.870521] raid6: sse2x4    1361 MB/s
Oct 28 01:19:57 node-1 kernel: [    2.675845] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 28 01:19:57 node-1 kernel: [    2.938271] raid6: avx2x1    8364 MB/s
Oct 28 01:19:57 node-1 kernel: [    3.010206] raid6: avx2x2   18865 MB/s
Oct 28 01:19:57 node-1 kernel: [    3.082144] raid6: avx2x4   21303 MB/s
Oct 28 01:19:57 node-1 kernel: [    3.088148] raid6: using algorithm avx2x4 (21303 MB/s)
Oct 28 01:19:57 node-1 kernel: [    3.094103] raid6: using avx2x2 recovery algorithm
Oct 28 01:19:57 node-1 kernel: [    3.099899] Switched to clocksource tsc
Oct 28 01:19:57 node-1 kernel: [    3.101077] megasas: FW now in Ready state
Oct 28 01:19:57 node-1 kernel: [    3.101319] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.101403] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.101534] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.101697] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.101825] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.101956] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102099] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102309] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102418] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102527] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102637] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102717] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102834] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.102989] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.103139] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.103220] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Oct 28 01:19:57 node-1 kernel: [    3.103751] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 28 01:19:57 node-1 kernel: [    3.122053] hidraw: raw HID events driver (C) Jiri Kosina
Oct 28 01:19:57 node-1 kernel: [    3.127831] xor: automatically using best checksumming function:
Oct 28 01:19:57 node-1 kernel: [    3.137903] usbcore: registered new interface driver usbhid
Oct 28 01:19:57 node-1 kernel: [    3.143495] usbhid: USB HID core driver
Oct 28 01:19:57 node-1 kernel: [    3.152744] 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 28 01:19:57 node-1 kernel: [    3.163824] 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 28 01:19:57 node-1 kernel: [    3.170048]    avx       : 35726.000 MB/sec
Oct 28 01:19:57 node-1 kernel: [    3.180988] 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 28 01:19:57 node-1 kernel: [    3.192908] async_tx: api initialized (async)
Oct 28 01:19:57 node-1 kernel: [    3.193082] 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 28 01:19:57 node-1 kernel: [    3.193137] 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 28 01:19:57 node-1 kernel: [    3.193492] 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 28 01:19:57 node-1 kernel: [    3.239032] md: raid6 personality registered for level 6
Oct 28 01:19:57 node-1 kernel: [    3.245533] md: raid5 personality registered for level 5
Oct 28 01:19:57 node-1 kernel: [    3.251933] md: raid4 personality registered for level 4
Oct 28 01:19:57 node-1 kernel: [    3.261228] md: raid10 personality registered for level 10
Oct 28 01:19:57 node-1 kernel: [    3.317143] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Oct 28 01:19:57 node-1 kernel: [    3.465860] megasas:IOC Init cmd success
Oct 28 01:19:57 node-1 kernel: [    3.517823] megasas: INIT adapter done
Oct 28 01:19:57 node-1 kernel: [    3.593749] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 28 01:19:57 node-1 kernel: [    3.600650] scsi0 : LSI SAS based MegaRAID driver
Oct 28 01:19:57 node-1 kernel: [    3.608115] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 01:19:57 node-1 kernel: [    3.627118] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 01:19:57 node-1 kernel: [    3.642663] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 28 01:19:57 node-1 kernel: [    3.649157] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 28 01:19:57 node-1 kernel: [    3.662121] sd 0:2:0:0: [sda] Write Protect is off
Oct 28 01:19:57 node-1 kernel: [    3.668489] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 28 01:19:57 node-1 kernel: [    3.668508] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 28 01:19:57 node-1 kernel: [    3.709063]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 28 01:19:57 node-1 kernel: [    3.715886] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 28 01:19:57 node-1 kernel: [    3.841885] random: lvm urandom read with 26 bits of entropy available
Oct 28 01:19:57 node-1 kernel: [    4.039125] bio: create slab <bio-1> at 1
Oct 28 01:19:57 node-1 kernel: [    5.019133] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 01:19:57 node-1 kernel: [    5.613916] random: nonblocking pool is initialized
Oct 28 01:19:57 node-1 kernel: [    5.728240] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Oct 28 01:19:57 node-1 kernel: [    5.755773] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 28 01:19:57 node-1 kernel: [    5.856160] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 28 01:19:57 node-1 kernel: [    5.951911] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 28 01:19:57 node-1 kernel: [    6.039485] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 01:19:57 node-1 kernel: [    6.209817] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 28 01:19:57 node-1 kernel: [    6.267305] XFS (dm-1): Mounting Filesystem
Oct 28 01:19:57 node-1 kernel: [    6.519932] XFS (dm-1): Ending clean mount
Oct 28 01:19:57 node-1 kernel: [    6.578438] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 01:19:57 node-1 kernel: [    6.612761] XFS (dm-2): Mounting Filesystem
Oct 28 01:19:57 node-1 kernel: [    6.694578] XFS (dm-2): Ending clean mount
Oct 28 01:19:57 node-1 kernel: [    6.846586] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 01:19:57 node-1 kernel: [    9.039308] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 28 01:19:57 node-1 kernel: [    9.062636] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 28 01:19:57 node-1 kernel: [    9.240248] systemd-udevd[801]: starting version 204
Oct 28 01:19:57 node-1 kernel: [    9.494847] power_meter ACPI000D:00: Found ACPI power meter.
Oct 28 01:19:57 node-1 kernel: [    9.494857] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 28 01:19:57 node-1 kernel: [    9.515022] wmi: Mapper loaded
Oct 28 01:19:57 node-1 kernel: [    9.519781] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 28 01:19:57 node-1 kernel: [    9.519786] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 01:19:57 node-1 kernel: [    9.519789] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 28 01:19:57 node-1 kernel: [    9.519790] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 01:19:57 node-1 kernel: [    9.519803] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 28 01:19:57 node-1 kernel: [    9.525989] IPMI System Interface driver.
Oct 28 01:19:57 node-1 kernel: [    9.526022] ipmi_si: probing via ACPI
Oct 28 01:19:57 node-1 kernel: [    9.526034] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 28 01:19:57 node-1 kernel: [    9.526035] ipmi_si: Adding ACPI-specified kcs state machine
Oct 28 01:19:57 node-1 kernel: [    9.526042] ipmi_si: probing via SMBIOS
Oct 28 01:19:57 node-1 kernel: [    9.526043] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 01:19:57 node-1 kernel: [    9.526043] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 28 01:19:57 node-1 kernel: [    9.526045] ipmi_si: probing via SPMI
Oct 28 01:19:57 node-1 kernel: [    9.526046] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 01:19:57 node-1 kernel: [    9.526046] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 28 01:19:57 node-1 kernel: [    9.526047] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 28 01:19:57 node-1 kernel: [    9.527296] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 28 01:19:57 node-1 kernel: [    9.597070] systemd-udevd[829]: renamed network interface eth0 to enp6s0
Oct 28 01:19:57 node-1 kernel: [    9.625079] systemd-udevd[831]: renamed network interface eth1 to enp7s0
Oct 28 01:19:57 node-1 kernel: [    9.656948] systemd-udevd[822]: renamed network interface eth3 to enp9s0
Oct 28 01:19:57 node-1 kernel: [    9.669266] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 28 01:19:57 node-1 kernel: [    9.669273] ipmi_si 00:09: IPMI kcs interface initialized
Oct 28 01:19:57 node-1 kernel: [    9.687657] systemd-udevd[820]: renamed network interface eth2 to enp8s0
Oct 28 01:19:57 node-1 kernel: [    9.950021] type=1400 audit(1477617568.942:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1092 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.950178] type=1400 audit(1477617568.942:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1092 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.950303] type=1400 audit(1477617568.942:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1092 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.961738] type=1400 audit(1477617568.954:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1094 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.961878] type=1400 audit(1477617568.954:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1094 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.961999] type=1400 audit(1477617568.954:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1094 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.968780] type=1400 audit(1477617568.962:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1091 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.969009] type=1400 audit(1477617568.962:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1091 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.969210] type=1400 audit(1477617568.962:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1091 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [    9.984635] type=1400 audit(1477617568.978:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1093 comm="apparmor_parser"
Oct 28 01:19:57 node-1 kernel: [   10.530413] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 28 01:19:57 node-1 kernel: [   10.540317] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 28 01:19:57 node-1 kernel: [   10.770220] enic 0000:06:00.0 enp6s0: Link UP
Oct 28 01:19:57 node-1 kernel: [   10.771346] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 28 01:19:57 node-1 kernel: [   10.771353] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 28 01:19:57 node-1 kernel: [   20.630536] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 28 01:19:57 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 28 01:19:58 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 28 01:19:58 node-1 kernel: [   38.954581] init: failsafe main process (8451) killed by TERM signal
Oct 28 01:19:59 node-1 kernel: [   39.257421] audit_printk_skb: 30 callbacks suppressed
Oct 28 01:19:59 node-1 kernel: [   39.257423] type=1400 audit(1477617599.222:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8562 comm="apparmor_parser"
Oct 28 01:19:59 node-1 kernel: [   39.257427] type=1400 audit(1477617599.222:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8562 comm="apparmor_parser"
Oct 28 01:19:59 node-1 kernel: [   39.257430] type=1400 audit(1477617599.222:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8562 comm="apparmor_parser"
Oct 28 01:19:59 node-1 kernel: [   39.257466] type=1400 audit(1477617599.222:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8563 comm="apparmor_parser"
Oct 28 01:19:59 node-1 kernel: [   39.257645] type=1400 audit(1477617599.222:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8562 comm="apparmor_parser"
Oct 28 01:19:59 node-1 kernel: [   39.257647] type=1400 audit(1477617599.222:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8562 comm="apparmor_parser"
Oct 28 01:19:59 node-1 kernel: [   39.257775] type=1400 audit(1477617599.222:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8562 comm="apparmor_parser"
Oct 28 01:19:59 node-1 dbus[8566]: [system] AppArmor D-Bus mediation is enabled
Oct 28 01:19:59 node-1 kernel: [   39.346834] type=1400 audit(1477617599.314:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8565 comm="apparmor_parser"
Oct 28 01:19:59 node-1 cron[8608]: (CRON) INFO (pidfile fd = 3)
Oct 28 01:19:59 node-1 anacron[8625]: Anacron 2.3 started on 2016-10-28
Oct 28 01:19:59 node-1 cron[8638]: (CRON) STARTUP (fork ok)
Oct 28 01:19:59 node-1 anacron[8625]: Will run job `cron.daily' in 5 min.
Oct 28 01:19:59 node-1 anacron[8625]: Will run job `cron.weekly' in 10 min.
Oct 28 01:19:59 node-1 anacron[8625]: Will run job `cron.monthly' in 15 min.
Oct 28 01:19:59 node-1 anacron[8625]: Jobs will be executed sequentially
Oct 28 01:19:59 node-1 multipathd: path checkers start up
Oct 28 01:19:59 node-1 cron[8638]: (CRON) INFO (Running @reboot jobs)
Oct 28 01:19:59 node-1 postfix/master[8787]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 28 01:20:01 node-1 CRON[8922]: (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 28 01:20:03 node-1 puppet-agent[9104]: Reopening log files
Oct 28 01:20:04 node-1 puppet-agent[9104]: Could not request certificate: Connection refused - connect(2)
Oct 28 01:20:05 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 01:20:05 node-1 nailgun-agent: D, [2016-10-28T01:20:01.694995 #8925] DEBUG -- : Sleep for 4 seconds before sending request
Oct 28 01:20:05 node-1 nailgun-agent: I, [2016-10-28T01:20:05.710040 #8925]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 28 01:20:06 node-1 nailgun-agent: D, [2016-10-28T01:20:06.070354 #8925] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 28 01:20:15 node-1 puppet-user[9321]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 28 01:20:16 node-1 puppet-user[9321]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 28 01:20:17 node-1 puppet-user[9321]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 28 01:20:17 node-1 puppet-user[9321]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 28 01:20:17 node-1 puppet-user[9321]: Finished catalog run in 1.00 seconds
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.942639 #8925] DEBUG -- : Trying to find block devices
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.942753 #8925] DEBUG -- : Found block device: sda
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.942800 #8925] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.942822 #8925] DEBUG -- : Trying to get list of physical devices
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.942992 #8925] DEBUG -- : Getting udev properties for device: sda
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.945012 #8925] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc7884
Oct 28 01:20:17 node-1 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70156", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.945039 #8925] DEBUG -- : Trying to find out if device sda is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.945091 #8925] DEBUG -- : Device sda removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.945108 #8925] DEBUG -- : Device sda seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.945533 #8925] DEBUG -- : Getting udev properties for device: dm-0
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.947295 #8925] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-qt08k7Bz0wyPAKfmfJX4RCdgMOuOdobNQu5dcqDS3UrqH6mCGZVNLOgJFtvqwK5s /dev/disk/by-uuid/4b86ea2b-7377-4bc8-a9ef-72e2b0b6d865 /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-qt08k7Bz0wyPAKfmfJX4RCdgMOuOdobNQu5dcqDS3UrqH6mCGZVNLOgJFtvqwK5s", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4b86ea2b-7377-4bc8-a9ef-72e2b0b6d865", "ID_FS_UUID_ENC"=>"4b86ea2b-7377-4bc8-a9ef-72e2b0b6d865", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93
Oct 28 01:20:17 node-1 nailgun-agent: 699", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.947344 #8925] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.947379 #8925] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.947408 #8925] DEBUG -- : Device dm-0 seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.947424 #8925] DEBUG -- : Getting udev properties for device: dm-1
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.949078 #8925] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-Y0Hz4d6WdNtQfFX7eO3LCQYMEzGGHjEF2iLQIfcJAJo1X2NkBFMypZlHOORrFsjq /dev/disk/by-uuid/3566bef9-b161-41d9-b713-4820af79a184 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-Y0Hz4d6WdNtQfFX7eO3LCQYMEzGGHjEF2iLQIfcJAJo1X2NkBFMypZlHOORrFsjq", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3566bef9-b161-41d9-b713-4820af79a184", "ID_FS_UUID_ENC"=>"3566bef9-b161-41d9-b713-4820af79a184", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17788", "nomdmonddf"=>"1", "nomd
Oct 28 01:20:17 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.949107 #8925] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.949179 #8925] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.949195 #8925] DEBUG -- : Device dm-1 seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.949211 #8925] DEBUG -- : Getting udev properties for device: dm-2
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.950681 #8925] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-ygY6vYha9gZT5OxEp7eFqzEM8Rqtm6ImZhO5L9lrYlplkDNC4sKI6BheL5SD0Ju9 /dev/disk/by-uuid/aeb594bf-ae56-4ff9-b2ad-9d1fd1904c30 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-ygY6vYha9gZT5OxEp7eFqzEM8Rqtm6ImZhO5L9lrYlplkDNC4sKI6BheL5SD0Ju9", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"aeb594bf-ae56-4ff9-b2ad-9d1fd1904c30", "ID_FS_UUID_ENC"=>"aeb594bf-ae56-4ff9-b2ad-9d1fd1904c30", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36
Oct 28 01:20:17 node-1 nailgun-agent: 576", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.950706 #8925] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.950753 #8925] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.950767 #8925] DEBUG -- : Device dm-2 seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.950781 #8925] DEBUG -- : Getting udev properties for device: dm-3
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.952311 #8925] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-13pDMEqqI4RSzT1FNeqlOeBivXKziQIPmRYGIEK3Y34EQ062nrHLfHnQB3HKNtRJ /dev/disk/by-uuid/790ca99f-13a9-4549-9b67-2d263a27e4aa /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-13pDMEqqI4RSzT1FNeqlOeBivXKziQIPmRYGIEK3Y34EQ062nrHLfHnQB3HKNtRJ", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"790ca99f-13a9-4549-9b67-2d263a27e4aa", "ID_FS_UUID_ENC"=>"790ca99f-13a9-4549-9b67-2d263a27e4aa", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46789", "nomdmond
Oct 28 01:20:17 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.952342 #8925] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.952386 #8925] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.952400 #8925] DEBUG -- : Device dm-3 seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.952414 #8925] DEBUG -- : Getting udev properties for device: dm-4
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.953977 #8925] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-u95c3xbxdicZFFz4dSBF4FkqZNvUs2qig4DMAiyVkBXqNtCbSANBZJtby9b8ozi5 /dev/disk/by-uuid/c92f491b-06dc-4c13-9066-60722c771d3a /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-u95c3xbxdicZFFz4dSBF4FkqZNvUs2qig4DMAiyVkBXqNtCbSANBZJtby9b8ozi5", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c92f491b-06dc-4c13-9066-60722c771d3a", "ID_FS_UUID_ENC"=>"c92f491b-06dc-4c13-9066-60722c771d3a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61624", "nomdmonddf"=>"1", 
Oct 28 01:20:17 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.954012 #8925] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.954059 #8925] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.954081 #8925] DEBUG -- : Device dm-4 seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.954106 #8925] DEBUG -- : Getting udev properties for device: dm-5
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.955807 #8925] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-3LyvMx0mz5fZPIFUdtV6dXZSr3G9jlCuJTihieffWkf0LrBm6IZczWzVLQu0GB61 /dev/disk/by-uuid/89357548-6ae6-4bf3-95f6-9fa83c618de3 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-3LyvMx0mz5fZPIFUdtV6dXZSr3G9jlCuJTihieffWkf0LrBm6IZczWzVLQu0GB61", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"89357548-6ae6-4bf3-95f6-9fa83c618de3", "ID_FS_UUID_ENC"=>"89357548-6ae6-4bf3-95f6-9fa83c618de3", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69549", "nomdmonddf"=>"1", "nomd
Oct 28 01:20:17 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.955831 #8925] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.955873 #8925] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.955888 #8925] DEBUG -- : Device dm-5 seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.955903 #8925] DEBUG -- : Getting udev properties for device: dm-6
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.957445 #8925] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-3LyvMx0mz5fZPIFUdtV6dXZSr3G9jlCuHWOrVDyBIYJ0H3iqZdveDfD43raT8Sua /dev/disk/by-uuid/85b5fd38-c8c2-4265-8599-d62a873f4751 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-3LyvMx0mz5fZPIFUdtV6dXZSr3G9jlCuHWOrVDyBIYJ0H3iqZdveDfD43raT8Sua", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"85b5fd38-c8c2-4265-8599-d62a873f4751", "ID_FS_UUID_ENC"=>"85b5fd38-c8c2-4265-8599-d62a873f4751", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69955", "nomdmonddf"=>"1", "nomdmonisw"
Oct 28 01:20:17 node-1 nailgun-agent: =>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.957479 #8925] DEBUG -- : Trying to find out if device dm-6 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.957528 #8925] DEBUG -- : Device dm-6 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.957598 #8925] DEBUG -- : Device dm-6 seems to be appropriate
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.957623 #8925] DEBUG -- : Getting udev properties for device: ram0
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.959198 #8925] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87986", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.959256 #8925] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.959297 #8925] DEBUG -- : Device ram0 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.959318 #8925] DEBUG -- : Getting udev properties for device: ram1
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.960764 #8925] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87993", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.960790 #8925] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.960829 #8925] DEBUG -- : Device ram1 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.960869 #8925] DEBUG -- : Getting udev properties for device: ram2
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.962265 #8925] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88079", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.962287 #8925] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.962318 #8925] DEBUG -- : Device ram2 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.962366 #8925] DEBUG -- : Getting udev properties for device: ram3
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.963693 #8925] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88095", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.963747 #8925] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.963783 #8925] DEBUG -- : Device ram3 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.963803 #8925] DEBUG -- : Getting udev properties for device: ram4
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.965151 #8925] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88114", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.965172 #8925] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.965203 #8925] DEBUG -- : Device ram4 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.965222 #8925] DEBUG -- : Getting udev properties for device: ram5
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.967084 #8925] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88129", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.967143 #8925] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.967187 #8925] DEBUG -- : Device ram5 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.967212 #8925] DEBUG -- : Getting udev properties for device: ram6
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.968865 #8925] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88145", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.968903 #8925] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.968937 #8925] DEBUG -- : Device ram6 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.968958 #8925] DEBUG -- : Getting udev properties for device: ram7
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.970413 #8925] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88161", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.970455 #8925] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.970503 #8925] DEBUG -- : Device ram7 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.970523 #8925] DEBUG -- : Getting udev properties for device: ram8
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.971943 #8925] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88177", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.971968 #8925] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.972019 #8925] DEBUG -- : Device ram8 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.972039 #8925] DEBUG -- : Getting udev properties for device: ram9
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.973840 #8925] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88191", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.973896 #8925] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.973955 #8925] DEBUG -- : Device ram9 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.973997 #8925] DEBUG -- : Getting udev properties for device: loop0
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.975526 #8925] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87923", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.975557 #8925] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.975600 #8925] DEBUG -- : Device loop0 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.975620 #8925] DEBUG -- : Getting udev properties for device: loop1
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.977139 #8925] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87933", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.977181 #8925] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.977215 #8925] DEBUG -- : Device loop1 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.977234 #8925] DEBUG -- : Getting udev properties for device: loop2
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.979395 #8925] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87941", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.979429 #8925] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.979474 #8925] DEBUG -- : Device loop2 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.979503 #8925] DEBUG -- : Getting udev properties for device: loop3
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.980890 #8925] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87947", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.980915 #8925] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.980952 #8925] DEBUG -- : Device loop3 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.980992 #8925] DEBUG -- : Getting udev properties for device: loop4
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.982408 #8925] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87954", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.982441 #8925] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.982474 #8925] DEBUG -- : Device loop4 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.982514 #8925] DEBUG -- : Getting udev properties for device: loop5
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.983857 #8925] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87963", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.983882 #8925] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.983933 #8925] DEBUG -- : Device loop5 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.983967 #8925] DEBUG -- : Getting udev properties for device: loop6
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.985341 #8925] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87972", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.985367 #8925] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.985400 #8925] DEBUG -- : Device loop6 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.985431 #8925] DEBUG -- : Getting udev properties for device: loop7
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.986859 #8925] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87979", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.986880 #8925] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.986911 #8925] DEBUG -- : Device loop7 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.986931 #8925] DEBUG -- : Getting udev properties for device: ram10
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.988820 #8925] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88007", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.988851 #8925] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.988899 #8925] DEBUG -- : Device ram10 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.988918 #8925] DEBUG -- : Getting udev properties for device: ram11
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.990345 #8925] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88020", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.990375 #8925] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.990447 #8925] DEBUG -- : Device ram11 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.990505 #8925] DEBUG -- : Getting udev properties for device: ram12
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.991998 #8925] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88031", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.992037 #8925] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.992077 #8925] DEBUG -- : Device ram12 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.992112 #8925] DEBUG -- : Getting udev properties for device: ram13
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.993588 #8925] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88044", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.993638 #8925] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.993681 #8925] DEBUG -- : Device ram13 removable parameter: "0"
Oct 28 01:20:17 node-1 nailgun-agent: D, [2016-10-28T01:20:17.993699 #8925] DEBUG -- : Getting udev properties for device: ram14
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:17.995103 #8925] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88057", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:17.995124 #8925] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:17.995174 #8925] DEBUG -- : Device ram14 removable parameter: "0"
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:17.995200 #8925] DEBUG -- : Getting udev properties for device: ram15
Oct 28 01:20:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001625 #8925] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88068", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001658 #8925] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001705 #8925] DEBUG -- : Device ram15 removable parameter: "0"
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001756 #8925] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001830 #8925] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001895 #8925] DEBUG -- : Found block device: dm-0
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001921 #8925] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001946 #8925] DEBUG -- : Found block device: dm-1
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001966 #8925] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001983 #8925] DEBUG -- : Found block device: dm-2
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.001999 #8925] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002015 #8925] DEBUG -- : Found block device: dm-3
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002033 #8925] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002050 #8925] DEBUG -- : Found block device: dm-4
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002117 #8925] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002134 #8925] DEBUG -- : Found block device: dm-5
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002150 #8925] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002164 #8925] DEBUG -- : Found block device: dm-6
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002178 #8925] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002190 #8925] DEBUG -- : Found block device: ram0
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002204 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002217 #8925] DEBUG -- : Found block device: ram1
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002231 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002286 #8925] DEBUG -- : Found block device: ram2
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002301 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002314 #8925] DEBUG -- : Found block device: ram3
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002328 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002340 #8925] DEBUG -- : Found block device: ram4
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002356 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002369 #8925] DEBUG -- : Found block device: ram5
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002383 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002395 #8925] DEBUG -- : Found block device: ram6
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002446 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002462 #8925] DEBUG -- : Found block device: ram7
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002476 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002489 #8925] DEBUG -- : Found block device: ram8
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002502 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002515 #8925] DEBUG -- : Found block device: ram9
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002530 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002543 #8925] DEBUG -- : Found block device: loop0
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002557 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002612 #8925] DEBUG -- : Found block device: loop1
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002628 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002640 #8925] DEBUG -- : Found block device: loop2
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002656 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002669 #8925] DEBUG -- : Found block device: loop3
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002682 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002694 #8925] DEBUG -- : Found block device: loop4
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002708 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002721 #8925] DEBUG -- : Found block device: loop5
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002780 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002794 #8925] DEBUG -- : Found block device: loop6
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002809 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002822 #8925] DEBUG -- : Found block device: loop7
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002836 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002848 #8925] DEBUG -- : Found block device: ram10
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002862 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002874 #8925] DEBUG -- : Found block device: ram11
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002888 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002901 #8925] DEBUG -- : Found block device: ram12
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002945 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002959 #8925] DEBUG -- : Found block device: ram13
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002975 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.002988 #8925] DEBUG -- : Found block device: ram14
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.003003 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.003015 #8925] DEBUG -- : Found block device: ram15
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.003029 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.003066 #8925] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.102744 #8925] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 28 01:20:18 node-1 nailgun-agent: D, [2016-10-28T01:20:18.102860 #8925] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 28 01:20:18 node-1 multipathd: uevent trigger error
Oct 28 01:20:18 node-1 puppet-user[9943]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 01:20:18 node-1 puppet-user[9943]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 28 01:20:18 node-1 puppet-user[9943]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 28 01:20:18 node-1 puppet-user[9943]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 28 01:20:18 node-1 puppet-user[9943]: (/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 28 01:20:18 node-1 puppet-user[9943]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 28 01:20:18 node-1 puppet-user[9943]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 28 01:20:18 node-1 puppet-user[9943]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 28 01:20:18 node-1 puppet-user[9943]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 28 01:20:18 node-1 puppet-user[9943]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 28 01:20:18 node-1 puppet-user[9943]: Finished catalog run in 0.07 seconds
Oct 28 01:20:20 node-1 puppet-user[10588]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 28 01:20:20 node-1 puppet-user[10588]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 28 01:20:20 node-1 puppet-user[10588]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 28 01:20:20 node-1 puppet-user[10588]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 28 01:20:20 node-1 puppet-user[10588]: Finished catalog run in 0.04 seconds
Oct 28 01:20:22 node-1 puppet-user[11053]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 28 01:20:22 node-1 puppet-user[11053]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 01:20:22 node-1 puppet-user[11053]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 28 01:20:22 node-1 puppet-user[11053]: Finished catalog run in 0.04 seconds
Oct 28 01:20:23 node-1 puppet-user[11507]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 28 01:20:23 node-1 puppet-user[11507]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Oct 28 01:20:24 node-1 puppet-user[11507]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 28 01:20:24 node-1 puppet-user[11507]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Oct 28 01:20:24 node-1 puppet-user[11507]: Finished catalog run in 0.44 seconds
Oct 28 01:20:25 node-1 puppet-user[11988]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 28 01:20:26 node-1 puppet-user[11988]: Compiled catalog for node-1.domain.tld in environment production in 0.28 seconds
Oct 28 01:20:26 node-1 puppet-user[11988]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Oct 28 01:20:26 node-1 puppet-user[11988]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 28 01:20:26 node-1 puppet-user[11988]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 28 01:20:26 node-1 puppet-user[11988]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 28 01:20:26 node-1 puppet-user[11988]: Finished catalog run in 0.27 seconds
Oct 28 01:20:28 node-1 puppet-user[12478]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 28 01:20:28 node-1 puppet-user[12478]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Oct 28 01:20:28 node-1 puppet-user[12478]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 28 01:20:28 node-1 kernel: [   68.582373] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 28 01:20:28 node-1 kernel: [   68.582422] 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 28 01:20:28 node-1 puppet-user[12478]: (/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 28 01:20:28 node-1 puppet-user[12478]: Finished catalog run in 0.07 seconds
Oct 28 01:20:28 node-1 kernel: [   68.878124] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 01:20:29 node-1 puppet-agent[9104]: Could not run: SIGTERM
Oct 28 01:20:29 node-1 kernel: [   69.173310] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 28 01:20:29 node-1 ec2: 
Oct 28 01:20:29 node-1 ec2: #############################################################
Oct 28 01:20:29 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 28 01:20:29 node-1 ec2: 1024 3e:4f:8b:60:5f:14:f1:6f:38:f1:1a:e0:4c:4d:5c:c2  root@node-1.domain.tld (DSA)
Oct 28 01:20:29 node-1 ec2: 256 90:ac:86:d6:4b:c6:06:a3:d7:bc:f4:dc:23:3a:27:d8  root@node-1.domain.tld (ECDSA)
Oct 28 01:20:29 node-1 ec2: 256 1c:b6:de:cf:7b:f0:be:4b:fb:e6:26:b1:49:fe:b4:d0  root@node-1.domain.tld (ED25519)
Oct 28 01:20:29 node-1 ec2: 2048 5e:98:a5:da:68:05:8d:9c:5e:55:53:01:1d:ef:86:1f  root@node-1.domain.tld (RSA)
Oct 28 01:20:29 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 28 01:20:29 node-1 ec2: #############################################################
Oct 28 01:20:30 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094429 #8925] DEBUG -- : Trying to find block devices
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094534 #8925] DEBUG -- : Found block device: sda
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094562 #8925] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094580 #8925] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094601 #8925] DEBUG -- : Found block device: dm-0
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094615 #8925] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094627 #8925] DEBUG -- : Found block device: dm-1
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094638 #8925] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094648 #8925] DEBUG -- : Found block device: dm-2
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094657 #8925] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094706 #8925] DEBUG -- : Found block device: dm-3
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094716 #8925] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094726 #8925] DEBUG -- : Found block device: dm-4
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094747 #8925] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094755 #8925] DEBUG -- : Found block device: dm-5
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094765 #8925] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094774 #8925] DEBUG -- : Found block device: dm-6
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094785 #8925] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094793 #8925] DEBUG -- : Found block device: ram0
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094804 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094813 #8925] DEBUG -- : Found block device: ram1
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094868 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094877 #8925] DEBUG -- : Found block device: ram2
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094887 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094896 #8925] DEBUG -- : Found block device: ram3
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094906 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094914 #8925] DEBUG -- : Found block device: ram4
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094923 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094932 #8925] DEBUG -- : Found block device: ram5
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094941 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094949 #8925] DEBUG -- : Found block device: ram6
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094986 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.094996 #8925] DEBUG -- : Found block device: ram7
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095007 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095015 #8925] DEBUG -- : Found block device: ram8
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095023 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095032 #8925] DEBUG -- : Found block device: ram9
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095042 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095050 #8925] DEBUG -- : Found block device: loop0
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095059 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095067 #8925] DEBUG -- : Found block device: loop1
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095077 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095111 #8925] DEBUG -- : Found block device: loop2
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095121 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095130 #8925] DEBUG -- : Found block device: loop3
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095139 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095147 #8925] DEBUG -- : Found block device: loop4
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095156 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095164 #8925] DEBUG -- : Found block device: loop5
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095174 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095182 #8925] DEBUG -- : Found block device: loop6
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095192 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095221 #8925] DEBUG -- : Found block device: loop7
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095231 #8925] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095239 #8925] DEBUG -- : Found block device: ram10
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095248 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095256 #8925] DEBUG -- : Found block device: ram11
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095265 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095295 #8925] DEBUG -- : Found block device: ram12
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095305 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095313 #8925] DEBUG -- : Found block device: ram13
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095322 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095331 #8925] DEBUG -- : Found block device: ram14
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095340 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095349 #8925] DEBUG -- : Found block device: ram15
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095360 #8925] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.095411 #8925] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct 28 01:20:30 node-1 nailgun-agent: D, [2016-10-28T01:20:30.243498 #8925] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 28 01:20:30 node-1 nailgun-agent: I, [2016-10-28T01:20:30.243689 #8925]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 28 01:20:30 node-1 puppet-user[13106]: (Scope(Class[main])) MODULAR: sync_time
Oct 28 01:20:30 node-1 puppet-user[13106]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 28 01:20:30 node-1 ntpdate[13641]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 28 01:20:36 node-1 ntpdate[13641]: adjust time server 10.20.0.2 offset -0.479114 sec
Oct 28 01:20:36 node-1 puppet-user[13106]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 28 01:20:36 node-1 puppet-user[13106]: Finished catalog run in 6.18 seconds
Oct 28 01:20:41 node-1 puppet-user[13823]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 01:20:41 node-1 puppet-user[13823]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 28 01:20:41 node-1 puppet-user[13823]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 28 01:20:41 node-1 puppet-user[13823]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs"]'
Oct 28 01:20:41 node-1 puppet-user[13823]: Finished catalog run in 0.08 seconds
Oct 28 01:20:42 node-1 puppet-user[14283]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 28 01:20:43 node-1 puppet-user[14283]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Oct 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:43 node-1 puppet-user[14283]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:43 node-1 puppet-user[14283]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:43 node-1 puppet-user[14283]: (/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 28 01:20:44 node-1 puppet-user[14283]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 28 01:20:44 node-1 puppet-user[14283]: Finished catalog run in 0.81 seconds
Oct 28 01:20:45 node-1 puppet-user[14795]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 28 01:20:45 node-1 puppet-user[14795]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct 28 01:20:49 node-1 puppet-user[14795]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 28 01:21:01 node-1 CRON[16746]: (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 28 01:21:18 node-1 puppet-user[14795]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 28 01:21:18 node-1 puppet-user[14795]: Finished catalog run in 32.65 seconds
Oct 28 01:21:20 node-1 puppet-user[17702]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 28 01:21:21 node-1 puppet-user[17702]: Compiled catalog for node-1.domain.tld in environment production in 0.62 seconds
Oct 28 01:21:21 node-1 puppet-user[17702]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 28 01:21:21 node-1 puppet-user[17702]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 28 01:21:21 node-1 puppet-user[17702]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 28 01:21:21 node-1 puppet-user[17702]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 28 01:21:21 node-1 puppet-user[17702]: Finished catalog run in 0.08 seconds
Oct 28 01:21:23 node-1 puppet-user[18176]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 28 01:21:23 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 01:21:23 node-1 nailgun-agent: I, [2016-10-28T01:21:23.418770 #16749]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 28 01:21:24 node-1 puppet-user[18176]: Compiled catalog for node-1.domain.tld in environment production in 0.91 seconds
Oct 28 01:21:24 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 28 01:21:24 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 28 01:21:24 node-1 crontab[18756]: (root) LIST (root)
Oct 28 01:21:24 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 28 01:21:24 node-1 crontab[18757]: (root) REPLACE (root)
Oct 28 01:21:25 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 28 01:21:26 node-1 puppet-user[18176]: (/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 28 01:21:26 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 28 01:21:27 node-1 puppet-user[18176]: (/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 28 01:21:27 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8423" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 01:21:27 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 28 01:21:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:21:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:22:32 node-1 ntpdate[29190]: no servers can be used, exiting
<27>Oct 28 01:23:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:23:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 01:24:29 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 01:24:35 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 01:24:35 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 01:24:41 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 01:24:47 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 01:24:47 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 01:24:54 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:54 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:54 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:54 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:54 node-1 multipathd: uevent trigger error
<27>Oct 28 01:24:54 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:07 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:09 node-1 haproxy[17312]: 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 28 01:25:10 node-1 haproxy[17316]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:11 node-1 haproxy[17316]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:11 node-1 haproxy[17316]: proxy mysqld has no server available!
<27>Oct 28 01:25:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:16 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:16 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:16 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:16 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:16 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:19 node-1 haproxy[20096]: 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 28 01:25:19 node-1 haproxy[20096]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:19 node-1 haproxy[20096]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:19 node-1 haproxy[20096]: proxy mysqld has no server available!
<129>Oct 28 01:25:20 node-1 haproxy[20103]: 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 28 01:25:20 node-1 haproxy[20103]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:20 node-1 haproxy[20103]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:20 node-1 haproxy[20103]: proxy object-storage has no server available!
<27>Oct 28 01:25:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:22 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:24 node-1 haproxy[21498]: 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 28 01:25:24 node-1 haproxy[21498]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:24 node-1 haproxy[21498]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:24 node-1 haproxy[21498]: proxy neutron has no server available!
<129>Oct 28 01:25:25 node-1 haproxy[21502]: 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 28 01:25:25 node-1 haproxy[21502]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:25 node-1 haproxy[21502]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:25 node-1 haproxy[21502]: proxy mysqld has no server available!
<129>Oct 28 01:25:25 node-1 haproxy[21502]: 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 28 01:25:26 node-1 haproxy[21502]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:26 node-1 haproxy[21502]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:26 node-1 haproxy[21502]: proxy object-storage has no server available!
<27>Oct 28 01:25:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:27 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:27 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:29 node-1 haproxy[23109]: 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 28 01:25:30 node-1 haproxy[23113]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:30 node-1 haproxy[23113]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:30 node-1 haproxy[23113]: proxy keystone-1 has no server available!
<129>Oct 28 01:25:30 node-1 haproxy[23113]: 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 28 01:25:30 node-1 haproxy[23113]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:30 node-1 haproxy[23113]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:30 node-1 haproxy[23113]: proxy keystone-2 has no server available!
<129>Oct 28 01:25:30 node-1 haproxy[23113]: 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 28 01:25:30 node-1 haproxy[23113]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:31 node-1 haproxy[23113]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:31 node-1 haproxy[23113]: proxy neutron has no server available!
<129>Oct 28 01:25:31 node-1 haproxy[23113]: 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 28 01:25:31 node-1 haproxy[23113]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:31 node-1 haproxy[23113]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:31 node-1 haproxy[23113]: proxy mysqld has no server available!
<129>Oct 28 01:25:31 node-1 haproxy[23113]: 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 28 01:25:31 node-1 haproxy[23113]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:31 node-1 haproxy[23113]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:31 node-1 haproxy[23113]: proxy object-storage has no server available!
<27>Oct 28 01:25:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:33 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:35 node-1 haproxy[24528]: 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 28 01:25:35 node-1 haproxy[24528]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:35 node-1 haproxy[24528]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:35 node-1 haproxy[24528]: proxy keystone-1 has no server available!
<129>Oct 28 01:25:35 node-1 haproxy[24528]: 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 28 01:25:35 node-1 haproxy[24528]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:36 node-1 haproxy[24532]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:36 node-1 haproxy[24532]: proxy keystone-2 has no server available!
<129>Oct 28 01:25:36 node-1 haproxy[24532]: 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 28 01:25:36 node-1 haproxy[24532]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:36 node-1 haproxy[24532]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:36 node-1 haproxy[24532]: proxy neutron has no server available!
<129>Oct 28 01:25:36 node-1 haproxy[24532]: 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 28 01:25:36 node-1 haproxy[24532]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:36 node-1 haproxy[24532]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:36 node-1 haproxy[24532]: proxy mysqld has no server available!
<129>Oct 28 01:25:36 node-1 haproxy[24532]: 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 28 01:25:36 node-1 haproxy[24532]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:37 node-1 haproxy[24532]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:37 node-1 haproxy[24532]: proxy object-storage has no server available!
<129>Oct 28 01:25:37 node-1 haproxy[24532]: 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 28 01:25:37 node-1 haproxy[24532]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:37 node-1 haproxy[24532]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:37 node-1 haproxy[24532]: proxy aodh has no server available!
<27>Oct 28 01:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:38 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:40 node-1 haproxy[25973]: 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 28 01:25:41 node-1 haproxy[25977]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:41 node-1 haproxy[25977]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:41 node-1 haproxy[25977]: proxy keystone-1 has no server available!
<129>Oct 28 01:25:41 node-1 haproxy[25977]: 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 28 01:25:41 node-1 haproxy[25977]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:41 node-1 haproxy[25977]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:41 node-1 haproxy[25977]: proxy keystone-2 has no server available!
<129>Oct 28 01:25:41 node-1 haproxy[25977]: 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 28 01:25:41 node-1 haproxy[25977]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:41 node-1 haproxy[25977]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:41 node-1 haproxy[25977]: proxy neutron has no server available!
<129>Oct 28 01:25:41 node-1 haproxy[25977]: 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 28 01:25:41 node-1 haproxy[25977]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:42 node-1 haproxy[25977]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:42 node-1 haproxy[25977]: proxy mysqld has no server available!
<129>Oct 28 01:25:42 node-1 haproxy[25977]: 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 28 01:25:42 node-1 haproxy[25977]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:42 node-1 haproxy[25977]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:42 node-1 haproxy[25977]: proxy object-storage has no server available!
<129>Oct 28 01:25:42 node-1 haproxy[25977]: 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 28 01:25:42 node-1 haproxy[25977]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:42 node-1 haproxy[25977]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:42 node-1 haproxy[25977]: proxy aodh has no server available!
<129>Oct 28 01:25:42 node-1 haproxy[25977]: 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 28 01:25:42 node-1 haproxy[25977]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:42 node-1 haproxy[25977]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:42 node-1 haproxy[25977]: proxy ceilometer has no server available!
<27>Oct 28 01:25:44 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:44 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:44 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:44 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:44 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:44 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:46 node-1 haproxy[27386]: 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 28 01:25:46 node-1 haproxy[27386]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:46 node-1 haproxy[27386]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:46 node-1 haproxy[27386]: proxy keystone-1 has no server available!
<129>Oct 28 01:25:46 node-1 haproxy[27386]: 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 28 01:25:46 node-1 haproxy[27386]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:47 node-1 haproxy[27390]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:47 node-1 haproxy[27390]: proxy keystone-2 has no server available!
<129>Oct 28 01:25:47 node-1 haproxy[27390]: 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 28 01:25:47 node-1 haproxy[27390]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:47 node-1 haproxy[27390]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:47 node-1 haproxy[27390]: proxy neutron has no server available!
<129>Oct 28 01:25:47 node-1 haproxy[27390]: 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 28 01:25:47 node-1 haproxy[27390]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:47 node-1 haproxy[27390]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:47 node-1 haproxy[27390]: proxy mysqld has no server available!
<129>Oct 28 01:25:47 node-1 haproxy[27390]: 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 28 01:25:47 node-1 haproxy[27390]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:47 node-1 haproxy[27390]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:47 node-1 haproxy[27390]: proxy object-storage has no server available!
<129>Oct 28 01:25:48 node-1 haproxy[27390]: 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 28 01:25:48 node-1 haproxy[27390]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:48 node-1 haproxy[27390]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:48 node-1 haproxy[27390]: proxy aodh has no server available!
<129>Oct 28 01:25:48 node-1 haproxy[27390]: 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 28 01:25:48 node-1 haproxy[27390]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:48 node-1 haproxy[27390]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:48 node-1 haproxy[27390]: proxy ceilometer has no server available!
<27>Oct 28 01:25:49 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:49 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:49 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:49 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:51 node-1 haproxy[28765]: 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 28 01:25:52 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 28 01:25:52 node-1 haproxy[28772]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:52 node-1 haproxy[28772]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:52 node-1 haproxy[28772]: proxy keystone-1 has no server available!
<129>Oct 28 01:25:52 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 28 01:25:52 node-1 haproxy[28772]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:52 node-1 haproxy[28772]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:52 node-1 haproxy[28772]: proxy keystone-2 has no server available!
<129>Oct 28 01:25:52 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 28 01:25:52 node-1 haproxy[28772]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:52 node-1 haproxy[28772]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:52 node-1 haproxy[28772]: proxy neutron has no server available!
<129>Oct 28 01:25:52 node-1 haproxy[28772]: 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 28 01:25:52 node-1 haproxy[28772]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:53 node-1 haproxy[28772]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:53 node-1 haproxy[28772]: proxy mysqld has no server available!
<129>Oct 28 01:25:53 node-1 haproxy[28772]: 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 28 01:25:53 node-1 haproxy[28772]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:53 node-1 haproxy[28772]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:53 node-1 haproxy[28772]: proxy object-storage has no server available!
<129>Oct 28 01:25:53 node-1 haproxy[28772]: 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 28 01:25:53 node-1 haproxy[28772]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:53 node-1 haproxy[28772]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:53 node-1 haproxy[28772]: proxy aodh has no server available!
<129>Oct 28 01:25:53 node-1 haproxy[28772]: 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 28 01:25:53 node-1 haproxy[28772]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:53 node-1 haproxy[28772]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:53 node-1 haproxy[28772]: proxy ceilometer has no server available!
<27>Oct 28 01:25:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:25:55 node-1 multipathd: uevent trigger error
<129>Oct 28 01:25:57 node-1 haproxy[30224]: 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 28 01:25:57 node-1 haproxy[30224]: 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 28 01:25:58 node-1 haproxy[30228]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:58 node-1 haproxy[30228]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:58 node-1 haproxy[30228]: proxy keystone-1 has no server available!
<129>Oct 28 01:25:58 node-1 haproxy[30228]: 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 28 01:25:58 node-1 haproxy[30228]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:58 node-1 haproxy[30228]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:58 node-1 haproxy[30228]: proxy keystone-2 has no server available!
<129>Oct 28 01:25:58 node-1 haproxy[30228]: 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 28 01:25:58 node-1 haproxy[30228]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:58 node-1 haproxy[30228]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:58 node-1 haproxy[30228]: proxy glance-api has no server available!
<129>Oct 28 01:25:58 node-1 haproxy[30228]: 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 28 01:25:58 node-1 haproxy[30228]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:58 node-1 haproxy[30228]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:58 node-1 haproxy[30228]: proxy glance-glare has no server available!
<129>Oct 28 01:25:58 node-1 haproxy[30228]: 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 28 01:25:58 node-1 haproxy[30228]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:58 node-1 haproxy[30228]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:58 node-1 haproxy[30228]: proxy neutron has no server available!
<129>Oct 28 01:25:58 node-1 haproxy[30228]: 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 28 01:25:58 node-1 haproxy[30228]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:58 node-1 haproxy[30228]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:58 node-1 haproxy[30228]: proxy glance-registry has no server available!
<129>Oct 28 01:25:59 node-1 haproxy[30228]: 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 28 01:25:59 node-1 haproxy[30228]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:59 node-1 haproxy[30228]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:59 node-1 haproxy[30228]: proxy mysqld has no server available!
<129>Oct 28 01:25:59 node-1 haproxy[30228]: 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 28 01:25:59 node-1 haproxy[30228]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:59 node-1 haproxy[30228]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:59 node-1 haproxy[30228]: proxy object-storage has no server available!
<129>Oct 28 01:25:59 node-1 haproxy[30228]: 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 28 01:25:59 node-1 haproxy[30228]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:59 node-1 haproxy[30228]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:59 node-1 haproxy[30228]: proxy aodh has no server available!
<129>Oct 28 01:25:59 node-1 haproxy[30228]: 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 28 01:25:59 node-1 haproxy[30228]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:25:59 node-1 haproxy[30228]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:25:59 node-1 haproxy[30228]: proxy ceilometer has no server available!
<27>Oct 28 01:26:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:01 node-1 multipathd: uevent trigger error
<129>Oct 28 01:26:03 node-1 haproxy[31687]: 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 28 01:26:04 node-1 haproxy[31691]: 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 28 01:26:04 node-1 haproxy[31691]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:04 node-1 haproxy[31691]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:04 node-1 haproxy[31691]: proxy keystone-1 has no server available!
<129>Oct 28 01:26:04 node-1 haproxy[31691]: 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 28 01:26:04 node-1 haproxy[31691]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:04 node-1 haproxy[31691]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:04 node-1 haproxy[31691]: proxy keystone-2 has no server available!
<129>Oct 28 01:26:04 node-1 haproxy[31691]: 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 28 01:26:04 node-1 haproxy[31691]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:04 node-1 haproxy[31691]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:04 node-1 haproxy[31691]: proxy nova-api has no server available!
<129>Oct 28 01:26:04 node-1 haproxy[31691]: 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 28 01:26:04 node-1 haproxy[31691]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:04 node-1 haproxy[31691]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:04 node-1 haproxy[31691]: proxy nova-metadata-api has no server available!
<129>Oct 28 01:26:04 node-1 haproxy[31691]: 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 28 01:26:04 node-1 haproxy[31691]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:04 node-1 haproxy[31691]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:04 node-1 haproxy[31691]: proxy glance-api has no server available!
<129>Oct 28 01:26:04 node-1 haproxy[31691]: 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 28 01:26:04 node-1 haproxy[31691]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:04 node-1 haproxy[31691]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:04 node-1 haproxy[31691]: proxy glance-glare has no server available!
<129>Oct 28 01:26:04 node-1 haproxy[31691]: 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 28 01:26:04 node-1 haproxy[31691]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:04 node-1 haproxy[31691]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:04 node-1 haproxy[31691]: proxy neutron has no server available!
<129>Oct 28 01:26:05 node-1 haproxy[31691]: 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 28 01:26:05 node-1 haproxy[31691]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:05 node-1 haproxy[31691]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:05 node-1 haproxy[31691]: proxy glance-registry has no server available!
<129>Oct 28 01:26:05 node-1 haproxy[31691]: 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 28 01:26:05 node-1 haproxy[31691]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:05 node-1 haproxy[31691]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:05 node-1 haproxy[31691]: proxy mysqld has no server available!
<129>Oct 28 01:26:05 node-1 haproxy[31691]: 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 28 01:26:05 node-1 haproxy[31691]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:05 node-1 haproxy[31691]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:05 node-1 haproxy[31691]: proxy object-storage has no server available!
<129>Oct 28 01:26:05 node-1 haproxy[31691]: 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 28 01:26:05 node-1 haproxy[31691]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:05 node-1 haproxy[31691]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:05 node-1 haproxy[31691]: proxy aodh has no server available!
<129>Oct 28 01:26:05 node-1 haproxy[31691]: 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 28 01:26:05 node-1 haproxy[31691]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:05 node-1 haproxy[31691]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:05 node-1 haproxy[31691]: proxy ceilometer has no server available!
<129>Oct 28 01:26:05 node-1 haproxy[31691]: 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 28 01:26:05 node-1 haproxy[31691]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:05 node-1 haproxy[31691]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:05 node-1 haproxy[31691]: proxy nova-novncproxy has no server available!
<27>Oct 28 01:26:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:07 node-1 multipathd: uevent trigger error
<129>Oct 28 01:26:09 node-1 haproxy[631]: 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 28 01:26:09 node-1 haproxy[631]: 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 28 01:26:09 node-1 haproxy[631]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:09 node-1 haproxy[631]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:09 node-1 haproxy[631]: proxy keystone-1 has no server available!
<129>Oct 28 01:26:09 node-1 haproxy[631]: 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 28 01:26:09 node-1 haproxy[631]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:09 node-1 haproxy[631]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:09 node-1 haproxy[631]: proxy keystone-2 has no server available!
<129>Oct 28 01:26:09 node-1 haproxy[631]: 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 28 01:26:09 node-1 haproxy[631]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:09 node-1 haproxy[631]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:09 node-1 haproxy[631]: proxy nova-api has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:10 node-1 haproxy[637]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:10 node-1 haproxy[637]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:10 node-1 haproxy[637]: proxy nova-metadata-api has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:10 node-1 haproxy[637]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:10 node-1 haproxy[637]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:10 node-1 haproxy[637]: proxy cinder-api has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:10 node-1 haproxy[637]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:10 node-1 haproxy[637]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:10 node-1 haproxy[637]: proxy glance-api has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:10 node-1 haproxy[637]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:10 node-1 haproxy[637]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:10 node-1 haproxy[637]: proxy glance-glare has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:10 node-1 haproxy[637]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:10 node-1 haproxy[637]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:10 node-1 haproxy[637]: proxy neutron has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:10 node-1 haproxy[637]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:10 node-1 haproxy[637]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:10 node-1 haproxy[637]: proxy glance-registry has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:10 node-1 haproxy[637]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:10 node-1 haproxy[637]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:10 node-1 haproxy[637]: proxy mysqld has no server available!
<129>Oct 28 01:26:10 node-1 haproxy[637]: 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 28 01:26:11 node-1 haproxy[637]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:11 node-1 haproxy[637]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:11 node-1 haproxy[637]: proxy object-storage has no server available!
<129>Oct 28 01:26:11 node-1 haproxy[637]: 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 28 01:26:11 node-1 haproxy[637]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:11 node-1 haproxy[637]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:11 node-1 haproxy[637]: proxy aodh has no server available!
<129>Oct 28 01:26:11 node-1 haproxy[637]: 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 28 01:26:11 node-1 haproxy[637]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:11 node-1 haproxy[637]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:11 node-1 haproxy[637]: proxy ceilometer has no server available!
<129>Oct 28 01:26:11 node-1 haproxy[637]: 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 28 01:26:11 node-1 haproxy[637]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:11 node-1 haproxy[637]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:11 node-1 haproxy[637]: proxy nova-novncproxy has no server available!
<27>Oct 28 01:26:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:12 node-1 multipathd: uevent trigger error
<129>Oct 28 01:26:15 node-1 haproxy[2110]: 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 28 01:26:15 node-1 haproxy[2110]: 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 28 01:26:15 node-1 haproxy[2110]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:15 node-1 haproxy[2110]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:15 node-1 haproxy[2110]: proxy keystone-1 has no server available!
<129>Oct 28 01:26:15 node-1 haproxy[2110]: 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 28 01:26:15 node-1 haproxy[2110]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:15 node-1 haproxy[2110]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:15 node-1 haproxy[2110]: proxy keystone-2 has no server available!
<129>Oct 28 01:26:15 node-1 haproxy[2110]: 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 28 01:26:15 node-1 haproxy[2110]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:15 node-1 haproxy[2110]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:15 node-1 haproxy[2110]: proxy nova-api has no server available!
<129>Oct 28 01:26:15 node-1 haproxy[2110]: 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 28 01:26:15 node-1 haproxy[2110]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:15 node-1 haproxy[2110]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:15 node-1 haproxy[2110]: proxy nova-metadata-api has no server available!
<129>Oct 28 01:26:15 node-1 haproxy[2110]: 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 28 01:26:16 node-1 haproxy[2117]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy cinder-api has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy glance-api has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy glance-glare has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy neutron has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy glance-registry has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy mysqld has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy object-storage has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy aodh has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:16 node-1 haproxy[2117]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:16 node-1 haproxy[2117]: proxy ceilometer has no server available!
<129>Oct 28 01:26:16 node-1 haproxy[2117]: 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 28 01:26:16 node-1 haproxy[2117]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:17 node-1 haproxy[2117]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:17 node-1 haproxy[2117]: proxy heat-api has no server available!
<129>Oct 28 01:26:17 node-1 haproxy[2117]: 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 28 01:26:17 node-1 haproxy[2117]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:17 node-1 haproxy[2117]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:17 node-1 haproxy[2117]: proxy heat-api-cfn has no server available!
<129>Oct 28 01:26:17 node-1 haproxy[2117]: 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 28 01:26:17 node-1 haproxy[2117]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:17 node-1 haproxy[2117]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:17 node-1 haproxy[2117]: proxy heat-api-cloudwatch has no server available!
<129>Oct 28 01:26:17 node-1 haproxy[2117]: 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 28 01:26:17 node-1 haproxy[2117]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 01:26:17 node-1 haproxy[2117]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 01:26:17 node-1 haproxy[2117]: proxy nova-novncproxy has no server available!
<27>Oct 28 01:26:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:26:29 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 28 01:26:53 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 28 01:26:55 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 28 01:27:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:27:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 01:27:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:27:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:27:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:27:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:27:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:27:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:07 node-1 multipathd: uevent trigger error
<43>Oct 28 01:30:28 node-1 apache2_error [Fri Oct 28 01:30:19.066629 2016] [mpm_event:notice] [pid 9602:tid 140663974958976] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 01:30:28 node-1 apache2_error [Fri Oct 28 01:30:19.066689 2016] [core:notice] [pid 9602:tid 140663974958976] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 01:30:28 node-1 apache2_error [Fri Oct 28 01:30:22.322823 2016] [mpm_event:notice] [pid 9602:tid 140663974958976] AH00491: caught SIGTERM, shutting down
<43>Oct 28 01:30:28 node-1 apache2_error [Fri Oct 28 01:30:23.411841 2016] [mpm_worker:notice] [pid 11214:tid 140091616946048] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 01:30:28 node-1 apache2_error [Fri Oct 28 01:30:23.411861 2016] [core:notice] [pid 11214:tid 140091616946048] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 01:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:30:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:30:36 node-1 multipathd: uevent trigger error
<43>Oct 28 01:31:48 node-1 apache2_error [Fri Oct 28 01:31:42.935654 2016] [mpm_worker:notice] [pid 11214:tid 140091616946048] AH00295: caught SIGTERM, shutting down
<43>Oct 28 01:31:48 node-1 apache2_error [Fri Oct 28 01:31:43.686930 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 01:31:48 node-1 apache2_error [Fri Oct 28 01:31:43.686971 2016] [core:notice] [pid 25176:tid 140622281189248] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 01:32:38 node-1 apache2_error [Fri Oct 28 01:32:28.772631 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 01:32:38 node-1 apache2_error [Fri Oct 28 01:32:28.964766 2016] [mpm_worker:warn] [pid 25176:tid 140622281189248] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 01:32:38 node-1 apache2_error [Fri Oct 28 01:32:28.968800 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 01:32:38 node-1 apache2_error [Fri Oct 28 01:32:28.968825 2016] [core:notice] [pid 25176:tid 140622281189248] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 01:33:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:13 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:34 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:34 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:34 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:34 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:34 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:36 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:33:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:33:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:00 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:34:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:35:55 node-1 multipathd: uevent trigger error
<27>Oct 28 01:36:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:37:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:37:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:37:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:37:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:37:04 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:02 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:24 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:24 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:24 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:24 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:24 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:24 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:38:30 node-1 multipathd: uevent trigger error
<27>Oct 28 01:39:39 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:40:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:40:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:40:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:40:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:40:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:20 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:20 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:20 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:20 node-1 multipathd: uevent trigger error
<27>Oct 28 01:41:20 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:42:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:43:15 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:15 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:15 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:15 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:15 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:15 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Interface
<27>Oct 28 01:43:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Port
<27>Oct 28 01:43:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-prv" in table Port
<27>Oct 28 01:43:23 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct 28 01:43:23 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct 28 01:43:23 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct 28 01:43:23 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:23 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:23 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:23 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:23 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:50 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:50 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:50 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:50 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:50 node-1 multipathd: uevent trigger error
<27>Oct 28 01:43:50 node-1 multipathd: uevent trigger error
<27>Oct 28 01:44:08 node-1 multipathd: uevent trigger error
<27>Oct 28 01:44:08 node-1 multipathd: uevent trigger error
<27>Oct 28 01:44:08 node-1 multipathd: uevent trigger error
<27>Oct 28 01:44:08 node-1 multipathd: uevent trigger error
<27>Oct 28 01:44:08 node-1 multipathd: uevent trigger error
<27>Oct 28 01:45:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:46:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:28 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:46:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:21 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:21 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:21 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:21 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:21 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:48 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:48 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:48 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:48 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:48 node-1 multipathd: uevent trigger error
<27>Oct 28 01:47:48 node-1 multipathd: uevent trigger error
<27>Oct 28 01:48:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:48:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:48:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:48:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:48:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:48:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:49:41 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:41 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:41 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:41 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:41 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:58 node-1 multipathd: uevent trigger error
<27>Oct 28 01:49:58 node-1 multipathd: uevent trigger error
<11>Oct 28 01:50:11 node-1 liberasurecode[12139]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:11 node-1 liberasurecode[12139]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:11 node-1 liberasurecode[12139]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:11 node-1 liberasurecode[12139]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:11 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:11 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:11 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:11 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:13 node-1 liberasurecode[13247]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:13 node-1 liberasurecode[13247]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:13 node-1 liberasurecode[13247]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:13 node-1 liberasurecode[13247]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14829]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14829]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14829]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14829]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14868]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14868]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14868]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14868]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14916]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14916]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14916]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:17 node-1 liberasurecode[14916]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14977]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14977]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14977]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14977]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14992]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14992]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14992]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[14992]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15006]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15006]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15006]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15006]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15018]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:18 node-1 liberasurecode[15018]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:27 node-1 liberasurecode[15491]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:27 node-1 liberasurecode[15491]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:27 node-1 liberasurecode[15491]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:50:27 node-1 liberasurecode[15491]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 01:50:35 node-1 multipathd: uevent trigger error
<27>Oct 28 01:50:35 node-1 multipathd: uevent trigger error
<27>Oct 28 01:50:35 node-1 multipathd: uevent trigger error
<27>Oct 28 01:50:36 node-1 multipathd: uevent trigger error
<27>Oct 28 01:50:36 node-1 multipathd: uevent trigger error
<43>Oct 28 01:51:29 node-1 apache2_error [Fri Oct 28 01:51:26.053486 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 01:51:29 node-1 apache2_error [Fri Oct 28 01:51:26.434925 2016] [mpm_worker:warn] [pid 25176:tid 140622281189248] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 01:51:29 node-1 apache2_error [Fri Oct 28 01:51:26.438061 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 01:51:29 node-1 apache2_error [Fri Oct 28 01:51:26.438081 2016] [core:notice] [pid 25176:tid 140622281189248] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 01:51:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 01:52:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:07 node-1 multipathd: uevent trigger error
<43>Oct 28 01:52:09 node-1 apache2_error [Fri Oct 28 01:52:03.159985 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 01:52:09 node-1 apache2_error [Fri Oct 28 01:52:03.354292 2016] [mpm_worker:warn] [pid 25176:tid 140622281189248] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 01:52:09 node-1 apache2_error [Fri Oct 28 01:52:03.358421 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 01:52:09 node-1 apache2_error [Fri Oct 28 01:52:03.358443 2016] [core:notice] [pid 25176:tid 140622281189248] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 01:52:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:14 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:14 node-1 multipathd: uevent trigger error
<43>Oct 28 01:52:49 node-1 apache2_error [Fri Oct 28 01:52:49.162286 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 01:52:49 node-1 apache2_error [Fri Oct 28 01:52:49.359197 2016] [mpm_worker:warn] [pid 25176:tid 140622281189248] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 01:52:49 node-1 apache2_error [Fri Oct 28 01:52:49.364211 2016] [mpm_worker:notice] [pid 25176:tid 140622281189248] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 01:52:49 node-1 apache2_error [Fri Oct 28 01:52:49.364227 2016] [core:notice] [pid 25176:tid 140622281189248] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 01:52:53 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:53 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:53 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:53 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:53 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:52:59 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:45 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:52 node-1 multipathd: uevent trigger error
<27>Oct 28 01:53:58 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 28 01:54:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:07 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:12 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:17 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:17 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:17 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:17 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:17 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:22 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:33 node-1 multipathd: uevent trigger error
<27>Oct 28 01:54:34 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 01:55:00 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:00 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:00 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:00 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:00 node-1 multipathd: uevent trigger error
<11>Oct 28 01:55:01 node-1 liberasurecode[10859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:55:01 node-1 liberasurecode[10859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:55:01 node-1 liberasurecode[10859]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 01:55:01 node-1 liberasurecode[10859]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 01:55:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:05 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:18 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:25 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:29 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:41 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:46 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:51 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:55:56 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:06 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:06 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:06 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:06 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:06 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:10 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:10 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:10 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:10 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:10 node-1 multipathd: uevent trigger error
<27>Oct 28 01:56:10 node-1 multipathd: uevent trigger error
