Sep 24 01:21:54 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8392" x-info="http://www.rsyslog.com"] start
Sep 24 01:21:53 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 24 01:21:54 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 24 01:21:54 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 24 01:21:54 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 24 01:21:54 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 24 01:21:54 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 24 01:21:54 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 24 01:21:54 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1c20c864-b690-4cb8-b630-2581e79208ce nomdmonddf nomdmonisw
Sep 24 01:21:54 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 24 01:21:54 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 24 01:21:54 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 24 01:21:54 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 24 01:21:54 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 24 01:21:54 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 24 01:21:54 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 24 01:21:54 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Sep 24 01:21:54 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 24 01:21:54 node-1 kernel: [    0.000000] No AGP bridge found
Sep 24 01:21:54 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 24 01:21:54 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 24 01:21:54 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 24 01:21:54 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 24 01:21:54 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 24 01:21:54 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 24 01:21:54 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 24 01:21:54 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 24 01:21:54 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 24 01:21:54 node-1 kernel: [    0.000000]   2 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000]   3 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000]   4 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000]   5 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000]   6 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000]   7 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000]   8 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000]   9 disabled
Sep 24 01:21:54 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 24 01:21:54 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 24 01:21:54 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 24 01:21:54 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 24 01:21:54 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 24 01:21:54 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 24 01:21:54 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 24 01:21:54 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 24 01:21:54 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 24 01:21:54 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 24 01:21:54 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 24 01:21:54 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 24 01:21:54 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 24 01:21:54 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 24 01:21:54 node-1 kernel: [    0.000000] Zone ranges:
Sep 24 01:21:54 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 24 01:21:54 node-1 kernel: [    0.000000] Early memory node ranges
Sep 24 01:21:54 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep 24 01:21:54 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 24 01:21:54 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 24 01:21:54 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 24 01:21:54 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep 24 01:21:54 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep 24 01:21:54 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 24 01:21:54 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 24 01:21:54 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 24 01:21:54 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 24 01:21:54 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 24 01:21:54 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 24 01:21:54 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 24 01:21:54 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 24 01:21:54 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 24 01:21:54 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 24 01:21:54 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 24 01:21:54 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 24 01:21:54 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 24 01:21:54 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 24 01:21:54 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 24 01:21:54 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 24 01:21:54 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 24 01:21:54 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Sep 24 01:21:54 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep 24 01:21:54 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 24 01:21:54 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1c20c864-b690-4cb8-b630-2581e79208ce nomdmonddf nomdmonisw
Sep 24 01:21:54 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 24 01:21:54 node-1 kernel: [    0.000000] Checking aperture...
Sep 24 01:21:54 node-1 kernel: [    0.000000] No AGP bridge found
Sep 24 01:21:54 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 24 01:21:54 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 24 01:21:54 node-1 kernel: [    0.000000] Memory: 32653452K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Sep 24 01:21:54 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 24 01:21:54 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 24 01:21:54 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 24 01:21:54 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 24 01:21:54 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 24 01:21:54 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 24 01:21:54 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 24 01:21:54 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 24 01:21:54 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 24 01:21:54 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 24 01:21:54 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 24 01:21:54 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 24 01:21:54 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 24 01:21:54 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 24 01:21:54 node-1 kernel: [    0.004000] tsc: Detected 3491.647 MHz processor
Sep 24 01:21:54 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.29 BogoMIPS (lpj=13966588)
Sep 24 01:21:54 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 24 01:21:54 node-1 kernel: [    0.000049] Security Framework initialized
Sep 24 01:21:54 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Sep 24 01:21:54 node-1 kernel: [    0.000068] Yama: becoming mindful.
Sep 24 01:21:54 node-1 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.006303] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.008227] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.008255] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.008545] Initializing cgroup subsys memory
Sep 24 01:21:54 node-1 kernel: [    0.008554] Initializing cgroup subsys devices
Sep 24 01:21:54 node-1 kernel: [    0.008555] Initializing cgroup subsys freezer
Sep 24 01:21:54 node-1 kernel: [    0.008557] Initializing cgroup subsys blkio
Sep 24 01:21:54 node-1 kernel: [    0.008559] Initializing cgroup subsys perf_event
Sep 24 01:21:54 node-1 kernel: [    0.008561] Initializing cgroup subsys hugetlb
Sep 24 01:21:54 node-1 kernel: [    0.008580] CPU: Physical Processor ID: 0
Sep 24 01:21:54 node-1 kernel: [    0.008582] CPU: Processor Core ID: 0
Sep 24 01:21:54 node-1 kernel: [    0.008586] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 24 01:21:54 node-1 kernel: [    0.008586] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 24 01:21:54 node-1 kernel: [    0.009280] mce: CPU supports 22 MCE banks
Sep 24 01:21:54 node-1 kernel: [    0.009307] CPU0: Thermal monitoring enabled (TM1)
Sep 24 01:21:54 node-1 kernel: [    0.009328] process: using mwait in idle threads
Sep 24 01:21:54 node-1 kernel: [    0.009331] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 24 01:21:54 node-1 kernel: [    0.009331] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 24 01:21:54 node-1 kernel: [    0.009331] tlb_flushall_shift: 6
Sep 24 01:21:54 node-1 kernel: [    0.009420] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 24 01:21:54 node-1 kernel: [    0.010146] ACPI: Core revision 20131115
Sep 24 01:21:54 node-1 kernel: [    0.022811] ACPI: All ACPI Tables successfully acquired
Sep 24 01:21:54 node-1 kernel: [    0.022974] ftrace: allocating 28617 entries in 112 pages
Sep 24 01:21:54 node-1 kernel: [    0.031955] dmar: Host address width 46
Sep 24 01:21:54 node-1 kernel: [    0.031957] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 24 01:21:54 node-1 kernel: [    0.031963] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 24 01:21:54 node-1 kernel: [    0.031965] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 24 01:21:54 node-1 kernel: [    0.031969] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 24 01:21:54 node-1 kernel: [    0.031971] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 24 01:21:54 node-1 kernel: [    0.031972] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 24 01:21:54 node-1 kernel: [    0.031973] dmar: ATSR flags: 0x0
Sep 24 01:21:54 node-1 kernel: [    0.031974] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 24 01:21:54 node-1 kernel: [    0.031975] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 24 01:21:54 node-1 kernel: [    0.032091] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 24 01:21:54 node-1 kernel: [    0.032092] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 24 01:21:54 node-1 kernel: [    0.032093] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 24 01:21:54 node-1 kernel: [    0.032094] HPET id 0 under DRHD base 0xc7ffc000
Sep 24 01:21:54 node-1 kernel: [    0.032095] Your BIOS is broken and requested that x2apic be disabled.
Sep 24 01:21:54 node-1 kernel: [    0.032095] This will slightly decrease performance.
Sep 24 01:21:54 node-1 kernel: [    0.032095] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 24 01:21:54 node-1 kernel: [    0.032527] Enabled IRQ remapping in xapic mode
Sep 24 01:21:54 node-1 kernel: [    0.032528] x2apic not enabled, IRQ remapping is in xapic mode
Sep 24 01:21:54 node-1 kernel: [    0.032532] Switched APIC routing to physical flat.
Sep 24 01:21:54 node-1 kernel: [    0.033109] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 24 01:21:54 node-1 kernel: [    0.072755] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 24 01:21:54 node-1 kernel: [    0.072761] TSC deadline timer enabled
Sep 24 01:21:54 node-1 kernel: [    0.072768] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 24 01:21:54 node-1 kernel: [    0.072774] ... version:                3
Sep 24 01:21:54 node-1 kernel: [    0.072775] ... bit width:              48
Sep 24 01:21:54 node-1 kernel: [    0.072776] ... generic registers:      4
Sep 24 01:21:54 node-1 kernel: [    0.072777] ... value mask:             0000ffffffffffff
Sep 24 01:21:54 node-1 kernel: [    0.072779] ... max period:             0000ffffffffffff
Sep 24 01:21:54 node-1 kernel: [    0.072779] ... fixed-purpose events:   3
Sep 24 01:21:54 node-1 kernel: [    0.072780] ... event mask:             000000070000000f
Sep 24 01:21:54 node-1 kernel: [    0.074167] x86: Booting SMP configuration:
Sep 24 01:21:54 node-1 kernel: [    0.088269] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 24 01:21:54 node-1 kernel: [    0.074169] .... node  #0, CPUs:        #1  #2  #3
Sep 24 01:21:54 node-1 kernel: [    0.116177] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 24 01:21:54 node-1 kernel: [    0.270300] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 24 01:21:54 node-1 kernel: [    0.325920] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 24 01:21:54 node-1 kernel: [    0.382969] x86: Booted up 2 nodes, 16 CPUs
Sep 24 01:21:54 node-1 kernel: [    0.382973] smpboot: Total of 16 processors activated (111745.08 BogoMIPS)
Sep 24 01:21:54 node-1 kernel: [    0.407501] devtmpfs: initialized
Sep 24 01:21:54 node-1 kernel: [    0.410606] EVM: security.selinux
Sep 24 01:21:54 node-1 kernel: [    0.410608] EVM: security.SMACK64
Sep 24 01:21:54 node-1 kernel: [    0.410609] EVM: security.ima
Sep 24 01:21:54 node-1 kernel: [    0.410610] EVM: security.capability
Sep 24 01:21:54 node-1 kernel: [    0.410660] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.411333] pinctrl core: initialized pinctrl subsystem
Sep 24 01:21:54 node-1 kernel: [    0.411394] regulator-dummy: no parameters
Sep 24 01:21:54 node-1 kernel: [    0.411426] RTC time:  1:21:12, date: 09/24/16
Sep 24 01:21:54 node-1 kernel: [    0.411460] NET: Registered protocol family 16
Sep 24 01:21:54 node-1 kernel: [    0.411545] cpuidle: using governor ladder
Sep 24 01:21:54 node-1 kernel: [    0.411546] cpuidle: using governor menu
Sep 24 01:21:54 node-1 kernel: [    0.411582] ACPI: bus type PCI registered
Sep 24 01:21:54 node-1 kernel: [    0.411584] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 24 01:21:54 node-1 kernel: [    0.411630] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 24 01:21:54 node-1 kernel: [    0.411632] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 24 01:21:54 node-1 kernel: [    0.425365] PCI: Using configuration type 1 for base access
Sep 24 01:21:54 node-1 kernel: [    0.426356] bio: create slab <bio-0> at 0
Sep 24 01:21:54 node-1 kernel: [    0.426635] ACPI: Added _OSI(Module Device)
Sep 24 01:21:54 node-1 kernel: [    0.426637] ACPI: Added _OSI(Processor Device)
Sep 24 01:21:54 node-1 kernel: [    0.426638] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 24 01:21:54 node-1 kernel: [    0.426639] ACPI: Added _OSI(Processor Aggregator Device)
Sep 24 01:21:54 node-1 kernel: [    0.439311] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 24 01:21:54 node-1 kernel: [    0.451075] ACPI: Interpreter enabled
Sep 24 01:21:54 node-1 kernel: [    0.451080] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 24 01:21:54 node-1 kernel: [    0.451084] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 24 01:21:54 node-1 kernel: [    0.451087] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 24 01:21:54 node-1 kernel: [    0.451094] ACPI: (supports S0 S4 S5)
Sep 24 01:21:54 node-1 kernel: [    0.451095] ACPI: Using IOAPIC for interrupt routing
Sep 24 01:21:54 node-1 kernel: [    0.451139] HEST: Table parsing has been initialized.
Sep 24 01:21:54 node-1 kernel: [    0.451142] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 24 01:21:54 node-1 kernel: [    0.451698] ACPI: No dock devices found.
Sep 24 01:21:54 node-1 kernel: [    0.463416] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 24 01:21:54 node-1 kernel: [    0.463420] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 24 01:21:54 node-1 kernel: [    0.463424] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 24 01:21:54 node-1 kernel: [    0.463450] PCI host bridge to bus 0000:ff
Sep 24 01:21:54 node-1 kernel: [    0.463452] pci_bus 0000:ff: root bus resource [bus ff]
Sep 24 01:21:54 node-1 kernel: [    0.463460] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 24 01:21:54 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 24 01:21:54 node-1 kernel: [    0.463499] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.463529] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463562] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463591] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.463620] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.463651] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463680] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463709] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463738] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463764] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463791] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463819] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463845] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463872] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463899] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463927] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463957] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.463984] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.464012] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464038] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.464064] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464090] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464120] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.464155] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464186] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464217] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464248] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464279] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464310] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464341] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464372] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464403] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464434] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464465] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464496] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464528] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464559] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464587] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464619] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464655] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464696] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464733] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464765] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464797] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464827] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464860] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464892] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464926] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464957] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.464990] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465019] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465049] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465078] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465108] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465144] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465176] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465234] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 24 01:21:54 node-1 kernel: [    0.465237] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 24 01:21:54 node-1 kernel: [    0.465240] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 24 01:21:54 node-1 kernel: [    0.465258] PCI host bridge to bus 0000:7f
Sep 24 01:21:54 node-1 kernel: [    0.465260] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 24 01:21:54 node-1 kernel: [    0.465265] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465292] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.465320] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465351] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465373] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.465398] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.465424] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465449] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465472] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465494] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465517] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465539] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465563] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465585] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465609] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465634] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465656] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465678] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465701] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.465725] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465747] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.465768] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465791] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465817] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 24 01:21:54 node-1 kernel: [    0.465849] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465876] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465904] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465931] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465957] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.465984] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466011] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466039] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466065] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466092] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466120] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466148] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466177] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466202] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466228] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466258] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466284] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466310] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466340] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466367] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466393] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466419] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466447] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466477] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466505] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466533] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466563] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466590] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466614] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466641] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466667] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466698] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.466725] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.467983] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 24 01:21:54 node-1 kernel: [    0.467986] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 24 01:21:54 node-1 kernel: [    0.469105] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 24 01:21:54 node-1 kernel: [    0.469621] PCI host bridge to bus 0000:00
Sep 24 01:21:54 node-1 kernel: [    0.469623] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 24 01:21:54 node-1 kernel: [    0.469625] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 24 01:21:54 node-1 kernel: [    0.469626] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 24 01:21:54 node-1 kernel: [    0.469627] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 24 01:21:54 node-1 kernel: [    0.469629] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 24 01:21:54 node-1 kernel: [    0.469630] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 24 01:21:54 node-1 kernel: [    0.469631] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 24 01:21:54 node-1 kernel: [    0.469637] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 24 01:21:54 node-1 kernel: [    0.469721] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.469751] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.469793] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 24 01:21:54 node-1 kernel: [    0.469813] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.469842] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.469882] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 24 01:21:54 node-1 kernel: [    0.469901] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.469931] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.469971] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 24 01:21:54 node-1 kernel: [    0.469989] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.470061] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.470140] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.470218] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 24 01:21:54 node-1 kernel: [    0.470223] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 24 01:21:54 node-1 kernel: [    0.470307] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 24 01:21:54 node-1 kernel: [    0.470454] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 24 01:21:54 node-1 kernel: [    0.470471] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 24 01:21:54 node-1 kernel: [    0.470549] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.470602] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 24 01:21:54 node-1 kernel: [    0.470623] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.470679] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.470722] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 24 01:21:54 node-1 kernel: [    0.470749] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.470805] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.470848] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 24 01:21:54 node-1 kernel: [    0.470872] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 24 01:21:54 node-1 kernel: [    0.470890] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 24 01:21:54 node-1 kernel: [    0.470967] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.471017] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 24 01:21:54 node-1 kernel: [    0.471043] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 24 01:21:54 node-1 kernel: [    0.471290] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 24 01:21:54 node-1 kernel: [    0.471296] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 24 01:21:54 node-1 kernel: [    0.471302] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.471308] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.471315] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 24 01:21:54 node-1 kernel: [    0.471345] pci 0000:01:00.0: supports D1 D2
Sep 24 01:21:54 node-1 kernel: [    0.481133] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 24 01:21:54 node-1 kernel: [    0.481139] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 24 01:21:54 node-1 kernel: [    0.481143] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 24 01:21:54 node-1 kernel: [    0.481407] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.481461] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 24 01:21:54 node-1 kernel: [    0.489128] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 24 01:21:54 node-1 kernel: [    0.489131] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.489133] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 24 01:21:54 node-1 kernel: [    0.489188] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.489256] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.489332] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.489377] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 24 01:21:54 node-1 kernel: [    0.489380] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.489382] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 24 01:21:54 node-1 kernel: [    0.489435] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.489591] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.489646] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 24 01:21:54 node-1 kernel: [    0.489648] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.489650] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.489702] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.489826] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.489870] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.489996] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.490034] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.490156] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.490196] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 24 01:21:54 node-1 kernel: [    0.490316] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 24 01:21:54 node-1 kernel: [    0.490356] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 24 01:21:54 node-1 kernel: [    0.490358] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.490360] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.490420] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 24 01:21:54 node-1 kernel: [    0.490484] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.490565] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.490605] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 24 01:21:54 node-1 kernel: [    0.490685] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 24 01:21:54 node-1 kernel: [    0.490791] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 24 01:21:54 node-1 kernel: [    0.490794] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.490796] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.490852] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 24 01:21:54 node-1 kernel: [    0.490906] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.490958] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.491168] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 24 01:21:54 node-1 kernel: [    0.491172] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 24 01:21:54 node-1 kernel: [    0.491234] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 24 01:21:54 node-1 kernel: [    0.491286] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.491335] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.491564] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 24 01:21:54 node-1 kernel: [    0.491567] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 24 01:21:54 node-1 kernel: [    0.491626] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 24 01:21:54 node-1 kernel: [    0.491689] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.491741] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 24 01:21:54 node-1 kernel: [    0.491963] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 24 01:21:54 node-1 kernel: [    0.491967] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 24 01:21:54 node-1 kernel: [    0.492142] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 24 01:21:54 node-1 kernel: [    0.492180] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 24 01:21:54 node-1 kernel: [    0.492256] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 24 01:21:54 node-1 kernel: [    0.492275] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 24 01:21:54 node-1 kernel: [    0.492288] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 24 01:21:54 node-1 kernel: [    0.492301] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 24 01:21:54 node-1 kernel: [    0.492351] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 24 01:21:54 node-1 kernel: [    0.497142] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 24 01:21:54 node-1 kernel: [    0.497151] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 24 01:21:54 node-1 kernel: [    0.497203] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 24 01:21:54 node-1 kernel: [    0.497943] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 24 01:21:54 node-1 kernel: [    0.497946] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 24 01:21:54 node-1 kernel: [    0.498065] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 24 01:21:54 node-1 kernel: [    0.498175] PCI host bridge to bus 0000:80
Sep 24 01:21:54 node-1 kernel: [    0.498177] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 24 01:21:54 node-1 kernel: [    0.498178] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 24 01:21:54 node-1 kernel: [    0.498180] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 24 01:21:54 node-1 kernel: [    0.498188] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.498251] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.498319] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 24 01:21:54 node-1 kernel: [    0.498381] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 24 01:21:54 node-1 kernel: [    0.498387] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 24 01:21:54 node-1 kernel: [    0.498457] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 24 01:21:54 node-1 kernel: [    0.498754] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 24 01:21:54 node-1 kernel: [    0.498786] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 24 01:21:54 node-1 kernel: [    0.498815] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 24 01:21:54 node-1 kernel: [    0.498845] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 24 01:21:54 node-1 kernel: [    0.498874] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 24 01:21:54 node-1 kernel: [    0.498904] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 24 01:21:54 node-1 kernel: [    0.498934] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 24 01:21:54 node-1 kernel: [    0.498964] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 24 01:21:54 node-1 kernel: [    0.499049] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 24 01:21:54 node-1 kernel: [    0.499053] ACPI: \_SB_.UNC1: notify handler is installed
Sep 24 01:21:54 node-1 kernel: [    0.499055] ACPI: \_SB_.UNC0: notify handler is installed
Sep 24 01:21:54 node-1 kernel: [    0.499070] ACPI: \_SB_.PCI0: notify handler is installed
Sep 24 01:21:54 node-1 kernel: [    0.499122] ACPI: \_SB_.PCI1: notify handler is installed
Sep 24 01:21:54 node-1 kernel: [    0.499202] Found 4 acpi root devices
Sep 24 01:21:54 node-1 kernel: [    0.499311] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 24 01:21:54 node-1 kernel: [    0.499313] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 24 01:21:54 node-1 kernel: [    0.499314] vgaarb: loaded
Sep 24 01:21:54 node-1 kernel: [    0.499315] vgaarb: bridge control possible 0000:0c:00.0
Sep 24 01:21:54 node-1 kernel: [    0.499433] SCSI subsystem initialized
Sep 24 01:21:54 node-1 kernel: [    0.499495] libata version 3.00 loaded.
Sep 24 01:21:54 node-1 kernel: [    0.499511] ACPI: bus type USB registered
Sep 24 01:21:54 node-1 kernel: [    0.499522] usbcore: registered new interface driver usbfs
Sep 24 01:21:54 node-1 kernel: [    0.499527] usbcore: registered new interface driver hub
Sep 24 01:21:54 node-1 kernel: [    0.499551] usbcore: registered new device driver usb
Sep 24 01:21:54 node-1 kernel: [    0.499717] PCI: Using ACPI for IRQ routing
Sep 24 01:21:54 node-1 kernel: [    0.503306] PCI: pci_cache_line_size set to 64 bytes
Sep 24 01:21:54 node-1 kernel: [    0.503527] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 24 01:21:54 node-1 kernel: [    0.503528] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep 24 01:21:54 node-1 kernel: [    0.503529] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 24 01:21:54 node-1 kernel: [    0.503594] NetLabel: Initializing
Sep 24 01:21:54 node-1 kernel: [    0.503596] NetLabel:  domain hash size = 128
Sep 24 01:21:54 node-1 kernel: [    0.503596] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 24 01:21:54 node-1 kernel: [    0.503606] NetLabel:  unlabeled traffic allowed by default
Sep 24 01:21:54 node-1 kernel: [    0.503664] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 24 01:21:54 node-1 kernel: [    0.503668] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 24 01:21:54 node-1 kernel: [    0.505742] Switched to clocksource hpet
Sep 24 01:21:54 node-1 kernel: [    0.510123] AppArmor: AppArmor Filesystem Enabled
Sep 24 01:21:54 node-1 kernel: [    0.510160] pnp: PnP ACPI init
Sep 24 01:21:54 node-1 kernel: [    0.510173] ACPI: bus type PNP registered
Sep 24 01:21:54 node-1 kernel: [    0.510354] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510366] pnp 00:01: [dma 4]
Sep 24 01:21:54 node-1 kernel: [    0.510384] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510419] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510444] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510465] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510512] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510623] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510625] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 24 01:21:54 node-1 kernel: [    0.510627] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510628] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510630] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510631] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510634] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 24 01:21:54 node-1 kernel: [    0.510636] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510638] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510639] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510641] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510642] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510644] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 24 01:21:54 node-1 kernel: [    0.510646] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510746] pnp 00:07: [dma 0 disabled]
Sep 24 01:21:54 node-1 kernel: [    0.510779] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510860] pnp 00:08: [dma 0 disabled]
Sep 24 01:21:54 node-1 kernel: [    0.510896] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 24 01:21:54 node-1 kernel: [    0.510954] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 24 01:21:54 node-1 kernel: [    0.511403] pnp: PnP ACPI: found 10 devices
Sep 24 01:21:54 node-1 kernel: [    0.511405] ACPI: bus type PNP unregistered
Sep 24 01:21:54 node-1 kernel: [    0.517418] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 24 01:21:54 node-1 kernel: [    0.517422] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 24 01:21:54 node-1 kernel: [    0.517425] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 24 01:21:54 node-1 kernel: [    0.517430] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 24 01:21:54 node-1 kernel: [    0.517432] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517447] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517476] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 24 01:21:54 node-1 kernel: [    0.517505] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517533] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 24 01:21:54 node-1 kernel: [    0.517548] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 24 01:21:54 node-1 kernel: [    0.517577] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 24 01:21:54 node-1 kernel: [    0.517591] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 24 01:21:54 node-1 kernel: [    0.517620] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 24 01:21:54 node-1 kernel: [    0.517622] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517637] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517666] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 24 01:21:54 node-1 kernel: [    0.517668] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517683] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517712] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 24 01:21:54 node-1 kernel: [    0.517714] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517721] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517726] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 24 01:21:54 node-1 kernel: [    0.517728] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517730] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517735] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 24 01:21:54 node-1 kernel: [    0.517741] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 24 01:21:54 node-1 kernel: [    0.517750] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 24 01:21:54 node-1 kernel: [    0.517753] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 24 01:21:54 node-1 kernel: [    0.517760] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 24 01:21:54 node-1 kernel: [    0.517761] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 24 01:21:54 node-1 kernel: [    0.517762] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 24 01:21:54 node-1 kernel: [    0.517763] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 24 01:21:54 node-1 kernel: [    0.517764] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 24 01:21:54 node-1 kernel: [    0.517765] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 24 01:21:54 node-1 kernel: [    0.517766] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 24 01:21:54 node-1 kernel: [    0.517767] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 24 01:21:54 node-1 kernel: [    0.517768] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517769] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517770] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517771] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517772] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517773] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517774] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517775] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517776] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 24 01:21:54 node-1 kernel: [    0.517777] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517778] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 24 01:21:54 node-1 kernel: [    0.517779] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 24 01:21:54 node-1 kernel: [    0.517780] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 24 01:21:54 node-1 kernel: [    0.517781] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 24 01:21:54 node-1 kernel: [    0.517784] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 24 01:21:54 node-1 kernel: [    0.517785] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 24 01:21:54 node-1 kernel: [    0.517826] NET: Registered protocol family 2
Sep 24 01:21:54 node-1 kernel: [    0.518123] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.518489] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.518655] TCP: Hash tables configured (established 262144 bind 65536)
Sep 24 01:21:54 node-1 kernel: [    0.518700] TCP: reno registered
Sep 24 01:21:54 node-1 kernel: [    0.518734] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.518842] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.519020] NET: Registered protocol family 1
Sep 24 01:21:54 node-1 kernel: [    0.557809] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 24 01:21:54 node-1 kernel: [    0.557817] PCI: CLS 64 bytes, default 64
Sep 24 01:21:54 node-1 kernel: [    0.557858] Trying to unpack rootfs image as initramfs...
Sep 24 01:21:54 node-1 kernel: [    0.780509] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Sep 24 01:21:54 node-1 kernel: [    0.780563] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 24 01:21:54 node-1 kernel: [    0.780565] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep 24 01:21:54 node-1 kernel: [    0.780967] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.780975] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.780984] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.780991] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781000] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781006] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781012] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781019] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781026] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781033] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781043] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781051] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781058] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781065] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781071] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781076] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 24 01:21:54 node-1 kernel: [    0.781137] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 24 01:21:54 node-1 kernel: [    0.781140] Scanning for low memory corruption every 60 seconds
Sep 24 01:21:54 node-1 kernel: [    0.781471] Initialise system trusted keyring
Sep 24 01:21:54 node-1 kernel: [    0.781532] audit: initializing netlink socket (disabled)
Sep 24 01:21:54 node-1 kernel: [    0.781543] type=2000 audit(1474680072.736:1): initialized
Sep 24 01:21:54 node-1 kernel: [    0.799403] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 24 01:21:54 node-1 kernel: [    0.800871] zbud: loaded
Sep 24 01:21:54 node-1 kernel: [    0.800997] VFS: Disk quotas dquot_6.5.2
Sep 24 01:21:54 node-1 kernel: [    0.801036] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 24 01:21:54 node-1 kernel: [    0.801424] fuse init (API version 7.22)
Sep 24 01:21:54 node-1 kernel: [    0.801486] msgmni has been set to 32768
Sep 24 01:21:54 node-1 kernel: [    0.801533] Key type big_key registered
Sep 24 01:21:54 node-1 kernel: [    0.802009] Key type asymmetric registered
Sep 24 01:21:54 node-1 kernel: [    0.802011] Asymmetric key parser 'x509' registered
Sep 24 01:21:54 node-1 kernel: [    0.802033] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 24 01:21:54 node-1 kernel: [    0.802099] io scheduler noop registered
Sep 24 01:21:54 node-1 kernel: [    0.802100] io scheduler deadline registered (default)
Sep 24 01:21:54 node-1 kernel: [    0.802119] io scheduler cfq registered
Sep 24 01:21:54 node-1 kernel: [    0.802516] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    0.802644] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    0.802764] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    0.802880] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    0.802999] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    0.803094] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    0.803477] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 24 01:21:54 node-1 kernel: [    0.803503] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 24 01:21:54 node-1 kernel: [    0.803519] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 24 01:21:54 node-1 kernel: [    0.803531] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803533] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803536] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 24 01:21:54 node-1 kernel: [    0.803541] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803543] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803544] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803546] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803548] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803549] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803550] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803552] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803553] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803555] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803556] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803558] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803560] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 24 01:21:54 node-1 kernel: [    0.803571] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803573] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 24 01:21:54 node-1 kernel: [    0.803583] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803593] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 24 01:21:54 node-1 kernel: [    0.803603] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803605] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 24 01:21:54 node-1 kernel: [    0.803608] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 24 01:21:54 node-1 kernel: [    0.803637] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 24 01:21:54 node-1 kernel: [    0.803643] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 24 01:21:54 node-1 kernel: [    0.803647] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 24 01:21:54 node-1 kernel: [    0.803655] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 24 01:21:54 node-1 kernel: [    0.803691] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 24 01:21:54 node-1 kernel: [    0.803693] vesafb: scrolling: redraw
Sep 24 01:21:54 node-1 kernel: [    0.803694] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 24 01:21:54 node-1 kernel: [    0.824399] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 24 01:21:54 node-1 kernel: [    0.832889] Console: switching to colour frame buffer device 80x30
Sep 24 01:21:54 node-1 kernel: [    0.841564] fb0: VESA VGA frame buffer device
Sep 24 01:21:54 node-1 kernel: [    0.841760] intel_idle: MWAIT substates: 0x2120
Sep 24 01:21:54 node-1 kernel: [    0.841761] intel_idle: v0.4 model 0x3F
Sep 24 01:21:54 node-1 kernel: [    0.841762] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 24 01:21:54 node-1 kernel: [    0.841993] ipmi message handler version 39.2
Sep 24 01:21:54 node-1 kernel: [    0.842266] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 24 01:21:54 node-1 kernel: [    0.842699] ACPI: AC Adapter [P111] (on-line)
Sep 24 01:21:54 node-1 kernel: [    0.847915] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 24 01:21:54 node-1 kernel: [    0.858905] ACPI: Power Button [PWRB]
Sep 24 01:21:54 node-1 kernel: [    0.864664] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 24 01:21:54 node-1 kernel: [    0.876283] ACPI: Power Button [PWRF]
Sep 24 01:21:54 node-1 kernel: [    0.895296] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 24 01:21:54 node-1 kernel: [    0.906917] pstore: Registered erst as persistent store backend
Sep 24 01:21:54 node-1 kernel: [    0.913103] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 24 01:21:54 node-1 kernel: [    0.925171] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 24 01:21:54 node-1 kernel: [    0.951957] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 24 01:21:54 node-1 kernel: [    0.985325] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 24 01:21:54 node-1 kernel: [    0.999384] Linux agpgart interface v0.103
Sep 24 01:21:54 node-1 kernel: [    1.007066] brd: module loaded
Sep 24 01:21:54 node-1 kernel: [    1.014109] loop: module loaded
Sep 24 01:21:54 node-1 kernel: [    1.020827] libphy: Fixed MDIO Bus: probed
Sep 24 01:21:54 node-1 kernel: [    1.027315] tun: Universal TUN/TAP device driver, 1.6
Sep 24 01:21:54 node-1 kernel: [    1.033782] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 24 01:21:54 node-1 kernel: [    1.040317] PPP generic driver version 2.4.2
Sep 24 01:21:54 node-1 kernel: [    1.046726] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 24 01:21:54 node-1 kernel: [    1.053176] ehci-pci: EHCI PCI platform driver
Sep 24 01:21:54 node-1 kernel: [    1.059702] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 24 01:21:54 node-1 kernel: [    1.066126] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 24 01:21:54 node-1 kernel: [    1.078663] ehci-pci 0000:00:1a.0: debug port 2
Sep 24 01:21:54 node-1 kernel: [    1.088874] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 24 01:21:54 node-1 kernel: [    1.088892] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 24 01:21:54 node-1 kernel: [    1.105228] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 24 01:21:54 node-1 kernel: [    1.111311] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 24 01:21:54 node-1 kernel: [    1.117483] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 24 01:21:54 node-1 kernel: [    1.129404] usb usb1: Product: EHCI Host Controller
Sep 24 01:21:54 node-1 kernel: [    1.135428] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 24 01:21:54 node-1 kernel: [    1.141475] usb usb1: SerialNumber: 0000:00:1a.0
Sep 24 01:21:54 node-1 kernel: [    1.147462] hub 1-0:1.0: USB hub found
Sep 24 01:21:54 node-1 kernel: [    1.153241] hub 1-0:1.0: 2 ports detected
Sep 24 01:21:54 node-1 kernel: [    1.159042] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 24 01:21:54 node-1 kernel: [    1.164629] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 24 01:21:54 node-1 kernel: [    1.175530] ehci-pci 0000:00:1d.0: debug port 2
Sep 24 01:21:54 node-1 kernel: [    1.184830] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 24 01:21:54 node-1 kernel: [    1.184833] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 24 01:21:54 node-1 kernel: [    1.201146] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 24 01:21:54 node-1 kernel: [    1.206364] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 24 01:21:54 node-1 kernel: [    1.211674] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 24 01:21:54 node-1 kernel: [    1.222246] usb usb2: Product: EHCI Host Controller
Sep 24 01:21:54 node-1 kernel: [    1.227714] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 24 01:21:54 node-1 kernel: [    1.233262] usb usb2: SerialNumber: 0000:00:1d.0
Sep 24 01:21:54 node-1 kernel: [    1.238826] hub 2-0:1.0: USB hub found
Sep 24 01:21:54 node-1 kernel: [    1.244260] hub 2-0:1.0: 2 ports detected
Sep 24 01:21:54 node-1 kernel: [    1.249660] ehci-platform: EHCI generic platform driver
Sep 24 01:21:54 node-1 kernel: [    1.254982] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 24 01:21:54 node-1 kernel: [    1.260377] ohci-pci: OHCI PCI platform driver
Sep 24 01:21:54 node-1 kernel: [    1.265724] ohci-platform: OHCI generic platform driver
Sep 24 01:21:54 node-1 kernel: [    1.270917] uhci_hcd: USB Universal Host Controller Interface driver
Sep 24 01:21:54 node-1 kernel: [    1.276256] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 24 01:21:54 node-1 kernel: [    1.468925] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 24 01:21:54 node-1 kernel: [    1.776667] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 24 01:21:54 node-1 kernel: [    1.793046] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 24 01:21:54 node-1 kernel: [    1.798664] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 24 01:21:54 node-1 kernel: [    1.804439] hub 1-1:1.0: USB hub found
Sep 24 01:21:54 node-1 kernel: [    1.810031] hub 1-1:1.0: 6 ports detected
Sep 24 01:21:54 node-1 kernel: [    1.924553] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 24 01:21:54 node-1 kernel: [    2.315285] i8042: No controller found
Sep 24 01:21:54 node-1 kernel: [    2.320819] mousedev: PS/2 mouse device common for all mice
Sep 24 01:21:54 node-1 kernel: [    2.326555] rtc_cmos 00:02: RTC can wake from S4
Sep 24 01:21:54 node-1 kernel: [    2.329031] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 24 01:21:54 node-1 kernel: [    2.329032] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 24 01:21:54 node-1 kernel: [    2.329676] hub 2-1:1.0: USB hub found
Sep 24 01:21:54 node-1 kernel: [    2.329910] hub 2-1:1.0: 8 ports detected
Sep 24 01:21:54 node-1 kernel: [    2.354841] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 24 01:21:54 node-1 kernel: [    2.360594] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 24 01:21:54 node-1 kernel: [    2.371920] device-mapper: uevent: version 1.0.3
Sep 24 01:21:54 node-1 kernel: [    2.377634] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 24 01:21:54 node-1 kernel: [    2.389015] ledtrig-cpu: registered to indicate activity on CPUs
Sep 24 01:21:54 node-1 kernel: [    2.395002] TCP: cubic registered
Sep 24 01:21:54 node-1 kernel: [    2.400876] NET: Registered protocol family 10
Sep 24 01:21:54 node-1 kernel: [    2.406958] NET: Registered protocol family 17
Sep 24 01:21:54 node-1 kernel: [    2.412751] Key type dns_resolver registered
Sep 24 01:21:54 node-1 kernel: [    2.418829] Loading compiled-in X.509 certificates
Sep 24 01:21:54 node-1 kernel: [    2.425064] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 24 01:21:54 node-1 kernel: [    2.436716] registered taskstats version 1
Sep 24 01:21:54 node-1 kernel: [    2.444813] Key type trusted registered
Sep 24 01:21:54 node-1 kernel: [    2.452612] Key type encrypted registered
Sep 24 01:21:54 node-1 kernel: [    2.458111] AppArmor: AppArmor sha1 policy hashing enabled
Sep 24 01:21:54 node-1 kernel: [    2.463616] IMA: No TPM chip found, activating TPM-bypass!
Sep 24 01:21:54 node-1 kernel: [    2.469728] regulator-dummy: disabling
Sep 24 01:21:54 node-1 kernel: [    2.475226]   Magic number: 0:747:357
Sep 24 01:21:54 node-1 kernel: [    2.480685] machinecheck machinecheck13: hash matches
Sep 24 01:21:54 node-1 kernel: [    2.486423] rtc_cmos 00:02: setting system clock to 2016-09-24 01:21:14 UTC (1474680074)
Sep 24 01:21:54 node-1 kernel: [    2.498833] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 24 01:21:54 node-1 kernel: [    2.504490] EDD information not available.
Sep 24 01:21:54 node-1 kernel: [    2.510067] PM: Hibernation image not present or could not be loaded.
Sep 24 01:21:54 node-1 kernel: [    2.510933] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 24 01:21:54 node-1 kernel: [    2.522258] Write protecting the kernel read-only data: 12288k
Sep 24 01:21:54 node-1 kernel: [    2.528682] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 24 01:21:54 node-1 kernel: [    2.541591] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 24 01:21:54 node-1 kernel: [    2.574144] device-mapper: multipath: version 1.6.0 loaded
Sep 24 01:21:54 node-1 kernel: [    2.582017] systemd-udevd[217]: starting version 204
Sep 24 01:21:54 node-1 kernel: [    2.603962] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 24 01:21:54 node-1 kernel: [    2.613138] md: linear personality registered for level -1
Sep 24 01:21:54 node-1 kernel: [    2.627109] md: multipath personality registered for level -4
Sep 24 01:21:54 node-1 kernel: [    2.635226] md: raid0 personality registered for level 0
Sep 24 01:21:54 node-1 kernel: [    2.643548] md: raid1 personality registered for level 1
Sep 24 01:21:54 node-1 kernel: [    2.654570] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 24 01:21:54 node-1 kernel: [    2.660855] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 24 01:21:54 node-1 kernel: [    2.661185] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 24 01:21:54 node-1 kernel: [    2.673557] megasas: FW now in Ready state
Sep 24 01:21:54 node-1 kernel: [    2.674071] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep 24 01:21:54 node-1 kernel: [    2.674080] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 24 01:21:54 node-1 kernel: [    2.674081] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 24 01:21:54 node-1 kernel: [    2.674546] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.674725] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.674843] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.674996] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.675221] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.692965] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep 24 01:21:54 node-1 kernel: [    2.692967] 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
Sep 24 01:21:54 node-1 kernel: [    2.692969] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 24 01:21:54 node-1 kernel: [    2.693391] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.693557] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.693726] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.693901] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.694035] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.694169] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.694511] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.715402] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep 24 01:21:54 node-1 kernel: [    2.715420] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 24 01:21:54 node-1 kernel: [    2.715444] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 24 01:21:54 node-1 kernel: [    2.716196] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.716380] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.716544] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.716631] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.716823] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.720076] raid6: sse2x1     550 MB/s
Sep 24 01:21:54 node-1 kernel: [    2.732677] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep 24 01:21:54 node-1 kernel: [    2.732679] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 24 01:21:54 node-1 kernel: [    2.732680] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 24 01:21:54 node-1 kernel: [    2.733007] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.733228] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.733306] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.733482] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.733886] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 24 01:21:54 node-1 kernel: [    2.747038] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 24 01:21:54 node-1 kernel: [    2.747039] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 24 01:21:54 node-1 kernel: [    2.747043] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 24 01:21:54 node-1 kernel: [    2.747044] usb 2-1.4: Manufacturer: Avocent
Sep 24 01:21:54 node-1 kernel: [    2.747061] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 24 01:21:54 node-1 kernel: [    2.788104] raid6: sse2x2     643 MB/s
Sep 24 01:21:54 node-1 kernel: [    2.855915] raid6: sse2x4    1329 MB/s
Sep 24 01:21:54 node-1 kernel: [    2.923862] raid6: avx2x1     881 MB/s
Sep 24 01:21:54 node-1 kernel: [    2.991639] raid6: avx2x2   17191 MB/s
Sep 24 01:21:54 node-1 kernel: [    3.063580] raid6: avx2x4   21239 MB/s
Sep 24 01:21:54 node-1 kernel: [    3.069257] raid6: using algorithm avx2x4 (21239 MB/s)
Sep 24 01:21:54 node-1 kernel: [    3.074869] raid6: using avx2x2 recovery algorithm
Sep 24 01:21:54 node-1 kernel: [    3.080553] Switched to clocksource tsc
Sep 24 01:21:54 node-1 kernel: [    3.080627] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080667] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080708] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080747] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080780] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080820] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080857] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080894] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080933] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.080970] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.081008] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.081044] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.081083] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.081116] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.081152] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.081190] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Sep 24 01:21:54 node-1 kernel: [    3.081344] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 24 01:21:54 node-1 kernel: [    3.097916] xor: automatically using best checksumming function:
Sep 24 01:21:54 node-1 kernel: [    3.111587] hidraw: raw HID events driver (C) Jiri Kosina
Sep 24 01:21:54 node-1 kernel: [    3.119839] usbcore: registered new interface driver usbhid
Sep 24 01:21:54 node-1 kernel: [    3.125271] usbhid: USB HID core driver
Sep 24 01:21:54 node-1 kernel: [    3.131644] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 24 01:21:54 node-1 kernel: [    3.142521]    avx       : 35726.000 MB/sec
Sep 24 01:21:54 node-1 kernel: [    3.148623] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 24 01:21:54 node-1 kernel: [    3.160047] async_tx: api initialized (async)
Sep 24 01:21:54 node-1 kernel: [    3.160082] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 24 01:21:54 node-1 kernel: [    3.160132] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 24 01:21:54 node-1 kernel: [    3.160184] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 24 01:21:54 node-1 kernel: [    3.160221] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 24 01:21:54 node-1 kernel: [    3.217402] md: raid6 personality registered for level 6
Sep 24 01:21:54 node-1 kernel: [    3.223794] md: raid5 personality registered for level 5
Sep 24 01:21:54 node-1 kernel: [    3.230043] md: raid4 personality registered for level 4
Sep 24 01:21:54 node-1 kernel: [    3.239282] md: raid10 personality registered for level 10
Sep 24 01:21:54 node-1 kernel: [    3.294235] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Sep 24 01:21:54 node-1 kernel: [    3.407324] megasas:IOC Init cmd success
Sep 24 01:21:54 node-1 kernel: [    3.435305] megasas: INIT adapter done
Sep 24 01:21:54 node-1 kernel: [    3.535224] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 24 01:21:54 node-1 kernel: [    3.542109] scsi0 : LSI SAS based MegaRAID driver
Sep 24 01:21:54 node-1 kernel: [    3.549479] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 24 01:21:54 node-1 kernel: [    3.568308] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 24 01:21:54 node-1 kernel: [    3.583900] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 24 01:21:54 node-1 kernel: [    3.590529] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 24 01:21:54 node-1 kernel: [    3.603646] sd 0:2:0:0: [sda] Write Protect is off
Sep 24 01:21:54 node-1 kernel: [    3.610010] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 24 01:21:54 node-1 kernel: [    3.610029] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 24 01:21:54 node-1 kernel: [    3.652430]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 24 01:21:54 node-1 kernel: [    3.659130] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 24 01:21:54 node-1 kernel: [    3.793125] random: lvm urandom read with 29 bits of entropy available
Sep 24 01:21:54 node-1 kernel: [    4.007620] bio: create slab <bio-1> at 1
Sep 24 01:21:54 node-1 kernel: [    4.816907] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 24 01:21:54 node-1 kernel: [    5.370851] init: plymouth-upstart-bridge main process (552) terminated with status 1
Sep 24 01:21:54 node-1 kernel: [    5.383290] init: plymouth-upstart-bridge main process ended, respawning
Sep 24 01:21:54 node-1 kernel: [    5.506517] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 24 01:21:54 node-1 kernel: [    5.532607] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 24 01:21:54 node-1 kernel: [    5.545414] random: nonblocking pool is initialized
Sep 24 01:21:54 node-1 kernel: [    5.659429] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 24 01:21:54 node-1 kernel: [    5.695458] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 24 01:21:54 node-1 kernel: [    5.746583] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 24 01:21:54 node-1 kernel: [    5.903104] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 24 01:21:54 node-1 kernel: [    5.958014] XFS (dm-0): Mounting Filesystem
Sep 24 01:21:54 node-1 kernel: [    6.133534] XFS (dm-0): Ending clean mount
Sep 24 01:21:54 node-1 kernel: [    6.177952] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 24 01:21:54 node-1 kernel: [    6.209352] XFS (dm-1): Mounting Filesystem
Sep 24 01:21:54 node-1 kernel: [    6.312169] XFS (dm-1): Ending clean mount
Sep 24 01:21:54 node-1 kernel: [    8.342707] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 24 01:21:54 node-1 kernel: [    8.366799] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 24 01:21:54 node-1 kernel: [    8.547453] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 24 01:21:54 node-1 kernel: [    8.547457] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 24 01:21:54 node-1 kernel: [    8.547460] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 24 01:21:54 node-1 kernel: [    8.547464] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 24 01:21:54 node-1 kernel: [    8.573071] systemd-udevd[778]: starting version 204
Sep 24 01:21:54 node-1 kernel: [    8.788592] power_meter ACPI000D:00: Found ACPI power meter.
Sep 24 01:21:54 node-1 kernel: [    8.788782] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 24 01:21:54 node-1 kernel: [    8.810407] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 24 01:21:54 node-1 kernel: [    8.810414] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 24 01:21:54 node-1 kernel: [    8.810418] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 24 01:21:54 node-1 kernel: [    8.810421] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 24 01:21:54 node-1 kernel: [    8.810441] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 24 01:21:54 node-1 kernel: [    8.811843] wmi: Mapper loaded
Sep 24 01:21:54 node-1 kernel: [    8.822533] IPMI System Interface driver.
Sep 24 01:21:54 node-1 kernel: [    8.822578] ipmi_si: probing via ACPI
Sep 24 01:21:54 node-1 kernel: [    8.822594] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 24 01:21:54 node-1 kernel: [    8.822596] ipmi_si: Adding ACPI-specified kcs state machine
Sep 24 01:21:54 node-1 kernel: [    8.822607] ipmi_si: probing via SMBIOS
Sep 24 01:21:54 node-1 kernel: [    8.822608] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 24 01:21:54 node-1 kernel: [    8.822609] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 24 01:21:54 node-1 kernel: [    8.822611] ipmi_si: probing via SPMI
Sep 24 01:21:54 node-1 kernel: [    8.822612] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 24 01:21:54 node-1 kernel: [    8.822613] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 24 01:21:54 node-1 kernel: [    8.822615] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 24 01:21:54 node-1 kernel: [    8.823942] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 24 01:21:54 node-1 kernel: [    8.883168] systemd-udevd[828]: renamed network interface eth2 to enp8s0
Sep 24 01:21:54 node-1 kernel: [    8.907001] systemd-udevd[802]: renamed network interface eth0 to enp6s0
Sep 24 01:21:54 node-1 kernel: [    8.930967] systemd-udevd[825]: renamed network interface eth1 to enp7s0
Sep 24 01:21:54 node-1 kernel: [    8.962980] systemd-udevd[806]: renamed network interface eth3 to enp9s0
Sep 24 01:21:54 node-1 kernel: [    9.001494] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 24 01:21:54 node-1 kernel: [    9.001500] ipmi_si 00:09: IPMI kcs interface initialized
Sep 24 01:21:54 node-1 kernel: [    9.269688] type=1400 audit(1474680081.283:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.269942] type=1400 audit(1474680081.283:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1057 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.270153] type=1400 audit(1474680081.283:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1057 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.271969] type=1400 audit(1474680081.287:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1058 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.272110] type=1400 audit(1474680081.287:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1058 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.272230] type=1400 audit(1474680081.287:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1058 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.278906] type=1400 audit(1474680081.295:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.279050] type=1400 audit(1474680081.295:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.279175] type=1400 audit(1474680081.295:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.292258] type=1400 audit(1474680081.307:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Sep 24 01:21:54 node-1 kernel: [    9.932587] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 24 01:21:54 node-1 kernel: [    9.937591] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 24 01:21:54 node-1 kernel: [   10.144132] enic 0000:06:00.0 enp6s0: Link UP
Sep 24 01:21:54 node-1 kernel: [   10.144563] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 24 01:21:54 node-1 kernel: [   10.144573] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 24 01:21:54 node-1 kernel: [   19.396171] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 24 01:21:54 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 24 01:21:54 node-1 kernel: [   42.272142] init: failsafe main process (8419) killed by TERM signal
Sep 24 01:21:54 node-1 dbus[8447]: [system] AppArmor D-Bus mediation is enabled
Sep 24 01:21:55 node-1 kernel: [   42.613771] audit_printk_skb: 30 callbacks suppressed
Sep 24 01:21:55 node-1 kernel: [   42.613772] type=1400 audit(1474680115.042:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8544 comm="apparmor_parser"
Sep 24 01:21:55 node-1 kernel: [   42.613776] type=1400 audit(1474680115.042:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Sep 24 01:21:55 node-1 kernel: [   42.613779] type=1400 audit(1474680115.042:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Sep 24 01:21:55 node-1 kernel: [   42.613993] type=1400 audit(1474680115.042:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Sep 24 01:21:55 node-1 kernel: [   42.613995] type=1400 audit(1474680115.042:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Sep 24 01:21:55 node-1 kernel: [   42.614106] type=1400 audit(1474680115.042:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Sep 24 01:21:55 node-1 kernel: [   42.616988] type=1400 audit(1474680115.042:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8545 comm="apparmor_parser"
Sep 24 01:21:55 node-1 kernel: [   42.700885] type=1400 audit(1474680115.126:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8547 comm="apparmor_parser"
Sep 24 01:21:55 node-1 anacron[8611]: Anacron 2.3 started on 2016-09-24
Sep 24 01:21:55 node-1 cron[8577]: (CRON) INFO (pidfile fd = 3)
Sep 24 01:21:55 node-1 anacron[8611]: Will run job `cron.daily' in 5 min.
Sep 24 01:21:55 node-1 anacron[8611]: Will run job `cron.weekly' in 10 min.
Sep 24 01:21:55 node-1 anacron[8611]: Will run job `cron.monthly' in 15 min.
Sep 24 01:21:55 node-1 anacron[8611]: Jobs will be executed sequentially
Sep 24 01:21:55 node-1 cron[8618]: (CRON) STARTUP (fork ok)
Sep 24 01:21:55 node-1 cron[8618]: (CRON) INFO (Running @reboot jobs)
Sep 24 01:21:55 node-1 multipathd: path checkers start up
Sep 24 01:21:55 node-1 postfix/master[8756]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 24 01:21:59 node-1 puppet-agent[8940]: Reopening log files
Sep 24 01:21:59 node-1 puppet-agent[8940]: Could not request certificate: Connection refused - connect(2)
Sep 24 01:22:01 node-1 CRON[8971]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 24 01:22:08 node-1 puppet-user[9030]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 24 01:22:08 node-1 puppet-user[9030]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 24 01:22:09 node-1 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 24 01:22:09 node-1 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 24 01:22:09 node-1 puppet-user[9030]: Finished catalog run in 1.01 seconds
Sep 24 01:22:10 node-1 multipathd: uevent trigger error
Sep 24 01:22:10 node-1 puppet-user[9470]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 24 01:22:10 node-1 puppet-user[9470]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 24 01:22:11 node-1 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 24 01:22:11 node-1 puppet-user[9470]: Finished catalog run in 0.06 seconds
Sep 24 01:22:12 node-1 puppet-user[9935]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 24 01:22:12 node-1 puppet-user[9935]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 24 01:22:12 node-1 puppet-user[9935]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 24 01:22:12 node-1 puppet-user[9935]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 24 01:22:12 node-1 puppet-user[9935]: Finished catalog run in 0.04 seconds
Sep 24 01:22:14 node-1 puppet-user[10402]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 24 01:22:14 node-1 puppet-user[10402]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Sep 24 01:22:14 node-1 puppet-user[10402]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 24 01:22:14 node-1 puppet-user[10402]: Finished catalog run in 0.04 seconds
Sep 24 01:22:16 node-1 puppet-user[10858]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 24 01:22:16 node-1 puppet-user[10858]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Sep 24 01:22:16 node-1 puppet-user[10858]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 24 01:22:16 node-1 puppet-user[10858]: (/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
Sep 24 01:22:16 node-1 puppet-user[10858]: Finished catalog run in 0.43 seconds
Sep 24 01:22:17 node-1 puppet-user[11336]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 24 01:22:18 node-1 puppet-user[11336]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 24 01:22:18 node-1 puppet-user[11336]: (/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
Sep 24 01:22:18 node-1 puppet-user[11336]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 24 01:22:18 node-1 puppet-user[11336]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 24 01:22:18 node-1 puppet-user[11336]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 24 01:22:18 node-1 puppet-user[11336]: Finished catalog run in 0.32 seconds
Sep 24 01:22:20 node-1 puppet-user[11823]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 24 01:22:20 node-1 puppet-user[11823]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Sep 24 01:22:20 node-1 puppet-user[11823]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 24 01:22:20 node-1 kernel: [   68.280139] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 24 01:22:20 node-1 kernel: [   68.280188] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 24 01:22:20 node-1 puppet-user[11823]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 24 01:22:20 node-1 puppet-user[11823]: Finished catalog run in 0.05 seconds
Sep 24 01:22:22 node-1 puppet-user[12418]: (Scope(Class[main])) MODULAR: sync_time
Sep 24 01:22:22 node-1 puppet-user[12418]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 24 01:22:22 node-1 ntpdate[12851]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 24 01:22:23 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 24 01:22:23 node-1 nailgun-agent: D, [2016-09-24T01:22:01.323837 #8974] DEBUG -- : Sleep for 22 seconds before sending request
Sep 24 01:22:23 node-1 nailgun-agent: I, [2016-09-24T01:22:23.335366 #8974]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 24 01:22:23 node-1 nailgun-agent: D, [2016-09-24T01:22:23.788204 #8974] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep 24 01:22:28 node-1 ntpdate[12851]: adjust time server 10.20.0.2 offset 0.000027 sec
Sep 24 01:22:28 node-1 puppet-user[12418]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 24 01:22:28 node-1 puppet-user[12418]: Finished catalog run in 6.18 seconds
Sep 24 01:22:33 node-1 puppet-user[13212]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 24 01:22:33 node-1 puppet-user[13212]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 24 01:22:33 node-1 puppet-user[13212]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 24 01:22:33 node-1 puppet-user[13212]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs"]'
Sep 24 01:22:33 node-1 puppet-user[13212]: Finished catalog run in 0.06 seconds
Sep 24 01:22:34 node-1 puppet-user[13854]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 24 01:22:35 node-1 puppet-user[13854]: Compiled catalog for node-1.domain.tld in environment production in 0.54 seconds
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 24 01:22:35 node-1 puppet-user[13854]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.773947 #8974] DEBUG -- : Trying to find block devices
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.774035 #8974] DEBUG -- : Found block device: sda
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.774078 #8974] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.774101 #8974] DEBUG -- : Trying to get list of physical devices
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.774257 #8974] DEBUG -- : Getting udev properties for device: sda
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.775990 #8974] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Sep 24 01:22:35 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15941", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.776018 #8974] DEBUG -- : Trying to find out if device sda is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.776062 #8974] DEBUG -- : Device sda removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.776095 #8974] DEBUG -- : Device sda seems to be appropriate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.776520 #8974] DEBUG -- : Getting udev properties for device: dm-0
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.778041 #8974] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-tnHjbOl7Y3oDrkxfVGzZNCzVqRt6YacmxMUgrqCBZbD7DtBO2GLXZWu61nN0GzPt /dev/disk/by-uuid/e363d979-51d0-4cfc-b7d1-9555a4f6e502 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-tnHjbOl7Y3oDrkxfVGzZNCzVqRt6YacmxMUgrqCBZbD7DtBO2GLXZWu61nN0GzPt", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e363d979-51d0-4cfc-b7d1-9555a4f6e502", "ID_FS_UUID_ENC"=>"e363d979-51d0-4cfc-b7d1-9555a4f6e502", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64667", "nomdmonddf"=>"1", "nomd
Sep 24 01:22:35 node-1 nailgun-agent: monisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.778069 #8974] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.778127 #8974] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.778141 #8974] DEBUG -- : Device dm-0 seems to be appropriate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.778155 #8974] DEBUG -- : Getting udev properties for device: dm-1
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.779666 #8974] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-0c733ocAVhMAJ8XGTE1296eWt36v5MobGrJXibxkUvHfEVaB7cjVp2HHT7GTex2s /dev/disk/by-uuid/4c2c92fa-0bb4-4ca9-8995-fcf4347093f1 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-0c733ocAVhMAJ8XGTE1296eWt36v5MobGrJXibxkUvHfEVaB7cjVp2HHT7GTex2s", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4c2c92fa-0bb4-4ca9-8995-fcf4347093f1", "ID_FS_UUID_ENC"=>"4c2c92fa-0bb4-4ca9-8995-fcf4347093f1", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93
Sep 24 01:22:35 node-1 nailgun-agent: 150", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.779694 #8974] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.779788 #8974] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.779802 #8974] DEBUG -- : Device dm-1 seems to be appropriate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.779815 #8974] DEBUG -- : Getting udev properties for device: dm-2
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.781318 #8974] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-xUj5Bv1R1iJcvF5i7Ka99RBgNto4cPwj3JxVvaguQB8Ak4y1dnOfKJfcZy44vu1Q /dev/disk/by-uuid/cf51f438-eadc-414f-9020-c31f55481932 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-xUj5Bv1R1iJcvF5i7Ka99RBgNto4cPwj3JxVvaguQB8Ak4y1dnOfKJfcZy44vu1Q", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cf51f438-eadc-414f-9020-c31f55481932", "ID_FS_UUID_ENC"=>"cf51f438-eadc-414f-9020-c31f55481932", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99289", "nomdmond
Sep 24 01:22:35 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.781345 #8974] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.781386 #8974] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.781412 #8974] DEBUG -- : Device dm-2 seems to be appropriate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.781426 #8974] DEBUG -- : Getting udev properties for device: dm-3
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.782956 #8974] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-vsE1024L6iCIEQrhlRlbaMlpuTrSxTTEXrWRvYSyltdr9Crz6peZf6vH3rKGXccQ /dev/disk/by-uuid/e33ed170-1222-4fb2-96e1-fa1798bdc95a /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-vsE1024L6iCIEQrhlRlbaMlpuTrSxTTEXrWRvYSyltdr9Crz6peZf6vH3rKGXccQ", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e33ed170-1222-4fb2-96e1-fa1798bdc95a", "ID_FS_UUID_ENC"=>"e33ed170-1222-4fb2-96e1-fa1798bdc95a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93899", "nomdmonddf"=>"1", 
Sep 24 01:22:35 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.783006 #8974] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.783051 #8974] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.783066 #8974] DEBUG -- : Device dm-3 seems to be appropriate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.783091 #8974] DEBUG -- : Getting udev properties for device: dm-4
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.784632 #8974] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-VPtO2wXPpenOxoy0t2cPhhtg3yHf7N2DDJqkEf5iaTuvYvb1jf4hFgif6dPCtyxq /dev/disk/by-uuid/1c20c864-b690-4cb8-b630-2581e79208ce /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-VPtO2wXPpenOxoy0t2cPhhtg3yHf7N2DDJqkEf5iaTuvYvb1jf4hFgif6dPCtyxq", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1c20c864-b690-4cb8-b630-2581e79208ce", "ID_FS_UUID_ENC"=>"1c20c864-b690-4cb8-b630-2581e79208ce", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99172", "nomdmonddf"=>"1", "nomd
Sep 24 01:22:35 node-1 nailgun-agent: monisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.784669 #8974] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.784700 #8974] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.784715 #8974] DEBUG -- : Device dm-4 seems to be appropriate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.784730 #8974] DEBUG -- : Getting udev properties for device: dm-5
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.786286 #8974] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-VPtO2wXPpenOxoy0t2cPhhtg3yHf7N2DLSKeQMow2QT2C38zLNOfeeeZ0pb4rc44 /dev/disk/by-uuid/4d5fa786-ee09-487a-8bdc-fecd1cacebfb /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-VPtO2wXPpenOxoy0t2cPhhtg3yHf7N2DLSKeQMow2QT2C38zLNOfeeeZ0pb4rc44", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"4d5fa786-ee09-487a-8bdc-fecd1cacebfb", "ID_FS_UUID_ENC"=>"4d5fa786-ee09-487a-8bdc-fecd1cacebfb", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"361", "nomdmonddf"=>"1", "nomdmonisw"=>
Sep 24 01:22:35 node-1 nailgun-agent: "1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.786313 #8974] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.786394 #8974] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.786408 #8974] DEBUG -- : Device dm-5 seems to be appropriate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.786422 #8974] DEBUG -- : Getting udev properties for device: ram0
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.787813 #8974] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59057", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.787838 #8974] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.787872 #8974] DEBUG -- : Device ram0 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.787908 #8974] DEBUG -- : Getting udev properties for device: ram1
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.789250 #8974] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59069", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.789275 #8974] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.789310 #8974] DEBUG -- : Device ram1 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.789330 #8974] DEBUG -- : Getting udev properties for device: ram2
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.790685 #8974] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59161", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.790711 #8974] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.790772 #8974] DEBUG -- : Device ram2 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.790792 #8974] DEBUG -- : Getting udev properties for device: ram3
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.792210 #8974] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59176", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.792243 #8974] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.792285 #8974] DEBUG -- : Device ram3 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.792310 #8974] DEBUG -- : Getting udev properties for device: ram4
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.793673 #8974] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59195", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.793698 #8974] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.793739 #8974] DEBUG -- : Device ram4 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.793775 #8974] DEBUG -- : Getting udev properties for device: ram5
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.795131 #8974] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59211", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.795156 #8974] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.795203 #8974] DEBUG -- : Device ram5 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.795223 #8974] DEBUG -- : Getting udev properties for device: ram6
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.796638 #8974] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59228", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.796665 #8974] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.796701 #8974] DEBUG -- : Device ram6 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.796720 #8974] DEBUG -- : Getting udev properties for device: ram7
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.798094 #8974] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59242", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.798135 #8974] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.798169 #8974] DEBUG -- : Device ram7 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.798188 #8974] DEBUG -- : Getting udev properties for device: ram8
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.799552 #8974] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59252", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.799577 #8974] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.799621 #8974] DEBUG -- : Device ram8 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.799640 #8974] DEBUG -- : Getting udev properties for device: ram9
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.801045 #8974] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59264", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.801071 #8974] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.801125 #8974] DEBUG -- : Device ram9 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.801144 #8974] DEBUG -- : Getting udev properties for device: loop0
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.802543 #8974] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58959", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.802569 #8974] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.802603 #8974] DEBUG -- : Device loop0 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.802637 #8974] DEBUG -- : Getting udev properties for device: loop1
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.804025 #8974] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58967", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.804062 #8974] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.804094 #8974] DEBUG -- : Device loop1 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.804114 #8974] DEBUG -- : Getting udev properties for device: loop2
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.805495 #8974] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58979", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.805521 #8974] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.805571 #8974] DEBUG -- : Device loop2 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.805591 #8974] DEBUG -- : Getting udev properties for device: loop3
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.806983 #8974] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58991", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.807021 #8974] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.807056 #8974] DEBUG -- : Device loop3 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.807076 #8974] DEBUG -- : Getting udev properties for device: loop4
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.808464 #8974] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59004", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.808490 #8974] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.808536 #8974] DEBUG -- : Device loop4 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.813729 #8974] DEBUG -- : Getting udev properties for device: loop5
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.815205 #8974] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59021", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.815231 #8974] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.815265 #8974] DEBUG -- : Device loop5 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.815284 #8974] DEBUG -- : Getting udev properties for device: loop6
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.816663 #8974] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59033", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.816688 #8974] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.816726 #8974] DEBUG -- : Device loop6 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.816746 #8974] DEBUG -- : Getting udev properties for device: loop7
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.818110 #8974] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59045", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.818135 #8974] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.818171 #8974] DEBUG -- : Device loop7 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.818190 #8974] DEBUG -- : Getting udev properties for device: ram10
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.819576 #8974] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59082", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.819601 #8974] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.819636 #8974] DEBUG -- : Device ram10 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.819655 #8974] DEBUG -- : Getting udev properties for device: ram11
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.821061 #8974] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59095", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.821087 #8974] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.821128 #8974] DEBUG -- : Device ram11 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.821148 #8974] DEBUG -- : Getting udev properties for device: ram12
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.822482 #8974] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59109", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.822508 #8974] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.822575 #8974] DEBUG -- : Device ram12 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.822595 #8974] DEBUG -- : Getting udev properties for device: ram13
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.823926 #8974] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59123", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.823952 #8974] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.823984 #8974] DEBUG -- : Device ram13 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.824045 #8974] DEBUG -- : Getting udev properties for device: ram14
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.825372 #8974] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59136", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.825398 #8974] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.825430 #8974] DEBUG -- : Device ram14 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.825450 #8974] DEBUG -- : Getting udev properties for device: ram15
Sep 24 01:22:35 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.826804 #8974] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59148", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.826829 #8974] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.826860 #8974] DEBUG -- : Device ram15 removable parameter: "0"
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.826897 #8974] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.826913 #8974] DEBUG -- : Block device seems to be physical data storage: sda
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.826995 #8974] DEBUG -- : Found block device: dm-0
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827012 #8974] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827026 #8974] DEBUG -- : Found block device: dm-1
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827037 #8974] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827046 #8974] DEBUG -- : Found block device: dm-2
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827057 #8974] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827065 #8974] DEBUG -- : Found block device: dm-3
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827076 #8974] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827084 #8974] DEBUG -- : Found block device: dm-4
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827095 #8974] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827139 #8974] DEBUG -- : Found block device: dm-5
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827151 #8974] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827160 #8974] DEBUG -- : Found block device: ram0
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827170 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827179 #8974] DEBUG -- : Found block device: ram1
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827190 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827199 #8974] DEBUG -- : Found block device: ram2
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827208 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827217 #8974] DEBUG -- : Found block device: ram3
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827228 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827237 #8974] DEBUG -- : Found block device: ram4
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827287 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827295 #8974] DEBUG -- : Found block device: ram5
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827304 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827313 #8974] DEBUG -- : Found block device: ram6
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827322 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827330 #8974] DEBUG -- : Found block device: ram7
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827340 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827349 #8974] DEBUG -- : Found block device: ram8
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827359 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827367 #8974] DEBUG -- : Found block device: ram9
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827413 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827423 #8974] DEBUG -- : Found block device: loop0
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827433 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827441 #8974] DEBUG -- : Found block device: loop1
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827451 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827459 #8974] DEBUG -- : Found block device: loop2
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827470 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827479 #8974] DEBUG -- : Found block device: loop3
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827488 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827497 #8974] DEBUG -- : Found block device: loop4
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827540 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827549 #8974] DEBUG -- : Found block device: loop5
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827559 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827567 #8974] DEBUG -- : Found block device: loop6
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827576 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827584 #8974] DEBUG -- : Found block device: loop7
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827593 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827602 #8974] DEBUG -- : Found block device: ram10
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827611 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827619 #8974] DEBUG -- : Found block device: ram11
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827629 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827679 #8974] DEBUG -- : Found block device: ram12
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827688 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827696 #8974] DEBUG -- : Found block device: ram13
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827706 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827713 #8974] DEBUG -- : Found block device: ram14
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827723 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827731 #8974] DEBUG -- : Found block device: ram15
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827740 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.827771 #8974] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.892573 #8974] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep 24 01:22:35 node-1 nailgun-agent: D, [2016-09-24T01:22:35.892630 #8974] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 24 01:22:36 node-1 puppet-user[13854]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 24 01:22:36 node-1 puppet-user[13854]: Finished catalog run in 0.80 seconds
Sep 24 01:22:37 node-1 puppet-user[14548]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 24 01:22:37 node-1 puppet-user[14548]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Sep 24 01:22:41 node-1 puppet-user[14548]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 24 01:22:44 node-1 kernel: [   92.513772] init: plymouth-upstart-bridge main process ended, respawning
Sep 24 01:22:45 node-1 puppet-agent[8940]: Could not run: SIGTERM
Sep 24 01:22:45 node-1 kernel: [   92.849460] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 24 01:22:45 node-1 ec2: 
Sep 24 01:22:45 node-1 ec2: #############################################################
Sep 24 01:22:45 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 24 01:22:45 node-1 ec2: 1024 d1:13:6f:b1:92:c0:bd:df:f7:3c:8a:fe:33:1b:45:ed  root@node-1.domain.tld (DSA)
Sep 24 01:22:45 node-1 ec2: 256 05:24:a7:3a:0f:9f:2e:cf:56:dc:c8:21:d0:d8:30:2f  root@node-1.domain.tld (ECDSA)
Sep 24 01:22:45 node-1 ec2: 256 33:e4:9e:9e:8d:80:77:55:04:3c:6a:0c:45:42:7d:e9  root@node-1.domain.tld (ED25519)
Sep 24 01:22:45 node-1 ec2: 2048 09:3f:96:89:80:42:57:d4:e8:c3:e3:12:70:4c:6e:da  root@node-1.domain.tld (RSA)
Sep 24 01:22:45 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 24 01:22:45 node-1 ec2: #############################################################
Sep 24 01:22:48 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989757 #8974] DEBUG -- : Trying to find block devices
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989876 #8974] DEBUG -- : Found block device: sda
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989905 #8974] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989925 #8974] DEBUG -- : Block device seems to be physical data storage: sda
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989958 #8974] DEBUG -- : Found block device: dm-0
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989970 #8974] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989982 #8974] DEBUG -- : Found block device: dm-1
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.989992 #8974] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990002 #8974] DEBUG -- : Found block device: dm-2
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990031 #8974] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990040 #8974] DEBUG -- : Found block device: dm-3
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990050 #8974] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990059 #8974] DEBUG -- : Found block device: dm-4
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990069 #8974] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990077 #8974] DEBUG -- : Found block device: dm-5
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990087 #8974] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990096 #8974] DEBUG -- : Found block device: ram0
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990105 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990133 #8974] DEBUG -- : Found block device: ram1
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990143 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990152 #8974] DEBUG -- : Found block device: ram2
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990161 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990169 #8974] DEBUG -- : Found block device: ram3
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990178 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990187 #8974] DEBUG -- : Found block device: ram4
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990196 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990204 #8974] DEBUG -- : Found block device: ram5
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990230 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990239 #8974] DEBUG -- : Found block device: ram6
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990248 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990256 #8974] DEBUG -- : Found block device: ram7
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990264 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990272 #8974] DEBUG -- : Found block device: ram8
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990281 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990289 #8974] DEBUG -- : Found block device: ram9
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990297 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990305 #8974] DEBUG -- : Found block device: loop0
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990332 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990340 #8974] DEBUG -- : Found block device: loop1
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990349 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990357 #8974] DEBUG -- : Found block device: loop2
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990365 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990373 #8974] DEBUG -- : Found block device: loop3
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990381 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990389 #8974] DEBUG -- : Found block device: loop4
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990398 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990428 #8974] DEBUG -- : Found block device: loop5
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990438 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990446 #8974] DEBUG -- : Found block device: loop6
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990455 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990463 #8974] DEBUG -- : Found block device: loop7
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990471 #8974] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990479 #8974] DEBUG -- : Found block device: ram10
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990487 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990495 #8974] DEBUG -- : Found block device: ram11
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990503 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990540 #8974] DEBUG -- : Found block device: ram12
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990550 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990558 #8974] DEBUG -- : Found block device: ram13
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990567 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990575 #8974] DEBUG -- : Found block device: ram14
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990584 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990592 #8974] DEBUG -- : Found block device: ram15
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990600 #8974] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:47.990629 #8974] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Sep 24 01:22:48 node-1 nailgun-agent: D, [2016-09-24T01:22:48.145391 #8974] DEBUG -- : Response: status: 200 body: {"id": 1}
Sep 24 01:22:48 node-1 nailgun-agent: I, [2016-09-24T01:22:48.148212 #8974]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 24 01:23:01 node-1 CRON[16954]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 24 01:23:08 node-1 puppet-user[14548]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 24 01:23:08 node-1 puppet-user[14548]: Finished catalog run in 30.24 seconds
Sep 24 01:23:10 node-1 puppet-user[17690]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 24 01:23:10 node-1 puppet-user[17690]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Sep 24 01:23:10 node-1 puppet-user[17690]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 24 01:23:10 node-1 puppet-user[17690]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 24 01:23:10 node-1 puppet-user[17690]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 24 01:23:10 node-1 puppet-user[17690]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 24 01:23:10 node-1 puppet-user[17690]: Finished catalog run in 0.08 seconds
Sep 24 01:23:12 node-1 puppet-user[18152]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 24 01:23:13 node-1 puppet-user[18152]: Compiled catalog for node-1.domain.tld in environment production in 0.89 seconds
Sep 24 01:23:13 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 24 01:23:13 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 24 01:23:13 node-1 crontab[18597]: (root) LIST (root)
Sep 24 01:23:13 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 24 01:23:13 node-1 crontab[18598]: (root) REPLACE (root)
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 24 01:23:15 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 24 01:23:16 node-1 puppet-user[18152]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 24 01:23:16 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8392" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 24 01:23:16 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 24 01:23:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:31 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:31 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:31 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:31 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:31 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:31 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:23:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:22 node-1 ntpdate[29471]: no servers can be used, exiting
<27>Sep 24 01:24:22 node-1 ntpdate[29607]: no servers can be used, exiting
<27>Sep 24 01:24:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:57 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:57 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:57 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:57 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:57 node-1 multipathd: uevent trigger error
<27>Sep 24 01:24:57 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:25:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:07 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:07 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:07 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:07 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:07 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 24 01:26:18 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 24 01:26:24 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 24 01:26:24 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 24 01:26:30 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 24 01:26:35 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 24 01:26:35 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 24 01:26:42 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:42 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:42 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:42 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:42 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:42 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:26:55 node-1 multipathd: uevent trigger error
<129>Sep 24 01:26:57 node-1 haproxy[17707]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:26:58 node-1 haproxy[17713]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:26:59 node-1 haproxy[17713]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:26:59 node-1 haproxy[17713]: proxy mysqld has no server available!
<27>Sep 24 01:27:01 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:01 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:01 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:01 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:01 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:01 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:04 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:04 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:04 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:04 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:04 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:07 node-1 haproxy[20462]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:07 node-1 haproxy[20462]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:07 node-1 haproxy[20462]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:07 node-1 haproxy[20462]: proxy mysqld has no server available!
<129>Sep 24 01:27:08 node-1 haproxy[20466]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:08 node-1 haproxy[20466]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:08 node-1 haproxy[20466]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:08 node-1 haproxy[20466]: proxy object-storage has no server available!
<27>Sep 24 01:27:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:10 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:12 node-1 haproxy[22038]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:12 node-1 haproxy[22038]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:13 node-1 haproxy[22042]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:13 node-1 haproxy[22042]: proxy neutron has no server available!
<129>Sep 24 01:27:13 node-1 haproxy[22042]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:13 node-1 haproxy[22042]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:13 node-1 haproxy[22042]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:13 node-1 haproxy[22042]: proxy mysqld has no server available!
<129>Sep 24 01:27:13 node-1 haproxy[22042]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:14 node-1 haproxy[22042]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:14 node-1 haproxy[22042]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:14 node-1 haproxy[22042]: proxy object-storage has no server available!
<27>Sep 24 01:27:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:15 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:15 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:18 node-1 haproxy[23475]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:18 node-1 haproxy[23475]: 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>Sep 24 01:27:18 node-1 haproxy[23475]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:18 node-1 haproxy[23475]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:18 node-1 haproxy[23475]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:18 node-1 haproxy[23475]: 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>Sep 24 01:27:18 node-1 haproxy[23475]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:18 node-1 haproxy[23475]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:18 node-1 haproxy[23475]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:19 node-1 haproxy[23484]: proxy neutron has no server available!
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:19 node-1 haproxy[23484]: proxy mysqld has no server available!
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:19 node-1 haproxy[23484]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:19 node-1 haproxy[23484]: proxy object-storage has no server available!
<27>Sep 24 01:27:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:21 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:23 node-1 haproxy[24916]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:23 node-1 haproxy[24916]: 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>Sep 24 01:27:23 node-1 haproxy[24916]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:23 node-1 haproxy[24916]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:23 node-1 haproxy[24916]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:24 node-1 haproxy[24920]: 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>Sep 24 01:27:24 node-1 haproxy[24920]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:24 node-1 haproxy[24920]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:24 node-1 haproxy[24920]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:24 node-1 haproxy[24920]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:24 node-1 haproxy[24920]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:24 node-1 haproxy[24920]: proxy neutron has no server available!
<129>Sep 24 01:27:24 node-1 haproxy[24920]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:24 node-1 haproxy[24920]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:24 node-1 haproxy[24920]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:24 node-1 haproxy[24920]: proxy mysqld has no server available!
<129>Sep 24 01:27:24 node-1 haproxy[24920]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:25 node-1 haproxy[24920]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:25 node-1 haproxy[24920]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:25 node-1 haproxy[24920]: proxy object-storage has no server available!
<129>Sep 24 01:27:25 node-1 haproxy[24920]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:25 node-1 haproxy[24920]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:25 node-1 haproxy[24920]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:25 node-1 haproxy[24920]: proxy aodh has no server available!
<27>Sep 24 01:27:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:27 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:27 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:29 node-1 haproxy[26506]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:29 node-1 haproxy[26506]: 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>Sep 24 01:27:29 node-1 haproxy[26506]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:29 node-1 haproxy[26506]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:29 node-1 haproxy[26506]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:29 node-1 haproxy[26506]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:29 node-1 haproxy[26506]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:29 node-1 haproxy[26506]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:29 node-1 haproxy[26506]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:29 node-1 haproxy[26506]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:30 node-1 haproxy[26510]: proxy neutron has no server available!
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:30 node-1 haproxy[26510]: proxy mysqld has no server available!
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:30 node-1 haproxy[26510]: proxy object-storage has no server available!
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:30 node-1 haproxy[26510]: proxy aodh has no server available!
<129>Sep 24 01:27:30 node-1 haproxy[26510]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:31 node-1 haproxy[26510]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:31 node-1 haproxy[26510]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:31 node-1 haproxy[26510]: proxy ceilometer has no server available!
<27>Sep 24 01:27:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:32 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:34 node-1 haproxy[27906]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:34 node-1 haproxy[27906]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:34 node-1 haproxy[27906]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:34 node-1 haproxy[27906]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:35 node-1 haproxy[27910]: 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>Sep 24 01:27:35 node-1 haproxy[27910]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:35 node-1 haproxy[27910]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:35 node-1 haproxy[27910]: proxy neutron has no server available!
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:35 node-1 haproxy[27910]: proxy mysqld has no server available!
<129>Sep 24 01:27:35 node-1 haproxy[27910]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:36 node-1 haproxy[27910]: proxy object-storage has no server available!
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:36 node-1 haproxy[27910]: proxy aodh has no server available!
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:36 node-1 haproxy[27910]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:36 node-1 haproxy[27910]: proxy ceilometer has no server available!
<27>Sep 24 01:27:37 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:37 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:37 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:37 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:38 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:40 node-1 haproxy[29321]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:40 node-1 haproxy[29321]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:40 node-1 haproxy[29321]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:40 node-1 haproxy[29321]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:40 node-1 haproxy[29321]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:40 node-1 haproxy[29321]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:40 node-1 haproxy[29321]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:40 node-1 haproxy[29321]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:40 node-1 haproxy[29321]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:41 node-1 haproxy[29325]: proxy neutron has no server available!
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:41 node-1 haproxy[29325]: proxy mysqld has no server available!
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:41 node-1 haproxy[29325]: proxy object-storage has no server available!
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:41 node-1 haproxy[29325]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:41 node-1 haproxy[29325]: proxy aodh has no server available!
<129>Sep 24 01:27:42 node-1 haproxy[29325]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:42 node-1 haproxy[29325]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:42 node-1 haproxy[29325]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:42 node-1 haproxy[29325]: proxy ceilometer has no server available!
<27>Sep 24 01:27:43 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:43 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:43 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:43 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:43 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:46 node-1 haproxy[30767]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:46 node-1 haproxy[30767]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:46 node-1 haproxy[30767]: proxy glance-api has no server available!
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:46 node-1 haproxy[30767]: proxy glance-glare has no server available!
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:46 node-1 haproxy[30767]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:47 node-1 haproxy[30771]: proxy neutron has no server available!
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:47 node-1 haproxy[30771]: proxy glance-registry has no server available!
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:47 node-1 haproxy[30771]: proxy mysqld has no server available!
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:47 node-1 haproxy[30771]: proxy object-storage has no server available!
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:47 node-1 haproxy[30771]: proxy aodh has no server available!
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:47 node-1 haproxy[30771]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:47 node-1 haproxy[30771]: proxy ceilometer has no server available!
<27>Sep 24 01:27:49 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:49 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:49 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:49 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:49 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:51 node-1 haproxy[32230]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:52 node-1 haproxy[32234]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: 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>Sep 24 01:27:52 node-1 haproxy[32234]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:52 node-1 haproxy[32234]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:52 node-1 haproxy[32234]: proxy nova-api has no server available!
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:52 node-1 haproxy[32234]: proxy nova-metadata-api has no server available!
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:52 node-1 haproxy[32234]: proxy glance-api has no server available!
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:52 node-1 haproxy[32234]: proxy glance-glare has no server available!
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:52 node-1 haproxy[32234]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:52 node-1 haproxy[32234]: proxy neutron has no server available!
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:53 node-1 haproxy[32234]: proxy glance-registry has no server available!
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:53 node-1 haproxy[32234]: proxy mysqld has no server available!
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:53 node-1 haproxy[32234]: proxy object-storage has no server available!
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:53 node-1 haproxy[32234]: proxy aodh has no server available!
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:53 node-1 haproxy[32234]: proxy ceilometer has no server available!
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:53 node-1 haproxy[32234]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:53 node-1 haproxy[32234]: proxy nova-novncproxy has no server available!
<27>Sep 24 01:27:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:27:54 node-1 multipathd: uevent trigger error
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:57 node-1 haproxy[1195]: proxy keystone-1 has no server available!
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: 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>Sep 24 01:27:57 node-1 haproxy[1195]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:57 node-1 haproxy[1195]: proxy keystone-2 has no server available!
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:57 node-1 haproxy[1195]: proxy nova-api has no server available!
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:57 node-1 haproxy[1195]: proxy nova-metadata-api has no server available!
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:57 node-1 haproxy[1195]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy cinder-api has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy glance-api has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy glance-glare has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy neutron has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy glance-registry has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy mysqld has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy object-storage has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:58 node-1 haproxy[1199]: proxy aodh has no server available!
<129>Sep 24 01:27:58 node-1 haproxy[1199]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:59 node-1 haproxy[1199]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:59 node-1 haproxy[1199]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:59 node-1 haproxy[1199]: proxy ceilometer has no server available!
<129>Sep 24 01:27:59 node-1 haproxy[1199]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:59 node-1 haproxy[1199]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:27:59 node-1 haproxy[1199]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:27:59 node-1 haproxy[1199]: proxy nova-novncproxy has no server available!
<27>Sep 24 01:28:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:00 node-1 multipathd: uevent trigger error
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy keystone-1 has no server available!
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy keystone-2 has no server available!
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy nova-api has no server available!
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy nova-metadata-api has no server available!
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy cinder-api has no server available!
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy glance-api has no server available!
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy glance-glare has no server available!
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:03 node-1 haproxy[2624]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:03 node-1 haproxy[2624]: proxy neutron has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy glance-registry has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy mysqld has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy object-storage has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy aodh has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy ceilometer has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy heat-api has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy heat-api-cfn has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy heat-api-cloudwatch has no server available!
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 24 01:28:04 node-1 haproxy[2631]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 24 01:28:04 node-1 haproxy[2631]: proxy nova-novncproxy has no server available!
<27>Sep 24 01:28:06 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:06 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:06 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:06 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:06 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:09 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:09 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:09 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:09 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:09 node-1 multipathd: uevent trigger error
<27>Sep 24 01:28:16 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 24 01:28:41 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Sep 24 01:28:43 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 24 01:29:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 24 01:29:15 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 24 01:29:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:29:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:29:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:29:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:29:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:32 node-1 multipathd: uevent trigger error
<43>Sep 24 01:31:47 node-1 apache2_error [Sat Sep 24 01:31:42.976948 2016] [mpm_event:notice] [pid 8182:tid 139671517079424] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 24 01:31:47 node-1 apache2_error [Sat Sep 24 01:31:42.977082 2016] [core:notice] [pid 8182:tid 139671517079424] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 24 01:31:47 node-1 apache2_error [Sat Sep 24 01:31:45.946417 2016] [mpm_event:notice] [pid 8182:tid 139671517079424] AH00491: caught SIGTERM, shutting down
<43>Sep 24 01:31:47 node-1 apache2_error [Sat Sep 24 01:31:47.040174 2016] [mpm_worker:notice] [pid 8544:tid 140667049613184] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 24 01:31:47 node-1 apache2_error [Sat Sep 24 01:31:47.040244 2016] [core:notice] [pid 8544:tid 140667049613184] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 24 01:31:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:31:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 24 01:32:37 node-1 apache2_error [Sat Sep 24 01:32:36.884791 2016] [mpm_worker:notice] [pid 8544:tid 140667049613184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 24 01:32:37 node-1 apache2_error [Sat Sep 24 01:32:36.892611 2016] [mpm_worker:warn] [pid 8544:tid 140667049613184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 24 01:32:37 node-1 apache2_error [Sat Sep 24 01:32:36.893492 2016] [mpm_worker:notice] [pid 8544:tid 140667049613184] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 24 01:32:37 node-1 apache2_error [Sat Sep 24 01:32:36.893505 2016] [core:notice] [pid 8544:tid 140667049613184] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 24 01:32:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:32:45 node-1 multipathd: uevent trigger error
<43>Sep 24 01:33:47 node-1 apache2_error [Sat Sep 24 01:33:46.236453 2016] [mpm_worker:notice] [pid 8544:tid 140667049613184] AH00295: caught SIGTERM, shutting down
<43>Sep 24 01:33:47 node-1 apache2_error [Sat Sep 24 01:33:46.979732 2016] [mpm_worker:notice] [pid 29860:tid 139667937056640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 24 01:33:47 node-1 apache2_error [Sat Sep 24 01:33:46.979757 2016] [core:notice] [pid 29860:tid 139667937056640] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 24 01:34:37 node-1 apache2_error [Sat Sep 24 01:34:30.963234 2016] [mpm_worker:notice] [pid 29860:tid 139667937056640] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 24 01:34:37 node-1 apache2_error [Sat Sep 24 01:34:30.974412 2016] [mpm_worker:warn] [pid 29860:tid 139667937056640] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 24 01:34:37 node-1 apache2_error [Sat Sep 24 01:34:30.979459 2016] [mpm_worker:notice] [pid 29860:tid 139667937056640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 24 01:34:37 node-1 apache2_error [Sat Sep 24 01:34:30.979478 2016] [core:notice] [pid 29860:tid 139667937056640] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 24 01:35:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 24 01:35:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:56 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:56 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:56 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:56 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:56 node-1 multipathd: uevent trigger error
<27>Sep 24 01:35:56 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:12 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:12 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:12 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:12 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:12 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:12 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:52 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:52 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:52 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:52 node-1 multipathd: uevent trigger error
<27>Sep 24 01:36:52 node-1 multipathd: uevent trigger error
<27>Sep 24 01:37:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:37:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:37:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:37:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:37:40 node-1 multipathd: uevent trigger error
<27>Sep 24 01:38:36 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 24 01:38:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:38:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:38:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:38:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:38:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:38:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:45 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:39:51 node-1 multipathd: uevent trigger error
<27>Sep 24 01:40:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:40:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:40:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:40:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:40:13 node-1 multipathd: uevent trigger error
<27>Sep 24 01:41:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 24 01:42:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:47 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:47 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:47 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:47 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:47 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:47 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:53 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:53 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:53 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:53 node-1 multipathd: uevent trigger error
<27>Sep 24 01:42:53 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:33 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:43:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 24 01:44:46 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:46 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:46 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:46 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:46 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Interface
<27>Sep 24 01:44:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Port
<27>Sep 24 01:44:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-prv" in table Port
<27>Sep 24 01:44:54 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 24 01:44:54 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 24 01:44:54 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 24 01:44:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:44:55 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:45:39 node-1 multipathd: uevent trigger error
<27>Sep 24 01:47:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 24 01:47:58 node-1 multipathd: uevent trigger error
<27>Sep 24 01:47:58 node-1 multipathd: uevent trigger error
<27>Sep 24 01:47:58 node-1 multipathd: uevent trigger error
<27>Sep 24 01:47:58 node-1 multipathd: uevent trigger error
<27>Sep 24 01:47:58 node-1 multipathd: uevent trigger error
<27>Sep 24 01:47:58 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:11 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:11 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:48:27 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Sep 24 01:49:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:38 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:43 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:43 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:43 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:49:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:24 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:24 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:24 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:24 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:24 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:24 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:28 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:28 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:28 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:28 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:28 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:32 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 24 01:50:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:44 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:50:50 node-1 multipathd: uevent trigger error
<27>Sep 24 01:51:16 node-1 multipathd: uevent trigger error
<27>Sep 24 01:51:16 node-1 multipathd: uevent trigger error
<27>Sep 24 01:51:16 node-1 multipathd: uevent trigger error
<27>Sep 24 01:51:16 node-1 multipathd: uevent trigger error
<27>Sep 24 01:51:16 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:22 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:52:36 node-1 multipathd: uevent trigger error
<11>Sep 24 01:52:49 node-1 liberasurecode[59976]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:49 node-1 liberasurecode[59976]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:49 node-1 liberasurecode[59976]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:49 node-1 liberasurecode[59976]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:49 node-1 liberasurecode[60000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:49 node-1 liberasurecode[60000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:49 node-1 liberasurecode[60000]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:49 node-1 liberasurecode[60000]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:51 node-1 liberasurecode[60382]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:51 node-1 liberasurecode[60382]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:51 node-1 liberasurecode[60382]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:51 node-1 liberasurecode[60382]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61000]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61000]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61036]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61036]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61080]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61080]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61080]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61080]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61149]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61149]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61149]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61149]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61163]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61163]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61163]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61163]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61175]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61175]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61212]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61212]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61212]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:52:56 node-1 liberasurecode[61212]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 24 01:53:13 node-1 liberasurecode[63530]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:53:13 node-1 liberasurecode[63530]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:53:13 node-1 liberasurecode[63530]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:53:13 node-1 liberasurecode[63530]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 24 01:53:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:53:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:53:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:53:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:53:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:53:21 node-1 multipathd: uevent trigger error
<27>Sep 24 01:53:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 24 01:54:09 node-1 apache2_error [Sat Sep 24 01:54:07.323270 2016] [mpm_worker:notice] [pid 29860:tid 139667937056640] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 24 01:54:09 node-1 apache2_error [Sat Sep 24 01:54:07.708348 2016] [mpm_worker:warn] [pid 29860:tid 139667937056640] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 24 01:54:09 node-1 apache2_error [Sat Sep 24 01:54:07.712493 2016] [mpm_worker:notice] [pid 29860:tid 139667937056640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 24 01:54:09 node-1 apache2_error [Sat Sep 24 01:54:07.712513 2016] [core:notice] [pid 29860:tid 139667937056640] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 24 01:54:48 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:48 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:48 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:48 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:48 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:48 node-1 multipathd: uevent trigger error
<43>Sep 24 01:54:49 node-1 apache2_error [Sat Sep 24 01:54:44.157384 2016] [mpm_worker:notice] [pid 29860:tid 139667937056640] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 24 01:54:49 node-1 apache2_error [Sat Sep 24 01:54:44.351656 2016] [mpm_worker:warn] [pid 29860:tid 139667937056640] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 24 01:54:49 node-1 apache2_error [Sat Sep 24 01:54:44.359317 2016] [mpm_worker:notice] [pid 29860:tid 139667937056640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 24 01:54:49 node-1 apache2_error [Sat Sep 24 01:54:44.359348 2016] [core:notice] [pid 29860:tid 139667937056640] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 24 01:54:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:54:54 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:00 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:00 node-1 multipathd: uevent trigger error
<11>Sep 24 01:55:01 node-1 liberasurecode[82054]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:55:01 node-1 liberasurecode[82054]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:55:01 node-1 liberasurecode[82054]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 01:55:01 node-1 liberasurecode[82054]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 24 01:55:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:10 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:25 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:25 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:25 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:26 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:47 node-1 multipathd: uevent trigger error
<27>Sep 24 01:55:54 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 24 01:56:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:03 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:08 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:18 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:23 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:23 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:23 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:23 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:23 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:23 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:36 node-1 multipathd: uevent trigger error
<27>Sep 24 01:56:39 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<11>Sep 24 02:00:01 node-1 liberasurecode[139903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:00:01 node-1 liberasurecode[139903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:00:01 node-1 liberasurecode[139903]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:00:01 node-1 liberasurecode[139903]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 24 02:01:41 node-1 multipathd: uevent trigger error
<27>Sep 24 02:01:41 node-1 multipathd: uevent trigger error
<27>Sep 24 02:01:41 node-1 multipathd: uevent trigger error
<27>Sep 24 02:01:41 node-1 multipathd: uevent trigger error
<27>Sep 24 02:01:41 node-1 multipathd: uevent trigger error
<11>Sep 24 02:05:01 node-1 liberasurecode[188928]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:05:01 node-1 liberasurecode[188928]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:05:01 node-1 liberasurecode[188928]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:05:01 node-1 liberasurecode[188928]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 24 02:06:46 node-1 multipathd: uevent trigger error
<27>Sep 24 02:06:46 node-1 multipathd: uevent trigger error
<27>Sep 24 02:06:46 node-1 multipathd: uevent trigger error
<27>Sep 24 02:06:46 node-1 multipathd: uevent trigger error
<27>Sep 24 02:06:46 node-1 multipathd: uevent trigger error
<11>Sep 24 02:10:01 node-1 liberasurecode[242691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:10:01 node-1 liberasurecode[242691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:10:01 node-1 liberasurecode[242691]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:10:01 node-1 liberasurecode[242691]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 24 02:11:50 node-1 multipathd: uevent trigger error
<27>Sep 24 02:11:50 node-1 multipathd: uevent trigger error
<27>Sep 24 02:11:50 node-1 multipathd: uevent trigger error
<27>Sep 24 02:11:50 node-1 multipathd: uevent trigger error
<27>Sep 24 02:11:50 node-1 multipathd: uevent trigger error
<11>Sep 24 02:15:01 node-1 liberasurecode[296520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:15:01 node-1 liberasurecode[296520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:15:01 node-1 liberasurecode[296520]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:15:01 node-1 liberasurecode[296520]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 24 02:16:55 node-1 multipathd: uevent trigger error
<27>Sep 24 02:16:55 node-1 multipathd: uevent trigger error
<27>Sep 24 02:16:55 node-1 multipathd: uevent trigger error
<27>Sep 24 02:16:55 node-1 multipathd: uevent trigger error
<27>Sep 24 02:16:55 node-1 multipathd: uevent trigger error
<11>Sep 24 02:20:01 node-1 liberasurecode[352156]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:20:01 node-1 liberasurecode[352156]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:20:01 node-1 liberasurecode[352156]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:20:01 node-1 liberasurecode[352156]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 24 02:22:00 node-1 multipathd: uevent trigger error
<27>Sep 24 02:22:00 node-1 multipathd: uevent trigger error
<27>Sep 24 02:22:00 node-1 multipathd: uevent trigger error
<27>Sep 24 02:22:00 node-1 multipathd: uevent trigger error
<27>Sep 24 02:22:00 node-1 multipathd: uevent trigger error
<11>Sep 24 02:25:01 node-1 liberasurecode[410602]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:25:01 node-1 liberasurecode[410602]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:25:01 node-1 liberasurecode[410602]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 24 02:25:01 node-1 liberasurecode[410602]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
