Oct 30 06:24:48 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8394" x-info="http://www.rsyslog.com"] start
Oct 30 06:24:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 30 06:24:48 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 30 06:24:48 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 30 06:24:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 30 06:24:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 30 06:24:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 30 06:24:48 node-1 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Oct 30 06:24:48 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=c99387e1-0759-41a1-8cf4-38dcbdbf5f39 nomdmonddf nomdmonisw
Oct 30 06:24:48 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 30 06:24:48 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 30 06:24:48 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 30 06:24:48 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 30 06:24:48 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 30 06:24:48 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 30 06:24:48 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 30 06:24:48 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct 30 06:24:48 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 30 06:24:48 node-1 kernel: [    0.000000] No AGP bridge found
Oct 30 06:24:48 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 30 06:24:48 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 30 06:24:48 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 30 06:24:48 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 30 06:24:48 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 30 06:24:48 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 30 06:24:48 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 30 06:24:48 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 30 06:24:48 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 30 06:24:48 node-1 kernel: [    0.000000]   2 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000]   3 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000]   4 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000]   5 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000]   6 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000]   7 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000]   8 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000]   9 disabled
Oct 30 06:24:48 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 30 06:24:48 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 30 06:24:48 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 30 06:24:48 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 30 06:24:48 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 30 06:24:48 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 30 06:24:48 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 30 06:24:48 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 30 06:24:48 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 30 06:24:48 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 30 06:24:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 30 06:24:48 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 30 06:24:48 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 30 06:24:48 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 30 06:24:48 node-1 kernel: [    0.000000] Zone ranges:
Oct 30 06:24:48 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 30 06:24:48 node-1 kernel: [    0.000000] Early memory node ranges
Oct 30 06:24:48 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct 30 06:24:48 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 30 06:24:48 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 30 06:24:48 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 30 06:24:48 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct 30 06:24:48 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct 30 06:24:48 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 30 06:24:48 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 30 06:24:48 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 30 06:24:48 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 30 06:24:48 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 30 06:24:48 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 30 06:24:48 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 30 06:24:48 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 30 06:24:48 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 30 06:24:48 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 30 06:24:48 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 30 06:24:48 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 30 06:24:48 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 30 06:24:48 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 30 06:24:48 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 30 06:24:48 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 30 06:24:48 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 30 06:24:48 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct 30 06:24:48 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct 30 06:24:48 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 30 06:24:48 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=c99387e1-0759-41a1-8cf4-38dcbdbf5f39 nomdmonddf nomdmonisw
Oct 30 06:24:48 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 30 06:24:48 node-1 kernel: [    0.000000] Checking aperture...
Oct 30 06:24:48 node-1 kernel: [    0.000000] No AGP bridge found
Oct 30 06:24:48 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 30 06:24:48 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 30 06:24:48 node-1 kernel: [    0.000000] Memory: 32653460K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct 30 06:24:48 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 30 06:24:48 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 30 06:24:48 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 30 06:24:48 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 30 06:24:48 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 30 06:24:48 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 30 06:24:48 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 30 06:24:48 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 30 06:24:48 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 30 06:24:48 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 30 06:24:48 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 30 06:24:48 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 30 06:24:48 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 30 06:24:48 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 30 06:24:48 node-1 kernel: [    0.004000] tsc: Detected 3492.188 MHz processor
Oct 30 06:24:48 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.37 BogoMIPS (lpj=13968752)
Oct 30 06:24:48 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 30 06:24:48 node-1 kernel: [    0.000047] Security Framework initialized
Oct 30 06:24:48 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Oct 30 06:24:48 node-1 kernel: [    0.000067] Yama: becoming mindful.
Oct 30 06:24:48 node-1 kernel: [    0.001477] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.006424] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.008351] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.008379] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.008669] Initializing cgroup subsys memory
Oct 30 06:24:48 node-1 kernel: [    0.008677] Initializing cgroup subsys devices
Oct 30 06:24:48 node-1 kernel: [    0.008679] Initializing cgroup subsys freezer
Oct 30 06:24:48 node-1 kernel: [    0.008681] Initializing cgroup subsys blkio
Oct 30 06:24:48 node-1 kernel: [    0.008683] Initializing cgroup subsys perf_event
Oct 30 06:24:48 node-1 kernel: [    0.008685] Initializing cgroup subsys hugetlb
Oct 30 06:24:48 node-1 kernel: [    0.008704] CPU: Physical Processor ID: 0
Oct 30 06:24:48 node-1 kernel: [    0.008705] CPU: Processor Core ID: 0
Oct 30 06:24:48 node-1 kernel: [    0.008709] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 30 06:24:48 node-1 kernel: [    0.008709] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 30 06:24:48 node-1 kernel: [    0.009402] mce: CPU supports 22 MCE banks
Oct 30 06:24:48 node-1 kernel: [    0.009430] CPU0: Thermal monitoring enabled (TM1)
Oct 30 06:24:48 node-1 kernel: [    0.009450] process: using mwait in idle threads
Oct 30 06:24:48 node-1 kernel: [    0.009453] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 30 06:24:48 node-1 kernel: [    0.009453] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 30 06:24:48 node-1 kernel: [    0.009453] tlb_flushall_shift: 6
Oct 30 06:24:48 node-1 kernel: [    0.009541] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 30 06:24:48 node-1 kernel: [    0.010263] ACPI: Core revision 20131115
Oct 30 06:24:48 node-1 kernel: [    0.023067] ACPI: All ACPI Tables successfully acquired
Oct 30 06:24:48 node-1 kernel: [    0.023231] ftrace: allocating 28622 entries in 112 pages
Oct 30 06:24:48 node-1 kernel: [    0.031982] dmar: Host address width 46
Oct 30 06:24:48 node-1 kernel: [    0.031985] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 30 06:24:48 node-1 kernel: [    0.031991] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 30 06:24:48 node-1 kernel: [    0.031993] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 30 06:24:48 node-1 kernel: [    0.031997] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 30 06:24:48 node-1 kernel: [    0.031998] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 30 06:24:48 node-1 kernel: [    0.031999] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 30 06:24:48 node-1 kernel: [    0.032001] dmar: ATSR flags: 0x0
Oct 30 06:24:48 node-1 kernel: [    0.032002] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 30 06:24:48 node-1 kernel: [    0.032003] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 30 06:24:48 node-1 kernel: [    0.032118] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 30 06:24:48 node-1 kernel: [    0.032119] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 30 06:24:48 node-1 kernel: [    0.032120] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 30 06:24:48 node-1 kernel: [    0.032121] HPET id 0 under DRHD base 0xc7ffc000
Oct 30 06:24:48 node-1 kernel: [    0.032123] Your BIOS is broken and requested that x2apic be disabled.
Oct 30 06:24:48 node-1 kernel: [    0.032123] This will slightly decrease performance.
Oct 30 06:24:48 node-1 kernel: [    0.032123] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 30 06:24:48 node-1 kernel: [    0.032553] Enabled IRQ remapping in xapic mode
Oct 30 06:24:48 node-1 kernel: [    0.032555] x2apic not enabled, IRQ remapping is in xapic mode
Oct 30 06:24:48 node-1 kernel: [    0.032558] Switched APIC routing to physical flat.
Oct 30 06:24:48 node-1 kernel: [    0.033140] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 30 06:24:48 node-1 kernel: [    0.072793] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 30 06:24:48 node-1 kernel: [    0.072799] TSC deadline timer enabled
Oct 30 06:24:48 node-1 kernel: [    0.072806] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 30 06:24:48 node-1 kernel: [    0.072812] ... version:                3
Oct 30 06:24:48 node-1 kernel: [    0.072813] ... bit width:              48
Oct 30 06:24:48 node-1 kernel: [    0.072814] ... generic registers:      4
Oct 30 06:24:48 node-1 kernel: [    0.072815] ... value mask:             0000ffffffffffff
Oct 30 06:24:48 node-1 kernel: [    0.072816] ... max period:             0000ffffffffffff
Oct 30 06:24:48 node-1 kernel: [    0.072817] ... fixed-purpose events:   3
Oct 30 06:24:48 node-1 kernel: [    0.072818] ... event mask:             000000070000000f
Oct 30 06:24:48 node-1 kernel: [    0.074215] x86: Booting SMP configuration:
Oct 30 06:24:48 node-1 kernel: [    0.088321] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 30 06:24:48 node-1 kernel: [    0.074217] .... node  #0, CPUs:        #1  #2  #3
Oct 30 06:24:48 node-1 kernel: [    0.116233] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 30 06:24:48 node-1 kernel: [    0.270390] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 30 06:24:48 node-1 kernel: [    0.326017] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 30 06:24:48 node-1 kernel: [    0.383077] x86: Booted up 2 nodes, 16 CPUs
Oct 30 06:24:48 node-1 kernel: [    0.383080] smpboot: Total of 16 processors activated (111762.03 BogoMIPS)
Oct 30 06:24:48 node-1 kernel: [    0.407553] devtmpfs: initialized
Oct 30 06:24:48 node-1 kernel: [    0.410068] EVM: security.selinux
Oct 30 06:24:48 node-1 kernel: [    0.410070] EVM: security.SMACK64
Oct 30 06:24:48 node-1 kernel: [    0.410071] EVM: security.ima
Oct 30 06:24:48 node-1 kernel: [    0.410072] EVM: security.capability
Oct 30 06:24:48 node-1 kernel: [    0.410123] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.410775] pinctrl core: initialized pinctrl subsystem
Oct 30 06:24:48 node-1 kernel: [    0.410836] regulator-dummy: no parameters
Oct 30 06:24:48 node-1 kernel: [    0.410867] RTC time:  6:24:12, date: 10/30/16
Oct 30 06:24:48 node-1 kernel: [    0.410901] NET: Registered protocol family 16
Oct 30 06:24:48 node-1 kernel: [    0.410985] cpuidle: using governor ladder
Oct 30 06:24:48 node-1 kernel: [    0.410987] cpuidle: using governor menu
Oct 30 06:24:48 node-1 kernel: [    0.411021] ACPI: bus type PCI registered
Oct 30 06:24:48 node-1 kernel: [    0.411022] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 30 06:24:48 node-1 kernel: [    0.411081] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 30 06:24:48 node-1 kernel: [    0.411084] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 30 06:24:48 node-1 kernel: [    0.424814] PCI: Using configuration type 1 for base access
Oct 30 06:24:48 node-1 kernel: [    0.425801] bio: create slab <bio-0> at 0
Oct 30 06:24:48 node-1 kernel: [    0.426085] ACPI: Added _OSI(Module Device)
Oct 30 06:24:48 node-1 kernel: [    0.426087] ACPI: Added _OSI(Processor Device)
Oct 30 06:24:48 node-1 kernel: [    0.426088] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 30 06:24:48 node-1 kernel: [    0.426090] ACPI: Added _OSI(Processor Aggregator Device)
Oct 30 06:24:48 node-1 kernel: [    0.438744] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 30 06:24:48 node-1 kernel: [    0.449398] ACPI: Interpreter enabled
Oct 30 06:24:48 node-1 kernel: [    0.449404] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 30 06:24:48 node-1 kernel: [    0.449408] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 30 06:24:48 node-1 kernel: [    0.449411] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 30 06:24:48 node-1 kernel: [    0.449418] ACPI: (supports S0 S4 S5)
Oct 30 06:24:48 node-1 kernel: [    0.449419] ACPI: Using IOAPIC for interrupt routing
Oct 30 06:24:48 node-1 kernel: [    0.449459] HEST: Table parsing has been initialized.
Oct 30 06:24:48 node-1 kernel: [    0.449462] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 30 06:24:48 node-1 kernel: [    0.450014] ACPI: No dock devices found.
Oct 30 06:24:48 node-1 kernel: [    0.461505] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 30 06:24:48 node-1 kernel: [    0.461510] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 06:24:48 node-1 kernel: [    0.461513] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 30 06:24:48 node-1 kernel: [    0.461540] PCI host bridge to bus 0000:ff
Oct 30 06:24:48 node-1 kernel: [    0.461542] pci_bus 0000:ff: root bus resource [bus ff]
Oct 30 06:24:48 node-1 kernel: [    0.461550] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461588] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.461618] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461653] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461681] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.461711] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.461741] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461771] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461800] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461831] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461857] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461883] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461911] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461938] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461964] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.461991] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462021] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462048] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462075] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.462103] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462129] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.462155] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462182] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462214] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.462251] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462283] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462313] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462344] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462375] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462406] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462437] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462469] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462500] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462534] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462567] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462599] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462632] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462662] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462690] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462722] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462756] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462792] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462827] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462859] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462889] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462918] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462947] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.462977] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463009] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463040] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463071] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463100] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463129] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463158] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463186] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463218] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463249] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463306] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 30 06:24:48 node-1 kernel: [    0.463309] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 06:24:48 node-1 kernel: [    0.463312] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 30 06:24:48 node-1 kernel: [    0.463329] PCI host bridge to bus 0000:7f
Oct 30 06:24:48 node-1 kernel: [    0.463331] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 30 06:24:48 node-1 kernel: [    0.463336] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463363] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.463391] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463420] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463442] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.463468] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.463494] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463518] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463545] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463569] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463593] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463617] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463642] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463664] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463687] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463713] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463734] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463757] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463780] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.463804] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463826] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.463848] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463870] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463897] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 30 06:24:48 node-1 kernel: [    0.463931] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463957] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.463983] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464009] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464034] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464063] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464091] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464121] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464145] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464174] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464203] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464232] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464261] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464287] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464314] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464342] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464367] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464393] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464421] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464449] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464475] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464501] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464527] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464553] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464577] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464603] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464632] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464657] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464679] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464704] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464728] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464757] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.464783] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.466025] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 30 06:24:48 node-1 kernel: [    0.466028] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 06:24:48 node-1 kernel: [    0.467147] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 30 06:24:48 node-1 kernel: [    0.467660] PCI host bridge to bus 0000:00
Oct 30 06:24:48 node-1 kernel: [    0.467663] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 30 06:24:48 node-1 kernel: [    0.467664] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 30 06:24:48 node-1 kernel: [    0.467666] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 30 06:24:48 node-1 kernel: [    0.467667] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 30 06:24:48 node-1 kernel: [    0.467668] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 30 06:24:48 node-1 kernel: [    0.467670] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 30 06:24:48 node-1 kernel: [    0.467671] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 30 06:24:48 node-1 kernel: [    0.467677] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 30 06:24:48 node-1 kernel: [    0.467759] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.467790] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.467834] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 30 06:24:48 node-1 kernel: [    0.467853] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.467882] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.467922] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 30 06:24:48 node-1 kernel: [    0.467942] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.467972] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.468012] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 30 06:24:48 node-1 kernel: [    0.468028] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.468098] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.468175] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.468248] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 30 06:24:48 node-1 kernel: [    0.468253] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 30 06:24:48 node-1 kernel: [    0.468337] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 30 06:24:48 node-1 kernel: [    0.468485] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 30 06:24:48 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 30 06:24:48 node-1 kernel: [    0.468503] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 30 06:24:48 node-1 kernel: [    0.468580] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.468634] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 30 06:24:48 node-1 kernel: [    0.468655] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.468710] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.468754] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 30 06:24:48 node-1 kernel: [    0.468780] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.468836] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.468879] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 30 06:24:48 node-1 kernel: [    0.468903] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 30 06:24:48 node-1 kernel: [    0.468920] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 30 06:24:48 node-1 kernel: [    0.468997] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.469047] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 30 06:24:48 node-1 kernel: [    0.469071] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 30 06:24:48 node-1 kernel: [    0.469316] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 30 06:24:48 node-1 kernel: [    0.469322] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 30 06:24:48 node-1 kernel: [    0.469328] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.469334] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.469341] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 30 06:24:48 node-1 kernel: [    0.469371] pci 0000:01:00.0: supports D1 D2
Oct 30 06:24:48 node-1 kernel: [    0.479539] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 30 06:24:48 node-1 kernel: [    0.479546] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 30 06:24:48 node-1 kernel: [    0.479550] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 30 06:24:48 node-1 kernel: [    0.479810] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.479870] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 30 06:24:48 node-1 kernel: [    0.487541] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 30 06:24:48 node-1 kernel: [    0.487543] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.487545] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 06:24:48 node-1 kernel: [    0.487599] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.487675] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.487750] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.487795] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 30 06:24:48 node-1 kernel: [    0.487799] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.487801] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 06:24:48 node-1 kernel: [    0.487852] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.487975] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.488028] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 30 06:24:48 node-1 kernel: [    0.488030] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.488032] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.488081] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.488200] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.488238] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.488357] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.488393] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.488514] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.488550] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 30 06:24:48 node-1 kernel: [    0.488687] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 30 06:24:48 node-1 kernel: [    0.488728] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 30 06:24:48 node-1 kernel: [    0.488731] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.488733] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.488790] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 30 06:24:48 node-1 kernel: [    0.488853] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.488906] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.488950] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 30 06:24:48 node-1 kernel: [    0.489032] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 30 06:24:48 node-1 kernel: [    0.489137] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 30 06:24:48 node-1 kernel: [    0.489140] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.489142] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.489198] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 30 06:24:48 node-1 kernel: [    0.489251] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.489300] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.489512] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 30 06:24:48 node-1 kernel: [    0.489516] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 30 06:24:48 node-1 kernel: [    0.489579] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 30 06:24:48 node-1 kernel: [    0.489647] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.489694] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.489902] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 30 06:24:48 node-1 kernel: [    0.489905] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 30 06:24:48 node-1 kernel: [    0.489964] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 30 06:24:48 node-1 kernel: [    0.490027] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.490079] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 30 06:24:48 node-1 kernel: [    0.490301] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 30 06:24:48 node-1 kernel: [    0.490305] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 30 06:24:48 node-1 kernel: [    0.490478] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 30 06:24:48 node-1 kernel: [    0.490516] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 30 06:24:48 node-1 kernel: [    0.490590] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 30 06:24:48 node-1 kernel: [    0.490609] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 30 06:24:48 node-1 kernel: [    0.490622] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 30 06:24:48 node-1 kernel: [    0.490635] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 30 06:24:48 node-1 kernel: [    0.490685] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 30 06:24:48 node-1 kernel: [    0.495555] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 30 06:24:48 node-1 kernel: [    0.495564] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 30 06:24:48 node-1 kernel: [    0.495616] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 30 06:24:48 node-1 kernel: [    0.496344] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 30 06:24:48 node-1 kernel: [    0.496347] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 06:24:48 node-1 kernel: [    0.496472] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 30 06:24:48 node-1 kernel: [    0.496577] PCI host bridge to bus 0000:80
Oct 30 06:24:48 node-1 kernel: [    0.496579] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 30 06:24:48 node-1 kernel: [    0.496581] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 30 06:24:48 node-1 kernel: [    0.496582] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 30 06:24:48 node-1 kernel: [    0.496590] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.496653] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.496721] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 30 06:24:48 node-1 kernel: [    0.496782] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 30 06:24:48 node-1 kernel: [    0.496788] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 30 06:24:48 node-1 kernel: [    0.496859] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 30 06:24:48 node-1 kernel: [    0.497157] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 30 06:24:48 node-1 kernel: [    0.497188] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 30 06:24:48 node-1 kernel: [    0.497218] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 30 06:24:48 node-1 kernel: [    0.497247] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 30 06:24:48 node-1 kernel: [    0.497276] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 06:24:48 node-1 kernel: [    0.497306] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 06:24:48 node-1 kernel: [    0.497336] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 06:24:48 node-1 kernel: [    0.497365] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 06:24:48 node-1 kernel: [    0.497451] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 30 06:24:48 node-1 kernel: [    0.497455] ACPI: \_SB_.UNC1: notify handler is installed
Oct 30 06:24:48 node-1 kernel: [    0.497456] ACPI: \_SB_.UNC0: notify handler is installed
Oct 30 06:24:48 node-1 kernel: [    0.497471] ACPI: \_SB_.PCI0: notify handler is installed
Oct 30 06:24:48 node-1 kernel: [    0.497524] ACPI: \_SB_.PCI1: notify handler is installed
Oct 30 06:24:48 node-1 kernel: [    0.497604] Found 4 acpi root devices
Oct 30 06:24:48 node-1 kernel: [    0.497713] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 30 06:24:48 node-1 kernel: [    0.497715] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 30 06:24:48 node-1 kernel: [    0.497717] vgaarb: loaded
Oct 30 06:24:48 node-1 kernel: [    0.497718] vgaarb: bridge control possible 0000:0c:00.0
Oct 30 06:24:48 node-1 kernel: [    0.497840] SCSI subsystem initialized
Oct 30 06:24:48 node-1 kernel: [    0.497905] libata version 3.00 loaded.
Oct 30 06:24:48 node-1 kernel: [    0.497921] ACPI: bus type USB registered
Oct 30 06:24:48 node-1 kernel: [    0.497931] usbcore: registered new interface driver usbfs
Oct 30 06:24:48 node-1 kernel: [    0.497936] usbcore: registered new interface driver hub
Oct 30 06:24:48 node-1 kernel: [    0.497962] usbcore: registered new device driver usb
Oct 30 06:24:48 node-1 kernel: [    0.498134] PCI: Using ACPI for IRQ routing
Oct 30 06:24:48 node-1 kernel: [    0.501739] PCI: pci_cache_line_size set to 64 bytes
Oct 30 06:24:48 node-1 kernel: [    0.501942] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 30 06:24:48 node-1 kernel: [    0.501943] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct 30 06:24:48 node-1 kernel: [    0.501944] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 30 06:24:48 node-1 kernel: [    0.502009] NetLabel: Initializing
Oct 30 06:24:48 node-1 kernel: [    0.502011] NetLabel:  domain hash size = 128
Oct 30 06:24:48 node-1 kernel: [    0.502012] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 30 06:24:48 node-1 kernel: [    0.502022] NetLabel:  unlabeled traffic allowed by default
Oct 30 06:24:48 node-1 kernel: [    0.502077] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 30 06:24:48 node-1 kernel: [    0.502082] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 30 06:24:48 node-1 kernel: [    0.504144] Switched to clocksource hpet
Oct 30 06:24:48 node-1 kernel: [    0.508162] AppArmor: AppArmor Filesystem Enabled
Oct 30 06:24:48 node-1 kernel: [    0.508176] pnp: PnP ACPI init
Oct 30 06:24:48 node-1 kernel: [    0.508183] ACPI: bus type PNP registered
Oct 30 06:24:48 node-1 kernel: [    0.508293] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508302] pnp 00:01: [dma 4]
Oct 30 06:24:48 node-1 kernel: [    0.508313] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508340] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508360] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508379] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508411] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508465] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508467] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 30 06:24:48 node-1 kernel: [    0.508469] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508470] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508472] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508477] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508479] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 30 06:24:48 node-1 kernel: [    0.508480] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508482] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508483] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508485] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508486] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508488] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 30 06:24:48 node-1 kernel: [    0.508490] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508574] pnp 00:07: [dma 0 disabled]
Oct 30 06:24:48 node-1 kernel: [    0.508602] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508676] pnp 00:08: [dma 0 disabled]
Oct 30 06:24:48 node-1 kernel: [    0.508709] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 30 06:24:48 node-1 kernel: [    0.508759] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 30 06:24:48 node-1 kernel: [    0.509105] pnp: PnP ACPI: found 10 devices
Oct 30 06:24:48 node-1 kernel: [    0.509106] ACPI: bus type PNP unregistered
Oct 30 06:24:48 node-1 kernel: [    0.515357] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 30 06:24:48 node-1 kernel: [    0.515360] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 30 06:24:48 node-1 kernel: [    0.515363] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 30 06:24:48 node-1 kernel: [    0.515367] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 30 06:24:48 node-1 kernel: [    0.515369] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515384] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515413] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 30 06:24:48 node-1 kernel: [    0.515428] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515457] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 30 06:24:48 node-1 kernel: [    0.515475] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 30 06:24:48 node-1 kernel: [    0.515503] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 30 06:24:48 node-1 kernel: [    0.515518] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 30 06:24:48 node-1 kernel: [    0.515547] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 30 06:24:48 node-1 kernel: [    0.515548] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515563] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515605] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 30 06:24:48 node-1 kernel: [    0.515607] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515622] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515651] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 30 06:24:48 node-1 kernel: [    0.515652] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515655] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515659] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 30 06:24:48 node-1 kernel: [    0.515661] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515663] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515667] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 30 06:24:48 node-1 kernel: [    0.515672] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 30 06:24:48 node-1 kernel: [    0.515680] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 30 06:24:48 node-1 kernel: [    0.515683] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 30 06:24:48 node-1 kernel: [    0.515689] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 30 06:24:48 node-1 kernel: [    0.515690] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 30 06:24:48 node-1 kernel: [    0.515691] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 30 06:24:48 node-1 kernel: [    0.515692] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 30 06:24:48 node-1 kernel: [    0.515693] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 30 06:24:48 node-1 kernel: [    0.515694] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 30 06:24:48 node-1 kernel: [    0.515695] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 30 06:24:48 node-1 kernel: [    0.515695] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 30 06:24:48 node-1 kernel: [    0.515696] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515697] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515698] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515699] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515700] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515701] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515702] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515703] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515704] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 30 06:24:48 node-1 kernel: [    0.515705] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515706] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 30 06:24:48 node-1 kernel: [    0.515707] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 30 06:24:48 node-1 kernel: [    0.515708] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 30 06:24:48 node-1 kernel: [    0.515709] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 30 06:24:48 node-1 kernel: [    0.515711] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 30 06:24:48 node-1 kernel: [    0.515712] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 30 06:24:48 node-1 kernel: [    0.515751] NET: Registered protocol family 2
Oct 30 06:24:48 node-1 kernel: [    0.516020] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.516359] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.516503] TCP: Hash tables configured (established 262144 bind 65536)
Oct 30 06:24:48 node-1 kernel: [    0.516539] TCP: reno registered
Oct 30 06:24:48 node-1 kernel: [    0.516568] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.516663] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.516808] NET: Registered protocol family 1
Oct 30 06:24:48 node-1 kernel: [    0.556237] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 30 06:24:48 node-1 kernel: [    0.556251] PCI: CLS 64 bytes, default 64
Oct 30 06:24:48 node-1 kernel: [    0.556327] Trying to unpack rootfs image as initramfs...
Oct 30 06:24:48 node-1 kernel: [    0.775856] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct 30 06:24:48 node-1 kernel: [    0.775900] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 30 06:24:48 node-1 kernel: [    0.775902] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct 30 06:24:48 node-1 kernel: [    0.776316] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776322] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776327] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776333] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776357] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776368] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776377] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776386] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776394] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776403] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776410] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776416] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776423] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776430] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776438] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776445] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 06:24:48 node-1 kernel: [    0.776518] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 30 06:24:48 node-1 kernel: [    0.776521] Scanning for low memory corruption every 60 seconds
Oct 30 06:24:48 node-1 kernel: [    0.776891] Initialise system trusted keyring
Oct 30 06:24:48 node-1 kernel: [    0.776947] audit: initializing netlink socket (disabled)
Oct 30 06:24:48 node-1 kernel: [    0.776963] type=2000 audit(1477808651.728:1): initialized
Oct 30 06:24:48 node-1 kernel: [    0.794713] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 30 06:24:48 node-1 kernel: [    0.796248] zbud: loaded
Oct 30 06:24:48 node-1 kernel: [    0.796374] VFS: Disk quotas dquot_6.5.2
Oct 30 06:24:48 node-1 kernel: [    0.796410] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 30 06:24:48 node-1 kernel: [    0.796783] fuse init (API version 7.22)
Oct 30 06:24:48 node-1 kernel: [    0.796843] msgmni has been set to 32768
Oct 30 06:24:48 node-1 kernel: [    0.796892] Key type big_key registered
Oct 30 06:24:48 node-1 kernel: [    0.797395] Key type asymmetric registered
Oct 30 06:24:48 node-1 kernel: [    0.797396] Asymmetric key parser 'x509' registered
Oct 30 06:24:48 node-1 kernel: [    0.797419] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 30 06:24:48 node-1 kernel: [    0.797486] io scheduler noop registered
Oct 30 06:24:48 node-1 kernel: [    0.797487] io scheduler deadline registered (default)
Oct 30 06:24:48 node-1 kernel: [    0.797506] io scheduler cfq registered
Oct 30 06:24:48 node-1 kernel: [    0.798068] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    0.798213] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    0.798330] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    0.798439] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    0.798554] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    0.798651] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    0.799120] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 30 06:24:48 node-1 kernel: [    0.799146] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 30 06:24:48 node-1 kernel: [    0.799162] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 30 06:24:48 node-1 kernel: [    0.799171] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799174] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799176] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 30 06:24:48 node-1 kernel: [    0.799182] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799183] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799185] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799186] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799187] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799189] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799190] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799192] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799193] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799194] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799196] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799197] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799200] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 30 06:24:48 node-1 kernel: [    0.799205] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799207] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 30 06:24:48 node-1 kernel: [    0.799222] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799225] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 30 06:24:48 node-1 kernel: [    0.799235] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799237] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 30 06:24:48 node-1 kernel: [    0.799240] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 30 06:24:48 node-1 kernel: [    0.799276] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 30 06:24:48 node-1 kernel: [    0.799283] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 30 06:24:48 node-1 kernel: [    0.799287] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 30 06:24:48 node-1 kernel: [    0.799297] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 30 06:24:48 node-1 kernel: [    0.799337] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 30 06:24:48 node-1 kernel: [    0.799339] vesafb: scrolling: redraw
Oct 30 06:24:48 node-1 kernel: [    0.799340] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 30 06:24:48 node-1 kernel: [    0.820166] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 30 06:24:48 node-1 kernel: [    0.828679] Console: switching to colour frame buffer device 80x30
Oct 30 06:24:48 node-1 kernel: [    0.837350] fb0: VESA VGA frame buffer device
Oct 30 06:24:48 node-1 kernel: [    0.837546] intel_idle: MWAIT substates: 0x2120
Oct 30 06:24:48 node-1 kernel: [    0.837547] intel_idle: v0.4 model 0x3F
Oct 30 06:24:48 node-1 kernel: [    0.837547] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 30 06:24:48 node-1 kernel: [    0.837767] ipmi message handler version 39.2
Oct 30 06:24:48 node-1 kernel: [    0.838045] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 30 06:24:48 node-1 kernel: [    0.838483] ACPI: AC Adapter [P111] (on-line)
Oct 30 06:24:48 node-1 kernel: [    0.843726] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 30 06:24:48 node-1 kernel: [    0.854756] ACPI: Power Button [PWRB]
Oct 30 06:24:48 node-1 kernel: [    0.860524] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 30 06:24:48 node-1 kernel: [    0.872177] ACPI: Power Button [PWRF]
Oct 30 06:24:48 node-1 kernel: [    0.889640] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 30 06:24:48 node-1 kernel: [    0.901306] pstore: Registered erst as persistent store backend
Oct 30 06:24:48 node-1 kernel: [    0.907496] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 30 06:24:48 node-1 kernel: [    0.919446] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 30 06:24:48 node-1 kernel: [    0.946179] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 30 06:24:48 node-1 kernel: [    0.979438] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 30 06:24:48 node-1 kernel: [    0.993561] Linux agpgart interface v0.103
Oct 30 06:24:48 node-1 kernel: [    1.001160] brd: module loaded
Oct 30 06:24:48 node-1 kernel: [    1.008185] loop: module loaded
Oct 30 06:24:48 node-1 kernel: [    1.014902] libphy: Fixed MDIO Bus: probed
Oct 30 06:24:48 node-1 kernel: [    1.021379] tun: Universal TUN/TAP device driver, 1.6
Oct 30 06:24:48 node-1 kernel: [    1.027859] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 30 06:24:48 node-1 kernel: [    1.034372] PPP generic driver version 2.4.2
Oct 30 06:24:48 node-1 kernel: [    1.040760] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 30 06:24:48 node-1 kernel: [    1.047189] ehci-pci: EHCI PCI platform driver
Oct 30 06:24:48 node-1 kernel: [    1.053706] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 30 06:24:48 node-1 kernel: [    1.060114] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 30 06:24:48 node-1 kernel: [    1.072742] ehci-pci 0000:00:1a.0: debug port 2
Oct 30 06:24:48 node-1 kernel: [    1.082926] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 30 06:24:48 node-1 kernel: [    1.082945] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 30 06:24:48 node-1 kernel: [    1.099640] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 30 06:24:48 node-1 kernel: [    1.105706] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 30 06:24:48 node-1 kernel: [    1.111869] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 30 06:24:48 node-1 kernel: [    1.123766] usb usb1: Product: EHCI Host Controller
Oct 30 06:24:48 node-1 kernel: [    1.129788] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 30 06:24:48 node-1 kernel: [    1.135831] usb usb1: SerialNumber: 0000:00:1a.0
Oct 30 06:24:48 node-1 kernel: [    1.141780] hub 1-0:1.0: USB hub found
Oct 30 06:24:48 node-1 kernel: [    1.147561] hub 1-0:1.0: 2 ports detected
Oct 30 06:24:48 node-1 kernel: [    1.153364] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 30 06:24:48 node-1 kernel: [    1.158949] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 30 06:24:48 node-1 kernel: [    1.169899] ehci-pci 0000:00:1d.0: debug port 2
Oct 30 06:24:48 node-1 kernel: [    1.179278] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 30 06:24:48 node-1 kernel: [    1.179281] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 30 06:24:48 node-1 kernel: [    1.195559] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 30 06:24:48 node-1 kernel: [    1.200765] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 30 06:24:48 node-1 kernel: [    1.206083] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 30 06:24:48 node-1 kernel: [    1.216674] usb usb2: Product: EHCI Host Controller
Oct 30 06:24:48 node-1 kernel: [    1.222156] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 30 06:24:48 node-1 kernel: [    1.227708] usb usb2: SerialNumber: 0000:00:1d.0
Oct 30 06:24:48 node-1 kernel: [    1.233243] hub 2-0:1.0: USB hub found
Oct 30 06:24:48 node-1 kernel: [    1.238612] hub 2-0:1.0: 2 ports detected
Oct 30 06:24:48 node-1 kernel: [    1.243921] ehci-platform: EHCI generic platform driver
Oct 30 06:24:48 node-1 kernel: [    1.249182] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 30 06:24:48 node-1 kernel: [    1.254508] ohci-pci: OHCI PCI platform driver
Oct 30 06:24:48 node-1 kernel: [    1.259816] ohci-platform: OHCI generic platform driver
Oct 30 06:24:48 node-1 kernel: [    1.265032] uhci_hcd: USB Universal Host Controller Interface driver
Oct 30 06:24:48 node-1 kernel: [    1.270398] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 30 06:24:48 node-1 kernel: [    1.463339] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 30 06:24:48 node-1 kernel: [    1.775129] tsc: Refined TSC clocksource calibration: 3491.914 MHz
Oct 30 06:24:48 node-1 kernel: [    1.791452] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 30 06:24:48 node-1 kernel: [    1.797084] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 30 06:24:48 node-1 kernel: [    1.802846] hub 1-1:1.0: USB hub found
Oct 30 06:24:48 node-1 kernel: [    1.808438] hub 1-1:1.0: 6 ports detected
Oct 30 06:24:48 node-1 kernel: [    1.922969] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 30 06:24:48 node-1 kernel: [    2.309050] i8042: No controller found
Oct 30 06:24:48 node-1 kernel: [    2.314607] mousedev: PS/2 mouse device common for all mice
Oct 30 06:24:48 node-1 kernel: [    2.320354] rtc_cmos 00:02: RTC can wake from S4
Oct 30 06:24:48 node-1 kernel: [    2.323441] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 30 06:24:48 node-1 kernel: [    2.323442] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 30 06:24:48 node-1 kernel: [    2.324213] hub 2-1:1.0: USB hub found
Oct 30 06:24:48 node-1 kernel: [    2.324446] hub 2-1:1.0: 8 ports detected
Oct 30 06:24:48 node-1 kernel: [    2.348762] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 30 06:24:48 node-1 kernel: [    2.354536] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 30 06:24:48 node-1 kernel: [    2.365898] device-mapper: uevent: version 1.0.3
Oct 30 06:24:48 node-1 kernel: [    2.371642] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 30 06:24:48 node-1 kernel: [    2.383047] ledtrig-cpu: registered to indicate activity on CPUs
Oct 30 06:24:48 node-1 kernel: [    2.389047] TCP: cubic registered
Oct 30 06:24:48 node-1 kernel: [    2.394942] NET: Registered protocol family 10
Oct 30 06:24:48 node-1 kernel: [    2.400990] NET: Registered protocol family 17
Oct 30 06:24:48 node-1 kernel: [    2.406777] Key type dns_resolver registered
Oct 30 06:24:48 node-1 kernel: [    2.412885] Loading compiled-in X.509 certificates
Oct 30 06:24:48 node-1 kernel: [    2.419135] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 30 06:24:48 node-1 kernel: [    2.430750] registered taskstats version 1
Oct 30 06:24:48 node-1 kernel: [    2.438863] Key type trusted registered
Oct 30 06:24:48 node-1 kernel: [    2.446476] Key type encrypted registered
Oct 30 06:24:48 node-1 kernel: [    2.451967] AppArmor: AppArmor sha1 policy hashing enabled
Oct 30 06:24:48 node-1 kernel: [    2.457482] IMA: No TPM chip found, activating TPM-bypass!
Oct 30 06:24:48 node-1 kernel: [    2.463570] regulator-dummy: disabling
Oct 30 06:24:48 node-1 kernel: [    2.469065]   Magic number: 4:289:419
Oct 30 06:24:48 node-1 kernel: [    2.474538] thermal cooling_device15: hash matches
Oct 30 06:24:48 node-1 kernel: [    2.480269] rtc_cmos 00:02: setting system clock to 2016-10-30 06:24:14 UTC (1477808654)
Oct 30 06:24:48 node-1 kernel: [    2.492691] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 30 06:24:48 node-1 kernel: [    2.498339] EDD information not available.
Oct 30 06:24:48 node-1 kernel: [    2.503908] PM: Hibernation image not present or could not be loaded.
Oct 30 06:24:48 node-1 kernel: [    2.504766] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 30 06:24:48 node-1 kernel: [    2.516063] Write protecting the kernel read-only data: 12288k
Oct 30 06:24:48 node-1 kernel: [    2.522470] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 30 06:24:48 node-1 kernel: [    2.535356] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 30 06:24:48 node-1 kernel: [    2.568493] device-mapper: multipath: version 1.6.0 loaded
Oct 30 06:24:48 node-1 kernel: [    2.576466] systemd-udevd[216]: starting version 204
Oct 30 06:24:48 node-1 kernel: [    2.597179] md: linear personality registered for level -1
Oct 30 06:24:48 node-1 kernel: [    2.599005] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 30 06:24:48 node-1 kernel: [    2.618206] md: multipath personality registered for level -4
Oct 30 06:24:48 node-1 kernel: [    2.626367] md: raid0 personality registered for level 0
Oct 30 06:24:48 node-1 kernel: [    2.634260] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 30 06:24:48 node-1 kernel: [    2.640781] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 30 06:24:48 node-1 kernel: [    2.640981] md: raid1 personality registered for level 1
Oct 30 06:24:48 node-1 kernel: [    2.653542] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 30 06:24:48 node-1 kernel: [    2.654136] megasas: FW now in Ready state
Oct 30 06:24:48 node-1 kernel: [    2.654202] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654237] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654275] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654340] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654380] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654415] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654455] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654494] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654530] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654568] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654606] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654640] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654675] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654711] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654749] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654786] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.654984] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 30 06:24:48 node-1 kernel: [    2.686908] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct 30 06:24:48 node-1 kernel: [    2.700658] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 06:24:48 node-1 kernel: [    2.714838] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 06:24:48 node-1 kernel: [    2.722009] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.722014] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.722018] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.722024] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.722067] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 06:24:48 node-1 kernel: [    2.745017] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct 30 06:24:48 node-1 kernel: [    2.746295] raid6: sse2x1    7624 MB/s
Oct 30 06:24:48 node-1 kernel: [    2.765582] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 06:24:48 node-1 kernel: [    2.779344] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 30 06:24:48 node-1 kernel: [    2.814199] raid6: sse2x2   11605 MB/s
Oct 30 06:24:48 node-1 kernel: [    2.886142] raid6: sse2x4   10141 MB/s
Oct 30 06:24:48 node-1 kernel: [    2.958075] raid6: avx2x1   14957 MB/s
Oct 30 06:24:48 node-1 kernel: [    3.030011] raid6: avx2x2   18870 MB/s
Oct 30 06:24:48 node-1 kernel: [    3.101955] raid6: avx2x4   21394 MB/s
Oct 30 06:24:48 node-1 kernel: [    3.108129] raid6: using algorithm avx2x4 (21394 MB/s)
Oct 30 06:24:48 node-1 kernel: [    3.114243] raid6: using avx2x2 recovery algorithm
Oct 30 06:24:48 node-1 kernel: [    3.120229] megasas:IOC Init cmd success
Oct 30 06:24:48 node-1 kernel: [    3.120232] Switched to clocksource tsc
Oct 30 06:24:48 node-1 kernel: [    3.131960] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.131965] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.131969] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.131973] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.131977] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.131981] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.132039] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.143841] xor: automatically using best checksumming function:
Oct 30 06:24:48 node-1 kernel: [    3.152325] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct 30 06:24:48 node-1 kernel: [    3.164334] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 06:24:48 node-1 kernel: [    3.176671] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 06:24:48 node-1 kernel: [    3.182873] megasas: INIT adapter done
Oct 30 06:24:48 node-1 kernel: [    3.185874]    avx       : 36731.000 MB/sec
Oct 30 06:24:48 node-1 kernel: [    3.194830] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.194835] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.194838] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.194842] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.194896] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.206598] async_tx: api initialized (async)
Oct 30 06:24:48 node-1 kernel: [    3.207695] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 30 06:24:48 node-1 kernel: [    3.207698] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 30 06:24:48 node-1 kernel: [    3.207700] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 30 06:24:48 node-1 kernel: [    3.207701] usb 2-1.4: Manufacturer: Avocent
Oct 30 06:24:48 node-1 kernel: [    3.207703] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 30 06:24:48 node-1 kernel: [    3.215896] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct 30 06:24:48 node-1 kernel: [    3.215897] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 06:24:48 node-1 kernel: [    3.215898] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 06:24:48 node-1 kernel: [    3.215959] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.215997] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.216036] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.216077] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.216153] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 06:24:48 node-1 kernel: [    3.265816] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 30 06:24:48 node-1 kernel: [    3.266183] scsi0 : LSI SAS based MegaRAID driver
Oct 30 06:24:48 node-1 kernel: [    3.273120] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 30 06:24:48 node-1 kernel: [    3.283896] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 30 06:24:48 node-1 kernel: [    3.288010] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 30 06:24:48 node-1 kernel: [    3.288115] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 30 06:24:48 node-1 kernel: [    3.288332] sd 0:2:0:0: [sda] Write Protect is off
Oct 30 06:24:48 node-1 kernel: [    3.288333] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 30 06:24:48 node-1 kernel: [    3.288395] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 30 06:24:48 node-1 kernel: [    3.320429]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 30 06:24:48 node-1 kernel: [    3.321814] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 30 06:24:48 node-1 kernel: [    3.380157] hidraw: raw HID events driver (C) Jiri Kosina
Oct 30 06:24:48 node-1 kernel: [    3.389169] usbcore: registered new interface driver usbhid
Oct 30 06:24:48 node-1 kernel: [    3.395542] usbhid: USB HID core driver
Oct 30 06:24:48 node-1 kernel: [    3.401880] md: raid6 personality registered for level 6
Oct 30 06:24:48 node-1 kernel: [    3.408199] md: raid5 personality registered for level 5
Oct 30 06:24:48 node-1 kernel: [    3.414312] md: raid4 personality registered for level 4
Oct 30 06:24:48 node-1 kernel: [    3.420408] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Oct 30 06:24:48 node-1 kernel: [    3.432818] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Oct 30 06:24:48 node-1 kernel: [    3.445512] md: raid10 personality registered for level 10
Oct 30 06:24:48 node-1 kernel: [    3.445551] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Oct 30 06:24:48 node-1 kernel: [    3.445599] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Oct 30 06:24:48 node-1 kernel: [    3.445654] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Oct 30 06:24:48 node-1 kernel: [    3.445698] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Oct 30 06:24:48 node-1 kernel: [    3.553932] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Oct 30 06:24:48 node-1 kernel: [    3.575122] random: lvm urandom read with 36 bits of entropy available
Oct 30 06:24:48 node-1 kernel: [    3.682210] bio: create slab <bio-1> at 1
Oct 30 06:24:48 node-1 kernel: [    4.457498] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 06:24:48 node-1 kernel: [    4.910543] random: nonblocking pool is initialized
Oct 30 06:24:48 node-1 kernel: [    5.163791] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 30 06:24:48 node-1 kernel: [    5.196556] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 30 06:24:48 node-1 kernel: [    5.322733] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 30 06:24:48 node-1 kernel: [    5.352674] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 30 06:24:48 node-1 kernel: [    5.463892] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 06:24:48 node-1 kernel: [    5.617504] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 30 06:24:48 node-1 kernel: [    5.661919] XFS (dm-0): Mounting Filesystem
Oct 30 06:24:48 node-1 kernel: [    5.971106] XFS (dm-0): Ending clean mount
Oct 30 06:24:48 node-1 kernel: [    6.026805] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 06:24:48 node-1 kernel: [    6.050864] XFS (dm-1): Mounting Filesystem
Oct 30 06:24:48 node-1 kernel: [    6.182366] XFS (dm-1): Ending clean mount
Oct 30 06:24:48 node-1 kernel: [    8.112850] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 30 06:24:48 node-1 kernel: [    8.137799] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 30 06:24:48 node-1 kernel: [    8.375585] systemd-udevd[776]: starting version 204
Oct 30 06:24:48 node-1 kernel: [    8.637824] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 30 06:24:48 node-1 kernel: [    8.637832] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 30 06:24:48 node-1 kernel: [    8.637835] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 30 06:24:48 node-1 kernel: [    8.637838] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 30 06:24:48 node-1 kernel: [    8.637869] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 30 06:24:48 node-1 kernel: [    8.656876] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 30 06:24:48 node-1 kernel: [    8.664884] power_meter ACPI000D:00: Found ACPI power meter.
Oct 30 06:24:48 node-1 kernel: [    8.664892] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 30 06:24:48 node-1 kernel: [    8.671701] wmi: Mapper loaded
Oct 30 06:24:48 node-1 kernel: [    8.679361] IPMI System Interface driver.
Oct 30 06:24:48 node-1 kernel: [    8.679753] ipmi_si: probing via ACPI
Oct 30 06:24:48 node-1 kernel: [    8.679767] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 30 06:24:48 node-1 kernel: [    8.679768] ipmi_si: Adding ACPI-specified kcs state machine
Oct 30 06:24:48 node-1 kernel: [    8.679786] ipmi_si: probing via SMBIOS
Oct 30 06:24:48 node-1 kernel: [    8.679787] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 30 06:24:48 node-1 kernel: [    8.679788] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 30 06:24:48 node-1 kernel: [    8.679790] ipmi_si: probing via SPMI
Oct 30 06:24:48 node-1 kernel: [    8.679791] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 30 06:24:48 node-1 kernel: [    8.679791] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 30 06:24:48 node-1 kernel: [    8.679793] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 30 06:24:48 node-1 kernel: [    8.737652] systemd-udevd[818]: renamed network interface eth1 to enp7s0
Oct 30 06:24:48 node-1 kernel: [    8.761520] systemd-udevd[815]: renamed network interface eth3 to enp9s0
Oct 30 06:24:48 node-1 kernel: [    8.797513] systemd-udevd[813]: renamed network interface eth2 to enp8s0
Oct 30 06:24:48 node-1 kernel: [    8.845482] systemd-udevd[812]: renamed network interface eth0 to enp6s0
Oct 30 06:24:48 node-1 kernel: [    8.853486] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 30 06:24:48 node-1 kernel: [    8.853492] ipmi_si 00:09: IPMI kcs interface initialized
Oct 30 06:24:48 node-1 kernel: [    9.025193] type=1400 audit(1477808661.050:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1023 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.025344] type=1400 audit(1477808661.050:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1023 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.025471] type=1400 audit(1477808661.050:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1023 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.027280] type=1400 audit(1477808661.050:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.027420] type=1400 audit(1477808661.050:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1062 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.027543] type=1400 audit(1477808661.050:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1062 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.041920] type=1400 audit(1477808661.066:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1024 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.042054] type=1400 audit(1477808661.066:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1024 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.042171] type=1400 audit(1477808661.066:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1024 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.046266] type=1400 audit(1477808661.070:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1025 comm="apparmor_parser"
Oct 30 06:24:48 node-1 kernel: [    9.661912] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 30 06:24:48 node-1 kernel: [    9.675414] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 30 06:24:48 node-1 kernel: [    9.840441] enic 0000:06:00.0 enp6s0: Link UP
Oct 30 06:24:48 node-1 kernel: [    9.840889] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 30 06:24:48 node-1 kernel: [    9.840898] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 30 06:24:48 node-1 kernel: [   19.050228] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 30 06:24:49 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 30 06:24:49 node-1 kernel: [   38.051476] init: failsafe main process (8421) killed by TERM signal
Oct 30 06:24:50 node-1 dbus[8454]: [system] AppArmor D-Bus mediation is enabled
Oct 30 06:24:50 node-1 kernel: [   38.338708] audit_printk_skb: 30 callbacks suppressed
Oct 30 06:24:50 node-1 kernel: [   38.338710] type=1400 audit(1477808690.203:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8546 comm="apparmor_parser"
Oct 30 06:24:50 node-1 kernel: [   38.340414] type=1400 audit(1477808690.207:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8545 comm="apparmor_parser"
Oct 30 06:24:50 node-1 kernel: [   38.340418] type=1400 audit(1477808690.207:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8545 comm="apparmor_parser"
Oct 30 06:24:50 node-1 kernel: [   38.340420] type=1400 audit(1477808690.207:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Oct 30 06:24:50 node-1 kernel: [   38.340640] type=1400 audit(1477808690.207:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8545 comm="apparmor_parser"
Oct 30 06:24:50 node-1 kernel: [   38.340642] type=1400 audit(1477808690.207:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Oct 30 06:24:50 node-1 kernel: [   38.340756] type=1400 audit(1477808690.207:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Oct 30 06:24:50 node-1 kernel: [   38.456190] type=1400 audit(1477808690.323:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8548 comm="apparmor_parser"
Oct 30 06:24:50 node-1 anacron[8614]: Anacron 2.3 started on 2016-10-30
Oct 30 06:24:50 node-1 cron[8579]: (CRON) INFO (pidfile fd = 3)
Oct 30 06:24:50 node-1 multipathd: path checkers start up
Oct 30 06:24:50 node-1 cron[8652]: (CRON) STARTUP (fork ok)
Oct 30 06:24:50 node-1 anacron[8614]: Will run job `cron.daily' in 5 min.
Oct 30 06:24:50 node-1 anacron[8614]: Will run job `cron.weekly' in 10 min.
Oct 30 06:24:50 node-1 anacron[8614]: Will run job `cron.monthly' in 15 min.
Oct 30 06:24:50 node-1 anacron[8614]: Jobs will be executed sequentially
Oct 30 06:24:50 node-1 cron[8652]: (CRON) INFO (Running @reboot jobs)
Oct 30 06:24:50 node-1 postfix/master[8758]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 30 06:24:54 node-1 puppet-agent[8942]: Reopening log files
Oct 30 06:24:54 node-1 puppet-agent[8942]: Could not request certificate: Connection refused - connect(2)
Oct 30 06:25:01 node-1 CRON[8974]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Oct 30 06:25:01 node-1 CRON[8975]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct 30 06:25:08 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 06:25:08 node-1 nailgun-agent: D, [2016-10-30T06:25:01.670348 #8978] DEBUG -- : Sleep for 7 seconds before sending request
Oct 30 06:25:08 node-1 nailgun-agent: I, [2016-10-30T06:25:08.699690 #8978]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 30 06:25:09 node-1 puppet-user[9034]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 30 06:25:09 node-1 puppet-user[9034]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 30 06:25:09 node-1 nailgun-agent: D, [2016-10-30T06:25:09.527597 #8978] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 30 06:25:10 node-1 puppet-user[9034]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 30 06:25:10 node-1 puppet-user[9034]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 30 06:25:10 node-1 puppet-user[9034]: Finished catalog run in 1.06 seconds
Oct 30 06:25:12 node-1 multipathd: uevent trigger error
Oct 30 06:25:12 node-1 puppet-user[9603]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 30 06:25:12 node-1 puppet-user[9603]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 30 06:25:12 node-1 puppet-user[9603]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 30 06:25:12 node-1 puppet-user[9603]: Finished catalog run in 0.07 seconds
Oct 30 06:25:13 node-1 puppet-user[10068]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 30 06:25:13 node-1 puppet-user[10068]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 30 06:25:13 node-1 puppet-user[10068]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 30 06:25:13 node-1 puppet-user[10068]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 30 06:25:13 node-1 puppet-user[10068]: Finished catalog run in 0.03 seconds
Oct 30 06:25:15 node-1 puppet-user[10535]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 30 06:25:15 node-1 puppet-user[10535]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 30 06:25:15 node-1 puppet-user[10535]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 30 06:25:15 node-1 puppet-user[10535]: Finished catalog run in 0.03 seconds
Oct 30 06:25:17 node-1 puppet-user[10996]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 30 06:25:17 node-1 puppet-user[10996]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Oct 30 06:25:17 node-1 puppet-user[10996]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 30 06:25:18 node-1 puppet-user[10996]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Oct 30 06:25:18 node-1 puppet-user[10996]: Finished catalog run in 1.70 seconds
Oct 30 06:25:20 node-1 puppet-user[11663]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 30 06:25:20 node-1 puppet-user[11663]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Oct 30 06:25:20 node-1 puppet-user[11663]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 30 06:25:20 node-1 puppet-user[11663]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Oct 30 06:25:20 node-1 puppet-user[11663]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 30 06:25:20 node-1 puppet-user[11663]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 30 06:25:20 node-1 puppet-user[11663]: Finished catalog run in 0.25 seconds
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.531088 #8978] DEBUG -- : Trying to find block devices
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.531187 #8978] DEBUG -- : Found block device: sda
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.531241 #8978] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.531269 #8978] DEBUG -- : Trying to get list of physical devices
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.531464 #8978] DEBUG -- : Getting udev properties for device: sda
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.533755 #8978] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Oct 30 06:25:21 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75886", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.533784 #8978] DEBUG -- : Trying to find out if device sda is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.533835 #8978] DEBUG -- : Device sda removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.533872 #8978] DEBUG -- : Device sda seems to be appropriate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.534311 #8978] DEBUG -- : Getting udev properties for device: dm-0
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.536296 #8978] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-38zL9Iuafg78c1WyHCwy2wpRuC1cd6eRTeml7pwX66N6ZEiToQ2MUsLbgQjlJbLV /dev/disk/by-uuid/9e6f4d63-d65b-4b78-b519-89aaf7cfb011 /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-38zL9Iuafg78c1WyHCwy2wpRuC1cd6eRTeml7pwX66N6ZEiToQ2MUsLbgQjlJbLV", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9e6f4d63-d65b-4b78-b519-89aaf7cfb011", "ID_FS_UUID_ENC"=>"9e6f4d63-d65b-4b78-b519-89aaf7cfb011", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36773", "nomdmonddf"=>"1", "nomd
Oct 30 06:25:21 node-1 nailgun-agent: monisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.536326 #8978] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.536371 #8978] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.536403 #8978] DEBUG -- : Device dm-0 seems to be appropriate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.536416 #8978] DEBUG -- : Getting udev properties for device: dm-1
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.538226 #8978] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-jCq7uQMFMkXZCPF3Hunsaf23wALMA7pdIEnPuDQqYGmpVtvR6ouPYMS0oN8n1ag4 /dev/disk/by-uuid/0bf03d94-fd0a-48ae-b6e9-4e9f38e6a4b3 /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-jCq7uQMFMkXZCPF3Hunsaf23wALMA7pdIEnPuDQqYGmpVtvR6ouPYMS0oN8n1ag4", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0bf03d94-fd0a-48ae-b6e9-4e9f38e6a4b3", "ID_FS_UUID_ENC"=>"0bf03d94-fd0a-48ae-b6e9-4e9f38e6a4b3", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53
Oct 30 06:25:21 node-1 nailgun-agent: 254", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.538332 #8978] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.538368 #8978] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.538382 #8978] DEBUG -- : Device dm-1 seems to be appropriate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.538416 #8978] DEBUG -- : Getting udev properties for device: dm-2
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.540304 #8978] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-cSFzGEL1cMUVRpqpsV2bsfCW15kAwEx4qxXid1sWSUJtf2T8vGEm8chnjJ8D7Nci /dev/disk/by-uuid/f71289b5-cf73-44bb-9764-f29f96a2bb47 /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-cSFzGEL1cMUVRpqpsV2bsfCW15kAwEx4qxXid1sWSUJtf2T8vGEm8chnjJ8D7Nci", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f71289b5-cf73-44bb-9764-f29f96a2bb47", "ID_FS_UUID_ENC"=>"f71289b5-cf73-44bb-9764-f29f96a2bb47", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59077", "nomdmond
Oct 30 06:25:21 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.540346 #8978] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.540379 #8978] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.540394 #8978] DEBUG -- : Device dm-2 seems to be appropriate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.540409 #8978] DEBUG -- : Getting udev properties for device: dm-3
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.542309 #8978] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-GK8hEhZmmJ3JFKDFGpWNshE2L7W6YvQjOQEhXAfCaa43js5qcIQw91XcNQkaVvzM /dev/disk/by-uuid/179b7efb-9146-41b5-9d76-fce08add776e /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-GK8hEhZmmJ3JFKDFGpWNshE2L7W6YvQjOQEhXAfCaa43js5qcIQw91XcNQkaVvzM", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"179b7efb-9146-41b5-9d76-fce08add776e", "ID_FS_UUID_ENC"=>"179b7efb-9146-41b5-9d76-fce08add776e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64576", "nomdmonddf"=>"1", 
Oct 30 06:25:21 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.542337 #8978] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.542369 #8978] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.542426 #8978] DEBUG -- : Device dm-3 seems to be appropriate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.542441 #8978] DEBUG -- : Getting udev properties for device: dm-4
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.544311 #8978] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-BvsssHMTgnN8AnIMBWU3oGSs68ruSrSoN3zWUsmahDIcHT5SPDZiLfwMdkH4IgEN /dev/disk/by-uuid/c99387e1-0759-41a1-8cf4-38dcbdbf5f39 /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-BvsssHMTgnN8AnIMBWU3oGSs68ruSrSoN3zWUsmahDIcHT5SPDZiLfwMdkH4IgEN", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c99387e1-0759-41a1-8cf4-38dcbdbf5f39", "ID_FS_UUID_ENC"=>"c99387e1-0759-41a1-8cf4-38dcbdbf5f39", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71355", "nomdmonddf"=>"1", "nomd
Oct 30 06:25:21 node-1 nailgun-agent: monisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.544340 #8978] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.544373 #8978] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.544387 #8978] DEBUG -- : Device dm-4 seems to be appropriate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.544400 #8978] DEBUG -- : Getting udev properties for device: dm-5
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.546333 #8978] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-BvsssHMTgnN8AnIMBWU3oGSs68ruSrSo6JgTkRPAetBHM9UnZXq35id2CJYSEyDK /dev/disk/by-uuid/5ee4884f-ea05-4a78-9e93-e2c17891d398 /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-BvsssHMTgnN8AnIMBWU3oGSs68ruSrSo6JgTkRPAetBHM9UnZXq35id2CJYSEyDK", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"5ee4884f-ea05-4a78-9e93-e2c17891d398", "ID_FS_UUID_ENC"=>"5ee4884f-ea05-4a78-9e93-e2c17891d398", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71797", "nomdmonddf"=>"1", "nomdmonisw"
Oct 30 06:25:21 node-1 nailgun-agent: =>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.546362 #8978] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.546409 #8978] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.546425 #8978] DEBUG -- : Device dm-5 seems to be appropriate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.546474 #8978] DEBUG -- : Getting udev properties for device: ram0
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.548380 #8978] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48982", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.548418 #8978] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.548452 #8978] DEBUG -- : Device ram0 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.548478 #8978] DEBUG -- : Getting udev properties for device: ram1
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.550139 #8978] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49092", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.550167 #8978] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.550203 #8978] DEBUG -- : Device ram1 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.550223 #8978] DEBUG -- : Getting udev properties for device: ram2
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.552013 #8978] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49810", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.552035 #8978] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.552075 #8978] DEBUG -- : Device ram2 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.552094 #8978] DEBUG -- : Getting udev properties for device: ram3
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.553730 #8978] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49908", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.553757 #8978] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.553807 #8978] DEBUG -- : Device ram3 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.553826 #8978] DEBUG -- : Getting udev properties for device: ram4
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.555588 #8978] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50020", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.555615 #8978] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.555674 #8978] DEBUG -- : Device ram4 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.555693 #8978] DEBUG -- : Getting udev properties for device: ram5
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.557415 #8978] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50154", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.557453 #8978] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.557498 #8978] DEBUG -- : Device ram5 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.557517 #8978] DEBUG -- : Getting udev properties for device: ram6
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.559249 #8978] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50269", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.559274 #8978] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.559307 #8978] DEBUG -- : Device ram6 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.559326 #8978] DEBUG -- : Getting udev properties for device: ram7
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.560769 #8978] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50342", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.560795 #8978] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.560838 #8978] DEBUG -- : Device ram7 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.560857 #8978] DEBUG -- : Getting udev properties for device: ram8
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.562303 #8978] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50472", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.562329 #8978] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.562386 #8978] DEBUG -- : Device ram8 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.562418 #8978] DEBUG -- : Getting udev properties for device: ram9
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.563837 #8978] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50566", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.563874 #8978] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.563920 #8978] DEBUG -- : Device ram9 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.563947 #8978] DEBUG -- : Getting udev properties for device: loop0
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.565425 #8978] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47943", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.565450 #8978] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.565504 #8978] DEBUG -- : Device loop0 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.565523 #8978] DEBUG -- : Getting udev properties for device: loop1
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.566906 #8978] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48228", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.566939 #8978] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.566971 #8978] DEBUG -- : Device loop1 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.567000 #8978] DEBUG -- : Getting udev properties for device: loop2
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.568454 #8978] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48341", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.568479 #8978] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.568516 #8978] DEBUG -- : Device loop2 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.568560 #8978] DEBUG -- : Getting udev properties for device: loop3
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.570078 #8978] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48418", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.570103 #8978] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.570137 #8978] DEBUG -- : Device loop3 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.570157 #8978] DEBUG -- : Getting udev properties for device: loop4
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.571664 #8978] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48520", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.571704 #8978] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.571740 #8978] DEBUG -- : Device loop4 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.571777 #8978] DEBUG -- : Getting udev properties for device: loop5
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.573185 #8978] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48622", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.573227 #8978] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.573262 #8978] DEBUG -- : Device loop5 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.573281 #8978] DEBUG -- : Getting udev properties for device: loop6
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.574763 #8978] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48745", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.574797 #8978] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.574842 #8978] DEBUG -- : Device loop6 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.574861 #8978] DEBUG -- : Getting udev properties for device: loop7
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.576296 #8978] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48878", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.576321 #8978] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.576381 #8978] DEBUG -- : Device loop7 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.576400 #8978] DEBUG -- : Getting udev properties for device: ram10
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.577823 #8978] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49224", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.577848 #8978] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.577892 #8978] DEBUG -- : Device ram10 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.577911 #8978] DEBUG -- : Getting udev properties for device: ram11
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.579402 #8978] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49317", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.579428 #8978] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.579462 #8978] DEBUG -- : Device ram11 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.579489 #8978] DEBUG -- : Getting udev properties for device: ram12
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.580961 #8978] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49397", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.580986 #8978] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.586966 #8978] DEBUG -- : Device ram12 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.587005 #8978] DEBUG -- : Getting udev properties for device: ram13
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.589453 #8978] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49480", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.589490 #8978] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.589541 #8978] DEBUG -- : Device ram13 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.589571 #8978] DEBUG -- : Getting udev properties for device: ram14
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.591264 #8978] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49574", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.591298 #8978] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.591347 #8978] DEBUG -- : Device ram14 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.591379 #8978] DEBUG -- : Getting udev properties for device: ram15
Oct 30 06:25:21 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593009 #8978] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49724", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593042 #8978] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593100 #8978] DEBUG -- : Device ram15 removable parameter: "0"
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593163 #8978] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593188 #8978] DEBUG -- : Block device seems to be physical data storage: sda
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593239 #8978] DEBUG -- : Found block device: dm-0
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593267 #8978] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593348 #8978] DEBUG -- : Found block device: dm-1
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593370 #8978] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593387 #8978] DEBUG -- : Found block device: dm-2
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593407 #8978] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593425 #8978] DEBUG -- : Found block device: dm-3
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593445 #8978] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593464 #8978] DEBUG -- : Found block device: dm-4
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593483 #8978] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593501 #8978] DEBUG -- : Found block device: dm-5
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593520 #8978] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593603 #8978] DEBUG -- : Found block device: ram0
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593627 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593646 #8978] DEBUG -- : Found block device: ram1
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593667 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593687 #8978] DEBUG -- : Found block device: ram2
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593708 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593725 #8978] DEBUG -- : Found block device: ram3
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593744 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593763 #8978] DEBUG -- : Found block device: ram4
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593841 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593866 #8978] DEBUG -- : Found block device: ram5
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593886 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593906 #8978] DEBUG -- : Found block device: ram6
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593926 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593946 #8978] DEBUG -- : Found block device: ram7
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593966 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.593985 #8978] DEBUG -- : Found block device: ram8
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594005 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594024 #8978] DEBUG -- : Found block device: ram9
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594100 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594120 #8978] DEBUG -- : Found block device: loop0
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594141 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594159 #8978] DEBUG -- : Found block device: loop1
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594177 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594196 #8978] DEBUG -- : Found block device: loop2
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594218 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594238 #8978] DEBUG -- : Found block device: loop3
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594261 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594344 #8978] DEBUG -- : Found block device: loop4
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594369 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594391 #8978] DEBUG -- : Found block device: loop5
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594421 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594441 #8978] DEBUG -- : Found block device: loop6
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594461 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594482 #8978] DEBUG -- : Found block device: loop7
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594503 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594521 #8978] DEBUG -- : Found block device: ram10
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594541 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594629 #8978] DEBUG -- : Found block device: ram11
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594652 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594673 #8978] DEBUG -- : Found block device: ram12
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594693 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594710 #8978] DEBUG -- : Found block device: ram13
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594729 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594747 #8978] DEBUG -- : Found block device: ram14
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594767 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594786 #8978] DEBUG -- : Found block device: ram15
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594851 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.594904 #8978] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.713066 #8978] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 30 06:25:21 node-1 nailgun-agent: D, [2016-10-30T06:25:21.713139 #8978] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 30 06:25:22 node-1 puppet-user[12150]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 30 06:25:22 node-1 puppet-user[12150]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct 30 06:25:22 node-1 puppet-user[12150]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 30 06:25:22 node-1 kernel: [   70.665004] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 30 06:25:22 node-1 kernel: [   70.665055] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Oct 30 06:25:22 node-1 puppet-user[12150]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Oct 30 06:25:22 node-1 puppet-user[12150]: Finished catalog run in 0.05 seconds
Oct 30 06:25:24 node-1 puppet-user[12786]: (Scope(Class[main])) MODULAR: sync_time
Oct 30 06:25:24 node-1 puppet-user[12786]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 30 06:25:24 node-1 ntpdate[13206]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 30 06:25:30 node-1 ntpdate[13206]: adjust time server 10.20.0.2 offset 0.092041 sec
Oct 30 06:25:30 node-1 puppet-user[12786]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 30 06:25:30 node-1 puppet-user[12786]: Finished catalog run in 6.16 seconds
Oct 30 06:25:33 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581753 #8978] DEBUG -- : Trying to find block devices
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581834 #8978] DEBUG -- : Found block device: sda
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581859 #8978] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581876 #8978] DEBUG -- : Block device seems to be physical data storage: sda
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581896 #8978] DEBUG -- : Found block device: dm-0
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581908 #8978] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581938 #8978] DEBUG -- : Found block device: dm-1
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581948 #8978] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581958 #8978] DEBUG -- : Found block device: dm-2
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581967 #8978] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581975 #8978] DEBUG -- : Found block device: dm-3
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581984 #8978] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.581992 #8978] DEBUG -- : Found block device: dm-4
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582001 #8978] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582025 #8978] DEBUG -- : Found block device: dm-5
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582034 #8978] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582042 #8978] DEBUG -- : Found block device: ram0
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582062 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582070 #8978] DEBUG -- : Found block device: ram1
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582079 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582087 #8978] DEBUG -- : Found block device: ram2
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582122 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582131 #8978] DEBUG -- : Found block device: ram3
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582140 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582148 #8978] DEBUG -- : Found block device: ram4
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582157 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582165 #8978] DEBUG -- : Found block device: ram5
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582174 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582181 #8978] DEBUG -- : Found block device: ram6
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582190 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582198 #8978] DEBUG -- : Found block device: ram7
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582232 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582240 #8978] DEBUG -- : Found block device: ram8
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582249 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582257 #8978] DEBUG -- : Found block device: ram9
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582266 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582274 #8978] DEBUG -- : Found block device: loop0
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582283 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582291 #8978] DEBUG -- : Found block device: loop1
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582300 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582308 #8978] DEBUG -- : Found block device: loop2
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582317 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582352 #8978] DEBUG -- : Found block device: loop3
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582362 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582369 #8978] DEBUG -- : Found block device: loop4
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582379 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582387 #8978] DEBUG -- : Found block device: loop5
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582402 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582411 #8978] DEBUG -- : Found block device: loop6
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582420 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582428 #8978] DEBUG -- : Found block device: loop7
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582455 #8978] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582463 #8978] DEBUG -- : Found block device: ram10
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582472 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582480 #8978] DEBUG -- : Found block device: ram11
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582489 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582496 #8978] DEBUG -- : Found block device: ram12
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582504 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582511 #8978] DEBUG -- : Found block device: ram13
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582520 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582527 #8978] DEBUG -- : Found block device: ram14
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582558 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582566 #8978] DEBUG -- : Found block device: ram15
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582574 #8978] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.582600 #8978] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct 30 06:25:33 node-1 nailgun-agent: D, [2016-10-30T06:25:33.746792 #8978] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 30 06:25:33 node-1 nailgun-agent: I, [2016-10-30T06:25:33.746950 #8978]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 30 06:25:36 node-1 puppet-user[13699]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 30 06:25:36 node-1 puppet-user[13699]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 30 06:25:36 node-1 puppet-user[13699]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 30 06:25:36 node-1 puppet-user[13699]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Oct 30 06:25:36 node-1 puppet-user[13699]: Finished catalog run in 0.06 seconds
Oct 30 06:25:37 node-1 puppet-user[14161]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 30 06:25:38 node-1 puppet-user[14161]: Compiled catalog for node-1.domain.tld in environment production in 0.39 seconds
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Oct 30 06:25:38 node-1 puppet-user[14161]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 30 06:25:39 node-1 puppet-user[14161]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 30 06:25:39 node-1 puppet-user[14161]: Finished catalog run in 0.73 seconds
Oct 30 06:25:40 node-1 puppet-user[14669]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 30 06:25:40 node-1 puppet-user[14669]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct 30 06:25:43 node-1 kernel: [   91.120612] init: plymouth-upstart-bridge main process ended, respawning
Oct 30 06:25:43 node-1 puppet-agent[8942]: Could not run: SIGTERM
Oct 30 06:25:43 node-1 kernel: [   91.403438] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 30 06:25:43 node-1 ec2: 
Oct 30 06:25:43 node-1 ec2: #############################################################
Oct 30 06:25:43 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 30 06:25:43 node-1 ec2: 1024 c1:32:77:b4:84:d4:7d:3a:45:fd:3c:66:83:4d:3f:bf  root@node-1.domain.tld (DSA)
Oct 30 06:25:43 node-1 ec2: 256 da:37:74:d7:5f:2b:1c:61:d0:6d:43:7f:1e:e1:62:3c  root@node-1.domain.tld (ECDSA)
Oct 30 06:25:43 node-1 ec2: 256 00:37:17:7a:a0:5a:bd:79:fc:ae:40:2e:ce:9f:a6:4a  root@node-1.domain.tld (ED25519)
Oct 30 06:25:43 node-1 ec2: 2048 01:43:8e:3b:5a:f3:dc:90:9e:6d:69:c0:a9:ef:fc:60  root@node-1.domain.tld (RSA)
Oct 30 06:25:43 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 30 06:25:43 node-1 ec2: #############################################################
Oct 30 06:25:43 node-1 puppet-user[14669]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 30 06:26:01 node-1 CRON[16499]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct 30 06:26:04 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 06:26:04 node-1 nailgun-agent: I, [2016-10-30T06:26:04.918652 #16503]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 30 06:26:10 node-1 puppet-user[14669]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 30 06:26:10 node-1 puppet-user[14669]: Finished catalog run in 30.05 seconds
Oct 30 06:26:12 node-1 puppet-user[17409]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 30 06:26:12 node-1 puppet-user[17409]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Oct 30 06:26:13 node-1 puppet-user[17409]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 30 06:26:13 node-1 puppet-user[17409]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 30 06:26:13 node-1 puppet-user[17409]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 30 06:26:13 node-1 puppet-user[17409]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 30 06:26:13 node-1 puppet-user[17409]: Finished catalog run in 0.09 seconds
Oct 30 06:26:14 node-1 puppet-user[17880]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 30 06:26:15 node-1 puppet-user[17880]: Compiled catalog for node-1.domain.tld in environment production in 0.83 seconds
Oct 30 06:26:15 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 30 06:26:15 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 30 06:26:16 node-1 crontab[18325]: (root) LIST (root)
Oct 30 06:26:16 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 30 06:26:16 node-1 crontab[18326]: (root) REPLACE (root)
Oct 30 06:26:17 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 30 06:26:17 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 06:26:17 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 30 06:26:17 node-1 nailgun-agent: I, [2016-10-30T06:26:17.960666 #16503]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 30 06:26:17 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 30 06:26:17 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 30 06:26:18 node-1 puppet-user[17880]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 30 06:26:18 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8394" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 06:26:18 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 30 06:26:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:26:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:25 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:25 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:25 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:25 node-1 multipathd: uevent trigger error
<27>Oct 30 06:27:25 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:05 node-1 ntpdate[1617]: no servers can be used, exiting
<27>Oct 30 06:28:05 node-1 ntpdate[1822]: no servers can be used, exiting
<27>Oct 30 06:28:37 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:37 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:37 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:37 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:37 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:28:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:29:59 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 06:29:59 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 06:30:05 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 06:30:05 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 06:30:11 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 06:30:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 06:30:16 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 06:30:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:51 node-1 multipathd: uevent trigger error
<129>Oct 30 06:30:53 node-1 haproxy[23855]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:30:54 node-1 haproxy[23859]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:30:55 node-1 haproxy[23859]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:30:55 node-1 haproxy[23859]: proxy mysqld has no server available!
<27>Oct 30 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:00 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:00 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:00 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:00 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:00 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:00 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:03 node-1 haproxy[26396]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:03 node-1 haproxy[26396]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:03 node-1 haproxy[26396]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:03 node-1 haproxy[26396]: proxy mysqld has no server available!
<129>Oct 30 06:31:04 node-1 haproxy[26402]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:04 node-1 haproxy[26402]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:04 node-1 haproxy[26402]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:04 node-1 haproxy[26402]: proxy object-storage has no server available!
<27>Oct 30 06:31:06 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:06 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:06 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:06 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:06 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:08 node-1 haproxy[27772]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:08 node-1 haproxy[27772]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:08 node-1 haproxy[27772]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:08 node-1 haproxy[27772]: proxy neutron has no server available!
<129>Oct 30 06:31:09 node-1 haproxy[27776]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:09 node-1 haproxy[27776]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:09 node-1 haproxy[27776]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:09 node-1 haproxy[27776]: proxy mysqld has no server available!
<129>Oct 30 06:31:09 node-1 haproxy[27776]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:09 node-1 haproxy[27776]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:10 node-1 haproxy[27776]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:10 node-1 haproxy[27776]: proxy object-storage has no server available!
<27>Oct 30 06:31:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:11 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:13 node-1 haproxy[29207]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:13 node-1 haproxy[29207]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:14 node-1 haproxy[29211]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:14 node-1 haproxy[29211]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:14 node-1 haproxy[29211]: proxy neutron has no server available!
<129>Oct 30 06:31:14 node-1 haproxy[29211]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:15 node-1 haproxy[29211]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:15 node-1 haproxy[29211]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:15 node-1 haproxy[29211]: proxy mysqld has no server available!
<129>Oct 30 06:31:15 node-1 haproxy[29211]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:15 node-1 haproxy[29211]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:15 node-1 haproxy[29211]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:15 node-1 haproxy[29211]: proxy object-storage has no server available!
<27>Oct 30 06:31:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:16 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:19 node-1 haproxy[30544]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:19 node-1 haproxy[30544]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:19 node-1 haproxy[30544]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:19 node-1 haproxy[30544]: proxy neutron has no server available!
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:20 node-1 haproxy[30548]: proxy mysqld has no server available!
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:20 node-1 haproxy[30548]: proxy object-storage has no server available!
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:20 node-1 haproxy[30548]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:20 node-1 haproxy[30548]: proxy aodh has no server available!
<27>Oct 30 06:31:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:22 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:24 node-1 haproxy[31898]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:24 node-1 haproxy[31898]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:24 node-1 haproxy[31898]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:24 node-1 haproxy[31898]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:24 node-1 haproxy[31898]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:24 node-1 haproxy[31898]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:25 node-1 haproxy[31904]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:25 node-1 haproxy[31904]: proxy neutron has no server available!
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:25 node-1 haproxy[31904]: proxy mysqld has no server available!
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:25 node-1 haproxy[31904]: proxy object-storage has no server available!
<129>Oct 30 06:31:25 node-1 haproxy[31904]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:26 node-1 haproxy[31904]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:26 node-1 haproxy[31904]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:26 node-1 haproxy[31904]: proxy aodh has no server available!
<129>Oct 30 06:31:26 node-1 haproxy[31904]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:26 node-1 haproxy[31904]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:26 node-1 haproxy[31904]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:26 node-1 haproxy[31904]: proxy ceilometer has no server available!
<27>Oct 30 06:31:27 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:28 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:30 node-1 haproxy[952]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:30 node-1 haproxy[952]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:30 node-1 haproxy[952]: proxy neutron has no server available!
<129>Oct 30 06:31:30 node-1 haproxy[952]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:31 node-1 haproxy[956]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:31 node-1 haproxy[956]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:31 node-1 haproxy[956]: proxy mysqld has no server available!
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:31 node-1 haproxy[956]: proxy object-storage has no server available!
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:31 node-1 haproxy[956]: proxy aodh has no server available!
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:31 node-1 haproxy[956]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:32 node-1 haproxy[956]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:32 node-1 haproxy[956]: proxy ceilometer has no server available!
<27>Oct 30 06:31:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:33 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:33 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:35 node-1 haproxy[2295]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:35 node-1 haproxy[2295]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:35 node-1 haproxy[2295]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:36 node-1 haproxy[2299]: proxy neutron has no server available!
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:36 node-1 haproxy[2299]: proxy mysqld has no server available!
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:36 node-1 haproxy[2299]: proxy object-storage has no server available!
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:36 node-1 haproxy[2299]: proxy aodh has no server available!
<129>Oct 30 06:31:36 node-1 haproxy[2299]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:37 node-1 haproxy[2299]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:37 node-1 haproxy[2299]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:37 node-1 haproxy[2299]: proxy ceilometer has no server available!
<27>Oct 30 06:31:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:38 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:40 node-1 haproxy[3872]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:40 node-1 haproxy[3872]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:41 node-1 haproxy[3876]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:41 node-1 haproxy[3876]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:41 node-1 haproxy[3876]: proxy glance-api has no server available!
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:41 node-1 haproxy[3876]: proxy glance-glare has no server available!
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:41 node-1 haproxy[3876]: proxy neutron has no server available!
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:41 node-1 haproxy[3876]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:42 node-1 haproxy[3876]: proxy glance-registry has no server available!
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:42 node-1 haproxy[3876]: proxy mysqld has no server available!
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:42 node-1 haproxy[3876]: proxy object-storage has no server available!
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:42 node-1 haproxy[3876]: proxy aodh has no server available!
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:42 node-1 haproxy[3876]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:42 node-1 haproxy[3876]: proxy ceilometer has no server available!
<27>Oct 30 06:31:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:44 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:46 node-1 haproxy[5280]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:47 node-1 haproxy[5284]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:47 node-1 haproxy[5284]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:47 node-1 haproxy[5284]: proxy nova-api has no server available!
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:47 node-1 haproxy[5284]: proxy nova-metadata-api has no server available!
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:47 node-1 haproxy[5284]: proxy glance-api has no server available!
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:47 node-1 haproxy[5284]: proxy glance-glare has no server available!
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:47 node-1 haproxy[5284]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:47 node-1 haproxy[5284]: proxy neutron has no server available!
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:48 node-1 haproxy[5284]: proxy glance-registry has no server available!
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:48 node-1 haproxy[5284]: proxy mysqld has no server available!
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:48 node-1 haproxy[5284]: proxy object-storage has no server available!
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:48 node-1 haproxy[5284]: proxy aodh has no server available!
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:48 node-1 haproxy[5284]: proxy ceilometer has no server available!
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:48 node-1 haproxy[5284]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:48 node-1 haproxy[5284]: proxy nova-novncproxy has no server available!
<27>Oct 30 06:31:49 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:49 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:49 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:49 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:50 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:50 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:52 node-1 haproxy[6626]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:52 node-1 haproxy[6626]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:52 node-1 haproxy[6626]: proxy nova-api has no server available!
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:52 node-1 haproxy[6626]: proxy nova-metadata-api has no server available!
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:52 node-1 haproxy[6626]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:52 node-1 haproxy[6626]: proxy cinder-api has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:53 node-1 haproxy[6633]: proxy glance-api has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:53 node-1 haproxy[6633]: proxy glance-glare has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:53 node-1 haproxy[6633]: proxy neutron has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:53 node-1 haproxy[6633]: proxy glance-registry has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:53 node-1 haproxy[6633]: proxy mysqld has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:53 node-1 haproxy[6633]: proxy object-storage has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:53 node-1 haproxy[6633]: proxy aodh has no server available!
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:53 node-1 haproxy[6633]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:54 node-1 haproxy[6633]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:54 node-1 haproxy[6633]: proxy ceilometer has no server available!
<129>Oct 30 06:31:54 node-1 haproxy[6633]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:54 node-1 haproxy[6633]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:54 node-1 haproxy[6633]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:54 node-1 haproxy[6633]: proxy nova-novncproxy has no server available!
<27>Oct 30 06:31:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:31:55 node-1 multipathd: uevent trigger error
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:58 node-1 haproxy[8012]: proxy keystone-1 has no server available!
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:58 node-1 haproxy[8012]: proxy keystone-2 has no server available!
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:58 node-1 haproxy[8012]: proxy nova-api has no server available!
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:58 node-1 haproxy[8012]: proxy nova-metadata-api has no server available!
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:58 node-1 haproxy[8012]: proxy cinder-api has no server available!
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:58 node-1 haproxy[8012]: proxy glance-api has no server available!
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:58 node-1 haproxy[8012]: proxy glance-glare has no server available!
<129>Oct 30 06:31:58 node-1 haproxy[8012]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy neutron has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy glance-registry has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy mysqld has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy object-storage has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy aodh has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy ceilometer has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy heat-api has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy heat-api-cfn has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:31:59 node-1 haproxy[8021]: proxy heat-api-cloudwatch has no server available!
<129>Oct 30 06:31:59 node-1 haproxy[8021]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:32:00 node-1 haproxy[8021]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 06:32:00 node-1 haproxy[8021]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 06:32:00 node-1 haproxy[8021]: proxy nova-novncproxy has no server available!
<27>Oct 30 06:32:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:32:11 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 30 06:32:36 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Oct 30 06:32:38 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 30 06:33:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:33:03 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 06:33:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:33:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:33:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:33:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:33:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:47 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:47 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:47 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:47 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:47 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:53 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:53 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:53 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:53 node-1 multipathd: uevent trigger error
<27>Oct 30 06:35:53 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 30 06:36:09 node-1 apache2_error [Sun Oct 30 06:36:04.142334 2016] [mpm_event:notice] [pid 16898:tid 140140014430080] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 30 06:36:09 node-1 apache2_error [Sun Oct 30 06:36:04.142446 2016] [core:notice] [pid 16898:tid 140140014430080] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 30 06:36:09 node-1 apache2_error [Sun Oct 30 06:36:07.185550 2016] [mpm_event:notice] [pid 16898:tid 140140014430080] AH00491: caught SIGTERM, shutting down
<43>Oct 30 06:36:09 node-1 apache2_error [Sun Oct 30 06:36:08.275566 2016] [mpm_worker:notice] [pid 17961:tid 140533711165312] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 30 06:36:09 node-1 apache2_error [Sun Oct 30 06:36:08.275602 2016] [core:notice] [pid 17961:tid 140533711165312] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 06:36:12 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:12 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:12 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:12 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:12 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:12 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:21 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:21 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:21 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:21 node-1 multipathd: uevent trigger error
<27>Oct 30 06:36:21 node-1 multipathd: uevent trigger error
<43>Oct 30 06:37:29 node-1 apache2_error [Sun Oct 30 06:37:23.122832 2016] [mpm_worker:notice] [pid 17961:tid 140533711165312] AH00295: caught SIGTERM, shutting down
<43>Oct 30 06:37:29 node-1 apache2_error [Sun Oct 30 06:37:23.877245 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 06:37:29 node-1 apache2_error [Sun Oct 30 06:37:23.877292 2016] [core:notice] [pid 30856:tid 140540626007936] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 30 06:38:10 node-1 apache2_error [Sun Oct 30 06:38:07.800637 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 06:38:10 node-1 apache2_error [Sun Oct 30 06:38:07.993211 2016] [mpm_worker:warn] [pid 30856:tid 140540626007936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 06:38:10 node-1 apache2_error [Sun Oct 30 06:38:07.996062 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 06:38:10 node-1 apache2_error [Sun Oct 30 06:38:07.996076 2016] [core:notice] [pid 30856:tid 140540626007936] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 06:38:52 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:52 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:52 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:52 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:52 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:38:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:39:14 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:14 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:14 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:14 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:14 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:31 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:31 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:31 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:31 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:31 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:31 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:36 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:36 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:36 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:36 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:36 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:36 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:39:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:40:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:40:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:40:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:40:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:40:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:40:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:40:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:41:45 node-1 multipathd: uevent trigger error
<27>Oct 30 06:41:45 node-1 multipathd: uevent trigger error
<27>Oct 30 06:41:45 node-1 multipathd: uevent trigger error
<27>Oct 30 06:41:45 node-1 multipathd: uevent trigger error
<27>Oct 30 06:41:45 node-1 multipathd: uevent trigger error
<27>Oct 30 06:42:06 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:42:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:42:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:42:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:42:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:42:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:03 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:03 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:03 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:03 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:03 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:03 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:43:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:45:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:29 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:48 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:45:54 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:34 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:34 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:34 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:34 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:34 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:46:40 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:46 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:46 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:46 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:46 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:46 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:46 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:46 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:53 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Oct 30 06:47:53 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Oct 30 06:47:53 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Oct 30 06:47:54 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Oct 30 06:47:54 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Oct 30 06:47:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:47:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:48:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:48:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:50:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:50:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:50:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:50:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:50:57 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:09 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:09 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:09 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:51:18 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:18 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:18 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:18 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:18 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:18 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:18 node-1 multipathd: uevent trigger error
<27>Oct 30 06:51:19 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct 30 06:52:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:52:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:04 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:20 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:53:55 node-1 multipathd: uevent trigger error
<27>Oct 30 06:54:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:54:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:54:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:54:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:54:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:54:59 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:15 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:15 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:15 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:15 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:15 node-1 multipathd: uevent trigger error
<11>Oct 30 06:55:27 node-1 liberasurecode[78308]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:27 node-1 liberasurecode[78308]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:27 node-1 liberasurecode[78308]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:27 node-1 liberasurecode[78308]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:27 node-1 liberasurecode[78444]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:27 node-1 liberasurecode[78444]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:27 node-1 liberasurecode[78444]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:27 node-1 liberasurecode[78444]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:29 node-1 liberasurecode[79524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:29 node-1 liberasurecode[79524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:29 node-1 liberasurecode[79524]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:29 node-1 liberasurecode[79524]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80764]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80764]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80764]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80764]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80800]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:33 node-1 liberasurecode[80800]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80844]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80844]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80906]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80906]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80906]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80906]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80920]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80920]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80920]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80920]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80935]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80935]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80935]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80935]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80949]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80949]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80949]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:34 node-1 liberasurecode[80949]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:42 node-1 liberasurecode[81593]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:42 node-1 liberasurecode[81593]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:42 node-1 liberasurecode[81593]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 06:55:42 node-1 liberasurecode[81593]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 30 06:55:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:51 node-1 multipathd: uevent trigger error
<27>Oct 30 06:55:51 node-1 multipathd: uevent trigger error
<43>Oct 30 06:56:41 node-1 apache2_error [Sun Oct 30 06:56:37.673513 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 06:56:41 node-1 apache2_error [Sun Oct 30 06:56:38.057086 2016] [mpm_worker:warn] [pid 30856:tid 140540626007936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 06:56:41 node-1 apache2_error [Sun Oct 30 06:56:38.059807 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 06:56:41 node-1 apache2_error [Sun Oct 30 06:56:38.059818 2016] [core:notice] [pid 30856:tid 140540626007936] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 06:57:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 06:57:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:19 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:19 node-1 multipathd: uevent trigger error
<43>Oct 30 06:57:21 node-1 apache2_error [Sun Oct 30 06:57:14.932693 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 06:57:21 node-1 apache2_error [Sun Oct 30 06:57:15.129869 2016] [mpm_worker:warn] [pid 30856:tid 140540626007936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 06:57:21 node-1 apache2_error [Sun Oct 30 06:57:15.136608 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 06:57:21 node-1 apache2_error [Sun Oct 30 06:57:15.136630 2016] [core:notice] [pid 30856:tid 140540626007936] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 06:57:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:26 node-1 multipathd: uevent trigger error
<27>Oct 30 06:57:26 node-1 multipathd: uevent trigger error
<43>Oct 30 06:58:01 node-1 apache2_error [Sun Oct 30 06:58:00.843975 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 06:58:01 node-1 apache2_error [Sun Oct 30 06:58:01.041546 2016] [mpm_worker:warn] [pid 30856:tid 140540626007936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 06:58:01 node-1 apache2_error [Sun Oct 30 06:58:01.047022 2016] [mpm_worker:notice] [pid 30856:tid 140540626007936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 06:58:01 node-1 apache2_error [Sun Oct 30 06:58:01.047048 2016] [core:notice] [pid 30856:tid 140540626007936] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 06:58:05 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:05 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:05 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:05 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:05 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:11 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:16 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:22 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:58:39 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:01 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:08 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:14 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 30 06:59:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:23 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:24 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:28 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:38 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:44 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:56 node-1 multipathd: uevent trigger error
<27>Oct 30 06:59:57 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:01 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:01 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:01 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:01 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:01 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:01 node-1 multipathd: uevent trigger error
<11>Oct 30 07:00:02 node-1 liberasurecode[139533]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 07:00:02 node-1 liberasurecode[139533]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 07:00:02 node-1 liberasurecode[139533]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 07:00:02 node-1 liberasurecode[139533]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 30 07:00:15 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:15 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:15 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:15 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:15 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:20 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:20 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:20 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:20 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:25 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:25 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:25 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:25 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:25 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:30 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:30 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:30 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:30 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:30 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:30 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:39 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:39 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:39 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:39 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:39 node-1 multipathd: uevent trigger error
<27>Oct 30 07:00:39 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:26 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:26 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:26 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:26 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:26 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:34 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:02:46 node-1 multipathd: uevent trigger error
<129>Oct 30 07:02:55 node-1 haproxy[162530]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 07:02:55 node-1 haproxy[162530]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 07:03:35 node-1 haproxy[162530]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 07:03:35 node-1 haproxy[162530]: proxy neutron has no server available!
<27>Oct 30 07:03:40 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:40 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:40 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:40 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:40 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:46 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:50 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:50 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:50 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:50 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:50 node-1 multipathd: uevent trigger error
<27>Oct 30 07:03:50 node-1 multipathd: uevent trigger error
<27>Oct 30 07:04:02 node-1 multipathd: uevent trigger error
<27>Oct 30 07:04:02 node-1 multipathd: uevent trigger error
<27>Oct 30 07:04:02 node-1 multipathd: uevent trigger error
<27>Oct 30 07:04:02 node-1 multipathd: uevent trigger error
<27>Oct 30 07:04:02 node-1 multipathd: uevent trigger error
<11>Oct 30 07:05:01 node-1 liberasurecode[191372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 07:05:01 node-1 liberasurecode[191372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 07:05:01 node-1 liberasurecode[191372]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 07:05:01 node-1 liberasurecode[191372]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
